Random BSOD BAD_POOL_HEADER IRQL_NOT_LESS_OR_EQUAL and others


  1. Posts : 3
    Windows 7 Professional x64
       #1

    Random BSOD BAD_POOL_HEADER IRQL_NOT_LESS_OR_EQUAL and others


    Hi,
    I'm having random BSOD and i update my drivers, bios etc.
    I run memtest for about 8 hours and it's fine.
    I'll post the minidump txt that i get with bluescreenview.

    Thanks

    Code:
    ==================================================
    Dump File         : 040312-17222-01.dmp
    Crash Time        : 03/04/2012 23:38:15
    Bug Check String  : BAD_POOL_HEADER
    Bug Check Code    : 0x00000019
    Parameter 1       : 00000000`00000020
    Parameter 2       : fffffa80`0cec43c0
    Parameter 3       : fffffa80`0cec4410
    Parameter 4       : 00000000`0405000b
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+66500
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7600.21094 (win7_ldr.111118-2051)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+66500
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\040312-17222-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 7600
    Dump File Size    : 276.184
    ==================================================
    
    ==================================================
    Dump File         : 040312-19952-01.dmp
    Crash Time        : 03/04/2012 19:52:23
    Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
    Bug Check Code    : 0x0000000a
    Parameter 1       : 00000000`08000000
    Parameter 2       : 00000000`00000002
    Parameter 3       : 00000000`00000000
    Parameter 4       : fffff800`030804e2
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+66500
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7600.21094 (win7_ldr.111118-2051)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+66500
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\040312-19952-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 7600
    Dump File Size    : 276.184
    ==================================================
    
    ==================================================
    Dump File         : 040312-15475-01.dmp
    Crash Time        : 03/04/2012 17:28:57
    Bug Check String  : BAD_POOL_HEADER
    Bug Check Code    : 0x00000019
    Parameter 1       : 00000000`00000020
    Parameter 2       : fffffa80`0d9d8d10
    Parameter 3       : fffffa80`0d9d8db0
    Parameter 4       : 00000000`040a0011
    Caused By Driver  : atikmdag.sys
    Caused By Address : atikmdag.sys+3d8370
    File Description  : 
    Product Name      : 
    Company           : 
    File Version      : 
    Processor         : x64
    Crash Address     : ntoskrnl.exe+66500
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\040312-15475-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 7600
    Dump File Size    : 276.184
    ==================================================
    
    ==================================================
    Dump File         : 040312-20451-01.dmp
    Crash Time        : 03/04/2012 02:44:28
    Bug Check String  : SYSTEM_SERVICE_EXCEPTION
    Bug Check Code    : 0x0000003b
    Parameter 1       : 00000000`c0000005
    Parameter 2       : 00000000`00000000
    Parameter 3       : fffff880`0b232e30
    Parameter 4       : 00000000`00000000
    Caused By Driver  : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+66500
    File Description  : NT Kernel & System
    Product Name      : Microsoft® Windows® Operating System
    Company           : Microsoft Corporation
    File Version      : 6.1.7600.21094 (win7_ldr.111118-2051)
    Processor         : x64
    Crash Address     : ntoskrnl.exe+66500
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\040312-20451-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 7600
    Dump File Size    : 276.184
    ==================================================
    
    ==================================================
    Dump File         : 040212-19983-01.dmp
    Crash Time        : 02/04/2012 20:35:16
    Bug Check String  : KMODE_EXCEPTION_NOT_HANDLED
    Bug Check Code    : 0x0000001e
    Parameter 1       : 00000000`00000000
    Parameter 2       : 00000000`00000000
    Parameter 3       : 00000000`00000000
    Parameter 4       : 00000000`00000000
    Caused By Driver  : Rt64win7.sys
    Caused By Address : Rt64win7.sys+1ba60
    File Description  : 
    Product Name      : 
    Company           : 
    File Version      : 
    Processor         : x64
    Crash Address     : ntoskrnl.exe+664d0
    Stack Address 1   : 
    Stack Address 2   : 
    Stack Address 3   : 
    Computer Name     : 
    Full Path         : C:\Windows\Minidump\040212-19983-01.dmp
    Processors Count  : 8
    Major Version     : 15
    Minor Version     : 7600
    Dump File Size    : 276.184
    ==================================================
      My Computer


  2. JMH
    Posts : 7,952
    Win 7 Ultimate 64-bit. SP1.
       #2



    We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

    If you are overclocking STOP

    We could also use some system information, which you can get easily by running msinfo32. To do that go to start>run>type msinfo32>enter

    When it is finished running go to file>save>name it and upload to us here.


    You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

    To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

    The procedure:
    * Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
    * Zip up the copy.
    * Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
    *If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

    To ensure minidumps are enabled:
    * Go to Start, in the Search Box type: sysdm.cpl, press Enter.
    * Under the Advanced tab, click on the Startup and Recovery Settings... button.
    * Ensure that Automatically restart is unchecked.
    * Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
    * Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.

    * OK your way out.
    * Reboot if changes have been made.
      My Computer


  3. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #3

    Ok, thank you for your help.
    The info from msinfo32 and the minidumps are attached.
      My Computer

  4.   My Computer


  5. Posts : 28,845
    Win 8 Release candidate 8400
       #5


    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.


    * If you are overclocking anything reset to default before running these tests.
    In other words STOP!!!

    * If you have raid update its Driver.




    Memtest.
    *Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

    *Boot from the CD, and leave it running for at least 5-7 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.

    RAM - Test with Memtest86+



    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.

    So, I'd suggest that you first backup your stuff 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).

    Then, here's 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 "Special Pool", "Force Pending I/O Requests" and "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.

    Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

    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.
      My Computer


  6. Posts : 3
    Windows 7 Professional x64
    Thread Starter
       #6

    I have updated to SP1.
    When i ran memtest86+ the pc froze with 1min37s, when it try to run all 8 processors together. I changed to sequencial and went until the pass 8, but the pc shutdown and the ligths in my voltage regulator lit both hi and low.
    Ah, the memtest found about 60 errors principally in the pass 5 i think.

    I'm with driver verifier on about 5 hours and no BSOD until now.
      My Computer


  7. Posts : 28,845
    Win 8 Release candidate 8400
       #7

    Dantalian said:
    I have updated to SP1.
    When i ran memtest86+ the pc froze with 1min37s, when it try to run all 8 processors together. I changed to sequencial and went until the pass 8, but the pc shutdown and the ligths in my voltage regulator lit both hi and low.
    Ah, the memtest found about 60 errors principally in the pass 5 i think.

    I'm with driver verifier on about 5 hours and no BSOD until now.
    If memtest finds errors it is a good indication. You might want to test individually to find which stick is bad
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 03:31.
Find Us