BSOD playing games in 4k resolution such as World of Tanks 0x00000124


  1. Posts : 3
    United States
       #1

    BSOD playing games in 4k resolution such as World of Tanks 0x00000124


    Hey guys, I've recently been encountering BSOD while playing graphically intensive games such as World of Tanks in 4k resolution. I thought it might be a temperature issue, so I manually turned up my GPU fan speed to 90% while playing, and my core temp. remained ~50°C. That didnt seem to fix the issue.

    My last crash gave me the ol' Stop: 0x00000124

    Here is my zip file containing the results of a DM Log Collector.

    Edit: My system specs are:
    CPU: i7-4790K @ 4.00GHz
    MB: ASUS MAXIMUS VII HERO LGA 1150 Intel Z97
    GPU: EVGA NVIDIA GForce GTX 780Ti
    RAM: 16Gb G.Skill Trident X @ 2400Mhz
    OS: Win7
    PSU: EVGA 1000P2
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    It seems to be overclocked.
    Code:
    CPUID:        "Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz"
    MaxSpeed:     4000
    CurrentSpeed: 4080
    And overclocking is one of the most frequent reasons of a stop 0x124 (though not the only reason).

    As you are experiencing BSODs, As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Then see if it still causing the same BSOD or not. If the BSOD continues to occur, let us know. We will take further attempts to troubleshoot the issue.
    _____________________________________________________
    Code:
    BugCheck 124, {0, fffffa800fa41028, be000000, 800400}
    
    Probably caused by : GenuineIntel
    
    Followup: MachineOwner
    ---------
    
    2: 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: fffffa800fa41028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
    
    Debugging Details:
    ------------------
    
    
    BUGCHECK_STR:  0x124_GenuineIntel
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  f
    
    ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
    
    STACK_TEXT:  
    fffff880`0336db58 fffff800`0320ba3b : 00000000`00000124 00000000`00000000 fffffa80`0fa41028 00000000`be000000 : nt!KeBugCheckEx
    fffff880`0336db60 fffff800`02d9ac33 : 00000000`00000001 fffffa80`0f9d3ea0 00000000`00000000 fffffa80`0f9d3ef0 : hal!HalBugCheckSystem+0x1e3
    fffff880`0336dba0 fffff800`0320b700 : 00000000`00000728 fffffa80`0f9d3ea0 fffff880`0336df30 fffff880`0336df00 : nt!WheaReportHwError+0x263
    fffff880`0336dc00 fffff800`0320b052 : fffffa80`0f9d3ea0 fffff880`0336df30 fffffa80`0f9d3ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`0336dd50 fffff800`0320af0d : 00000000`00000008 00000000`00000001 fffff880`0336dfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`0336dd90 fffff800`031fee88 : 00000000`00000000 fffff880`03365180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`0336ddc0 fffff800`02c801ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`0336ddf0 fffff800`02c80013 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`0336df30 fffff880`053d79c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`0338db58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm!C1Halt+0x2
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    IMAGE_VERSION:  
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x124_genuineintel_processor_mae
    
    FAILURE_ID_HASH:  {addebe90-d04a-b9c9-a39c-2531fe75dd4e}
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 3
    United States
    Thread Starter
       #3

    I went into my bios setting and saw that I wasn't over clocking anything other than my RAM, but just to be sure, I hit the button to return everything to default. I hope that maybe it changed something. Thank you for your help. :)
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    OK, report us for any further BSOD, we will check it again. :)
      My Computer


  5. Posts : 3
    United States
    Thread Starter
       #5

    Arc said:
    OK, report us for any further BSOD, we will check it again. :)
    You sir, are awesome. Thank you very much!
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:37.
Find Us