locked
SYSTEM_SERVICE_EXCEPTION (HELP!) RRS feed

  • Question

  • Hello, My computer very recently started giving my the blue screen of sad face with the error (SYSTEM_SERVICE_EXCEPTION).

    It happens when i'm playing a game, watching a video or watching twitch streams. I have updated windows to it's latest version updated my graphics drivers to the latest versions and even factory reset my computer. All to no success, I will link my .dmp files in a zip. any help is appreciated! Thanks for reading.

    .dmp zip https://onedrive.live.com/?cid=653B40D315B79E1E&id=653B40D315B79E1E%21107


    • Edited by GWOODgg Friday, February 13, 2015 12:43 AM
    Friday, February 13, 2015 12:42 AM

Answers

  • GW

    These are called BCC124 and are related to hardware.  Read how to diagnose and hopefully to fix them read this wiki

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\021215-21843-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is: 
    SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    Machine Name:
    Kernel base = 0xfffff800`01407000 PsLoadedModuleList = 0xfffff800`016dd370
    Debug session time: Thu Feb 12 19:21:07.783 2015 (UTC - 5:00)
    System Uptime: 0 days 0:17:20.496
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    ......................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, ffffe0012ba82028, b0800000, 40151}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe0012ba82028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  Rome2.exe
    
    CURRENT_IRQL:  f
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    STACK_TEXT:  
    ffffd001`d6c49e28 fffff800`01bd4213 : 00000000`00000124 00000000`00000000 ffffe001`2ba82028 00000000`b0800000 : nt!KeBugCheckEx
    ffffd001`d6c49e30 fffff800`015caf49 : 00000000`00000001 ffffe001`28aaa5c0 ffffe001`28aaa5c0 ffffe001`2ba82028 : hal!HalBugCheckSystem+0xcf
    ffffd001`d6c49e70 fffff800`01bd46a0 : 00000000`00000728 00000000`00000004 ffffd001`d6c4a230 00000000`00000000 : nt!WheaReportHwError+0x22d
    ffffd001`d6c49ed0 fffff800`01bd4a0d : ffffe001`00000010 ffffe001`28aaa5c0 ffffd001`d6c4a078 ffffe001`28aaa5c0 : hal!HalpMcaReportError+0x50
    ffffd001`d6c4a020 fffff800`01bd48f8 : ffffe001`28aa9dd0 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
    ffffd001`d6c4a070 fffff800`01bd4cd8 : ffffe001`28aa9dd0 ffffd001`d6c4a2b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
    ffffd001`d6c4a0b0 fffff800`01560cbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x49
    ffffd001`d6c4a0e0 fffff800`01560a71 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffd001`d6c4a220 00000000`59381e2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    00000000`0424fd30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x59381e2a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_cache
    
    FAILURE_ID_HASH:  {b533751b-676e-7546-bcdc-24e6c40d0064}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Michael_LS Thursday, February 19, 2015 4:21 AM
    • Marked as answer by ZigZag3143x Thursday, February 19, 2015 12:17 PM
    Tuesday, February 17, 2015 1:06 AM

