win 7 bsod

[paxa]

I was preparing to watch some movies on my htpc. when accidentally pressed the sleep button on my keyboard, when the computer boots up again i'm presented with a bsod with the message bad pool header. i start windows repair tool from the startup. wait it to finnish reboot and there's the bsod again.

what could be the problem?

i'm attaching the minidump file.

sorry about the double attachment, either one contains the minidump file.

as of now, i removed the hd from the computer and hooked it up to a usb case and the disk is now running a long generic test in seatools.

help would be appreciated.

thanks in advance.

minidump.zip

minidump.zip

[paxa]

seatools gave it a clean bill of health.

ran the windows scan for errors...there were some problems with the files, it corrected them.

plugged the hd back and the same error.

ran mem test 4.00 it gave me a pass complete, no errors.

[jnelsoninjax]

Download and run Whocrashed this will give you a better idea as to what might be causing the BSOD.

[paxa]

just did and it gives me this:

On Sat 12-05-2012 18:45:09 GMT your computer crashed

crash dump file: C:\Windows\Minidump\051212-24913-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0xDCE34)

Bugcheck code: 0x34 (0x50830, 0xFFFFFFFF8DD0B8A0, 0xFFFFFFFF8DD0B480, 0xFFFFFFFF82CDF851)

Error: CACHE_MANAGER

Bug check description: This indicates that a problem occurred in the file system's cache manager.

This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

[jnelsoninjax]

Have you run the system file checker?

SFC/scannow

errors such as you are reporting generally indicate that a system file is corrupt. Also I would suggest disabling the sleep button on the keyboard to avoid problems like this!

[paxa]

as i have the hd of the htpc hooked up on a usb case on another computer. i'm going to try the system file checker on that drive.

then, try to repair my installation. to see if it works

[Detection]

Did you try booting in safemode or last good known configuration first ?

Check the event logs when your in, its probably a corrupt driver or at the worst the partition table / mbr is messed up

[Princess Katie Pixie]

What is the BSOD when I don't even have one in my whole life using Windows? You guys are hillarious.

[paxa]

the only boot that wouldn't crash the system is safe mode with command prompt, that's the one selected and running, i'm now in the process of sfc /scannow to see if the system comes back to life so to say. i tried and boot it up with the option of logging one of the times, when it's over checking with sfc i'm going to see the log file and check if the problem resides with one of the drivers

[paxa]

chica ami...that's good for you

[paxa]

sfc just finished and it's reporting that it did not find any integraty violations

[Hum]

I would try going to Windows Update -- see if there are any fixes to Install.

Maybe directly replace the ntkrnlpa.exe file, from the original Windows 7 dvd.

^ You will need to do this from Safe Mode, with Command Prompt.

[Detection]

Worst come to worst, just run an upgrade of the same Win 7 DVD over the top, it'll sort windows out and leave all your files alone (Has to be started from inside windows, not booted from DVD)

[paxa]

going to try two things. load up gparted and check the mbr and then try and copy ntkrnlpa.exe

[Detection]

going to try two things. load up gparted and check the mbr and then try and copy ntkrnlpa.exe

Check in the BIOS incase when it entered sleep mode, the BIOS didn't bug out and switch SATA controller from AHCI to IDE or vice versa, that would cause a BSOD on boot every time

[paxa]

going to check it out, going to see if the problem is in the bios

[paxa]

nop, i believe the problem resides elsewhere...going to see if driver verifier gives some insight

[paxa]

it was a realtek driver that fracked it up...try to remove it and reinstall, borked up the system. so i decided to format it. thanks for the help jnelsoninjax and +Detection