locked
Windows 8 BSOD Error: 'Bad pool Error' & 'Not less or equal' RRS feed

  • General discussion

  • I have Windows 8 on my PC, and just recently I started getting multiple BSODs and crashes. Earlier, my PC would simply restart at frequent intervals (once or twice in a couple of hours), but it showed no BSOD. At times when I start my PC, the monitor shows no signal available and stays dark, after which I've to try restarting my PC multiple times till the monitor finally comes alive.

    So, can someone please help me with my PC issues? The BSODs are really troublesome. I've attached three of the dump files the crash generated. Let me know if some extra info is needed.

    http://sdrv.ms/187jxnN

    http://sdrv.ms/187jAjj

    http://sdrv.ms/187jE2y


    Thursday, May 23, 2013 7:55 AM

All replies

  • These crashes were caused by memory corruption (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem.  


    *Dont forget to upload any further DMP files (especially those when verifier is running)

    *If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!   If you dont know what this means you probably arent

    1-Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. http://www.memtest.org 
    *Boot from the CD, and leave it running for at least 5 or 6 passes.
    *Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
    *Test the sticks individually, and if you find a good one, test it in all slots.

    Any errors are indicative of a memory problem.
    If a known good stick fails in a motherboard slot it is probably the slot.


    2-Driver verifier

    Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

    *But sometimes it'll crash and won't tell you the driver.
    *Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
    *I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
    *Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

    Here is the procedure:

    - Go to Start and type in "verifier" (without the quotes) and press Enter
    - Select "Create custom settings (for code developers)" and click "Next"
    - Select "Select individual settings from a full list" and click "Next"
    - Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
    - Select "Select driver names from a list" and click "Next"
    *Then select all drivers NOT provided by Microsoft and click "Next"
    - Select "Finish" on the next page.
    *Reboot the system and wait for it to crash to the Blue Screen.
    *Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
    *If you can't get into Windows because it crashes too soon, try it in Safe Mode.
    *If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

    *Further Reading
    http://support.microsoft.com/kb/244617

    Unable to load image Unknown_Module_63b40bc5, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Unknown_Module_63b40bc5
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_63b40bc5
    Unknown module 'Unknown_Module_63b40bc5' found on stack, using vad to reload module.
    !vad_reload -1 0x63b40bc5
    Unable to get LeftChild of nt!_MMVAD_SHORT at 859cd748
    Probably caused by : memory_corruption ( nt!MiIdentifyPfn+12a )


    Wanikiya & Dyami--Team Zigzag

    Thursday, May 23, 2013 8:02 AM
  • Thank you for your reply.

    I'm not overclocking anything. And I've a problem...my CD drive is dead, so can I download the iso and then copy it onto my pen drive (after making sure to make it bootable).

    And you mentioned sticks; I didn't really get what that means.

    The driver verification seems extremely risky and cumbersome...is there any alternative?

    Thursday, May 23, 2013 8:15 AM
  • SW

    If you can boot from USB (most can) Your pen/flash will work

    By "sticks" I was refering to your RAM.  If you are talking about Memtest you would first run the computer for 6-8 passes with all ram in.  If it passes with ZERO errors (it probably will) then move on to driver verifier.


    Wanikiya & Dyami--Team Zigzag

    Thursday, May 23, 2013 6:05 PM
  • Oh ok, thank you, then I'll do the memtest ASAP.

    And I got another dump file, this time with a new error.

    http://sdrv.ms/18mCErx

    Friday, May 24, 2013 6:14 AM
  • Please try to update your grahpic card driver manually or remove it and let Windows 8 reload the driver again.

    Niki Han
    TechNet Community Support

    Friday, May 24, 2013 8:59 AM
  • SW

    The DMP was inconclusive.


    Wanikiya & Dyami--Team Zigzag

    Friday, May 24, 2013 3:30 PM
  • Try to update the BIOS to F6d, you use F5.

    "A programmer is just a tool which converts caffeine into code"

    Friday, May 24, 2013 8:09 PM
    Answerer