[SOLVED] PC screen randomly goes black rx 6700 xt ( not in games )

[Kolagner]

Hello. I've built a new pc no more than 2 months ago, and now getting some issues. Occasionally, once a day/few days, everything on both my computer screens will freeze, and soon after the screen will turn black. This happeons outside of games, usually when im browsing ( i can play rdr2 for several hours, then quit, and will get a freeze 30 mins browsing youtube ). Also, I have noticed that the last time it happened, my computer audio was still playing just fine, and I could even shut down pc with the keyboard.

In reliability monitor I get LiveKernelEvent 141 and LiveKernelEvent 1a1. Google did not really help in understanding what those codes are relaying to. C/windows/minidump does not exist, so there are no dump files created when the issue happens.
Specs:
i512400f, Kingston FURY Beast DDR5 16GB 5200MHz CL40 , msi z690 pro wifi, rx6700 xt,750W Seasonic FOCUS-GX-750 80, SAMSUNG SSD 870 EVO 1TB



I'm trying to pinpoint if the issue is in the mobo/psu/gpu.

What I have done:
I have done the memory test with win mem diagnostics, the Ram seems to be fine.
I have run gpu benchmarks in furmark, 3dmark, unigine heaven benchmark. All benchmarks completed without freeze/blackscreen. This is odd, as I was sure its the gpu.
I have uninstalled and reinstalled the gpu driver several times, even updated it to the most recent one on amd website.

I cant deicide if its the mobo/psu or the gpu and I have no idea how to determine. Any help would be appreciated.

P.S
In event viewer, at the time of the black screen. I have 3 events around that time. First two are warnings that display driver amdwddmg stopped responding and has successfully recovered. And the next one was an error, The program explorer.exe version 10.0.19041.1706 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. So did the driver failure cause the windows to hang?

Edit: I checked the livekernel .dmp files. Most of them contain :

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: ffffb505e0a5b040, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80232a617a0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys

 

[Aeacus]

I have uninstalled and reinstalled the gpu driver several times, even updated it to the most recent one on amd website.

Did you use DDU or Windows Remove Programs?

I cant deicide if its the mobo/psu or the gpu and I have no idea how to determine. Any help would be appreciated.

If you can boot to OS, it is not MoBo. And if you do not experience sudden restarts or shut downs, it isn't PSU either.

I have run gpu benchmarks in furmark, 3dmark, unigine heaven benchmark. All benchmarks completed without freeze/blackscreen. This is odd, as I was sure its the gpu.

First two are warnings that display driver amdwddmg stopped responding and has successfully recovered. And the next one was an error, The program explorer.exe version 10.0.19041.1706 stopped interacting with Windows and was closed.

Just because your GPU can bench fine, doesn't mean GPU drivers are 100% working. What your errors show, is that for 2 times, GPU drivers were able to recover while for the 3rd time, it was not, resulting the loss of image signal.

You have 3 things to do/try:

1 - Uninstall current GPU drivers with DDU and install version or two of older drivers.
It is somewhat common that latest drivers may not work right, or at all. Needing to use few versions of older drivers. And once even newer set of drivers are released, you can update to those, skipping the "bad" version. <- I've done this few times with my Nvidia GPU.
2 - Test with 2nd, known to work GPU in your system. If 2nd GPU also produces same issues, then you can look towards OS issues (driver conflicts). If 2nd GPU works like a charm, then:
3 - Buy a new GPU. Since your current GPU has strange fault in it.

For the most of the times, reverting GPU drivers back helps. And if it doesn't help, the clean install of Win usually does the trick, since that removes all current software issues. But when even clean OS install doesn't help, then the issue is with hardware (GPU), and time to look towards new GPU.

 

[Kolagner]

Did you use DDU or Windows Remove Programs?
If you can boot to OS, it is not MoBo. And if you do not experience sudden restarts or shut downs, it isn't PSU either.

Just because your GPU can bench fine, doesn't mean GPU drivers are 100% working. What your errors show, is that for 2 times, GPU drivers were able to recover while for the 3rd time, it was not, resulting the loss of image signal.

You have 3 things to do/try:

