Recurring BSOD, BAD_POOL_HEADER, CRITICAL_STRUCTURE_CORRUPTION, IRQL_N

whitebloodcell · 06 Jun 2010

Windows 7 x64
No overclocking
8GB Ram
All temps normal.

I suddenly seem to be getting the BSOD every couple of hours recently. Nothing has changed as far as I can remember, I had installed newer ATI drivers recently but have since reverted to the previous ones (10.4) but am still having problems.

Read out from "WhoCrashed Home Edition 2.1" below. As you can see the crashes seem to be caused by various errors.

I will run memtest as soon as I can, I have an exam tomorrow though so am trying to keep my computer useable and not waste time (memtest will take a couple of hours right? - haven't used it before).

On Sun 06/06/2010 14:22:45 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002D15410)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\060610-61635-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 05/06/2010 16:22:56 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002CCB410)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\060510-19125-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 05/06/2010 13:47:17 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D89D531849, 0x0, 0x2D12EC06A4D0E0E6, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\060510-24632-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 05/06/2010 08:50:16 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D89C66E934, 0x0, 0xA4F5E9508D6E6F81, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\060510-32807-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Thu 03/06/2010 19:17:35 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x22, 0x1000000000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\060310-37845-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

usasma · 06 Jun 2010

5 memory dumps from the last 4 days (3 to 6 Jun 2010)
3 different STOP errors with 3 different causes:
- 2 STOP 0xA - error info here: BSOD Index
- 1 STOP 0x19 - error info here: BSOD Index
- 2 STOP 0x109 - error info here: BSOD Index

I would suggest running Driver Verifier to see if we can force Windows to give up the name of a faulting driver.
Please follow these instructions to run 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 "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 (an estimate on my part).

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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Code:

Delete these registry keys (verified in Win7 and Vista only):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Also, please remove or update these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall OR remove:

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: http://www.carrona.org/drvrdown.html

Here's the older drivers. Please pay particular attention to any dated 2008 or earlier:

Code:

ASACPI.sys   Sun Mar 27 22:30:36 2005 - Asus ATK0110 ACPI Utility (a known BSOD maker).  Also a part of the Asus PCProbe and AISuite   Utilities, update IMMEDIATELY - http://www.carrona.org/dvrref.html#ASACPI.sys
ctac32k.sys  Wed Jul 02 04:38:22 2008 - Creative Audio Driver - http://www.carrona.org/dvrref.html#ctac32k.sys
SaiH8000.sys Fri Apr 04 07:26:34 2008 - Saitek Hid driver - http://www.carrona.org/dvrref.html#SaiH8000.sys
wdcsam.sys   Wed Apr 16 04:39:08 2008 - Western Digital External Drive RAID Manager - http://www.carrona.org/dvrref.html#wdcsam.sys

Summary of the BSOD's:
[CODE]

Code:

