Ongoing BSODs

Josh M · 17 Oct 2010

Hi there I've been dealing with an ongoing computer problem for the past month with no hope. I seem to be getting BSOD's in spurts and different ones with no pattern. Here is the following of what I've tested to resolve the problem:

PSU
HDD
RAM
Motherboard appears fine with no bulging capacitors, I've also run a stress test.

Here is a list of BSOD's.

BAD_SYSTEM_CONFIG_INFO

SYSTEM_SERVICE_EXCEPTION
0X0000003B | WIN32K.SYS

IMMOUNTABLE_BOOT_VOLUME

0X000000ED
PROCESS1_INITIAZTION_FAILED

0X0000006B

and the most common:

0x000000F4

I've looked through BlueScreenView and it says ntoskrnel.exe caused 0X000000F4.
Please help
Thanks in advance.

Jonathan_King · 17 Oct 2010

Bad hard drive.

Test with SeaTools: | Seagate

If you have another hard drive you can install to, try it.

...Summary of the Dumps:

Code:


Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 18 08:47:02.421 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:51.000
BugCheck F4, {3, fffffa8005897b30, fffffa8005897e10, fffff800021985d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 18 08:20:02.002 2010 (UTC - 4:00)
System Uptime: 0 days 0:00:57.784
BugCheck F4, {3, fffffa800591f040, fffffa800591f320, fffff80002d8e5d0}
Probably caused by : smss.exe
PROCESS_NAME:  taskmgr.exe
BUGCHECK_STR:  0xF4_taskmgr.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 18 08:18:24.562 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:12.062
BugCheck F4, {3, fffffa8005d93b30, fffffa8005d93e10, fffff800021845d0}
Probably caused by : wininit.exe
PROCESS_NAME:  taskmgr.exe
BUGCHECK_STR:  0xF4_taskmgr.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 18 08:16:29.594 2010 (UTC - 4:00)
System Uptime: 0 days 0:01:55.172
BugCheck F4, {3, fffffa8005d1cb30, fffffa8005d1ce10, fffff8000217e5d0}
Probably caused by : _
PROCESS_NAME:  taskmgr.exe
BUGCHECK_STR:  0xF4_taskmgr.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Mon Oct 18 07:15:38.198 2010 (UTC - 4:00)
System Uptime: 0 days 0:23:13.963
BugCheck F4, {3, fffffa800599fb30, fffffa800599fe10, fffff80002dca5d0}
Probably caused by : _
PROCESS_NAME:  taskmgr.exe
BUGCHECK_STR:  0xF4_taskmgr.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Oct 13 05:43:37.240 2010 (UTC - 4:00)
System Uptime: 0 days 2:53:16.021
BugCheck F4, {3, fffffa8005eb1b30, fffffa8005eb1e10, fffff80002dd45d0}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR_C000000E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Wed Jan  4 06:49:20.221 2006 (UTC - 4:00)
System Uptime: 0 days 11:26:15.018
BugCheck F4, {3, fffffa8005fb4b30, fffffa8005fb4e10, fffff80002d925d0}
Probably caused by : csrss.exe
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_C0000005
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Tue Jan  3 10:25:07.223 2006 (UTC - 4:00)
System Uptime: 0 days 0:01:30.020
BugCheck F4, {3, fffffa80049bc430, fffffa80049bc710, fffff80002d8c5d0}
Probably caused by : hardware_disk
PROCESS_NAME:  csrss.exe
BUGCHECK_STR:  0xF4_IOERR_C000000E
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨

Josh M · 17 Oct 2010

I used the WD utility though.

Josh M · 17 Oct 2010

I'm beginning to agree with you now, now im getting constant bsods related to registry and system files.

Jonathan_King · 18 Oct 2010

Fortunately, hard drives are cheap. I advise purchasing a new hard drive (500GB for < $60!), and if it turns out not to be the cause, you can use it for backup, or even sell it.

Josh M · 18 Oct 2010

Yeah that sounds like a good idea. Thanks for the help.

Josh M · 22 Oct 2010

SOLVED: HDD appeared with no errors through disk utilitys but was turning off randomly.

Jonathan_King · 22 Oct 2010

Great, glad it's all sorted out.

Just to make sure, how did you determine the drive was the cause?

Josh M · 23 Oct 2010

When I re-installed windows on a new drive I plugged in the old one and ran a chkdsk. The chkdsk ran fine until I could literally hear the drive turning off and then on again. It then told me the drive couldn't be accessed.