Bsods :(

casual123 · 3 Feb 2011 at 00:58

Ive been Gettting bsods or random shutdowns for quite some time now (only since i upgraded to 64bit windows 7) i upgraded from 32 bit with 3gb ram to 64bit with 4gb ram and ever since ive been getting random bsods such as BAD POOL HEADER and the memory dump refers to ntoskrnl.exe & win32k.sys. The thing is it doesnt happen whilst im playing any games, the most recent one was when i went to talk on ts3 i just got horizontal coloured lines and a bsod. This is really doing my head in and i want to find the cause. Ive ran memtest on each stick to check for errors but they all come through with no errors

My specs
Asus m4a785tdv-evo mobo
Amd phenom x2 550be unlocked to quad (never had any problems with it in 32bit so i dont think its the cause)
4gb ddr3 kingston ram
Coolermaster silent pro 700w modular psu
HIS 6850 1gb
one hitatchi deskstar 320gb sata drive & also an 80gb one.

All temps are fine so it isnt to do with temps

any help please. :confused:

angela · 3 Feb 2011 at 01:02

How long you run memtest for? is your CPU OC'ed? maybe ATI Driver too?

casual123 · 3 Feb 2011 at 01:05

angela said:
How long you run memtest for? is your CPU OC'ed? maybe ATI Driver too?

I ran memtest for atleast 3 passes on each stick and they came back with no errors, apart from the unlock my cpu isnt overclocked ,ive also tried many ati drivers with no luck, even a fresh install of windows

Kouba · 3 Feb 2011 at 01:06

"One way to fix such a kind of a problem is to purchase a registry cleaner software. This is because a bad pool header error is caused by a corrupt registry. The registry is simply the brain of the computer and if corrupted this starts a whole chain of reaction that will lead to the eventual crashing of your computer. The other remedy is to always scan your computer."

Seems like some corrupt registries.

I recommend RegCure, its a fantastic piece of kit, you may be able to find it somewhere on the net without having to pay of course *cough*

casual123 · 3 Feb 2011 at 01:08

Dirty-Blade said:
"One way to fix such a kind of a problem is to purchase a registry cleaner software. This is because a bad pool header error is caused by a corrupt registry. The registry is simply the brain of the computer and if corrupted this starts a whole chain of reaction that will lead to the eventual crashing of your computer. The other remedy is to always scan your computer."

Seems like some corrupt registries.

I recommend RegCure, its a fantastic piece of kit, you may be able to find it somewhere on the net without having to pay of course *cough*

i ran ccleaner and cleaned the registry after the most recent bsod (is ccleaner ok?) i just dont see why bsods would still persist after a fresh install, it must be hardware related? i have no idea :confused:

Kouba · 3 Feb 2011 at 01:11

Not sure how well Ccleaner is in terms of repairing registries, maybe try this just to be sure:

http://regcure.net/

Regcure seems to be better since it doesnt just scan the registries, but other corrupt data that may be stored on the pc, as well as valuable OS data.

casual123 · 3 Feb 2011 at 01:17

Dirty-Blade said:
Not sure how well Ccleaner is in terms of repairing registries, maybe try this just to be sure:

http://regcure.net/

Regcure seems to be better since it doesnt just scan the registries, but other corrupt data that may be stored on the pc, as well as valuable OS data.

ok ill give that a try, does anyone think this could be the psu? the psu is only one or two months old though

Kouba · 3 Feb 2011 at 01:23

PSU? Seriously doubt it, it doesnt seem to be hardware related in any way, as you stated in your post, the BSOD is "BAD POOL HEADER". Its usually registry or driver related issues that cause this bsod.

casual123 · 3 Feb 2011 at 01:37

Well regcure is currently running/scanning and so far it says 728 problems 0_o ?

Kouba · 3 Feb 2011 at 01:39

Well there you go my friend

Hope you got the full version though, cause im not sure if that free version lets you repair those problems.

Savvy · 3 Feb 2011 at 01:40

Think you might of found the problem

also update your drivers too

casual123 · 3 Feb 2011 at 01:42

oh my god, nearly two thousand now!

casual123 · 4 Feb 2011 at 08:40

seems it didnt fix it, just got a bsod saying "irql not less or equal"

Savvy · 4 Feb 2011 at 11:19

Did you test each ram stick in all 4 slots? also turn off core unlocker if its that is causing the problem

Philtor · 4 Feb 2011 at 11:24

Make sure you have done a thorough enough test with Memtest first of all. Then have a look at Who Crashed.

s innes · 4 Feb 2011 at 11:27

it could be that the upgrade disk is bad
i'd send it back and get a new one or there is a problem with one or more 64bit drivers

casual123 · 5 Feb 2011 at 03:01

Savvy said:
Did you test each ram stick in all 4 slots? also turn off core unlocker if its that is causing the problem

the thing is i dont think its my cpu unlocked, because it ran fine for nearly a year unlocked running 32bit windows, and ive only got bsods since 64bit so i just dont know what it is :/

bremen1874 · 5 Feb 2011 at 03:23

If you’re trying to diagnose this sort of issue the first thing to do is set every back to stock settings (including any bonus cores). Make sure it’s stable with the 64bit OS at stock and then work up from there. Anything else is just guesswork!