All replies

  • 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

    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

    Friday, February 13, 2015 2:08 AM
  • I did the driver verifier last night and on start up I got a blue screen telling me that the verifier found something then would restart. I was forced to go back to a earlier backup I made right before I used Verifier. how do I find out what the verifier said is causing the problem? thanks so much for the help!
    Friday, February 13, 2015 8:35 PM
  • 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

    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

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


    Wanikiya and Dyami--Team Zigzag


    Friday, February 13, 2015 8:36 PM
  • 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

    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

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


    Wanikiya and Dyami--Team Zigzag



    Huh?  Please be specific

    Wanikiya and Dyami--Team Zigzag

    Friday, February 13, 2015 8:38 PM
  • Last night I used driver verifier to find what driver was causing the problem. Unfortunatly it did find a problem resulting in me not able to access my computer. So in order to get back on my computer i set it back to a back up i created right before using the verifier. I still don't know what driver is causing the problem i just know it's one of them I had clicked when i used verifier last night. hope this is more descriptive! how do i find out which driver it is?
    • Edited by GWOODgg Friday, February 13, 2015 10:11 PM
    Friday, February 13, 2015 10:07 PM
  • GW

    First we could have helped log back in without reverting

    Second, upload the DMP file created when verifier crashed


    Wanikiya and Dyami--Team Zigzag

    Friday, February 13, 2015 10:12 PM
  • https://onedrive.live.com/?cid=653B40D315B79E1E&id=653B40D315B79E1E%21107

    in the bdlog file I think this is what you wanted? thanks for all the help again

    Tuesday, February 17, 2015 12:36 AM
  • GW

    These are called BCC124 and are related to hardware.  Read how to diagnose and hopefully to fix them read this wiki

    Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Ken\Desktop\021215-21843-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    WARNING: Whitespace at start of path element
    WARNING: Whitespace at end of path element
    Error: Empty Path.
    Symbol search path is: 
    SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
    Executable search path is: 
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 9600.17328.amd64fre.winblue_r3.140827-1500
    Machine Name:
    Kernel base = 0xfffff800`01407000 PsLoadedModuleList = 0xfffff800`016dd370
    Debug session time: Thu Feb 12 19:21:07.783 2015 (UTC - 5:00)
    System Uptime: 0 days 0:17:20.496
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ......................
    Loading User Symbols
    Loading unloaded module list
    ......................................
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, ffffe0012ba82028, b0800000, 40151}
    
    Probably caused by : AuthenticAMD
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffe0012ba82028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b0800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000040151, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_AuthenticAMD
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    PROCESS_NAME:  Rome2.exe
    
    CURRENT_IRQL:  f
    
    ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
    
    STACK_TEXT:  
    ffffd001`d6c49e28 fffff800`01bd4213 : 00000000`00000124 00000000`00000000 ffffe001`2ba82028 00000000`b0800000 : nt!KeBugCheckEx
    ffffd001`d6c49e30 fffff800`015caf49 : 00000000`00000001 ffffe001`28aaa5c0 ffffe001`28aaa5c0 ffffe001`2ba82028 : hal!HalBugCheckSystem+0xcf
    ffffd001`d6c49e70 fffff800`01bd46a0 : 00000000`00000728 00000000`00000004 ffffd001`d6c4a230 00000000`00000000 : nt!WheaReportHwError+0x22d
    ffffd001`d6c49ed0 fffff800`01bd4a0d : ffffe001`00000010 ffffe001`28aaa5c0 ffffd001`d6c4a078 ffffe001`28aaa5c0 : hal!HalpMcaReportError+0x50
    ffffd001`d6c4a020 fffff800`01bd48f8 : ffffe001`28aa9dd0 00000000`00000001 00000000`00000004 00000000`00000000 : hal!HalpMceHandlerCore+0xe1
    ffffd001`d6c4a070 fffff800`01bd4cd8 : ffffe001`28aa9dd0 ffffd001`d6c4a2b0 00000000`00000000 00000000`00000000 : hal!HalpMceHandler+0xe4
    ffffd001`d6c4a0b0 fffff800`01560cbb : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x49
    ffffd001`d6c4a0e0 fffff800`01560a71 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x7b
    ffffd001`d6c4a220 00000000`59381e2a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x171
    00000000`0424fd30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x59381e2a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: AuthenticAMD
    
    IMAGE_NAME:  AuthenticAMD
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    BUCKET_ID:  0x124_AuthenticAMD_PROCESSOR_CACHE
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x124_authenticamd_processor_cache
    
    FAILURE_ID_HASH:  {b533751b-676e-7546-bcdc-24e6c40d0064}
    
    Followup: MachineOwner
    ---------
    
    


    Wanikiya and Dyami--Team Zigzag

    • Proposed as answer by Michael_LS Thursday, February 19, 2015 4:21 AM
    • Marked as answer by ZigZag3143x Thursday, February 19, 2015 12:17 PM
    Tuesday, February 17, 2015 1:06 AM