Sometimes BSOD on game crashes, sometimes not.

bp32795

Member
Joined
Aug 14, 2023
Posts
5
I built my PC in March 23, stats are in the DxDiag attached. Around July 23 I started experiencing issues with some games crashing. Sometimes it would BSOD, sometimes just crash with a different error, but not BSOD. I ended up shipping away my GPU because a recurring error was with RDR2 and 'video_engine_timeout_detected'. The manufacturer did nothing aside from label it as physical damage, which you can see here. I decided not to replace it and got it back. I took the whole system to a local store to run diagnostics and they uncovered a bad ram stick. I confirmed and RMA'd that.In the meantime I am just using one 16gb stick to game and use my machine. Overall, most games do not crash now. However, RDR2 still does, so I suspect something is still off somewhere, and I am trying to figure out where. I ran UserBenchmark which gave me these results and do not indicate anything wrong. I am currently running OCCT to stress test my system, but nothing is obvious yet.

Attached are the files required. I have been stressing trying to figure this out, so any help is appreciated. Please let me know what advice or questions you have.
 

Attachments

Hello, and welcome!

There certainly looks to be a hardware issue on there still, there are many of these errors in your System log...
Code:
Event[50]
  Log Name: System
  Source: Microsoft-Windows-WHEA-Logger
  Date: 2023-08-14T19:42:50.8640000Z
  Event ID: 18
  Task: N/A
  Level: Error
  Opcode: Info

  Keyword: N/A
  User: S-1-5-19
  User Name: NT AUTHORITY\LOCAL SERVICE
  Computer: Umbreon
  Description:
A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Unknown Error
Processor APIC ID: 0

The details view of this entry contains further information.
The 'reported by processor core' doesn't automatically mean that you have a CPU issue, the key words there are 'reported by'. The dumps also strongly indicate a hardware issue too, and I think it's most likely to be RAM related. I say that because two of your dumps fail when manipulating PTEs (page table entries), one is for a stack pointer error, and one is for a file system cache manager failure. The common denominator there is RAM.

There is an outlier in one of the dumps however. This one points to the wireguard.sys driver as being at fault. Is that part of the WireGuard VPN, or some other networking product? The version of this driver is old, dating from 2021...
Code:
3: kd> lmvm wireguard
Browse full module list
start             end                 module name
fffff806`a2ee0000 fffff806`a2f7a000   wireguard T (no symbols)         
    Loaded symbol image file: wireguard.sys
    Image path: \SystemRoot\System32\drivers\wireguard.sys
    Image name: wireguard.sys
    Browse all global symbols  functions  data
    Timestamp:        Tue Oct 12 19:09:12 2021 (6165B328)
    CheckSum:         0007DA65
    ImageSize:        0009A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
For testing purposes, and since you do seem to have a hardware issue, it might be wise to disable or uninstall this product. We can return to this potential problem once we've fixed the hardware problem you seem to have.

To test your RAM I'd suggest you download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough), and then boot that USB drive. Memtest86 will start running as soon as it boots, if no errors are reported after the four iterations of the 13 different tests that the free version does, please restart Memtest86 and do another four iterations.

Let's see how that goes before we look elsewhere.
 
Thanks for both tips! The wireguard I imagine is part of NordVPN, as that is the only thing I can think of that would be using it. Also, I just moved, so I do not have a flash drive handy to check, but I will get one and report back with results.
 
Updated the BIOS, Memtest passed as well. Ran the collector again and is attached. So far, so good. I'm wondering if it was the mobo update, but I will let you know if anything crashes again. Thanks so much for the help!
 

Attachments

There's no need for running the collector again until a new crash occurs.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top