According to Microsoft, the
BAD_POOL_HEADER BSOD is
“perhaps, the most obscure error message. In most cases, if you receive this error, it's related to the most recent change you've made on your system. Try undoing the change to get rid of the error.” Ref.:
link.
However, oftentimes it occurs due to corrupted drivers, and NetGear wireless cards are infamous of generating this BSOD [
reference]. What kind of hardware did you added recently? Any changes whatsoever? Updated drivers or anything? If so, rollback, go back to the last known configuration, or do something about it.
On the other hand, its cause may be the oh-so common memory fault too. You already know my answer. Grab Memtest86+, run it overnight, and see for yourself. Hopefully your RAMs are fine and in that case you can hope that the problem mystically vanishes or that you can make it go away fiddling a bit with your drivers.
If still no luck then I'd download
WinDbg, load your most recent minidump, and hopefully it's going to point out that file it thinks caused the said BSOD. In that case, you can figure out which driver dynamic link library or sys file. You could also run
Driver Verifier Manager (start -> run -> "verifier.exe"), Next, Next, and verify the "Pool Allocations." That options tells you which driver failed how many times and all that.
All in all, its cause is one of the following: 1./ conflict of any device driver; 2./ system is restored to a previous date which makes a driver out of date; 3./ there is a possibility of RAM problem, Memtest86+ overnight, other sticks, trial-and-error; 4./ wireless cards are infamous of causing these BSODs; 5./ all-around driver problems (ATi?).
For more informations regarding how to fix BSODs check out
this guide and you may also want to grab and burn yourself a copy of
Ultimate Boot CD (it is jam-packed with useful utilities; all freeware).
Good luck, PaPa!