I know theres google but this is more thorough.
I've just gotten this BSOD for the first time and am curious as how to fix it. It said bad pool header and with a google search, people say to clean your registries.
What do I do?
What did you do to cause it
Well I don't generally try and cause BSOD's so I don't how to answer that.
What did you change? have you googled the stop code?
I haven't changed anything, thats the thing. Nothing out of place or ordinary has happened recently. IF anything, I've been going less on my computer recently so why this has happened is kinda worrying me.
The sites that said to clean your registry are lying.
It could be a number of things, bad ram, corrupt hardware or drivers, i did see one thing about it being the Bios so try and get the latest one.
Do not only post the error-name, post the corresponding error codes. They look like 0x0000000A. Post the first three of those 0x... entries or even google for it.
Well how would I go about to pull back the error report?
replicate it and write it down?
:downs:
[editline]19th January 2011[/editline]
(it's on the bottom of the blue screen like aVoN posted above)
image it
this is the first thing I would try (before I asked the internet)
put in windows disc
wait for prompt
press r for recovery console
run chkdsk c: /F
[QUOTE=Roo-kie;27505662]this is the first thing I would try (before I asked the internet)
put in windows disc
wait for prompt
press r for recovery console
run chkdsk c: /F[/QUOTE]
Why do you associate a filesystem error with a bluescreen? It's like with a person getting to the next car shop saying "hey, my car does not start" and the mechanic says "The first thing I do then is cleaning my car before I get it to a workshop - It could help".
He has simply provided too less information yet. Also @op: For retrieving an old BSOD message, go to the Event Log and browse for errors. Google tells you how to bring up the Event Log.
cause he reckons he didn't do anything.
every time i have had a random bluescreen it's been a filesystem error
[QUOTE=Roo-kie;27506547]cause he reckons he didn't do anything.
every time i have had a random bluescreen it's been a filesystem error[/QUOTE]
Filesystem errors do not cause BSOD (in 99.999% of all cases) but BSOD can cause filesystem errors. But hardware faults of your drive or motherboard can cause a BSOD and FS-errors.
Anyway, what I meant with my original post was that there is no general treatment for BSOD and a FS-Scan is mostly useless since BSOD are generally caused by faulty software running in kernel-mode (such as drivers) or faulty hardware.
[editline]19th January 2011[/editline]
Found a probably analytical method to fight the error: [url]http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/a394599a-3752-4d36-aca3-a7d1671ae86f[/url]
They suggest using [i]driver verifier[/i] to find the faulty driver. Also the last error-message you posted was the BSOD, [url=http://www.osronline.com/ddkx/ddtools/bccodes_519j.htm]0x19 = BAD_POOL_HEADER and 0x3 in the brackets is the sub-category[/url]. The other numbers are memory-addresses and irrelevant for you.
Sorry for sounding stupid or not understanding, what exactly do I need to do?
Sorry, you need to Log In to post a reply to this thread.