Different BSODs during gaming (Rocket League)


  1. Posts : 2
    Windows 10 64bit
       #1

    Different BSODs during gaming (Rocket League)


    Hi everybody.

    Since I upgraded from Win7 to Windows 10 last summer, I've had really frustrating BSODs now and then. I mostly use my PC for music production but I'm also playing one single game and that's Rocket League. Since the upgrade, I've had random BSODs when playing the game. However, since 1 week ago, the frequency of the BSODs has risen dramatically. I can now, on average, play the game for 10 mins before it crashes. A couple of times I've had a BSOD randomly when just doing nothing in Windows.

    I've run memtest with no problems found. I've also run system file checker with no problems. I've cleaned the inside of the chassi from dust. My CPU temp in Windows is around 30°C and my GPU temp in Windows is around 37°C. I've not checked the temperature when in-game.

    I've included the dmp files that Windows has gathered.

    My specs are the following:

    • ASRock Z77 EXTREME6, ATX
    • i7-3770K 3,50 GHz
    • 16 Gb RAM (Corsair (4x4096MB) CL9 1600Mhz VENGEANCE LP)
    • Asus Radeon R9 280 TOP Direct CU II 3GB DDR5
    • 2TB Seagate Barracuda 7200rpm SATA 6Gbit/s
    • SSD 120GB Intel 520
    • Fractal Design Tesla 550W 80+
    • Windows 10 64bit

    I would be really grateful for any kind of help! :(

    Thank you.
      My Computer


  2. Posts : 1,656
    Windows 10 Pro x64
       #2

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 7A, {1, ffffffffc0000005, ffffc5803ca7f800, fffffd7e9ffc1000}
    
    
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    
    
    Followup:     memory_corruption
    ---------
    None of the .dmp files are giving me anything concrete to work with.

    Please run a minimum of 8 passes of MemTest86+, by following this then report back:
    MemTest86+ - Test RAM
      My Computers


  3. Posts : 2
    Windows 10 64bit
    Thread Starter
       #3

    Thanks for the reply!

    I've now run MemTest for 8 passes and no errors found (took 20 hours ).

    Golden said:
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 7A, {1, ffffffffc0000005, ffffc5803ca7f800, fffffd7e9ffc1000}
    
    
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    
    
    Followup:     memory_corruption
    ---------
    None of the .dmp files are giving me anything concrete to work with.

    Please run a minimum of 8 passes of MemTest86+, by following this then report back:
    MemTest86+ - Test RAM
      My Computer


  4. Posts : 1,656
    Windows 10 Pro x64
       #4

    OK.

    Please do the following:

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

    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.
      My Computers


 

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

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




Windows 10 Forums