BSODs: BAD_POOL_CALLER; Bad_Pool_Header; SYSTEM_SERVICE_EXCEPTION

I've been having BSODs about every other day for a couple of weeks. Bluescreen View usually cites ntoskrnl.exe as the driver cause. This most recent BSOD has Bluescreen View citing afd.sys as the driver cause with ntoskrnl.exe+7cc40 as the driver address. This is the same address mentioned in the previous BSODs.

Attached is the requested zipped Windows_NT6_BSOD_jcgriff2 folder and perfmon.html

Also attached are 2 pics of the info screen from bluescreen view for multiple dump files, giving an overview of each (only the latest dump is represented in the Windows_NT6_BSOD_jcgriff2 folder.

System specs:
-Win7 pro x64
-OS is original installation
-full retail
-system is ~3 years old
-OS installation age ~3 years (no re-installation/etc. since I built the system, OS was installed clean to new HD, no upgrade from previous OS)

Computer boots up fine, runs for hours just fine. There is no common activity at the time of crash (sometimes in World of Tanks, sometimes just using firefox to browse, sometimes when unattended and no program running other than the background programs). I do hear a buzzing sound as the crash occurs but unsure if that's a cause or effect.

What I've tried:
-swapped out keyboard
-drivermax says all drivers are up-to-date except nvidia display (didn't install the 3D drivers) and they're 296.10 -- pretty recent -- and were a clean install (uninstalled the old ones, safemode reboot and deleted all traces then used driver sweeper, etc.). Sound card drivers updated too (ASUS Xonar Essence STX).
-ran repair from installation CD, passed
-ran win7 chkdsk on boot hd twice, clean
-ran memtest86+4.2 overnight for 8 hours, no errors
-replaced ntoskrn.exe using the expand~ntoskrnl.ex_ off a WinXP Pro installation disk
-been systematically uninstalling programs

What I have yet to try:
-can of compressed air to clean out the case (tho I did a cleaning a month or so ago)
-reseat sound and video cards
-reformat and reinstall
-replace boot hd (tho it's passed dskchk twice)

I think I covered all the basics, apologies if I missed something and I'll rectify any omissions pronto.

Thanks for any help with this!

I view this as a learning experience, and can usually solve these things myself. First time I've been stumped (so far anyhoo!).

I am a big fan of Nir Sofer's work, BUT blueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

We prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

If you look at parameter 1 in all the BSV crashes it is a C00000005 (which is a memory exception).

Before we begin to investigate that there is one thing you need to do which may solve the problem in itself.

Asacpi.sys. Yours is from 2005

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

If after updating the asacpi.sys you are still crashing with the same parameter please run the following tests



These crashes were caused by memory corruption/exception (Cx05) 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 a Raid update its Driver.



Memtest. I know you have run it already. I just dont know how many passes and if you did the sticks individually.

*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 Verifer

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 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).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

First -- thank you for your speedy and detailed reply!

I have downloaded, installed, and verified the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" as directed and ASACPI.sys is now 5/14/2009 date and not the previous 2005 date (I checked the old date before installing).I will see if this fixes the BSODs. If not I'll follow your next steps (memtest again and driver verifier).

No overclocking, no raid (but 4 HDs total, but not in RAID)

You mention my running memtest -- I ran 8 full passes (~8 hours total, no errors) but didn't do sticks individually. I used the default test settings (I'm new at this, I think the 'bit fade' test was optional and so not done).

As the BSODs occur only every day or 2 it may 2-3 days before I reply again. If all is well I will mark this 'solved' to close the thread (and to thank you again!). If BSODs continue I will post that (and include any new info) and do the further tests you suggest and report their results.

Again -- thanks!

Nick Danger said:

First -- thank you for your speedy and detailed reply!

I have downloaded, installed, and verified the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" as directed and ASACPI.sys is now 5/14/2009 date and not the previous 2005 date (I checked the old date before installing).I will see if this fixes the BSODs. If not I'll follow your next steps (memtest again and driver verifier).

No overclocking, no raid (but 4 HDs total, but not in RAID)

You mention my running memtest -- I ran 8 full passes (~8 hours total, no errors) but didn't do sticks individually. I used the default test settings (I'm new at this, I think the 'bit fade' test was optional and so not done).

As the BSODs occur only every day or 2 it may 2-3 days before I reply again. If all is well I will mark this 'solved' to close the thread (and to thank you again!). If BSODs continue I will post that (and include any new info) and do the further tests you suggest and report their results.

Again -- thanks!

I hope it works. asacpi.sys is well known so fingers crossed.

Good luck

Well it's been 5 days, no crashes. Previously I had 12 crashes in 20 days, that's 3 per 5 days, so I'm going out on a limb, knocking on wood, and saying your advice has *Peter Seller's Inspector Clousseau voice* sol-ved my problem!

Thank you for your time and effort, it's much appreciated!