Windows 10: Varying Game Errors and Crashes - Memory Corruption Large / DXGI_ERROR_DEVICE_HUNG / d3d...

System Information ------------------ Time of this report: 3/29/2023, 20:12:59 Operating System: Windows 10 Pro 64-bit 10.0, Build 19045 19041.vb_release.191206-1406 BIOS: 4602 type: UEFI Processor: AMD Ryzen 9 3900X 12-Core Processor 24 CPUs, ~3.8GHzMotherboard: ASUS TUF Gaming X570-Plus Wi-FiCard name: NVIDIA GeForce RTX 3080 TiMemory: 65536MB RAM Available OS Memory: 65450MB RAM Page File: 13742MB used, 117243MB available Windows Dir: C:\Windows DirectX Version: DirectX 12 DX Setup Parameters: Not found User DPI Setting: 96 DPI 100 percent System DPI Setting: 96 DPI 100 p

:)

 

Regular BSOD with varying error messages

Hi

I get Blue Screen Of Death crashes on a regular basis. When I livestream gameplay with Streamlabs OBS, I can be 85% sure to have a crash in the first about 90 minutes. However, after that first crash I can be pretty sure not to have one afterwards, even
though I play and stream for many hours.

There is no pattern in regards of which game.

Sometimes, I also have a crash when not streaming. It has happened across a variety of games, but not as often.

Here is a link to minidumps, memory file and system info.

The error codes vary. I've had:

• CRTITICAL_PROCESS_DIED
• KMODE_EXCEPTION_NOT_HANDLED
• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
• DRIVER_IRQL_NOT_LESS_OR_EQUAL
• PAGE_FAULT_IN_NONPAGES_AREA

I have

• installed Windows 10 on a completely new drive
• run RAM tests (allegedly no errors)
• checked and updated drivers (as far as I know)
• swapped graphic card (my bf had the same he didn't use anymore)
• moved games over to a completely new harddrive
• run tests on the old harddrive (allegedly no errors)
• regularly checked Windows updates

Thank you!

 

From BSOD to Windows Crash


Memory corruption is a thing that is the most coming back in the dumps, because the memory mechanism of Windows is extremely large and complicated. When memory corruption is shown the first step is to rule out the memory as best as possible. The next step is to rule out the drivers what can be done with driver verifier if none is flagged. If drivers are also not causing any problems then we (or at least myself) usually check for the hard drives. Hard drives can also cause memory corruption, as it is the non-volatile version of memory, but there are usually signs about hard drive problems when we suggest something for the hard drive. Another memory corruption is the VRAM, but when that happens there are also signs about it.

 

BSOD/crash playing games, memory error on shutdown

I recently bought and built myself a new gaming PC and have had a few issues with it. The first is that any time I shut down my computer after it was in sleep mode, it shows a memory error. The second is that with games, if I play long enough my computer either blue screens or the application crashes and I'm unable to relaunch it without restarting my computer.

With the first issue, the error message that pops up is: 'The instruction at 0x0000000000000000 referenced memory at 0x0000000000000000. The memory could not be read.' The memory addresses are sometimes random, but 0x0 is very common. I've searched online to see if anyone has solved this and it seems to be a bug in Explorer that Microsoft knows about, but is like 'meh, doesn't hurt anything...it's shutting down anyways'. My previous computer used to do the same thing as well. An interesting thing I've noticed, which I don't think has been pointed out elsewhere, is that it only seems to happen after I have had my computer in sleep mode, or the second issue I've been having happened.

With the second issue, I'm able to play games for varying amounts of time. I was able to play Shadow of War for 5 hours yesterday without the issue happening, but happened again today after 1 hour. With Shadow of War, I have noticed that it starts to get jumpy/audio is messed up just before the crash. This happens even worse with Divinity: Original Sin 2. My computer has BSOD'd 3 times now playing Divinity, each time a different stop message, and it has crashed even more often. I've also had it happen on FFXIV. With Shadow of War and FFXIV, I'm not able to relaunch the game until I restart my computer. Divinity is usually able to be restarted if it didn't BSOD, but I did have one instance where I had to reboot for it to start again.

I've already tried the Windows memory check tool, and did a sfc /scannow (but it ran way too short to have actually scanned anything, so I'm going to try it again). Any other suggestions of where to check next?