Author Topic: Need help with BlueScreen BAD_POOL_HEADER (Read 1750 times)

Mr.jacksaunt · April 04, 2013, 08:08:17 PM

everyone of you need to stop until we get KoopaScooper in here

Ad Bot · Advertisement

Tyler66 · April 04, 2013, 08:09:59 PM

Quote from: Linkusofepica on April 04, 2013, 08:03:20 PM

sonce.jpeg incoming. I CAN'T STOP IT.

asdf

loving ANDROID KEYPAD AGGHH

Quote from: Maxx_ on April 04, 2013, 08:04:08 PM

Alright, should I do a chkdsk or something?
Just to see if everything is working.

chkdsk would probably not do anything to solve your problem. Since BAD_POOL_HEADER is usually for driver issues or issues in RAM.
But I guess if you really want to check for hard disk corruption; by all means go for it.

Executive · April 04, 2013, 08:31:37 PM

NT is Windows NT 3.1 to Windows 8 so it's pretty much all of windows so do a chkdsk or reinstall
OT: you have a bad pool
fix it

Tokthree · April 04, 2013, 08:34:46 PM

Quote from: Executive on April 04, 2013, 08:31:37 PM

you have a bad pool
fix it

Pools closed due to aids

Maxx_ · April 04, 2013, 09:06:41 PM

Quote from: Tokthree on April 04, 2013, 08:34:46 PM

Pools closed due to aids

lel
Anyway, ran ram diagnostics, no problems. doing a clean install i guess

Maxx_ · April 04, 2013, 10:48:29 PM

Back, did a entire reinstall with the reset option to reset the compooter

Trymos · April 04, 2013, 11:06:15 PM

one god damn blue screen.

i got the exact same god damn blue screen with the exact same god damn file.

it's not god damned corrupt.

it's your god damned drivers they don't have to lead to the god damned driver file god damn it.

you should've just ignored it until further issues came in.

Maxx_ · April 04, 2013, 11:10:15 PM

Quote from: Trymos on April 04, 2013, 11:06:15 PM

one god damn blue screen.

i got the exact same god damn blue screen with the exact same god damn file.

it's not god damned corrupt.

it's your god damned drivers they don't have to lead to the god damned driver file god damn it.

you should've just ignored it until further issues came in.

thats alot of goddamns
heuhuehue

Axolotl2 · April 04, 2013, 11:17:34 PM

Run the Command Prompt in admin mode and type in sfc /checknow.

This will detect whether your files are really corrupt or not.

Quote from: Snow2 on April 04, 2013, 07:56:57 PM

ntoskrnl.exe is the Kernel shell of the Operating System, And since it's highlited in red, The operating system is Indicating that the problem was with that specific file.

This is how "Irrelevant" i can get

It doesn't have to be corrupt in order for it to cause the system to go into a stop error.

Something on the ring that can control ntoskrnl.exe can issue it a weird instruction that crashes it, which will cause a stop error.

tkepahama · April 04, 2013, 11:17:42 PM

Quote from: Trymos on April 04, 2013, 11:06:15 PM

one god damn blue screen.

i got the exact same god damn blue screen with the exact same god damn file.

it's not god damned corrupt.

it's your god damned drivers they don't have to lead to the god damned driver file god damn it.

you should've just ignored it until further issues came in.

god damn

Trymos · April 04, 2013, 11:19:12 PM

Quote from: Axolotl2 on April 04, 2013, 11:17:34 PM

Run the Command Prompt in admin mode and type in sfc /checknow

This will detect whether your files are really corrupt or not.

Quote from: Maxx_ on April 04, 2013, 10:48:29 PM

Back, did a entire reinstall with the reset option to reset the compooter

Axolotl2 · April 04, 2013, 11:23:51 PM

Quote from: Trymos on April 04, 2013, 11:19:12 PM

I need to read.

I'm keeping the post as is because knowing how to run the System File Checker is very important.