none
Blue screen "Unexpected store exception" and "Critical Process Died" RRS feed

  • Question

  • Hi i have Blue screen "Unexpected store exception" and "Critical Process Died". 

    This shows if I play games in random time 

    I have file C:/Windows/Minidump 

    Can You help me fix this problem ? 

    https://mega.nz/#F!UVNGzCTA!KCxGUlDgByUhUB1XJbokQw

    Friday, December 27, 2019 9:00 PM

All replies

  • You could first install the latest drivers to your computer from the manufacturer's site.

    Then you can use the CHKDSK tool.

    Start --> Run --> CMD (as administrator)

    chkdsk /r

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

    CRITICAL_PROCESS_DIED (ef)
            A critical system process died
    Arguments:
    Arg1: ffffb58c00508080, Process object or thread object
    Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
    Arg3: 0000000000000000
    Arg4: 0000000000000000

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

    ETW minidump data unavailable

    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  17134.1.amd64fre.rs4_release.180410-1804

    DUMP_TYPE:  2

    BUGCHECK_P1: ffffb58c00508080

    BUGCHECK_P2: 0

    BUGCHECK_P3: 0

    BUGCHECK_P4: 0

    PROCESS_NAME:  services.exe

    CRITICAL_PROCESS:  services.exe

    EXCEPTION_CODE: (Win32) 0x11d8600 (18712064) - <Unable to get error code text>

    ERROR_CODE: (NTSTATUS) 0x11d8600 - <Unable to get error code text>

    CPU_COUNT: 6

    CPU_MHZ: dbc

    CPU_VENDOR:  AuthenticAMD

    CPU_FAMILY: 15

    CPU_MODEL: 2

    CPU_STEPPING: 0

    CUSTOMER_CRASH_COUNT:  2

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

    BUGCHECK_STR:  0xEF

    CURRENT_IRQL:  0

    ANALYSIS_SESSION_HOST:  DESKTOP-A6NEAFA

    ANALYSIS_SESSION_TIME:  12-30-2019 07:39:53.0854

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    LAST_CONTROL_TRANSFER:  from fffff80056e38011 to fffff80056840650

    STACK_TEXT:  
    ffff840c`2c29fd98 fffff800`56e38011 : 00000000`000000ef ffffb58c`00508080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
    ffff840c`2c29fda0 fffff800`56d246f7 : 00000000`00000001 fffff800`5678e241 ffffb58c`00508080 00000000`c0000006 : nt!PspCatchCriticalBreak+0xfd
    ffff840c`2c29fe40 fffff800`56c14144 : ffffb58c`00000000 00000000`00000000 ffffb58c`00508080 ffffb58c`00508358 : nt!PspTerminateAllThreads+0x1c0b9b
    ffff840c`2c29feb0 fffff800`56c13f05 : ffffffff`ffffffff ffff840c`2c29ffe0 ffffb58c`00508080 fffff800`566f7000 : nt!PspTerminateProcess+0xe0
    ffff840c`2c29fef0 fffff800`56852f13 : 00000000`000002a0 ffffb58c`011d8600 ffffb58c`00508080 ffff840c`2c2a0130 : nt!NtTerminateProcess+0xa9
    ffff840c`2c29ff60 fffff800`56844680 : fffff800`566b9af0 ffff840c`2c2a0a58 ffff840c`2c2a0a58 ffff840c`2c2a0130 : nt!KiSystemServiceCopyEnd+0x13
    ffff840c`2c2a00f8 fffff800`566b9af0 : ffff840c`2c2a0a58 ffff840c`2c2a0a58 ffff840c`2c2a0130 00000000`0000000d : nt!KiServiceLinkage
    ffff840c`2c2a0100 fffff800`56853602 : 00000000`00000000 ffffb58b`ff1dc010 ffff840c`2c2a0b00 ffff840c`00000000 : nt!KiDispatchException+0x520
    ffff840c`2c2a0920 fffff800`5684f89d : 0000007f`f5992a70 00007ffd`a9431a07 0000007f`f5981db0 0000007f`f59ff1f0 : nt!KiExceptionDispatch+0xc2
    ffff840c`2c2a0b00 00007ffd`ab2d6a28 : 0000007f`f59812c0 0000007f`f59818c0 00007ffd`ab43874c 00000000`00000000 : nt!KiPageFault+0x49d
    0000007f`f59811c0 0000007f`f59812c0 : 0000007f`f59818c0 00007ffd`ab43874c 00000000`00000000 00000000`00000000 : 0x00007ffd`ab2d6a28
    0000007f`f59811c8 0000007f`f59818c0 : 00007ffd`ab43874c 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0000007f`f59812c0
    0000007f`f59811d0 00007ffd`ab43874c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0000007f`f59818c0
    0000007f`f59811d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`ab43874c


    THREAD_SHA1_HASH_MOD_FUNC:  f6b0f7fafbd5253fc3d42ad0a11af14fddabdcf0

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  a74f529b89c27bddc3170edc867586e6f87ce789

    THREAD_SHA1_HASH_MOD:  bc100a5647b828107ac4e18055e00abcbe1ec406

    FOLLOWUP_IP: 
    nt!PspCatchCriticalBreak+fd
    fffff800`56e38011 cc              int     3

    FAULT_INSTR_CODE:  ed8440cc

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!PspCatchCriticalBreak+fd

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  5acd8966

    IMAGE_VERSION:  10.0.17134.1

    STACK_COMMAND:  .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET:  fd

    FAILURE_BUCKET_ID:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_11d8600_nt!PspCatchCriticalBreak

    BUCKET_ID:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_11d8600_nt!PspCatchCriticalBreak

    PRIMARY_PROBLEM_CLASS:  0xEF_services.exe_BUGCHECK_CRITICAL_PROCESS_11d8600_nt!PspCatchCriticalBreak

    TARGET_TIME:  2019-12-26T21:08:36.000Z

    OSBUILD:  17134

    OSSERVICEPACK:  1

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  784

    PRODUCT_TYPE:  1

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 10

    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS Personal

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2018-04-11 07:04:54

    BUILDDATESTAMP_STR:  180410-1804

    BUILDLAB_STR:  rs4_release

    BUILDOSVER_STR:  10.0.17134.1.amd64fre.rs4_release.180410-1804

    ANALYSIS_SESSION_ELAPSED_TIME:  9bb5

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:0xef_services.exe_bugcheck_critical_process_11d8600_nt!pspcatchcriticalbreak

    FAILURE_ID_HASH:  {eea64bf4-09ea-a8c8-3ed3-a95207dc3986}

    Followup:     MachineOwner

    Monday, December 30, 2019 5:48 AM
  • your Windows version is still 1803, which is no longer supported (unless on Enterprise editions).
    But even on 1803, the file version seems out of date:
    Loaded symbol image file: ntkrnlmp.exe
        Timestamp:        Wed Apr 11 06:04:54 2018 (5ACD8966)
        File version:     10.0.17134.1

    Monday, December 30, 2019 7:13 AM
  • Hi,

    According to the forum's security policy, please understand that we do not provide analysis of dump/log files. For root case analysis or specific log diagnose, you may need to create a support request:

    https://support.microsoft.com/en-gb/hub/4343728/support-for-business

    Hope can help you.

    Best regards,

    Kiki


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, December 31, 2019 7:29 AM
  • To evaluate the BSOD please post logs for troubleshooting.

    Using administrative command prompt copy and paste this whole command.

    Make sure the default language is English so that the logs can be scanned and read.

    https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

    The command will automatically collect the computer files and place them on the desktop.

    Then use 7zip to organize the files and one drive, drop box, or google drive to place share links into the thread for troubleshooting.

    https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

    This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

    Open administrative command prompt and copy and paste the whole command:

    copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop\"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles\"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

    There are two files for you to find manually:

    a) C:\Windows\MEMORY.DMP

    Use file explorer > this PC > local C: drive > right upper corner search enter the above to find results.

    b) dxdiag:  

    In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread
    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is: 

    Propose as answer = answered the question

    On the left side of each post:  Vote = a helpful post
    .
    .
    .
    .
    .
    Tuesday, December 31, 2019 9:39 AM