Black screen with sound followed by manual restart with no dump

setup:
i9 9900k
Gigabyte 3080 VISION OC
PSU: corsair hxi 750w
32gb ram 3200mhz
ROG STRIX Z390-F GAMING
winver: Screenshot - 491dd1e44c317af8df42c56cd27c8801 - Gyazo

For the past few weeks I've been having random black screen freezes, where the sound goes on for a few more second followed by a complete freeze.
Dumps are enabled: Screenshot - ca3572433f4d644f8a0e992c30580e3d - Gyazo
Using NotMyFault (https://docs.microsoft.com/en-us/sys...ads/notmyfault) dump are working fine.
Mini dump from "self triggered" bsod:
Screenshot - 553b0c897876cf894f20970c78354182 - Gyazo

However when this happens I have the following event in event viewer.
Screenshot - 412f23396186fbb745305a78276c17ab - Gyazo
- System
- Provider
[ Name] volmgr
- EventID 161
[ Qualifiers] 49156
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2020-12-04T14:32:12.4597853Z
EventRecordID 12825
Correlation
- Execution
[ ProcessID] 4
[ ThreadID] 572
Channel System
Computer DESKTOP-FP5PJN6
Security
- EventData
\Device\HarddiskVolume7
000000000100000000000000A10004C081000200010000C000000000000000000000000000000000


It seem to happen at random times.
I reinstalled my graphics driver using DDU via Safe mode.

As a side note, I have the 3080 for around one month now, and this only started happening for the past week-ish.
Hah 6 of these events in the past 7 days, two of them happened more or less back to back.

To troubleshoot, I left a game on the main screen overnight a few time, GPU underload, CPU underload and it went for 10+ hours straight with no problems.

SSD Health status is good in CrystalDiskInfo(97% for windows partition)

Is there anything else I can check to point me in the right direction ?
Could it be the PSU ?


later edit: temperatures are well within limits for both CPU and GPU
later later edit: no OC on either CPU or GPU
later later later edit:
1. sfc /scannow
2. DISM /Online /Cleanup-Image /RestoreHealth
ran both, no issues

Attachment 309186

- - - Updated - - -

The mini dump from the .zip is not related to the crashes I've been having, that's a self triggered bsod to check if dumps are being generated

- - - Updated - - -

aida64 extreme has been running with all stress tests enabled for the past 2 hours(and still going)
GPU power draw at 100% load was constant at ~306w
CPU max power draw was 148 then "regulated" to 95W throughout the test
GPU core temp was around 64-66 degrees
CPU temps were ~65 degrees

Screenshot - 644776f52f63add2b5ff7fe38c20117f - Gyazo

- - - Updated - - -

A bit over 3 hours now, on aida64. Manually stopped the test.
Will play the game for a bit then run aida64 again overnight

- - - Updated - - -

another useful thing I might have left out, my pc more or less run 24/7, with a manual restart in the morning and a manual restart about 6PM GMT.
During the day I use it as a workstation with BDO(Black desert online) in the background(either minimized in the tray running at 3fps, or in the background if I watch the market) and overnight my character does "afk" stuff usually minimized ,however in my last few overnight tests I left it in the foreground with no black screen issue( but it did black screen during the day)

No real dumps in the zip file then, bummer. WER data from msinfo32 shows only the dump you forced.

Looks like you had 7 BSODs.

Attachment 309199

This is the System Event log info around it:

Attachment 309200

Without dumps it's hard to know what the cause is.

I recommend enabling Driver Verifier to see if that shakes out a bad driver.

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

One other thing, check the PSU voltages in UEFI setup then using HWMONITOR.

Ztruker said:

No real dumps in the zip file then, bummer. WER data from msinfo32 shows only the dump you forced.

Looks like you had 7 BSODs.

Attachment 309199

This is the System Event log info around it:

Attachment 309200

Without dumps it's hard to know what the cause is.

I recommend enabling Driver Verifier to see if that shakes out a bad driver.

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

One other thing, check the PSU voltages in UEFI setup then using HWMONITOR.

Thanks alot, will have a look at driver verifier the next few days(I'll be out for the weekend).

Voltages in HW Monitor throughout the Aida64 test seemed fine.
Screenshot - c7de7cbfcf84936568417cfb62257c59 - Gyazo

edit: just a small question, the link you provided wrt. driver verifier mentions different setting to be used. Which one should I follow ?
https://www.tenforums.com/attachment...d-settings.jpg
or
the other one

edit2: how can I add more drivers to be verified ? do I need to stop the verifier and restart the whole process ,or can I simply open the verifier app(which should already be running) select more driver, reboot etc. I guess what I'm asking is if I need to stop driver verifier every time, in between adding more drivers to be checked.

- - - Updated - - -

Ztruker said:

No real dumps in the zip file then, bummer. WER data from msinfo32 shows only the dump you forced.

Looks like you had 7 BSODs.

Attachment 309199

This is the System Event log info around it:

Attachment 309200

Without dumps it's hard to know what the cause is.

I recommend enabling Driver Verifier to see if that shakes out a bad driver.

Driver Verifier-- tracking down a mis-behaving driver.

Following the instructions in the above link will check for problems in all non-Microsoft drivers.

What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

To check if verifier is active, open a Command Prompt and enter:

verifier /query

If not active it will respond with

No drivers are currently verified.

Follow instructions here to decide which drivers you want to test. 3-5 is a good start. Add 3-5 more every two hours until all are selected or you get a BSOD.

Enable and Disable Driver Verifier in Windows 10

Familiarize yourself with how to get out of Driver verifier from the above link and from the first link.

One other thing, check the PSU voltages in UEFI setup then using HWMONITOR.

quoting to make sure you'll see me previous post edits + to add the below:

Screenshot - dda30b068815c3f2b57d4cf0deb3770f - Gyazo
Screenshot - 875fca0e575baeadc335da7b2d7fc42d - Gyazo

These are the only non Microsoft drivers I have installed.
Any particular ones I should start with ?

I would uninstall Bit Defender completely and run with Windows Defender for now. Use the Bit Defender removal tool.


Next check the Intel drivers and test for a couple hours and if okay then add the Logitech drivers then run for up to 48 hours or until you get a BSOD. If you do get one, reset Verifier then run V2 and upload the zip. Make sure you understand how to get rid of Verifier before you use it. Both of the links I post have info on how to do that.

Also, if there is a C:\Windows\MEMORY.DMP file, zip it and upload that to a file sharing site and post a link to it here.

The dmp shows a video problem occurred:

Code:

VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffff8c84e76bb050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8022c062298, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 000000000000056c, Optional internal context dependent data.

Do you still have the old video card? If yes can you remove the 3080 and install the old card and test. Since you've already installed the latest Nvidia driver using DDU this is looking more like a hardware problem, unless you are doing some over clocking. Are you?