locked
Windows7 Blue Screen STOP 0xF4, {3, fffffab002f76060, fffffab002f76340, fffff80001bd6db0} RRS feed

  • Question

  • The Dump File

    https://1drv.ms/u/s!AkMBHMzsqIvO0VTS8rsK_YMgaZe3

    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck F4, {3, fffffab002f76060, fffffab002f76340, fffff80001bd6db0}

    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: fffffab002f76060, Terminating object
    Arg3: fffffab002f76340, Process image file name
    Arg4: fffff80001bd6db0, Explanatory message (ascii)

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


    PROCESS_OBJECT: fffffab002f76060

    IMAGE_NAME:  wininit.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    MODULE_NAME: wininit

    FAULTING_MODULE: 0000000000000000

    PROCESS_NAME:  wininit.exe

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0xF4

    CURRENT_IRQL:  0

    STACK_TEXT:  
    00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    FAILURE_BUCKET_ID:  X64_0xF4_IMAGE_wininit.exe

    BUCKET_ID:  X64_0xF4_IMAGE_wininit.exe

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

    Thursday, July 28, 2016 12:02 PM

Answers

  • The dump is inconclusive.  Please run driver verifier to find the underlying cause

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!!  If you do not know what this means you probably are not


    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)


    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Thursday, July 28, 2016 12:14 PM
  • Hi AxisRay,

    Most common causes of f4 bsod, file system corruption, bad sector on hard drive, virus or malware. The PROCESS_NAME:  wininit.exe. I suggest that we could check in Safe Mode and try use the command “sfc /scannow” to repair the system files. Please check the link below about Error: Crash caused by wininit.exe

    http://answers.microsoft.com/en-us/windows/forum/all/error-crash-caused-by-wininitexe/d7d59083-1f43-4ec6-89a1-08f9b23b357c

    Hope it will be helpful to you


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Friday, July 29, 2016 9:26 AM

All replies

  • The dump is inconclusive.  Please run driver verifier to find the underlying cause

    These crashes were related to memory corruption (probably caused by a driver). 

    Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless verifier does not find the cause, or you want to.


    If you are over-clocking anything reset to default before running these tests.
    In other words STOP!!!  If you do not know what this means you probably are not


    1-Driver verifier (for complete directions see our wiki here)

    2-Memtest. (You can read more about running memtest here)


    Wanikiya and Dyami--Team Zigzag Windows IT-PRO (MS-MVP)

    Thursday, July 28, 2016 12:14 PM
  • Hi AxisRay,

    Most common causes of f4 bsod, file system corruption, bad sector on hard drive, virus or malware. The PROCESS_NAME:  wininit.exe. I suggest that we could check in Safe Mode and try use the command “sfc /scannow” to repair the system files. Please check the link below about Error: Crash caused by wininit.exe

    http://answers.microsoft.com/en-us/windows/forum/all/error-crash-caused-by-wininitexe/d7d59083-1f43-4ec6-89a1-08f9b23b357c

    Hope it will be helpful to you


    Please mark the reply as an answer if you find it is helpful.

    If you have feedback for TechNet Support, contact tnmff@microsoft.com

    Friday, July 29, 2016 9:26 AM