Solved BSOD BAD_POOL_CALLER - No Minidump

[aeternum86]

I have an old All-in-one Siragon desktop PC with the following specifications:

-1GHz AMD S200U Processor
-Realtek High Definition Audio Device
-Ralink 802.11n Wireless LAN Card
-NIC Fast Ethernet PCI-E Realtek RTL8102E/RTL8103E Family (NDIS 6.20)
-300 Gb HD
-2 GB RAM
-ATI RadeonHD 4500 Video Card
-Memory Reader 3 in 1
-3 USB ports
-Generic Bluetooth Device

It came with Windows 7 Home Premium when i bought it (almost 2 years ago, or so).

Last week i tried to make a clean Windows 7 installation on it (due it was excessively slow), however i got a BSOD after first installation process reboot. I tried again with no luck.

I got the HD out the PC and plug it to my laptop (regular SATA connection) to be able to finnish the windows 7 installation, since i knew it was about hardware / drivers issues.

Why did i do this? in order to, at last, be able to boot in safe mode and update drivers as well as to enable BSOD crash info logging if issue coulnd't be fixed.

Finally, i found this forum and toke a look at many related threads but i wasn't able to fix BOSD on my machine.

The only info i have about the BSOD is this:

BAD_POOL_CALLER
0x000000C2 (0x00000099, 0x84C32048, 0x00000000, 00000000)

No Minidump/Memory.dmp is generated (and belive me, i have googled a lot to find out how to enable it and i've got nothing).

What should i do now? Please help!

 

[zigzag3143]

There are several reasons that may prevent you from having a DMP file in the usual places.

If you control panel is not configured for small dump you probably will then find it in C:\windows and it will be called MEMORY.dmp. It will overwrite every crash.

Other reasons are if you have UAC turned off, if you have a small page file, or a page file on a different HD than the OS.




BCC C2 is usually caused by a driver. If you can boot run verifier to find out which one.


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

* If you have raid update its Driver.


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.

 

[aeternum86]

Hey zigzag3134, thanks for your reply.

I'm still dealing with this issue.

I found out that BSOD occurs before crash report service is loaded, how do i know this? I induced a system crash on safe mode by killing csrss.exe process which generated a crash report file in C:\Windows\Minidump\ whilst the real BSOD doesn't generate anything!

What should i do know? Is there a way to make crash report service available before drivers load or something? Any idea?

 

[zigzag3143]

Hey zigzag3134, thanks for your reply.

I'm still dealing with this issue.

I found out that BSOD occurs before crash report service is loaded, how do i know this? I induced a system crash on safe mode by killing csrss.exe process which generated a crash report file in C:\Windows\Minidump\ whilst the real BSOD doesn't generate anything!

What should i do know? Is there a way to make crash report service available before drivers load or something? Any idea?

You can change the priority of the CRS but I doubt it will work

Since you can boot in safe mode, check msconfig to see if both max cpu and max ram is unchecked.

 

[aeternum86]

You can change the priority of the CRS but I doubt it will work

Since you can boot in safe mode, check msconfig to see if both max cpu and max ram is unchecked.

I did that too, but it didn't work. However... i keep googling and read somewhere out the internet about AHCI/BIOS config./Whatever, causing this kind of crashes too, so i ended up landing in [url="http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html]this thread[/url]

Since i wasn't able to find anything related to AHCI in my BIOS configuration, i decided to disabled it through regedit (safe mode), and voilà! BSOD disappeared!

 

[zigzag3143]

You can change the priority of the CRS but I doubt it will work

Since you can boot in safe mode, check msconfig to see if both max cpu and max ram is unchecked.

I did that too, but it didn't work. However... i keep googling and read somewhere out the internet about AHCI/BIOS config./Whatever, causing this kind of crashes too, so i ended up landing in this thread

Since i wasn't able to find anything related to AHCI in my BIOS configuration, i decided to disabled it through regedit (safe mode), and voilà! BSOD disappeared!

Good news, I wonder how it got changed though.