BSOD While Gaming

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 64 Bit home premium
       #1

    BSOD While Gaming


    Hey guys, first off let me thank you guys for taking the time to help me. A week ago, I built my very first computer. It has been working great, except that I have been getting BSOD while gaming sometimes. The first time it happened it was while I was playing Skyrim. I shrugged it off as a random occurrence. Then it happened again, and again, and again. Some games have been working fine, but I get BSOD on the following games:
    Skyrim
    Fallout New Vegas
    Minecraft

    I haven't been able to figure out why they are happening, and happen at random points throughout the game, not whenever I do something specific.Here are my computer specs.
    Computer type: PC/Desktop
    Computer Manufacturer/Model Number: Custom
    OS: Windows 7 64 Bit home premium
    CPU: I5- 4570k @ 4.0 GhZ
    Motherboard: MSI Z87 G45
    Memory: Crucial 16GB Ballistix Sport
    Graphics Card(s): Gigabyte GTX 770
    Hard Drives: Samsung 120 GB SSD
    Seagate Barracuda 1TB
    Antivirus: Microsoft Essentials
    Browser: Firefox
    Last edited by l3radrocks; 13 Jul 2013 at 21:28.
      My Computer


  2. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #2

    Please follow the instructions here to get BSOD help:

    System Info - See Your System Specs

    Blue Screen of Death (BSOD) Posting Instructions
      My Computer


  3. Posts : 8
    Windows 7 64 Bit home premium
    Thread Starter
       #3

    Sorry, I should have followed the instructions. I just rushed the post. I fixed it now, please let me know if there is anything else you guys need.
      My Computer


  4. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #4

    Code:
    crash dump file: E:\BSOD\070913-2979-01.dmp
    uptime: 00:00:01
    This was probably caused by the following module: ntkrnlmp.exe (nt!WheapCreateLiveTriageDump+0x6C) 
    Bugcheck code: 0x124 (0x0, 0xFFFFFA800E7A88F8, 0x0, 0x0)
    Error: WHEA_UNCORRECTABLE_ERROR
    Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). 
    This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
    All your errors are 0x124 - hardware specific.

    Please follow this first:

    CPU - Stress Test Using IntelBurnTest
      My Computer


  5. Posts : 8
    Windows 7 64 Bit home premium
    Thread Starter
       #5

    I ran the normal stress test, and averaged about C 60. It maxed at C 70. I will run the other two In a while, I have to go run and do some other stuff.

    EDIT: I managed to run the High stress test, and the temp averaged around 64. The max was 71.
      My Computer


  6. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #6

    What about the residual values?

    Please also refer to this thread...
    Stop 0x124 - what it means and what to try
      My Computer


  7. Posts : 8
    Windows 7 64 Bit home premium
    Thread Starter
       #7



    There is the results for the high stress test. I will re-run the normal stress test and give you those results.
      My Computer


  8. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #8

    Thats fine.....they are stable on high, so they will be stable on the others.

    Please see that thread about 0x124 errors.
      My Computer


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

    A stop 0x124 is a hardware error, usually.

    Alongwith Golden's suggestion to run CPU - Stress Test Using IntelBurnTest, I would suggest you to run a few more hardware tests.

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings. Also set the BIOS to default, too.
    How To Clear CMOS (Reset BIOS)

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    At least 30% extra is safe. Also let us know the wattage of your PSU.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

    And dont worry. As it is a new build, your hardware are under warranty. Now it is to determine which hardware component is failing actually, and then RMA it.
    _____________________________________________________________
    BSOD ANALYSIS:
    Code:
    ..............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 124, {0, fffffa800d31a028, bf800000, 124}
    
    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: fffffa800d31a028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000124, 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:  svchost.exe
    
    CURRENT_IRQL:  f
    
    STACK_TEXT:  
    fffff880`0316da58 fffff800`02c12a3b : 00000000`00000124 00000000`00000000 fffffa80`0d31a028 00000000`bf800000 : nt!KeBugCheckEx
    fffff880`0316da60 fffff800`02dd5443 : 00000000`00000001 fffffa80`0d123a60 00000000`00000000 fffffa80`0d123ab0 : hal!HalBugCheckSystem+0x1e3
    fffff880`0316daa0 fffff800`02c12700 : 00000000`00000728 fffffa80`0d123a60 fffff880`0316de30 fffff880`0316de00 : nt!WheaReportHwError+0x263
    fffff880`0316db00 fffff800`02c12052 : fffffa80`0d123a60 fffff880`0316de30 fffffa80`0d123a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`0316dc50 fffff800`02c11f0d : 00000000`00000004 00000000`00000001 fffff880`0316deb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`0316dc90 fffff800`02c05e88 : 00000000`00000007 00000000`0175e0c8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`0316dcc0 fffff800`02cbd4ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`0316dcf0 fffff800`02cbd353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`0316de30 fffff800`0306a260 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`0bb69908 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpCallCallBacks
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: GenuineIntel
    
    IMAGE_NAME:  GenuineIntel
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    
    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE
    
    Followup: MachineOwner
    ---------
      My Computer


  10. Posts : 8
    Windows 7 64 Bit home premium
    Thread Starter
       #10

    I will run the Memory test over night, and hopefully reinstall the OS in the morning. I was running Furmark, but the temperatures started to level out, so I took the advice on the GPU Stress Test post and stopped the test.

    Is there a log that I could post that contained all the info prior to the termination of the test?
      My Computer


 
Page 1 of 2 12 LastLast

  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 14:39.
Find Us