[font=lucida console]
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sun Jun  6 10:05:08.306 2010 (GMT-4)
System Uptime: 0 days 20:44:57.367
BugCheck A, {28, 2, 0, fffff80002d15410}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  explorer.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 12:19:58.555 2010 (GMT-4)
System Uptime: 0 days 2:33:13.601
BugCheck A, {28, 2, 0, fffff80002ccb410}
Probably caused by : memory_corruption ( nt!MiFindNodeOrParent+0 )
BUGCHECK_STR:  0xA
PROCESS_NAME:  SearchFilterHo
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 09:44:22.498 2010 (GMT-4)
System Uptime: 0 days 4:55:00.934
BugCheck 109, {a3a039d89d531849, 0, 2d12ec06a4d0e0e6, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Sat Jun  5 04:46:57.866 2010 (GMT-4)
System Uptime: 1 days 13:30:00.610
BugCheck 109, {a3a039d89c66e934, 0, a4f5e9508d6e6f81, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  0x109
PROCESS_NAME:  System
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Thu Jun  3 15:13:49.338 2010 (GMT-4)
System Uptime: 2 days 3:45:22.829
BugCheck 19, {22, 1000000000000, 0, 0}
Probably caused by : Npfs.SYS ( Npfs!NpFsdWrite+76 )
BUGCHECK_STR:  0x19_22
PROCESS_NAME:  chrome.exe

whitebloodcell · 06 Jun 2010

Do you want me to uninstall/update the drivers you mentioned before or after the driver verifier bit?

Update: I assumed you do so am updating the asus driver now, how do I do it without using device manager though?

I am using the driver linked two in the second post of this thread.

zigzag3143 · 06 Jun 2010

whitebloodcell said:

Windows 7 x64
No overclocking
8GB Ram
All temps normal.

I suddenly seem to be getting the BSOD every couple of hours recently. Nothing has changed as far as I can remember, I had installed newer ATI drivers recently but have since reverted to the previous ones (10.4) but am still having problems.

Read out from "WhoCrashed Home Edition 2.1" below. As you can see the crashes seem to be caused by various errors.

I will run memtest as soon as I can, I have an exam tomorrow though so am trying to keep my computer useable and not waste time (memtest will take a couple of hours right? - haven't used it before).

On Sun 06/06/2010 14:22:45 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002D15410)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\060610-61635-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 05/06/2010 16:22:56 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xA (0x28, 0x2, 0x0, 0xFFFFF80002CCB410)
Error: IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\060510-19125-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 05/06/2010 13:47:17 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D89D531849, 0x0, 0x2D12EC06A4D0E0E6, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\060510-24632-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Sat 05/06/2010 08:50:16 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x109 (0xA3A039D89C66E934, 0x0, 0xA4F5E9508D6E6F81, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
Dump file: C:\Windows\Minidump\060510-32807-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

On Thu 03/06/2010 19:17:35 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x22, 0x1000000000000, 0x0, 0x0)
Error: BAD_POOL_HEADER
Dump file: C:\Windows\Minidump\060310-37845-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.

These all had different probable causes. with that many I have to think there is a hardware problem. Use these instructions to see what it means and what to try. https://www.sevenforums.com/crash-loc...-what-try.html

Let us know if you need help with this.

Ken

usasma · 06 Jun 2010

The Driver Verifier test is more important than the driver updates - but updating the drivers may fix other issues, so it may be less complicated if you do them first.

The ASACPI.sys file should be updated immediately as we know it causes BSOD's in Win7 when using the 2005 or 2004 versions.

To do this, follow these instructions:
- go to this page: ASUSTeK Computer Inc.-Support-
- enter the specifics for your motherboard or system
- enter the OS type when asked
- scroll down to the Utilities section on the next page
- download the ACPI ATK0110 ACPI utility
- extract it (double click on it) and remember where it extracts to.
- navigate to the "MB WIN 7 ATK" folder and double click on it
- double click on the folder named "64"
- double click on the file named "AsAcpiIns.exe"

That will install it, then go to C:\Windows\System32\drivers to check and see if it's been updated.

whitebloodcell · 06 Jun 2010

I've updated all the drivers I could from the list usasma gave me, there doesn't appear to be a suitable Saitek one on the manufacturer site for my keyboard. These BSOD only started after I was forced to reinstall windows on an (old) replacement HDD. Originally I had two set up in RAID1, both failed in quick succession and are away for RMA atm. In the meantime I needed a computer so installed Windows on an old drive I had, that's the only hardware that has changed so I guess it could be that that is causing problems.

usasma · 06 Jun 2010

If there are drivers that you couldn't update - then please uninstall the software/drivers for the devices and remove them from the system while we're troubleshooting.

Free hardware tests:

H/W Diagnostics:
Please start by running these bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)

whitebloodcell · 07 Jun 2010

Still kept happening despite updating drivers, I ran Seatools test "Long DST" on the HDD and it failed so will image the drive and replace it tonight when I get home. Hopefully that will sort things.

whitebloodcell · 09 Jun 2010

Since replacing the drive things seem to be working as you would expect. First attempt typically I made a major cockup and reimaged onto my External USB drive (My imaging program did not see the drive I wanted, so in my haste I copied to the drive with the same size, ie. My USB drive), wiping out all the stuff I had just copied to it for safe keeping. Rather upsetting, running R-Studio on it now to see what I can salvage...sigh.