Frequent BSODs

[shawnj]

I had an issue about a month ago (see link below) which this site helped me with. I didn't have any issues for 3 weeks but in the last few days I am having random and frequent BSODs.

Previous issue: http://www.sevenforums.com/bsod-help-support/334243-bsod-after-15-minutes-driver_irql.html

A MBAM sweep shows no issues. I have tried running a CHDSK but it does not appear to complete. I ran CCleaner but things seemed to get worse after this.

When a BSOD happens it does not re-boot but just freezes. There are no Minidump files being created even though my Write Debugging Information is set to "Small Memory Dump". I have attached a screen shot of my settings.

Any help would be appreciated.

Thanks,
Shawn

 

[shawnj]

For whatever reason, when another BSOD happened a few minutes ago a Minidump file was generated. I have attached it here.

 

[koolkat77]

F4 is usually a storage error.

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\071114-25974-01\071114-25974-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0281b000 PsLoadedModuleList = 0xfffff800`02a5e890
Debug session time: Sat Jul 12 06:49:05.598 2014 (UTC + 6:00)
System Uptime: 0 days 0:51:13.472
Loading Kernel Symbols
...............................................................
..................................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck F4, {3, fffffa80077bab30, fffffa80077bae10, fffff80002b96270}

----- ETW minidump data unavailable-----
Probably caused by : wininit.exe

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80077bab30, Terminating object
Arg3: fffffa80077bae10, Process image file name
Arg4: fffff80002b96270, Explanatory message (ascii)

Debugging Details:
------------------

----- ETW minidump data unavailable-----

PROCESS_OBJECT: fffffa80077bab30

IMAGE_NAME:  wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000 

PROCESS_NAME:  wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR:  0xF4_IOERR

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`081e70e8 fffff800`02c1eab2 : 00000000`000000f4 00000000`00000003 fffffa80`077bab30 fffffa80`077bae10 : nt!KeBugCheckEx
fffff880`081e70f0 fffff800`02bc9abb : ffffffff`ffffffff fffffa80`07fac580 fffffa80`077bab30 fffffa80`077bab30 : nt!PspCatchCriticalBreak+0x92
fffff880`081e7130 fffff800`02b48f04 : ffffffff`ffffffff 00000000`00000001 fffffa80`077bab30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`081e7180 fffff800`0288fe53 : fffffa80`077bab30 fffff800`c0000006 fffffa80`07fac580 00000000`02580d20 : nt!NtTerminateProcess+0xf4
fffff880`081e7200 fffff800`0288c410 : fffff800`028db82f fffff880`081e7b78 fffff880`081e78d0 fffff880`081e7c20 : nt!KiSystemServiceCopyEnd+0x13
fffff880`081e7398 fffff800`028db82f : fffff880`081e7b78 fffff880`081e78d0 fffff880`081e7c20 000007fe`fdd5e7b4 : nt!KiServiceLinkage
fffff880`081e73a0 fffff800`02890242 : fffff880`081e7b78 00000000`02600000 fffff880`081e7c20 000007fe`fdd67018 : nt! ?? ::FNODOBFM::`string'+0x488e4
fffff880`081e7a40 fffff800`0288edba : 00000000`00000000 000007fe`fdd5e7b7 00000000`777a8d01 00000000`02600000 : nt!KiExceptionDispatch+0xc2
fffff880`081e7c20 00000000`77698f56 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x23a
00000000`025812e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77698f56


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

BUCKET_ID:  X64_0xF4_IOERR_IMAGE_wininit.exe

Followup: MachineOwner
---------

Run Disk Check on your Hard Drive for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

Upload a screenshot of your hard disk using Crystal Disk Info:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Test your Hard Drive with SeaTools:

• How to Use SeaTools for DOS and Windows Disk Check Utility

 

[shawnj]

Well, that escalated quickly. For a while there I couldn't even boot up in Safe mode and in normal mode I get a BSOD within a minute or so. I kept trying and eventually I was able to boot up in Safe mode.

Disk Check:

Ran check only (neither box was checked).
- Disk Check reported that there were file system errors found.

Ran with "Automatically fix file system errors" checked. This requires a re-boot since this my only HD.
- See attached for screen shots of what was reported.

Ran with "Scan and recover bad sectors" checked.
- It only ran a few minutes before I got a BSOD.

Seatools:

Note - I have a Seagate 1TB HD

Started short test
- got a notification that SMART had been tripped. I hit continue.
- Short test passed

Started Long test
- got a notification that SMART had been tripped. I hit continue.
- Completed about 1-2% and got a message that "the drive is not responding to commands"

Re-ran Short test
- got an unknown failure

Rebooted

Started short test
- got a notification that SMART had been tripped. I hit continue.
- Short test passed

Rebooted

Started Long test
- got a notification that SMART had been tripped. I hit continue.
- Completed about 1-2% and got a message that "the drive is not responding to commands" & possible bad sector

-----------------

I haven't had a chance to try the Crystal Disk thing yet.

Is it safe to say that my HD is defective at this point? I dug around and found the recovery disks I made when I bought this computer so I should be able to start fresh with a new drive if needed. My files have been backed up an external drive.

Thanks,
Shawn

 

[shawnj]

I downloaded CrystalDiskInfo 6.1.14 and tried running it. I got a "Disk Not Found". It is possible this is user error on my part as the instructions are limited.