Windows 10: Games crashing back to desktop, variation of the same handful of errors in event viewer

Hello!I've been having issues with games crashing back to the desktop. Usually it only crashes to the desktop, but sometimes the PC gets a black screen, and once I saw about a 3/4 inch blue bar on the screen as the game froze, then black screen. It seems to have started ramping up, used to happen only occasionally to now anywhere from every 10 minutes to sometimes lasting 2 hours without crashing. I'll list everything I've tried below, then the event viewer error reports.Troubleshooting:Reinstalled Windows 3 times, replaced my RAM, replaced my CPU, loaded optimized defaults, ran sfc /scannow m

:)

 

Games crashing back to desktop, variation of the same handful of errors in event viewer

Hello!

I've been having issues with games crashing back to the desktop. Usually it only crashes to the desktop, but sometimes the PC gets a black screen, and once I saw about a 3/4 inch blue bar on the screen as the game froze, then black screen. It seems to have started ramping up, used to happen only occasionally to now anywhere from every 10 minutes to sometimes lasting 2 hours without crashing. I'll list everything I've tried below, then the event viewer error reports.

Troubleshooting:

Reinstalled Windows 3 times, replaced my RAM, replaced my CPU, loaded optimized defaults, ran sfc /scannow multiple times (did occasionally find and correct corrupted files) cleared the CMOS on my MOBO. I'm going to try to RMA the GPU tomorrow, but I'm starting to worry that it's worse. Could I have some sort of Kernel level malware that's coming back on an SSD or something along those lines? Because the event viewer repeatedly has this Exception Code (0xc0000005).

Specs:

Asus ROG STRIX Z790-H

i9-13900K

EVGA FTW3 ULTRA 3080ti

TeamGroup UD5-5600 2x16gb (temporarily tried G.SKILL Trident z5 Neo RGB 6000 2x16gb)

Asus Ryujin 1 CPU Cooler

Samsung 990 Pro NVMe PCIe M.2 1TB

CT1000BX500SSD1 1TB

Event Viewer Examples:

Faulting application name: SonsOfTheForest.exe, version: 2022.2.16.13700, time stamp: 0x6432304e

Faulting module name: UnityPlayer.dll, version: 2022.2.16.13700, time stamp: 0x6432337a

Exception code: 0xc0000005

Fault offset: 0x000000000034def7

Faulting process id: 0x0x35A8

Faulting application start time: 0x0x1DA678BA6FF4B29

Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Sons Of The Forest\SonsOfTheForest.exe

Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Sons Of The Forest\UnityPlayer.dll

Report Id: 8ce14a8a-c177-4dba-8d46-e6148f8f36a9

Faulting package full name:

Faulting package-relative application ID:

Faulting application name: dwm.exe, version: 10.0.22621.2506, time stamp: 0xdef1fe51

Faulting module name: ucrtbase.dll, version: 10.0.22621.2506, time stamp: 0x097c794c

Exception code: 0xc0000005

Fault offset: 0x0000000000051316

Faulting process id: 0x0x7C4

Faulting application start time: 0x0x1DA6785B4DB7546

Faulting application path: C:\Windows\system32\dwm.exe

Faulting module path: C:\Windows\System32\ucrtbase.dll

Report Id: 6e213e5d-c19c-4e47-b608-dc7c407203c4

Faulting package full name:

Faulting package-relative application ID:

Faulting application name: WindowsPackageManagerServer.exe, version: 1.17.2203.10001, time stamp: 0x622a8641

Faulting module name: WindowsPackageManager.dll, version: 1.17.2203.10001, time stamp: 0x622a8613

Exception code: 0xc0000005

Fault offset: 0x0000000000089bf3

Faulting process id: 0x0x1D5C

Faulting application start time: 0x0x1DA677782DB9B2F

Faulting application path: C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.17.10691.0_x64__8wekyb3d8bbwe\WindowsPackageManagerServer.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.17.10691.0_x64__8wekyb3d8bbwe\WindowsPackageManager.dll

Report Id: ac5d3d61-9518-4095-8281-ef2ea517e4a4

Faulting package full name: Microsoft.DesktopAppInstaller_1.17.10691.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: winget

Faulting application name: SonsOfTheForest.exe, version: 2022.2.16.13700, time stamp: 0x6432304e

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00007fff00000006

Faulting process id: 0x0x48AC

Faulting application start time: 0x0x1DA6777ACAA2B47

Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Sons Of The Forest\SonsOfTheForest.exe

Faulting module path: unknown

Report Id: 82468eb0-f613-4034-8535-534301d9fecf

Faulting package full name:

Faulting package-relative application ID:

 

Getting nvlddmkm error in event viewer, game crashing

Hi,

I've been getting nvlddmkm errors in event viewer every time I play the game Outlast 2 which was just released. I'm using Lenovo IdeaPad laptop, while not high specs, it can run the game at 60fps at mid-high settings with no problem so I highly doubt that it's not meeting minimum requirements. Gonna keep it point form for easy read.

Symptoms:

• Within 1-10min of gameplay, game would freeze for a few seconds then throw a "Outlast 2 has stopped working" Windows error
• Few seconds after clicking "close program" in the error, it would throw a "Rendering thread exception - fatal error"
• After closing that, it would finally throw a Microsoft Visual C++ runtime error "RUNTIME ERROR! R6025 -pure virtual function call"
• In event viewer, I get about 16 or so error events, "The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer" (screenshot)
• Also get a warning event in event viewer usually on top of error events, "Display driver nvlddmkm stopped responding and has successfully recovered"
• Only game crashes, windows not affected

Specs:

• Windows 10 64-bit with anniversary update, no creators edition
• i7-4700MQ
• 8GB RAM
• Nvidia GT750M Optimus, latest driver as of this post which is 383.22

Things already tried:

• Absolute minimum graphic settings in-game + windowed mode
• Disable hibernate/quick start in power options and restart computer
• Use DDU-safe mode to uninstall everything Nvidia related, then manually download 383.22 and reinstall it, didn't install GeForce Experience or PhysX
• Use DDU-safe mode to uninstall everything Nvidia related, then manually download 368.81 to roll back, didn't install GeForce Experience or PhysX
• Power options -> PCI Express -> maximum power settings
• Power options -> processor power management -> max processor state -> change to 99% instead of 100%
• sfc scannow in CMD (no errors)
• DISM checkhealth in CMD (no errors)
• Adding TDRDelay registry key and set it to 10
• Whitelist entire game directory in Windows Defender
• Create new windows user account and launch game from that account
• Force game to use integrated Intel HD graphics -> this would prevent any crash, but obviously be unplayable at like 5fps. So this means it's something wrong with Nvidia drivers, and not my computer?

I even chatted with service rep from Nvidia, they're out of ideas too and told me "check with Lenovo", lol.

Does anyone have any other ideas?

 

Error in Event Viewer

Hi,



Thank you for writing to Microsoft Community Forums.



As you have mentioned, you have performed a repair installation on the computer and you see Event 508, 510 and 533 in Event Viewer.



I would like to inform that if you see any critical error in Event Viewer, please share the event logs with us to help you with the appropriate troubleshooting steps. Please follow the steps mentioned below to share the event logs:

1. Press Windows + X from the keyboard, select
   Event Viewer.
   
2. Expand Windows Logs from the left pane and select
   Applications.
   
3. Click Filter Current Log from extreme right pane. Then in the new windows check the box beside
   Error and click OK.
   
4. Now, look for a critical Error in the list and note down the message/information from the
   General Tab in the lower section.
   

Please reply with the status of the issue, we will be glad to help you further.



Regards,

Nikhar Khare

Microsoft Community - Moderator