1 - Uninstall current GPU drivers with DDU and install version or two of older drivers.
It is somewhat common that latest drivers may not work right, or at all. Needing to use few versions of older drivers. And once even newer set of drivers are released, you can update to those, skipping the "bad" version. <- I've done this few times with my Nvidia GPU.
2 - Test with 2nd, known to work GPU in your system. If 2nd GPU also produces same issues, then you can look towards OS issues (driver conflicts). If 2nd GPU works like a charm, then:
3 - Buy a new GPU. Since your current GPU has strange fault in it.

For the most of the times, reverting GPU drivers back helps. And if it doesn't help, the clean install of Win usually does the trick, since that removes all current software issues. But when even clean OS install doesn't help, then the issue is with hardware (GPU), and time to look towards new GPU.

I did the driver reinstall with DDU. Just now did it again, without installing adrenaline, driver only. I have also tried different driver versions. This issue happened first time on day 2 of new PC, I doubt its the OS since I have barely installed anything since ( it ran around 2 weeks without black screen ).

In regards to the mobo, can it not be a faulty pci slot? Before I rule out the psu and mobo I want to be more or less sure its the gpu so I can start looking for a temp gpu to use.
Also, can a DP or hdmi cable cause something like this?

 

[rolli59]

Can you try the GPU in a different system?

 

[Kolagner]

Can you try the GPU in a different system?

Unfortunately i dont have another setup to test the gpu. I can get my hands on an old gtx 1050 though. My only concern is whether or not testing with 1050 would be valid, since the rx 6700 xt is more powerful and uses more power ( in case its a psu/mobo issue? )

 

[rolli59]

Unfortunately i dont have another setup to test the gpu. I can get my hands on an old gtx 1050 though. My only concern is whether or not testing with 1050 would be valid, since the rx 6700 xt is more powerful and uses more power ( in case its a psu/mobo issue? )

That would be fine because if it is the slot issue would be with both cards.

 

[Aeacus]

Also, can a DP or hdmi cable cause something like this?

Unlikely, since GPU will output the signal regardless if it has monitor cables connected to it and/or if monitor is turned on or not.

Still, if you have spare cables, it doesn't hurt to try.

My only concern is whether or not testing with 1050 would be valid, since the rx 6700 xt is more powerful and uses more power ( in case its a psu/mobo issue? )

If you are concerned about power draw and want to keep it, more-or-less at the same levels with GTX 1050, then run CPU and GPU bench at the same time. E.g Cinebench + Unigine Superposition. This is so called "ultimate bench" since you'd be stressing your whole system at once, and not just CPU or GPU. And that will increase the load on PSU. Load on PSU should be around the same levels as running RX 6700 XT alone.

 

[Kolagner]

Just in case, posting here content one of the .dmp files:

VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the display engines failed to respond in timely fashion.
(This code can never be used for a real BugCheck.)
Arguments:
Arg1: ffffc98fd2aee460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff804446816f0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000fc0, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2608

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3387

Key : Analysis.Init.CPU.mSec
Value: 530

Key : Analysis.Init.Elapsed.mSec
Value: 10361

Key : Analysis.Memory.CommitPeak.Mb
Value: 93


FILE_IN_CAB: WATCHDOG-20220513-2303.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 141

BUGCHECK_P1: ffffc98fd2aee460

BUGCHECK_P2: fffff804446816f0

BUGCHECK_P3: 0

BUGCHECK_P4: fc0

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffc98fd2aee460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000fc0

PROCESS_NAME: System

