BSOD / during gaming / Windows 11 24H2 (OS Build 26100.4061) / 64-bit / incl V2Log and Minidump

I've been getting random BSOD's only very recently (past few months) under some unique conditions that I'm hoping someone can shed some light on. Attached are the v2 Logs and a Minidump file

BSOD and its circumstances:
- only happens during gaming
- always happens on the latest Windows updates and NVIDIA drivers, I always maintain the most recent updates no matter what
- nothing is overclocked, no XMP profile is used for memory, everything is at stock settings
- usually during games that are Steam Early Access (betas), indie studio games, but has happened very rarely for big studio games if it's a popularly documented crash. however, when it's just a crash out of the game to desktop for others, it's always a BSOD for me instead
- the BSOD screen doesn't remain as in all my past BSOD's, it vanishes very quickly and the system restarts, preventing a good look at the error
- doesn't always happens during high GPU usage with the fans blowing at max rpm's, but usually during some computationally heavy moments (alot of particles, movement, zooming, etc)
- CPU/GPU temps all look normal, but it could be a sudden spike i'm not seeing
- no hitches, artifacting, drop in FPS or any in-game signs foreshadowing the BSOD event, system will suddenly freeze for a second then BSOD
- it's 95% repeatable and not very random, if i follow what i was doing up to that point of the crash in-game i can cause the crash to happen again without fail
- my processor is an unpopular i9-10980XE and may have fringe cases; it's quite terrible for gaming

V2 Log: DESKTOP-(2025-05-23_17-57-14).zip
Minidump: Minidump.zip

What games are the BSODs happening in?

AugPal said:

What games are the BSODs happening in?

Click to expand...

ODDRoom - right in the first room when control is passed to the player; this just happened today
Resident Evil 4 Remake - the only triple-A title that's crashed me like this. occurs during the last act Island stage during "player observation events" where the player uses binoculars to observe the scene from afar; this hasn't happened in awhile
Path of Exile 2 - during its first week of release, in Act 3 at the Jungle Ruins where the additional foliage all around will BSOD the system; this no longer happens
... many other indie demos, betas I can't remember off the cuff right now

I definitely think less optimized code increases its occurence, because subsequent updates from the gamedevs, Windows OS, NVIDIA drivers seem to slowly resolve these on their own. However it happened today again on a recently released game, ODDRoom.

I'm only bringing it to these forums because I'm still suspecting some hardware issues on my end, since it shouldn't be happening at all. I've had this system for more than 5 years, owned many systems in the past, take good care of them, and these regular BSOD's are happening only recently, and it always exhibits the same qualities I described above. I understand Intel have been having issues with their processors recently, some by fault of their own production, some in tandem with Windows, Windows issues with NVME drives, and these BSOD's are generally feeling like the result of an overall downturn in quality coming out of tech recently. Even so, I still shouldn't be BSOD'ing so often and so regularly.

1) Please run Tuneup plus > post a share link


Batch files for use in BSOD debugging - Page 2 - Windows 10 Forums

Batch files for use in BSOD debugging - Windows 10 Forums



2) Read this link on Windows Driver Verifier (WDV):




3) Create a new restore point




4) Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail



(option number nine)



5) Plan to run the tool with various customized test settings.

a) Test all non-Microsoft drivers

b) Test no Microsoft drivers

c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial



6) Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

verifier /querysettings

Post a share link.



Customized tests will then be posted for the next run of WDV.



WDV can run continuously during the testing.



For any BSOD post a new V2 share link into the newest post.