TechSpot

BSOD - Addition help req

By martine737
Oct 28, 2008
Topic Status:
Not open for further replies.
  1. Hello,

    I'm receiving the Blue Screen Of Death during every boot-up (but not during a Safe Mode boot). The screen details..

    "BAD_POOL_HEADED" *** STOP: 0x00000019 (0x00000022,0x94ACE000,0x00000001,0x00000000)"

    .. the numbers/hex post 0x00000022 change after each reboot.


    After booting into Safe Mode, the OS pop-up details the following message..

    ========================================
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.0.6001.2.1.0.256.1
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 19
    BCP1: 00000022
    BCP2: 952CB000
    BCP3: 00000001
    BCP4: 00000000
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    G:\Windows\Minidump\Mini102808-06.dmp
    G:\Users\Vista\AppData\Local\Temp\WER-32671-0.sysdata.xml
    G:\Users\Vista\AppData\Local\Temp\WERD9B6.tmp.version.txt
    ========================================

    Reading past posts in this forum and on aumha.org, it appears I may have a driver issue?. I have zipped the last five minidumps and would be very grateful is someone could assist - Thank you,

    Regards..
     
  2. almcneil

    almcneil TS Guru Posts: 1,554

    Yes, this sounds like a problem with your video card or device driver for it. In Safe Mode, go into Deviec Manager and disable the video card. Then restart to Normal Mode and see if you make it (no BSOD)

    Repost with results and we'll take it from there.

    Best,
    -- Andy
     
  3. martine737

    martine737 TS Rookie Topic Starter


    Thank you for your rapid - I'm very impressed!

    Unfortunately, disabling the video card (display adapters - attached) resulted in OS boot-up recycling over and over, and the following OS pop-up being detailed during Safe Mode..

    =========================================
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.0.6001.2.1.0.256.1
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 19
    BCP1: 00000022
    BCP2: 94AC4000
    BCP3: 00000001
    BCP4: 00000000
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    G:\Windows\Minidump\Mini102808-08.dmp
    G:\Users\Vista\AppData\Local\Temp\WER-28765-0.sysdata.xml
    G:\Users\Vista\AppData\Local\Temp\WERD030.tmp.version.txt
    =========================================

    I have attached new minidump outputs for consideration - Thank you again..
     
  4. CCT

    CCT TS Evangelist Posts: 3,556

    One incidence of this I read about says to turn OFF Indexing Service in Administrative Services (in Safe Mode).

    Then try to boot normally.
     
  5. martine737

    martine737 TS Rookie Topic Starter

    Thank you CCT, apologies for my ignorance, you do mean the "Windows Search" service and not the "NMIndexing Serivce"?. I disabled the Windows Search Service, and still having the same issue....
     
  6. CCT

    CCT TS Evangelist Posts: 3,556

    No, I meant the Indexing Service.

    Start, Control Panel, Admin Tools, Services, Indexing Service
     
  7. peterdiva

    peterdiva TechSpot Ambassador Posts: 1,202

    Uninstall AVG AV in safe mode, and then see if you can boot in normal mode. All the crashes are the same.

    BugCheck 19, {22, 8d6ba000, 1, 0}
    Probably caused by : avgldx86.sys ( avgldx86+4b8 )
    8ffc5000 8ffdb480 avgldx86 avgldx86.sys Tue Jul 15 03:46:33 2008 (487B9F09)
     
  8. martine737

    martine737 TS Rookie Topic Starter


    CCT, Thank you for your reply, routing via Start > Control Panel > Admin Tools > Services, I don't have a service called "Indexing Service" within either the Extended or Standard View per se, please see attachment. As previously mentioned I can only see "NMIndexing Serivce" and "Windows Search Service". On a side note, I can see "Indexing Options" within Systems and Maintenance via the Control Panel - but nothing obvious to turn off.



    Peterdiva, Thank you for your reply and input, un-installing the AVG Antivirus from Safe Mode and booting normally brought the OS back up safely. Also, re-enabling my display adapter (from a previous suggestion in this thread) and rebooting also resulted in a successful boot.....



    Unfortunately my problems seem to continue. The OS still seems to be unstable - It just keeps rebooting without warning during normal use.

    ====================================
    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.0.6001.2.1.0.256.1
    Locale ID: 2057

    Additional information about the problem:
    BCCode: 19
    BCP1: 00000022
    BCP2: 94AC4000
    BCP3: 00000001
    BCP4: 00000000
    OS Version: 6_0_6001
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    G:\Windows\Minidump\Mini102808-08.dmp
    G:\Users\Vista\AppData\Local\Temp\WER-28765-0.sysdata.xml
    G:\Users\Vista\AppData\Local\Temp\WERD030.tmp.version.txt
    ====================================

    Again I have attached a minidump of the error in the hope you may be able to assist.... Thank you again..

    If the minidumps are something I can diagnose and rectify myself easily, perhaps you could point me in the right direction to save your own time?
     
  9. CCT

    CCT TS Evangelist Posts: 3,556

  10. almcneil

    almcneil TS Guru Posts: 1,554

    I presume you're still able to boot to Safe Mode, not Normal Mode.

    What this typically means is that it's one of your devices. The key difference between Normal and Safe Modes is that optional hardware devices are disabled in Safe Mode (video, audio, printing, ... ) You're using the minimum hardware setup. We've eliminated the video card by disabling it permanently in Safe Mode and then trying to reboot in Normal Mode. You need to repeat this for the other devices such as audio, network, ...

    There is another difference between Safe and Normal Modes and that is not all MS services are started. This could also be a problem there.

    But usually, it's hardware that's the culprit in this situation. Let's eliminate that possibility first.

    Best,
    -- Andy
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.