STACK_TEXT:
ffff8282fd057550 fffff8043e3b0ea0 : ffffc98fd2aee460 ffff8282fd0577c0 ffffc98fd2aee460 ffffc98fd51bb730 : watchdog!WdpDbgCaptureTriageDump+0x64a
ffff8282fd057600 fffff8043e255019 : 0000000000000007 ffffc98fc938d000 ffffc98fd02e90a0 ffffc98fd0ce3000 : watchdog!WdDbgReportRecreate+0xd0
ffff8282fd057660 fffff8043f5810d9 : 0000000000000000 0000000000000000 ffffc98fd2aee460 ffffc98fd0ce3000 : dxgkrnl!TdrUpdateDbgReport+0x119
ffff8282fd0576c0 fffff8043f6211b5 : ffffc98fd0ce3000 0000000000000000 ffffc98fc938d000 ffffc98fd0ce3001 : dxgmms2!VidSchiResetEngine+0x709
ffff8282fd057870 fffff8043f5eb21f : ffffc98fc938d000 0000000000000001 0000000000000000 0000000000000000 : dxgmms2!VidSchiResetEngines+0xb1
ffff8282fd0578c0 fffff8043f5b8142 : ffff8282fd057901 0000000000427bed 0000000000989680 0000000000000001 : dxgmms2!VidSchiCheckHwProgress+0x330af
ffff8282fd057930 fffff8043f55a11a : 0000000000000000 ffffc98fc938d000 ffff8282fd057a59 ffffc98fc938d000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x372
ffff8282fd057a00 fffff8043f5dd3d5 : ffffc98fd2172a00 ffffc98fc938d000 ffffc98fd2172a20 ffffc98fcf5e5760 : dxgmms2!VidSchiScheduleCommandToRun+0x2ca
ffff8282fd057ac0 fffff8043f5dd38a : ffffc98fc938d400 fffff8043f5dd2c0 ffffc98fc938d000 ffff92814c500100 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffff8282fd057b10 fffff80423f55a15 : ffffc98fc9ee40c0 fffff80400000001 ffffc98fc938d000 000fe47fbd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffff8282fd057b50 fffff80423ffeef8 : ffff92814c500180 ffffc98fc9ee40c0 fffff80423f559c0 71ba166cc0080f80 : nt!PspSystemThreadStartup+0x55
ffff8282fd057ba0 0000000000000000 : ffff8282fd058000 ffff8282fd051000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: amdkmdag+d16f0

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: LKD_0x141_IMAGE_amdkmdag.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {48b738dd-5a92-7ff8-63d0-f075fc680fe0}

Followup: MachineOwner



There is an win32 error 0n2 (which is file not found ). Can this be related to the ssd, or is it the result of gpu/driver failure? SSD health check shows up as ok

 

[Aeacus]

There is an win32 error 0n2 (which is file not found ). Can this be related to the ssd, or is it the result of gpu/driver failure? SSD health check shows up as ok

What "SFC/ scannow" says?

If you don't know what it is, or how to run it, further reading,
link: https://support.microsoft.com/en-us...em-files-79aa86cb-ca52-166a-92a3-966e85d4094e

 

[Kolagner]

What "SFC/ scannow" says?

If you don't know what it is, or how to run it, further reading,
link: https://support.microsoft.com/en-us...em-files-79aa86cb-ca52-166a-92a3-966e85d4094e

Sfc scan now passes.
I have now installed a gtx 1050 after getting another black screen a day ago ( 5 days no black screens ).

Problem with this test, is that a 1050 has only a 6 pin psu connector, while the rx 6700 xt had a 14 pin one ( 2x6 + 2 ). I have my doubts that even if there will be no BS, it might still be related to the psu.

 

[Aeacus]

Sfc scan now passes.

Yes, it does pass, but does it find and fix/replace any missing Win files as well?

Problem with this test, is that a 1050 has only a 6 pin psu connector, while the rx 6700 xt had a 14 pin one ( 2x6 + 2 ). I have my doubts that even if there will be no BS, it might still be related to the psu.

Well, you can try with another PSU, to rule out if it really is PSU issue or not. But signs point towards GPU, and your PSU is good quality unit. Then again, there are lemons even among the best.

 

[Kolagner]

Yes, it does pass, but does it find and fix/replace any missing Win files as well?



Well, you can try with another PSU, to rule out if it really is PSU issue or not. But signs point towards GPU, and your PSU is good quality unit. Then again, there are lemons even among the best.

It did replace some corrupt ones it said, did not specify which ones.

Don't have another psu to test. Right now testing the 1050, I assume that at least if the problem is with mobo or SSD it will show up again. If there will be no issues with the 1050 in 2 weeks time, then its either psu or gpu.

What bugs me is the fact that the issue never came up during games. Always during browser/music/movie watching. And the gpu passes all tests. I'd assume a problem with gpu will manifest itself sooner than once 1-7 days. What can it be thats wrong with it? Gpu memory?

