• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win7 64 - BSoD Bad_Pool.....

DaveU

Member
6 month old machine Win7 64, Quad core i7 820, EVGA x58 MB, 6 gig ram, Nvidia GTX 275,
minor overclock from manufacturer. No new software or hardware, No Bios updates... Just started random BSoD "Bad_Pool_ Header" or "Bad_Pool_Caller" reboot sometimes ok. or i'll have to completely shut down, sit for a few, then restart. System may run fine for days, then random BSoD again. Seems to hapen mostly when browsing and using the scroll wheel? Ran Prime 95 overnight and no issues, reseated ram and sata cables, any thoughts? Thanks!
 
Basically, I have the same problem with Windows 7 now, 32bit.
I did a clean installation of Windows 7 on my PC.
Then it keeps giving random BSOD. Checks on HDD has been done. Nothing wrong. I read a lot of posts that it's most likely caused by bad drivers. But each time with a different BSOD, I have no idea how to fix it. Now every time I turn on my PC, I have to wait until windows 7 is stable, which is probably after 5-to-infinite times of BSOD & restart.

p.s. strangely, the Windows 7 64bit I installed on my laptop has no problem.
 
Last edited:
I would start by running memtest86. Thats usually not a ram issue, but it's easier than BSOD for five days just to have to do it anyway.
If I were you I'd try it in safe mode. If still no go open that puppy out and remove EVERYTHING non-essential, go to one ram stick etc. If it is a driver issue you should be able to at least isolate it and update everything leading up to it.

Also, I know I never set restore points so I'm far from chastizing you if you don't, but can you restore to an earlier time? If it's a driver issue and you haven't installed anything right before the BSODs it's possible windows auto-updated and is causing the issue.
 
Last edited:
Back
Top