BSOD While Playing Dota 2 - Happens Back to Back


  1. Posts : 1
    Windows 10
       #1

    BSOD While Playing Dota 2 - Happens Back to Back


    Long time lurker and finally got fed up. Thanks in advance for the help.

    I get the BSOD error only when I play Dota 2. Sometimes I can go hours without it. But lately, it's been happening more frequently. Sometimes it happens back to back where after I restart my computer, 2 mins into the game, it crashes.

    I attached my log for reference.
      My Computer


  2. Posts : 41,472
    windows 10 professional version 1607 build 14393.969 64 bit
       #2

    Within the log files there were no mini dump files for debugging.
    There was information that prior bugchecks were WHEA 0 x 124 and 9C.
    Both of these bugchecks typically occur when there is a hardware problem.

    For all tests /steps please post images into the thread.
    If there are any problems posting images please use one drive or drop box share links.
    Share OneDrive files and folders - Office Support
    Upload photos and files to OneDrive - OneDrive
    Share OneDrive files and folders - Office Support
    Upload photos and files to OneDrive - OneDrive


    1) Open administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /restorehealth
    4) chkdsk /scan
    5) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    6) Make sure that there is no over clocking while troubleshooting.

    7) Sometimes there are problems in the bios that produce bsod.
    The BIOS: BIOS Version/Date American Megatrends Inc. 1502, 3/2/2011
    8) Please check to see if this is the most up to date version.
    9) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

    10) To ensure that there are no improper bios settings please reset the bios.
    11) Sometimes there can be failure to boot after resetting the bios.
    12) Backup the computer files to another drive or to the cloud.
    13) Make a backup image usig Macrium:
    Macrium Software | Macrium Reflect Free:
    Macrium Software | Macrium Reflect Free

    14) And please create a brand new restore point.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    15) If the computer has Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread

    16) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread

    17) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings
    > on the advanced tab under startup and recovery click settings > post an image of the startup and recovery into the thread.
    > on the advanced tab under performance > click on settings > click on advanced tab > under virtual memory click on change > post an image of the virtual memory tab into the thread

    19) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
    http://www.resplendence.com/whocrashed
    20) Click analyze > look for dead or deaddead in the results > post the results into the thread
    21) Run this version of the log collector ater the above steps:
    log collector v2-beta08.zip

    22) Read these links on windows driver verifier:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
    Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials
    23) Do not use windows driver verifier until it is communicated in the thread.

    Code:
    1/20/2018 1:19 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 124
    P2: 0
    P3: ffffe58dd9d58028
    P4: be000000
    P5: 800400
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\012018-4343-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-6750-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3827.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3846.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3856.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_124_93281c7f12fd94b2bd2447f7c1e75f8c12e32_00000000_cab_1d0c3b72
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: eeb56746-9e13-422b-86d7-4a9e858cd411
    Report Status: 2049
    Hashed bucket:1/20/2018 1:19 PM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 124
    P2: 0
    P3: ffffe58dd9d58028
    P4: be000000
    P5: 800400
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\012018-4343-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-6750-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3827.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3846.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3856.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_124_93281c7f12fd94b2bd2447f7c1e75f8c12e32_00000000_02b43855
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: eeb56746-9e13-422b-86d7-4a9e858cd411
    Report Status: 4
    Hashed bucket:
    12/31/2017 2:18 AM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffffa700681ec760
    P4: 0
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\123017-4296-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-6546-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3316.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3335.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3346.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_9c_d98a9de9d125b7b4cc87afac067534e8fd9b4_00000000_cab_19c83e51
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e2290117-3647-44d5-8970-bc2166857cb5
    Report Status: 2049
    Hashed bucket:
    12/31/2017 2:18 AM    Windows Error Reporting    Fault bucket , type 0
    Event Name: BlueScreen
    Response: Not available
    Cab Id: 0
    
    Problem signature:
    P1: 9c
    P2: 0
    P3: ffffa700681ec760
    P4: 0
    P5: 0
    P6: 10_0_16299
    P7: 0_0
    P8: 768_1
    P9: 
    P10: 
    
    Attached files:
    \\?\C:\WINDOWS\Minidump\123017-4296-01.dmp
    \\?\C:\WINDOWS\TEMP\WER-6546-0.sysdata.xml
    \\?\C:\WINDOWS\MEMORY.DMP
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3316.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3335.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3346.tmp.txt
    
    These files may be available here:
    C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_9c_d98a9de9d125b7b4cc87afac067534e8fd9b4_00000000_02ac3345
    
    Analysis symbol: 
    Rechecking for solution: 0
    Report Id: e2290117-3647-44d5-8970-bc2166857cb5
    Report Status: 4
    Hashed bucket:
    Code:
    Event[3179]:  Log Name: System
      Source: Volsnap
      Date: 2018-01-17T00:40:51.784
      Event ID: 33
      Task: N/A
      Level: Information
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: DESKTOP-653BU1N
      Description: 
    The oldest shadow copy of volume C: was deleted to keep disk space usage for shadow copies of volume C: below the user defined limit.
      My Computer


 

  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 05:41.
Find Us




Windows 10 Forums