Same question to psu =/

 

[Aeacus]

It did replace some corrupt ones it said, did not specify which ones.

It does. At the end of the scan, there is path to the log file, which you can open and read for each and every file, if it was able to recover them or not.

What bugs me is the fact that the issue never came up during games. Always during browser/music/movie watching. And the gpu passes all tests. I'd assume a problem with gpu will manifest itself sooner than once 1-7 days. What can it be thats wrong with it? Gpu memory?

When i was running my GTX 1060 3GB, with Win 7, i also had instances where graphics driver suddenly stopped, followed by black screen and once graphics drivers restarted, image came back. And that too while in desktop (outside of games). Those were completely random, without any apparent cause. At some days, it was as bad as 2-3 such graphic driver restarts per day, while at other times, it took several weeks or even months without issue.

All-in-all, what eventually "fixed" those graphic driver restarts (meaning that graphic drivers didn't had that issue anymore), was when i upgraded my OS from Win7 to Win10.
Nowadays, i'm running GTX 1660 Ti, while my GTX 1060 3GB is retired (it sits in it's retail box). Also, i have not had any of those graphical driver reboots anymore.

As of why graphical drivers suddenly stop and then restart again - i have no idea. Now, i know that none of the code is ever 100% solid or bug free, and i guess those reboots (with black screen), are just due to imperfect code.

 

[Kolagner]

It does. At the end of the scan, there is path to the log file, which you can open and read for each and every file, if it was able to recover them or not.



When i was running my GTX 1060 3GB, with Win 7, i also had instances where graphics driver suddenly stopped, followed by black screen and once graphics drivers restarted, image came back. And that too while in desktop (outside of games). Those were completely random, without any apparent cause. At some days, it was as bad as 2-3 such graphic driver restarts per day, while at other times, it took several weeks or even months without issue.

All-in-all, what eventually "fixed" those graphic driver restarts (meaning that graphic drivers didn't had that issue anymore), was when i upgraded my OS from Win7 to Win10.
Nowadays, i'm running GTX 1660 Ti, while my GTX 1060 3GB is retired (it sits in it's retail box). Also, i have not had any of those graphical driver reboots anymore.

As of why graphical drivers suddenly stop and then restart again - i have no idea. Now, i know that none of the code is ever 100% solid or bug free, and i guess those reboots (with black screen), are just due to imperfect code.

So, today I gave the 6700 for warranty repair. And just when I came home and started my pc ( which has the gtx 1050 atm in it ), 20 secs later I get the BS once again. Got the log from the dmp here:

Spoiler: dmp log

VIDEO_DXGKRNL_LIVEDUMP (193)
Livedumps triggered by dxgkrnl
Arguments:
Arg1: 0000000000000810, Reason Code.
100 Internal
Arg2: ffffd807da7c8000, Reserved.
Arg3: ffffd807dfacb300, Reserved.
Arg4: 00000000000001c3, Reserved.

Debugging Details:
------------------

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5859

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 13048

Key : Analysis.Init.CPU.mSec
Value: 374

Key : Analysis.Init.Elapsed.mSec
Value: 13529

Key : Analysis.Memory.CommitPeak.Mb
Value: 96

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: WATCHDOG-20220523-1319.dmp

DUMP_FILE_ATTRIBUTES: 0x10
Live Generated Dump

BUGCHECK_CODE: 193

BUGCHECK_P1: 810

BUGCHECK_P2: ffffd807da7c8000

BUGCHECK_P3: ffffd807dfacb300

BUGCHECK_P4: 1c3

PROCESS_NAME: System

