Random & infrequent BSOD

Started Driver Verifier. Now we wait...

Increase the customized tests by 5 now.

Clicked "Display information about the currently verified drivers". Clicked Change and added: Special pool, Force IRQL checking, Randomized low resources simulation, Pool tracking, Deadlock detection.
Clicked OK. When I clicked Next, the screen blanked out. No BSOD though. Waited a few minutes, then force restarted.

The new verifier settings didn't hold, so I tried the same settings again.
Clicked OK. When I clicked "Next", this time I received a message that says "The coverage pool allocation verification is only 0%. Adding more physical memory to your computer could improve your coverage." Before I could click OK on that message, I had a BSOD.
Stop code: VIDEO TDR FAILURE
What failed: nvlddmkm.sys

Booted to Safe Mode and ran verifier /reset at an administrative command prompt & rebooted.

Log files to follow when I can get them updated. I'm typing some of this on another computer to help document my progress.
Forgot to create a system restore for the first run, but created one now.

- - - Updated - - -

Here is the link to the memory dmp file. The date on the file is still 05-20-2020.
Google Drive: Sign-in

Newest v2 file attached.

There were no dump files collected.
For memory dumps only post when they are for the current BSOD.
When posting links please make them available without sign on.

Restart Windows driver verifier with 5 customized tests.
Then increase by 3 - 5 / hour.

If there are performance problems then you can uncheck some boxes that were tested well.

Sorry about the bad link. I was in a hurry & not paying attention.

Restarted Driver Verifier again with the 3 recommended ones plus these: Special pool, Force IRQL checking, Randomized low resources simulation, Pool tracking, Deadlock detection. Same as before.

Was running Audacity & AVSnap and trying to set the display to not blank after 20 minutes, when it had a BSOD. The new v2 log is attached.

There were no new dump files.

See if the computer can be upgraded: Windows 1909 > 2004
https://www.microsoft.com/en-us/soft...load/windows10



Then restart Windows driver verifier.

If I am reading the report below correctly, I should probably hold off updating to Win 10 2004. There are issues with some older Nvidia drivers. I have updated my GeForce 8400GS to the latest available - v342.01.
https://docs.microsoft.com/en-us/win...004#418msgdesc

Issue with older drivers for Nvidia display adapters (GPU)Nvidia and Microsoft have found incompatibility issues with certain versions of Nvidia display adapter drivers and Windows 10, version 2004 (the Windows 10 May 2020 Update). Windows 10 devices with affected Nvidia display driver versions might receive a stop error with a blue screen or other issues during or after installing the update to Windows 10, version 2004. The affected drivers are any version lower than 358.00.



In the meantime, I am going to try increasing the customized Verifier tests more than the 8 I did earlier, and check on it in the morning.

Thanks for your help.
Ken

Here is my latest v2 file. I had a BSOD over the weekend.
Stop code: DRIVER VERIFIER DETECTED VIOLATION

Driver Verifier CUSTOMIZED TESTS:
Special pool, Force IRQL checking, Randomized low resources simulation, Pool tracking, Deadlock Detection.

NEW customized tests since last report:
DMA checking, Security checks, Force ending I/O requests, IRP logging, Miscellaneous checks, Invariant MDL checking for stack, Invariant MDL checking for driver, Power framework delay fuzzing, Port/miniport interface checking.

Thanks again for your help.

If there are no performance problems or very slow boot increase the simultaneous customized settings by 5 up to the 19 simultaneous customized settings in this link:
https://answers.microsoft.com/en-us/...3-c48669e4c983


For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive