New
#1
BSOD 0x00000f4
Hello.
I have BSOD randomly per week, when I turn on my laptop. I reintalled OS, something like 4 weeks ago. I don't know where is a problem.
Could You help me, please?
My laptop is Asus K72JT.
Hello.
I have BSOD randomly per week, when I turn on my laptop. I reintalled OS, something like 4 weeks ago. I don't know where is a problem.
Could You help me, please?
My laptop is Asus K72JT.
Hi Qwerty1234567,
Welcome to the 7forums.
It looks like the crashes are from an Input/Output error from the hard drive
Please scan your hard drive for errors.
If you have an SSD, use chkdsk only.
Diagnostics Test
HDD TEST
Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use
NoteDo not run SeaTools on an SSD as the results will be invalid.
Run chkdsk Disk Check
Code:BugCheck F4, {3, fffffa800809bb10, fffffa800809bdf0, fffff80003778e20} ----- ETW minidump data unavailable----- Probably caused by : wininit.exe Followup: MachineOwner --------- 3: 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: fffffa800809bb10, Terminating object Arg3: fffffa800809bdf0, Process image file name Arg4: fffff80003778e20, Explanatory message (ascii) Debugging Details: ------------------ ----- ETW minidump data unavailable----- PROCESS_OBJECT: fffffa800809bb10 IMAGE_NAME: wininit.exe DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: wininit FAULTING_MODULE: 0000000000000000 PROCESS_NAME: wininit.exe EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - De instructie op 0x%p verwijst naar geheugen op 0x%p. De benodigde gegevens zijn niet in het geheugen geplaatst vanwege een I/O-foutstatus van 0x%x. BUGCHECK_STR: 0xF4_IOERR CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT CURRENT_IRQL: 0 ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre STACK_TEXT: fffff880`05be6b08 fffff800`0380b582 : 00000000`000000f4 00000000`00000003 fffffa80`0809bb10 fffffa80`0809bdf0 : nt!KeBugCheckEx fffff880`05be6b10 fffff800`037c199b : ffffffff`ffffffff fffffa80`0809fb50 fffffa80`0809bb10 fffffa80`0809bb10 : nt!PspCatchCriticalBreak+0x92 fffff880`05be6b50 fffff800`0372d26c : ffffffff`ffffffff 00000000`00000001 fffffa80`0809bb10 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x29d16 fffff880`05be6ba0 fffff800`03474b53 : fffffa80`0809bb10 00000000`c0000006 fffffa80`0809fb50 000007ff`fffdd000 : nt!NtTerminateProcess+0xf4 fffff880`05be6c20 00000000`7721de7a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`000ff888 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7721de7a STACK_COMMAND: kb FOLLOWUP_NAME: MachineOwner IMAGE_VERSION: FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xf4_ioerr_image_wininit.exe FAILURE_ID_HASH: {7e8d25f6-54c6-2456-f4df-269f2fd35200} Followup: MachineOwner