STACK_TEXT:
fffff58aaf617000 fffff80423b93e1a : ffffffffffffffff fffff58aaf6170a0 0000000000000000 0000000000000000 : nt!IopLiveDumpEndMirroringCallback+0xb4
fffff58aaf617050 fffff80423ba9b43 : 0000000000000000 0000000000000000 ffffd807d9f36ba0 ffffd807d9f36ba0 : nt!MmDuplicateMemory+0x2be
fffff58aaf6170e0 fffff80423a93e4f : ffffd807d9f36ba0 ffffd807d9f36ba0 0000000000000000 0000000000000000 : nt!IopLiveDumpCaptureMemoryPages+0x9f
fffff58aaf617230 fffff804236e9d17 : 0000000000000000 ffffb00fc0edf910 0000000000000000 7fffd807d7585950 : nt!IoCaptureLiveDump+0x3e7
fffff58aaf617410 fffff80423a5e540 : ffffd80700000022 ffffffff8000211c 0000000000000000 ffffd807d75858d0 : nt!DbgkCaptureLiveKernelDump+0x2ef
fffff58aaf6174a0 fffff804236096b5 : 0000000000000025 fffff58aaf6177f0 ffffffff00000040 0000000000000000 : nt!NtSystemDebugControl+0x9f970
fffff58aaf6175b0 fffff804235fbbc0 : fffff80439bb54af ffffd807d26c8fe0 fffff80439bc213a ffffffff8000218c : nt!KiSystemServiceCopyEnd+0x25
fffff58aaf6177b8 fffff80439bb54af : ffffd807d26c8fe0 fffff80439bc213a ffffffff8000218c ffffd807d26c8d30 : nt!KiServiceLinkage
fffff58aaf6177c0 fffff80439bc0ebf : ffffd807da7c8000 fffff58aaf617aa0 ffffd807c56b14a0 fffff58aaf617aa0 : watchdog!WdpDbgCaptureKernelDump+0x73
fffff58aaf617840 fffff80439bc0d7d : ffff9c00da250100 ffff9c00da25b340 ffffd807d5874040 0000000000000000 : watchdog!WdDbgReportRecreate+0xef
fffff58aaf6178a0 fffff80439a1ff2f : 0000000000000000 0000000000000000 0000000000000000 0000000023bb2019 : watchdog!WdDbgReportCreate+0x3d
fffff58aaf617900 fffff80439a0d90e : ffffd807da7c8000 fffff58aaf617aa0 ffffd807c56b14a0 ffff9c00da250180 : dxgkrnl!DxgCreateLiveDumpWithWdLogs+0x3f
fffff58aaf617950 fffff804234bfae5 : ffffd807d5874040 fffff80423970b50 ffffd807c56b14a0 ffffd80700000000 : dxgkrnl!ProcessDeadlockThread+0x4e
fffff58aaf617ab0 fffff804234eea75 : ffffd807d5874040 0000000000000080 ffffd807c5698200 fffffa6a19044ea0 : nt!ExpWorkerThread+0x105
fffff58aaf617b50 fffff804235ff3b8 : ffff9c00da30a180 ffffd807d5874040 fffff804234eea20 fffff80423452fc3 : nt!PspSystemThreadStartup+0x55
fffff58aaf617ba0 0000000000000000 : fffff58aaf618000 fffff58aaf611000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgkrnl!DxgCreateLiveDumpWithWdLogs+3f

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.1620

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 3f

FAILURE_BUCKET_ID: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4b6fafa0-b740-8186-967a-4fb4d108708f}

So, if it happens with the 1050 as well ( different error, but its nvidia so no amd service ). I'm back to it being psu/mobo/ssd.

 

[Aeacus]

I'm back to it being psu/mobo/ssd.

In this case, i'd look towards SSD, since what you have, is software issue. Perhaps, some data blocks on SSD are corrupt.

MoBo could also be issue, albeit smaller likelihood.

And PSU is completely hardware. What PSU does, is supplying power. So, even if PSU would supply out of spec voltages, there's no way that PSU can "target" specific software on your OS drive and make that to reboot, while keeping the rest of the OS running.

---

Have you tried running in Safe Mode? To see, if the issue appears in Safe Mode as well.

 

[Kolagner]

In this case, i'd look towards SSD, since what you have, is software issue. Perhaps, some data blocks on SSD are corrupt.

MoBo could also be issue, albeit smaller likelihood.

And PSU is completely hardware. What PSU does, is supplying power. So, even if PSU would supply out of spec voltages, there's no way that PSU can "target" specific software on your OS drive and make that to reboot, while keeping the rest of the OS running.

---

Have you tried running in Safe Mode? To see, if the issue appears in Safe Mode as well.

