RTX 3080 Crashing

Page 1 of 2 12 LastLast

  1. Posts : 6
    Windows 10
       #1

    RTX 3080 Crashing


    Hello,

    I am experiencing crashes in multiple different games. I originally thought the crashes were purely related to Call of Duty games but I have now experienced crashes in Doom Eternal, Madden 21, and Rocket Arena. Funnily enough, I never experienced a crash in Cyberpunk...

    Anyways, the most recent error I've had was in Madden 21 which stated
    DirectX function "GetDeviceRemovedReason" failed with DXGI_ERROR_DEVICE_HUNG ("The GPU will not respond to more commands"). GPU: "NVIDIA GeForce RTX 3080", Driver: 46192. This error is usually caused by the graphics driver crashing: try installing the latest driver.

    My Warzone crash code is typically 6068. I'm not sure what my other codes are in other games. However, I've experienced crashes through multiple different driver updates. I've tried doing a new install of windows. I've tried dropping the clockspeed down on the GPU. I've tried removing the XMP file of my RAM. I've tried creating a new username. I use discord while gaming and have turned off hardware acceleration.

    I just experienced a crash and here are some logs from Event Viewer. The logs are not always the same.

    Fault bucket 1971500614047190473, type 5
    Event Name: D3DDRED2
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: VEN_10DE
    P2: 27.21.14.6181
    P3: 0x887A0006
    P4: 7
    P5: ModernWarfare.exe
    P6: 1.0.0.0
    P7:
    P8:
    P9:
    P10:

    Attached files:
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB7C.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB9D.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCB9C.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCBCB.tmp.txt

    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_VEN_10DE_1abe7dd0b682ada7feebcf99 d875abe34f6cca0_00000000_18d10bbe-4cc7-492b-ad62-9c18564d97c1

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 18d10bbe-4cc7-492b-ad62-9c18564d97c1
    Report Status: 268435456
    Hashed bucket: 3eaa0d3e3076c813cb5c2d5ceebf4dc9
    Cab Guid: 0






    Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 141
    P2: ffff9801d4d0a460
    P3: fffff80454bdbb7c
    P4: 0
    P5: 52f0
    P6: 10_0_19042
    P7: 0_0
    P8: 256_1
    P9:
    P10:

    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20210404-2225.dmp
    \\?\C:\WINDOWS\TEMP\WER-192793375-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5BD.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5CE.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5CF.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5EF.tmp.txt

    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_2e1ff257671eb06c82a789c63c1179cb4488 a8_00000000_40a9ea99-c29a-4a58-ad01-e4d125fb5ece

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 40a9ea99-c29a-4a58-ad01-e4d125fb5ece
    Report Status: 4
    Hashed bucket:
    Cab Guid: 0







    Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 141
    P2: ffff9801d4d0a460
    P3: fffff80454bdbb7c
    P4: 0
    P5: 52f0
    P6: 10_0_19042
    P7: 0_0
    P8: 256_1
    P9:
    P10:

    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20210404-2225.dmp
    \\?\C:\WINDOWS\TEMP\WER-192793375-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5BD.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5CE.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5CF.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD5EF.tmp.txt

    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_2e1ff257671eb06c82a789c63c1179cb44 88a8_00000000_cab_40a9ea99-c29a-4a58-ad01-e4d125fb5ece

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 40a9ea99-c29a-4a58-ad01-e4d125fb5ece
    Report Status: 2049
    Hashed bucket:
    Cab Guid: 0






    Display driver nvlddmkm stopped responding and has successfully recovered.

    This last code ALWAYS shows in event viewer no matter the game I play (when it crashes). I've tried chatting with Nvidia and at this point, they have requested that I try putting the GPU in a different system to test it out. I don't have access to another system to test it out, unfortunately... Considering getting it tested a microcenter if needed.

    My PC parts are: 3700x, 750watt Bronze EVGA PSU, Strix 3080. Some people say if I upgrade my PSU then my problems will go away while others state they have the exact same problems as me with better PSUs.
      My Computer


  2. Posts : 737
    win10 home
       #2

    Have you tried disconnecting one monitor?
    Often the signal[s] sent to both monitors cannot be processed within the two second default delay time allocated and the Timeout Detection and Recovery [TDR] then operates and causes the freeze.
    Check Reliability History and ---dxdiag---for any entries
    Also look in ---msinfo32--->components>problem devices,then >software environment>windows error reporting.
    There may be useful information given.
    750W psu is marginal for heavy modern gaming.As with memory,more is never too much.
      My Computer


  3. Posts : 337
    Windows 10 Home 20H2 x64
       #3

    "Display driver nvlddmkm stopped responding and has successfully recovered." -> Classic GPU core instability. Are you overclocking your GPU core?
      My Computers


  4. Posts : 6
    Windows 10
    Thread Starter
       #4

    joeandmarg0 said:
    Have you tried disconnecting one monitor?
    Often the signal[s] sent to both monitors cannot be processed within the two second default delay time allocated and the Timeout Detection and Recovery [TDR] then operates and causes the freeze.
    Check Reliability History and ---dxdiag---for any entries
    Also look in ---msinfo32--->components>problem devices,then >software environment>windows error reporting.
    There may be useful information given.
    750W psu is marginal for heavy modern gaming.As with memory,more is never too much.
    Last week I was running a one monitor setup all week and still experienced the same amount of crashes.
    I just opened up Check Reliability History and I see three Windows Hardware error's at the same times as when my game crashed last night. All three of them say this when clicked on:

    Description
    A problem with your hardware caused Windows to stop working correctly.

    Problem signature
    Problem Event Name: LiveKernelEvent
    Code: 141
    Parameter 1: ffff9801d4d0a460
    Parameter 2: fffff80454bdbb7c
    Parameter 3: 0
    Parameter 4: 52f0
    OS version: 10_0_19042
    Service Pack: 0_0
    Product: 256_1
    OS Version: 10.0.19042.2.0.0.256.48
    Locale ID: 1033

    Inside msinfo32, Problem Devices that both my keyboard and mouse state "This device is not present, is not working properly, or does not have all its drivers installed." I have both Razer software and Logitech software for the keyboard and mouse respectively to keep the drivers up to date.
    Under the Windows Error Reporting tab, there are a ton of errors but none that line up with the timing of the crashes last night. Common error codes include:

    4/4/2021 10:50 PM Windows Error Reporting Fault bucket , type 0
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: etocfile.exe
    P2: 8.0.0.16
    P3: 5e4663a1
    P4: KERNELBASE.dll
    P5: 10.0.19041.804
    P6: b610d74d
    P7: e0434352
    P8: 0012a8b2
    P9:
    P10:

    Attached files:

    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_etocfile.exe_df1483aaf2a1d7ad691f8a7f5 226c4cff6b68f_35d202cc_96e91534-a69f-41ee-a8b2-127c54310a60

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: fdb89028-6647-4c9c-b74f-c4cad0afd84a
    Report Status: 6
    Hashed bucket:
    Cab Guid: 0


    4/4/2021 1:28 AM Application Error Faulting application name: etocfile.exe, version: 8.0.0.16, time stamp: 0x5e4663a1
    Faulting module name: KERNELBASE.dll, version: 10.0.19041.804, time stamp: 0xb610d74d
    Exception code: 0xe0434352
    Fault offset: 0x0012a8b2
    Faulting process id: 0x1f1c
    Faulting application start time: 0x01d728f1e3291b94
    Faulting application path: C:\Program Files (x86)\GIGABYTE\EasyTune\etocfile.exe
    Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
    Report Id: 26b8c4ff-fb39-4400-8e99-05e27c88d5ef
    Faulting package full name:
    Faulting package-relative application ID:




    4/4/2021 10:50 PM Application Error Faulting application name: LAClient.exe, version: 1.1.163.0, time stamp: 0x5af0e2de
    Faulting module name: LAClient.exe, version: 1.1.163.0, time stamp: 0x5af0e2de
    Exception code: 0xc0000005
    Fault offset: 0x0000000000004bf7
    Faulting process id: 0x2ec4
    Faulting application start time: 0x01d728f1ec3ecb35
    Faulting application path: C:\Program Files\Logitech Gaming Software\LAClient\LAClient.exe
    Faulting module path: C:\Program Files\Logitech Gaming Software\LAClient\LAClient.exe
    Report Id: e40d8542-88f0-4a24-921f-ac3520276925
    Faulting package full name:
    Faulting package-relative application ID:





    I went back a few days and found this Hardware error as well. Not sure if this occurred during a game crash but thought I'd post it anyway since it is different.






    Description
    A problem with your hardware caused Windows to stop working correctly.

    Problem signature
    Problem Event Name: LiveKernelEvent
    Code: 141
    Parameter 1: ffffd28d9fb61010
    Parameter 2: fffff8028f67eba8
    Parameter 3: 0
    Parameter 4: 3810
    OS version: 10_0_19042
    Service Pack: 0_0
    Product: 256_1
    OS Version: 10.0.19042.2.0.0.256.48
    Locale ID: 1033

    Extra information about the problem
    Bucket ID: LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Ampere_SCG3D
    Server information: 92f372be-70e4-4c65-a9d7-3e0a376a32fa






    I have 32 GB of RAM which I believe should be more than enough but I am willing to try almost anything to stop these annoying crashes!

    Thank you again so much for your help!

    - - - Updated - - -

    RJARRRPCGP said:
    "Display driver nvlddmkm stopped responding and has successfully recovered." -> Classic GPU core instability. Are you overclocking your GPU core?
    I am not overclocking my card past its factory overclocking. In fact, I've tried using GPU Tweak II (since it's an ASUS product) to lower the core clock speed and memory speed but I still get occasional crashes. I am going to try setting the card into debug mode in nvidia control panel to remove the factory overclock all together.


    I should say also that my crashes don't happen at a specific timing and I can't seem to replicate them. Sometimes I'll go a few days with no crashes and other nights I'll get 5 in one hour. I don't believe I have ever had a crash while playing a single player game but Discord is the only application I have open when playing games with friends. I have turned off both hardware accelerations in discord to try to stop discord from using my GPU as much but still get crashes.

    - - - Updated - - -

    Update: Was playing Modern Warfare with no issues when settings were on very low. I decided to try to make things more unstable by cranking up everything to max (which I should be able to do with a 3080 anyways) and debug mode was on so absolutely no overclocking. The game crashed the next round after cranking up the settings. Here are my error codes from event viewer.

    Display driver nvlddmkm stopped responding and has successfully recovered.


    Fault bucket 2023511919853889036, type 5
    Event Name: RADAR_PRE_LEAK_64
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: EADesktop.exe
    P2: 12.0.65.4872
    P3: 10.0.19042.2.0.0
    P4:
    P5:
    P6:
    P7:
    P8:
    P9:
    P10:

    Attached files:
    \\?\C:\Users\SWUNDE~1\AppData\Local\Temp\RDREE19.tmp\empty.txt
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE1A.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE3B.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE48.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREE78.tmp.txt

    These files may be available here:


    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 400651a6-7a9b-4e5a-be58-3bdfcc4e9bf9
    Report Status: 268435456
    Hashed bucket: 0c2e7a5bbf7e5a8cac14f55ebda8e60c
    Cab Guid: 0


    Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 141
    P2: ffffae0d8e66e460
    P3: fffff80626d43ee8
    P4: 0
    P5: 4eb4
    P6: 10_0_19042
    P7: 0_0
    P8: 256_1
    P9:
    P10:

    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20210405-1120.dmp
    \\?\C:\WINDOWS\TEMP\WER-1577453-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F89.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F9A.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F9B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FBB.tmp.txt

    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_193c3f4abc431b57cc82b95e2c22eeedc07c 487a_00000000_34e4230e-24df-4ff6-848d-c435673bce3f

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 34e4230e-24df-4ff6-848d-c435673bce3f
    Report Status: 4
    Hashed bucket:
    Cab Guid: 0


    Fault bucket , type 0
    Event Name: LiveKernelEvent
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: 141
    P2: ffffae0d8e66e460
    P3: fffff80626d43ee8
    P4: 0
    P5: 4eb4
    P6: 10_0_19042
    P7: 0_0
    P8: 256_1
    P9:
    P10:

    Attached files:
    \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20210405-1120.dmp
    \\?\C:\WINDOWS\TEMP\WER-1577453-0.sysdata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F89.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F9A.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F9B.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1FBB.tmp.txt

    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_193c3f4abc431b57cc82b95e2c22eeedc0 7c487a_00000000_cab_34e4230e-24df-4ff6-848d-c435673bce3f

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 34e4230e-24df-4ff6-848d-c435673bce3f
    Report Status: 2049
    Hashed bucket:
    Cab Guid: 0


    Fault bucket 1933575072569962866, type 5
    Event Name: D3DDRED2
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: VEN_10DE
    P2: 27.21.14.6589
    P3: 0x887A0006
    P4: 7
    P5: ModernWarfare.exe
    P6: 1.0.0.0
    P7:
    P8:
    P9:
    P10:

    Attached files:
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER12B8.tmp.WERInternalMetadata.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER12F7.tmp.xml
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER12F6.tmp.csv
    \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1336.tmp.txt

    These files may be available here:
    \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_VEN_10DE_fb528de60d9ab1f5751dd72b dfad2a4c5f6943_00000000_72c850c7-ac07-4517-a164-092fefe365aa

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 72c850c7-ac07-4517-a164-092fefe365aa
    Report Status: 268435456
    Hashed bucket: 35eb449b7d3d7cbc4ad57048b3153172
    Cab Guid: 0


    Successfully created restore point (Process = C:\PROGRA~1\EAGAME~1\Apex\__INST~1\directx\redist\dxsetup.exe /silent; Description = Installed DirectX).


    Scoping started for shadowcopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3.


    Scoping completed for shadowcopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3.


    Scoping successfully completed for shadowcopy \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3.


    Beginning a Windows Installer transaction: d:\6b71b3069d65265800604da0\vc_red.msi. Client Process Id: 21028.


    Product: Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219 -- Configuration completed successfully.


    Windows Installer reconfigured the product. Product Name: Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219. Product Version: 10.0.40219. Product Language: 0. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.


    Ending a Windows Installer transaction: d:\6b71b3069d65265800604da0\vc_red.msi. Client Process Id: 21028.
      My Computer


  5. Posts : 737
    win10 home
       #5

    Suggest you uninstall the Razer and Logitech driver software and allow Win 10 to install the relevant drivers and see if that is problem free.
    The use of Display Driver Uninstaller [DDU],in Safe Mode,is an effective method of clearing out the junk.
    The live kernel event is a good indication of hardware difficulties,but unfortunately doesn't fully explain.
    If driver/display adapter changes don't work then seriously consider a clean install,of course having backed up first.
      My Computer


  6. Posts : 6
    Windows 10
    Thread Starter
       #6

    joeandmarg0 said:
    Suggest you uninstall the Razer and Logitech driver software and allow Win 10 to install the relevant drivers and see if that is problem free.
    The use of Display Driver Uninstaller [DDU],in Safe Mode,is an effective method of clearing out the junk.
    The live kernel event is a good indication of hardware difficulties,but unfortunately doesn't fully explain.
    If driver/display adapter changes don't work then seriously consider a clean install,of course having backed up first.
    I have tried a clean install in the past but to no avail. I've done as you said and the "Problem "Devices" tab is now blank but crashing still occurs in game. Is it possible that this has something to do with online games specifically? That would help explain why every stress test that any person has suggested never results in a crash and even a game like Cyberpunk 2077 for a few hours doesnt crash but CoD in 720p can still crash.
      My Computer


  7. Posts : 152
    Windows 10 Pro 64-bit OEM
       #7

    If all else fails. I would do a clean install of Windows 10. If it continues after a fresh reformat. Then it probably is hardware related.
      My Computer


  8. Posts : 6
    Windows 10
    Thread Starter
       #8

    ern88 said:
    If all else fails. I would do a clean install of Windows 10. If it continues after a fresh reformat. Then it probably is hardware related.
    I've done that in the past and still got errors... But I reinstalled most applications before testing games again. I never did a clean install and then downloaded one game and gave it a shot. Have people had issues with Oculus drivers causing issues to 3000 series graphics cards? I'm really out of ideas here.
      My Computer


  9. Posts : 737
    win10 home
       #9

    What type of connection to the internet do you have,ethernet or wifi?
    Can you check the modem/router functions,which is normally a numerical address given by the maker and gives dropouts, speed etc.
    Does the pc function normally when not gaming,if so,then gaming is imposing too heavy a resource demand,shown by ---nvlddmkm---.Modern games can be resource hogs.
      My Computer


  10. Posts : 6
    Windows 10
    Thread Starter
       #10

    ISSUE APPEARS TO BE FIXED!!

    My friend suggested turning of google chrome's hardware accelerator and background processes. I gamed in Warzone (the most unstable game I noticed) for 2 hours at max settings with NO CRASHES! Of course, I will probably be posting back here next week saying that the crashes are back but this really has seemed to fixed my issue.

    PLEASE SUGGEST THIS ISSUE TO ANYONE AND EVERYONE WHO HAS THE SAME ERROR!
      My Computer


 
Page 1 of 2 12 LastLast

  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 12:29.
Find Us




Windows 10 Forums