BSOD playing CS:GO

Page 1 of 3 123 LastLast

  1. Posts : 65
    Windows 7 Home Premium x64
       #1

    BSOD playing CS:GO


    Yesterday, I was playing Counter Strike: Global Offensive as I regularly do. I was in the middle of a Matchmaking match when my computer blue screened for the first time ever, even after overclocking. I don't remember the error message, but it had hardware in it. Note, I have my RAM, GPU, and CPU all overclocked, but stable after hours of stress testing. I will be testing Memtest later tonight. What's the issue here?
      My Computer


  2. Posts : 65
    Windows 7 Home Premium x64
    Thread Starter
       #2

    bump
      My Computer


  3. Posts : 65
    Windows 7 Home Premium x64
    Thread Starter
       #3

    help?
      My Computer


  4. Posts : 65
    Windows 7 Home Premium x64
    Thread Starter
       #4

    memtest showed no errors, still wondering why it bsod'd
      My Computer


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

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9C, {0, fffff880009f6b70, 0, 0}
    
    Probably caused by : intelppm.sys ( intelppm!C1Halt+2 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    MACHINE_CHECK_EXCEPTION (9c)
    A fatal Machine Check Exception has occurred.
    KeBugCheckEx parameters;
        x86 Processors
            If the processor has ONLY MCE feature available (For example Intel
            Pentium), the parameters are:
            1 - Low  32 bits of P5_MC_TYPE MSR
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of P5_MC_ADDR MSR
            4 - Low  32 bits of P5_MC_ADDR MSR
            If the processor also has MCA feature available (For example Intel
            Pentium Pro), the parameters are:
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
        IA64 Processors
            1 - Bugcheck Type
                1 - MCA_ASSERT
                2 - MCA_GET_STATEINFO
                    SAL returned an error for SAL_GET_STATEINFO while processing MCA.
                3 - MCA_CLEAR_STATEINFO
                    SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA.
                4 - MCA_FATAL
                    FW reported a fatal MCA.
                5 - MCA_NONFATAL
                    SAL reported a recoverable MCA and we don't support currently
                    support recovery or SAL generated an MCA and then couldn't
                    produce an error record.
                0xB - INIT_ASSERT
                0xC - INIT_GET_STATEINFO
                      SAL returned an error for SAL_GET_STATEINFO while processing INIT event.
                0xD - INIT_CLEAR_STATEINFO
                      SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event.
                0xE - INIT_FATAL
                      Not used.
            2 - Address of log
            3 - Size of log
            4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO
        AMD64 Processors
            1 - Bank number
            2 - Address of MCA_EXCEPTION structure
            3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
            4 - Low  32 bits of MCi_STATUS MSR for the MCA bank that had the error
    Arguments:
    Arg1: 0000000000000000
    Arg2: fffff880009f6b70
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    
    Debugging Details:
    ------------------
    What did you use to check the stability of the overclock? Which components are overclocked?
      My Computer


  6. Posts : 65
    Windows 7 Home Premium x64
    Thread Starter
       #6

    Golden said:
    What did you use to check the stability of the overclock? Which components are overclocked?
    I used IntelBurnTest, AIDA64, OCCT, and Prime95 for my RAM/CPU.

    I manually overclocked my GPU in MSI Afterburner and stress tested it with Furmark to ensure stability.

    Every component is fine from my stress testing, CPU never goes over 65 C and GPU is only 110MHz oc'd on both Memory and Core.
      My Computer


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

    OK. Do this please:

    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
    Driver Verifier - Enable and Disable

    Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.

    I recommend creating a system restore point before turning on driver verifier:
    System Restore Point - Create

    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
    Safe Mode
      My Computer


  8. Posts : 65
    Windows 7 Home Premium x64
    Thread Starter
       #8

    Golden said:
    Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
    If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode
    Hello! I'm talking to you from the realms of Safe Mode + Networking. Windows BSOD'd the second it booted in, saying something along the lines of "Drivers need to be replaced." It's in an endless cycle of BSOD's because of verifer. However, I think we found the problem. Where do I go from here?
      My Computer


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

    In Safe Mode, turn off Driver Verfier. Now reboot back into normal mode, then do the following:

    1. Download the DM Log Collector application to your desktop by clicking the link below

    DM Log Collector.exe

    2. Run it by double-clicking the icon on your desktop, and follow the prompts.
    3. Locate the .ZIP file that is created on your desktop, and upload it here in your next reply.

      My Computer


  10. Posts : 65
    Windows 7 Home Premium x64
    Thread Starter
       #10

    Here it is.
      My Computer


 
Page 1 of 3 123 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 04:46.
Find Us