The issue is too random to test in safe mode. It can occur 2 times a day, or once per 6 days. Also, what makes you sure its 100% software? I mean I checked the ssd several times, connections as well, seems to be in order. The pc also freezes for the duration completely ( it does seemingly recover like a minute later, but video signal never comes back ). During the initial BS nothing seems to work ( though 2 times I still had sound playing ), even the kb caps lock light wont trigger. It can be def ssd, but wouldnt there be something else as well that would indicate this? So far any errors are related to graphics driver/files.

 

[alexdmi]

The issue is too random to test in safe mode. It can occur 2 times a day, or once per 6 days. Also, what makes you sure its 100% software? I mean I checked the ssd several times, connections as well, seems to be in order. The pc also freezes for the duration completely ( it does seemingly recover like a minute later, but video signal never comes back ). During the initial BS nothing seems to work ( though 2 times I still had sound playing ), even the kb caps lock light wont trigger. It can be def ssd, but wouldnt there be something else as well that would indicate this? So far any errors are related to graphics driver/files.

The problem may be related to video memory. You need to try resetting the timings settings. To do this, you can either flash the bios. Or download MPT to put memory timing control 2. Reboot, and set it again 1. Reboot again.

 

[Kolagner]

The problem may be related to video memory. You need to try resetting the timings settings. To do this, you can either flash the bios. Or download MPT to put memory timing control 2. Reboot, and set it again 1. Reboot again.

Can you be a bit more specific? Video memory as in gpu's memory? The issue is happening on 2 different gpus.
What is MPT?

 

[alexdmi]

MPT- More power tools . The problem may arise due to the fact that some programs, for example, for mining. They can change the timings to increase the speed.

 

[Kolagner]

MPT- More power tools . The problem may arise due to the fact that some programs, for example, for mining. They can change the timings to increase the speed.

I will look into it, but change the timings of what exactly? If something was changed with the gpu shouldnt a driver reinstall fix this? If not, then why would it persist on the second gpu as well?

Edit: It seems MPT would not support the 6700 xt?

 

[Kolagner]

Also, I seem to lo longer able to open the bios. During startup I no longer see the brief msi logo and pres del to enter bios. If i keep pressing del during startup, pc screen just stays black.

 

[alexdmi]

Also, I seem to lo longer able to open the bios. During startup I no longer see the brief msi logo and pres del to enter bios. If i keep pressing del during startup, pc screen just stays black.

My friend, you need to get more information on the Internet, or contact a specialist. You need to update the vbios, not the bios of the motherboard.

 

[Kolagner]

My friend, you need to get more information on the Internet, or contact a specialist. You need to update the vbios, not the bios of the motherboard.

Thanks, I get what you mean now. I will consider it, but given the fact that the issue is happening with two different cards , and the fact that I did not OC/mine anything, I doubt its the gpu bios that is causing this.

 

[Aeacus]

Also, what makes you sure its 100% software? I mean I checked the ssd several times, connections as well, seems to be in order. The pc also freezes for the duration completely ( it does seemingly recover like a minute later, but video signal never comes back ). During the initial BS nothing seems to work ( though 2 times I still had sound playing ), even the kb caps lock light wont trigger. It can be def ssd, but wouldnt there be something else as well that would indicate this? So far any errors are related to graphics driver/files.

Since what you are experiencing are software issues, namely screen going black (loss of video signal), and with two different GPUs, something is wrong with your software. Since in my years of dealing with PC tech support (20+ years and counting), almost all such video signal losses have been caused by software issue(s).

Now, i know that you've dealt with GPU drivers with DDU, but how about display drivers? Have you touched those? Since after some Google-Fu, i found this checklist to try,
link: https://www.auslogics.com/en/articles/fix-video-driver-crashed-and-was-reset/

And addition to that, found this too:

You can quickly reset your graphics driver using the Win + Ctrl + Shift + B keyboard combination. This command makes your screen turn black for a second, but it restarts your graphics driver, which can potentially fix any issues you've been having.

 

[shasoosh]

Hey @Kolagner , did you ever figured out the culprit here?
I'm facing the same issue with a new build and a 6700XT.