BSOD After playing H1Z1 for 30 minutes with new computer


  1. Posts : 6
    Windows 7 Home Premium 64-bit
       #1

    BSOD After playing H1Z1 for 30 minutes with new computer


    Hello!

    As you can read from the title, I bought a new CPU, Motherboard and Case and assembled a new PC.
    I played GTA V For 2 hours and everything went well. I loaded up a game on H1Z1, played it for 30 minutes and then it froze and blue screened. After the PC booted back up, I got no error message.
    I ran the info collector which is provided on this website. I will attach the .zip file to this post aswell.

    Thank you in advance!
    Last edited by 1codekiller; 03 Jun 2015 at 15:00. Reason: miss spelling :P
      My Computer


  2. Posts : 646
    NT4
       #2

    There are no dumps in the upload, it you get any more bsods run the tool again and hopefully there will be something for us to analyse.
      My Computer


  3. Posts : 6
    Windows 7 Home Premium 64-bit
    Thread Starter
       #3

    I just got another BSOD. This time with an error report and a minidump file. I ran the dm log collector and will post the .zip file here.

    Thanks!
      My Computer


  4. Posts : 6
    Windows 7 Home Premium 64-bit
    Thread Starter
       #4

    Experienced 2 Blue screens of death today. I would really appreciate a fast reply, since this thing tends to happen mid gaming sessions, which usually leads to a ban from csgo matches
      My Computer


  5. Posts : 6,741
    W7 Pro x64 SP1 | W10 Pro IP x64 | W8.1 Pro x64 VM | Linux Mint VM
       #5

    We'd really appreciate some patience as we have to miss gaming sessions to help people who are having BSODs. There are lots of them as well as you may have noticed.

    Your single dump is a 0x124 which indicates a hardware failure but doesn't indicate what.
    Code:
    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: fffffa800a32a028, 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.
    
    2: kd> !errrec fffffa800a32a028
    ===============================================================================
    Common Platform Error Record @ fffffa800a32a028
    -------------------------------------------------------------------------------
    Record Id     : 01d0ac5707c2ede3
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 6/22/2015 20:00:48 (UTC)
    Flags         : 0x00000000
    
    ===============================================================================
    Section 0     : Processor Generic
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800a32a0a8
    Section       @ fffffa800a32a180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Cache error
    Operation     : Generic
    Flags         : 0x00
    Level         : 0
    CPU Version   : 0x00000000000306c3
    Processor ID  : 0x0000000000000004
    
    ===============================================================================
    Section 1     : x86/x64 Processor Specific
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800a32a0f0
    Section       @ fffffa800a32a240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    
    Local APIC Id : 0x0000000000000004
    CPU Id        : c3 06 03 00 00 08 10 04 - bf fb fa 7f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    
    Proc. Info 0  @ fffffa800a32a240
    
    ===============================================================================
    Section 2     : x86/x64 MCA
    -------------------------------------------------------------------------------
    Descriptor    @ fffffa800a32a138
    Section       @ fffffa800a32a2c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    
    Error         : DCACHEL0_WR_ERR (Proc 2 Bank 1)
      Status      : 0xbf80000000000124
      Address     : 0x000000021a01db80
      Misc.       : 0x0000000000000086



    STOP 0x124 Troubleshooting

    Read carefully before proceeding.



       Warning
    If you're overclocking your system, revert back to stock clocks now.

       Note
    Test the system once the overclock is removed before continuing with the steps outlined below.


    Part One: CPU Stress Test
    Part Two: MemTest86+ RAM Diagnostic
    Part Three: Hard Drive Diagnostics
    Part Four: GPU Stress Test




    ONE

     CPU TEST


    Run Prime95 to stress test your CPU. Hardware - Stress Test With Prime95

       Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.





    TWO

     RAM TEST


    Run MemTest86+ to analyse your RAM. RAM - Test with Memtest86+

       Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.





    THREE

     HDD TEST


    Run SeaTools to check the integrity of your HDD. SeaTools for DOS and Windows - How to Use

       Note
    Do not run SeaTools on an SSD as the results will be invalid.


    Run chkdsk Disk Check




    FOUR

     GPU TEST


    Run Furmark to stress test your GPU. Video Card - Stress Test with Furmark

       Note
    Run Furmark for around 30 minutes.
       Warning
    Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if overheating occurs.
      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 20:56.
Find Us