My monitor keeps shutting off and won't detect my computer until I do a restart

[Church]

I don't know why but my computer monitor keeps turning off in the middle of my games and won't reconnect to my computer until I restart my computer. I have no idea what could be causing the issue everything is brand new I just bought it and put it together less than a month ago and everything was working completely fine up until now, it's a brand new RTX 3060 on a NEXT motherboard With a 12 core AMD 5900. At first I thought maybe my GPU overheated but after watching it's thermals beforehand Its temperature isn't the problem because it never goes over 70ﾟ ,I turned off my G force auto tune but that didn't help it all either. I'm at a loss of what could be the problem Because I know it's not the CPU or mobo because my computer is still running even after my display turns off because when I'm in a discord call with my friends I can still hear and talk to them. The only thing I could think of Is maybe a power supply issue but my computer should be getting more than enough power because I have a Thermaltake Smart 600 W 80+ Certified ATX Power Supply with only a 400 W estimated power usage. My full build is this https://pcpartpicker.com/list/3TKsTn
Any input would be amazing, I got a few ideas left like switching the port for my GPU or updating my mobo and monitors bios but besides that I am completely stumped and don't have enough money to replace any of the parts, everything except the mobo has a warranty too.

 

[Lei]

@Church
Are you using dev channel insider builds of windows?
My monitor wasn't turning on after I come from sleep. It was a Windows bug and got fixed in later updates.

Did you fully uninstall GPU drivers before adding 3060?
May be you should DDU in safe mode and then try reinstalling GPU drivers from scratch.

Also you can underclock your gpu/cpu to see if less power usage will fix your problem.
In Nvidia control panel you can limit the cuda cores. In BIOS you can turn off some of your cpu cores.
You can cap the fps to 30 and see if you still get your monitor turned off while gaming....

 

[nomdeplume]

I don't know why but my computer monitor keeps turning off in the middle of my games and won't reconnect to my computer until I restart my computer.

No monitor listed. Dig DEEP into the monitor OSD for an ECO setting at fault.
Also go ahead and update the snot out of everything.
I'd then try reversing your display cable if there is still an issue.
This is almost certainly a power saver setting on the monitor. Or a cable that isn't a good match.

 

[Church]

Hey i just wanted to let everyone know I found out what was wrong, also my monitor is a Asus 1080p 144hrz monitor idk the exact model but I could find out if I needed. Anyhow basically I had used the Nividia Geforce auto tune after I first got my pc and for some reason I think that's what was causing it, I will also mention in case anyone else has this problem but it didn't fix my pc until I opened my computers Bios page and looked through my over-clocking settings, I didn't change anything in there when I fixed it but that was the last thing I did before that bug stopped happening. But anyhow thanks to anyone who responded lol

 

[nomdeplume]

Hey i just wanted to let everyone know I found out what was wrong, also my monitor is a Asus 1080p 144hrz monitor idk the exact model but I could find out if I needed. Anyhow basically I had used the Nividia Geforce auto tune after I first got my pc and for some reason I think that's what was causing it, I will also mention in case anyone else has this problem but it didn't fix my pc until I opened my computers Bios page and looked through my over-clocking settings, I didn't change anything in there when I fixed it but that was the last thing I did before that bug stopped happening. But anyhow thanks to anyone who responded lol

Glad you figured this out. Odd simply opening BIOS without saving any changes pushed something, but great.

 

[Kodehawa]

Glad you figured this out. Odd simply opening BIOS without saving any changes pushed something, but great.

Monitors are cursed. Power-cycling mines made it... work... somehow.

 

[Church]

Hey so i need help again, the problem started happening again and I don't know why. I was tired of it keep happening so I just reset my who pc, updated my bios, installed all the AMD drivers I could think of and it still keeps happening. Any ideas on what I should try next? I want to believe it's a software issue but at this point I am leaning into a hardware problem. Is there possibly any program I can run that can record everything going on in my pc so I can see what happens when the monitor shuts off?

 

[nomdeplume]

You could start by running HWiNFO logging to catch all of your power info before, during, and after the monitor goes on the blink.

Monitor is the likely suspect if it alone shuts off. Maybe try full screening a pure white background and turn the monitor brightness way up. IF it's going into protection mode that is one way to trigger it faster than normal. Very well could be a component unrelated to pixel display though. RTFM and checking the support page for diagnosis software?

 

[Church]

I just recorded the error and got more info on what's happening, anyhow the only other think i got was that there was a solid red led on my GPU right next to the 8pin power input.

This is the google sheets logs from the HWiNFO logging

Logs.CSV

docs.google.com

Hey got some more info, I was working with a more tech savvy friend (which was hard because usually I am the one people go to for help) and we managed to get a mini dump file after disabling the TDR recovery context because he believed that was why my computer wasn't at least giving me an error file for what was happening because previously the closest thing i got to an error file was the HWiNFO64 file which really only told me that my GPU stopped working a couple moments before I restarted it. After looking through the file with WinDbg preview this is what I found
Also this isn't too important but I forgot to mention that I actually have an 800w power supply and not a 600w, same manufacture though.

Also this is just my personal thoughts but I am almost certain its my gpu or something connecting to my gpu because I tested to see how long I could run processes in the backround after the crash and I was able to GTA V and Discord at the same time and was able to talk to my friends and everything perfectly fine and my monitor even connected to my old macbook when I plugged it in but still would not connect to my computer, I was gonna try and plug it into my motherboards HDMI but I don't have integrated graphics.

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Aedan\Desktop\040123-15265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`16c00000 PsLoadedModuleList = 0xfffff801`1782a290
Debug session time: Sat Apr 1 03:12:04.656 2023 (UTC - 4:00)
System Uptime: 0 days 1:29:23.245
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`16ffbbf0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8489`7764f950=0000000000000116
21: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe38f50cc1460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8013a0d3720, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000001, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_50916785244854f2\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3952

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9312

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x116

Key : Bugcheck.Code.Register
Value: 0x116

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: 040123-15265-01.dmp

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffe38f50cc1460

BUGCHECK_P2: fffff8013a0d3720

BUGCHECK_P3: 0

BUGCHECK_P4: 1

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

PROCESS_OBJECT: 0000000000000001

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8489`7764f948 fffff801`279c555e : 00000000`00000116 ffffe38f`50cc1460 fffff801`3a0d3720 00000000`00000000 : nt!KeBugCheckEx
ffff8489`7764f950 fffff801`279c3748 : fffff801`3a0d3720 ffffe38f`50cc1460 00000000`00000200 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8489`7764f990 fffff801`4603114a : ffffe38f`4c5c0000 00000000`00000001 ffffe38f`00000001 ffff8489`7764fa98 : dxgkrnl!TdrAllowToDebugEngineTimeout+0x1b8
ffff8489`7764f9c0 fffff801`45ffb24f : ffffe38f`4c510000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0x36
ffff8489`7764fa10 fffff801`45f69e9f : ffffe38f`4b467bb0 00000000`00053c42 00000000`00989680 00000000`00000200 : dxgmms2!VidSchiCheckHwProgress+0x330df
ffff8489`7764fa80 fffff801`45fed405 : ffffe38f`5648e000 ffffe38f`4c510000 ffffe38f`5648e010 ffffe38f`4b8b1010 : dxgmms2!VidSchiScheduleCommandToRun+0x4f
ffff8489`7764fb40 fffff801`45fed3ba : ffffe38f`4c510400 fffff801`45fed2f0 ffffe38f`4c510000 ffffd381`00700100 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffff8489`7764fb90 fffff801`16f265f5 : ffffe38f`4c461080 fffff801`00000001 ffffe38f`4c510000 000fe067`bcbbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffff8489`7764fbd0 fffff801`17004828 : ffffd381`00700180 ffffe38f`4c461080 fffff801`16f265a0 00066b76`ffffffe0 : nt!PspSystemThreadStartup+0x55
ffff8489`7764fc20 00000000`00000000 : ffff8489`77650000 ffff8489`77649000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+1073720

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
---------

if anybody needs the whole file let me know because it wouldn't let me attach it so I can just upload it to my onedrive and put a link in here after work

If anybody can help It would make my day, I can't find any other way to fix it.

 

[Kodehawa]

> anyhow the only other think i got was that there was a solid red led on my GPU right next to the 8pin power input.

PSU is not supplying enough power to it if that happens when it shuts off the monitor

 

[mäggäri]

I don't know why but my computer monitor keeps turning off in the middle of my games and won't reconnect to my computer until I restart my computer. I have no idea what could be causing the issue everything is brand new I just bought it and put it together less than a month ago and everything was working completely fine up until now, it's a brand new RTX 3060 on a NEXT motherboard With a 12 core AMD 5900. At first I thought maybe my GPU overheated but after watching it's thermals beforehand Its temperature isn't the problem because it never goes over 70ﾟ ,I turned off my G force auto tune but that didn't help it all either. I'm at a loss of what could be the problem Because I know it's not the CPU or mobo because my computer is still running even after my display turns off because when I'm in a discord call with my friends I can still hear and talk to them. The only thing I could think of Is maybe a power supply issue but my computer should be getting more than enough power because I have a Thermaltake Smart 600 W 80+ Certified ATX Power Supply with only a 400 W estimated power usage. My full build is this https://pcpartpicker.com/list/3TKsTn
Any input would be amazing, I got a few ideas left like switching the port for my GPU or updating my mobo and monitors bios but besides that I am completely stumped and don't have enough money to replace any of the parts, everything except the mobo has a warranty too.

Modern PCs use mainly 12V line, other voltages are regulated from this. Your TT Smart 600W PSU is too limited, feeds only 42A for 12V which makes 504W.

Your CPU + GPU that spikes high (not visible in HWinfo etc, but with equipment), is the cause. Peak wattage on 3060 is probably 300-350W.

For example basic Fractal Ion+/Ion2+ give 55A and rated as 660W. So this means your Thermaltake is basically 500W PSU.

edit: oh well, "the bug" seems to be sorted out. Living on the edge.

 

[Mister300]

I just recorded the error and got more info on what's happening, anyhow the only other think i got was that there was a solid red led on my GPU right next to the 8pin power input.

This is the google sheets logs from the HWiNFO logging

Logs.CSV

docs.google.com

Hey got some more info, I was working with a more tech savvy friend (which was hard because usually I am the one people go to for help) and we managed to get a mini dump file after disabling the TDR recovery context because he believed that was why my computer wasn't at least giving me an error file for what was happening because previously the closest thing i got to an error file was the HWiNFO64 file which really only told me that my GPU stopped working a couple moments before I restarted it. After looking through the file with WinDbg preview this is what I found
Also this isn't too important but I forgot to mention that I actually have an 800w power supply and not a 600w, same manufacture though.

Also this is just my personal thoughts but I am almost certain its my gpu or something connecting to my gpu because I tested to see how long I could run processes in the backround after the crash and I was able to GTA V and Discord at the same time and was able to talk to my friends and everything perfectly fine and my monitor even connected to my old macbook when I plugged it in but still would not connect to my computer, I was gonna try and plug it into my motherboards HDMI but I don't have integrated graphics.

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Aedan\Desktop\040123-15265-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff801`16c00000 PsLoadedModuleList = 0xfffff801`1782a290
Debug session time: Sat Apr 1 03:12:04.656 2023 (UTC - 4:00)
System Uptime: 0 days 1:29:23.245
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
..........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`16ffbbf0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8489`7764f950=0000000000000116
21: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe38f50cc1460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8013a0d3720, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000001, Optional internal context dependent data.

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

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_50916785244854f2\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3952

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 9312

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x116

Key : Bugcheck.Code.Register
Value: 0x116

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: 040123-15265-01.dmp

BUGCHECK_CODE: 116

BUGCHECK_P1: ffffe38f50cc1460

BUGCHECK_P2: fffff8013a0d3720

BUGCHECK_P3: 0

BUGCHECK_P4: 1

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

PROCESS_OBJECT: 0000000000000001

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8489`7764f948 fffff801`279c555e : 00000000`00000116 ffffe38f`50cc1460 fffff801`3a0d3720 00000000`00000000 : nt!KeBugCheckEx
ffff8489`7764f950 fffff801`279c3748 : fffff801`3a0d3720 ffffe38f`50cc1460 00000000`00000200 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffff8489`7764f990 fffff801`4603114a : ffffe38f`4c5c0000 00000000`00000001 ffffe38f`00000001 ffff8489`7764fa98 : dxgkrnl!TdrAllowToDebugEngineTimeout+0x1b8
ffff8489`7764f9c0 fffff801`45ffb24f : ffffe38f`4c510000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0x36
ffff8489`7764fa10 fffff801`45f69e9f : ffffe38f`4b467bb0 00000000`00053c42 00000000`00989680 00000000`00000200 : dxgmms2!VidSchiCheckHwProgress+0x330df
ffff8489`7764fa80 fffff801`45fed405 : ffffe38f`5648e000 ffffe38f`4c510000 ffffe38f`5648e010 ffffe38f`4b8b1010 : dxgmms2!VidSchiScheduleCommandToRun+0x4f
ffff8489`7764fb40 fffff801`45fed3ba : ffffe38f`4c510400 fffff801`45fed2f0 ffffe38f`4c510000 ffffd381`00700100 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffff8489`7764fb90 fffff801`16f265f5 : ffffe38f`4c461080 fffff801`00000001 ffffe38f`4c510000 000fe067`bcbbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffff8489`7764fbd0 fffff801`17004828 : ffffd381`00700180 ffffe38f`4c461080 fffff801`16f265a0 00066b76`ffffffe0 : nt!PspSystemThreadStartup+0x55
ffff8489`7764fc20 00000000`00000000 : ffff8489`77650000 ffff8489`77649000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+1073720

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
---------

if anybody needs the whole file let me know because it wouldn't let me attach it so I can just upload it to my onedrive and put a link in here after work

If anybody can help It would make my day, I can't find any other way to fix it.

What error does event viewer in Windows show you? Here is mine.

 

[Church]

What error does event viewer in Windows show you? Here is mine.

View attachment 290058

I am at work right now but I will upload it around 10:30 when I get out. Thanks for the help

Modern PCs use mainly 12V line, other voltages are regulated from this. Your TT Smart 600W PSU is too limited, feeds only 42A for 12V which makes 504W.

Your CPU + GPU that spikes high (not visible in HWinfo etc, but with equipment), is the cause. Peak wattage on 3060 is probably 300-350W.

For example basic Fractal Ion+/Ion2+ give 55A and rated as 660W. So this means your Thermaltake is basically 500W PSU.

edit: oh well, "the bug" seems to be sorted out. Living on the

> anyhow the only other think i got was that there was a solid red led on my GPU right next to the 8pin power input.

PSU is not supplying enough power to it if that happens when it shuts off the monitor

I wanted to put this out but I made a mistake on my pcu wattage, it's actually a 800w power supply, same brand I just got a higher voltage cuz a computer guy I was talking to when I built it said get more just in case. Also as far as I got in my research was something to do with my GPU's firmware with an image called nvlddmkm.sys. I made a second post towards the end that has an error log and such, when I get out of work I will try to take a recording of my pc's power draw and see if I can get a second error report from my pc after it crashes.

 

[mäggäri]

I am at work right now but I will upload it around 10:30 when I get out. Thanks for the help




I wanted to put this out but I made a mistake on my pcu wattage, it's actually a 800w power supply, same brand I just got a higher voltage cuz a computer guy I was talking to when I built it said get more just in case. Also as far as I got in my research was something to do with my GPU's firmware with an image called nvlddmkm.sys. I made a second post towards the end that has an error log and such, when I get out of work I will try to take a recording of my pc's power draw and see if I can get a second error report from my pc after it crashes.

Which model exactly? Would like to check on the specs anyway. Unable to find with google, when typing "Thermaltake Smart 800W". There's some 700W, 850W and a model called TR2 800W.

If tilting occurs, pay attention at GPU Hotspot temperature in HWInfo. Shouldn't exceed 100'C basically, since 105'C is nvidia's limit and throws fans 100% and restricts frequency anyway. With faulty contact between GPU-contact and cooler, it is possible to have 70'C GPU temp, while hotspot goes wild. On air coolers the difference should be max 15'C on air and less than 10'C with liquid coolers. On the other hand, these values can be obtained from looking on the architecture max temps, core: 93 and for hotspot that 105. Which gives us 12'C difference. Had almost 10 cards, all of those sit 11-13'C range in all cases, when thermalpaste has been applied succesfully.

Quite common failure with "naked" GPUs is to apply some ball of thermalpaste and start installing cooler back. There will be clean areas on the core and hotspot will show 105'C again, since the hotspot is any random spot on the GPU. Like on CPUs same story, not to do things 2 times, apply enough and spread completely. Having nice thoughts and beliefs regarding the way how to apply thermalpastes, can't bend laws of physics.

 

[Church]

Hey so a new update on my situation and its not as bad as I thought (I originally believed it was a hardware issue) but through a ton of research think I have found a few culprits but I am not smart enough to really understand all of it. Basically there is some form of error in the N7 B550 (my mobo) firmware that can cause incorrect ram calibration settings which can lead to a ton of problems such as computer crashes and such but a main indicator is the mobo cpu and ram LED's lighting up during startup which I discovered after watching it start up a couple times (pic included), this is the thread I was reading about it earlier

https://www.reddit.com/r/ASRock/comments/hnzo47/_/g16x2uh
I don't really understand how to do this 100% but would be awesome if u guys figured it out. I wasn't able to do this yet but do want to try if the other option doesn't fix it.

The second possible solution was something like Disabling CPB (Core performance boost) and PBO (Precision boost overdrive) which was apparently an error caused by N7 B550 bios firmware that did not work well with AMD CPU's in general. (Here is the link to that page)

Re: Ryzen 5900x: System constantly crashing/restarting WHEA-Logger ID 18 and critical error Kernel-P

Im having a similar issue, x570 aorus and 5600x. Have same errors on windows. Disable CBP and PBO and run it at default settings (3.7 ghz and xmp on). That works for me.

community.amd.com

I already did this option and am going to test it over this weekend. Also sorry for the long post gap I had a ton of tests over this week because of Easter break and couldn't handle this and studying at the same time, hopefully you guys can understand this better than I can.
Also I wanted to throw this out there for anybody wondering if it's a PCU problem, I ran furmarks at 8k resolution for 15 min at max settings because I wanted to know if it was my pcu that was acting up and my computer ran it perfectly and even stabilized at 70c. I am still going to try and contact the pcu and gpu manufacturers myself tomorrow if I have time but for now this is all I got.

Also 1st pic is my Ram calibration info on its page, to anybody who doesn't know that isn't my actual ram settings because they are all auto but that is the recommended amount (I think?)

Also I will be getting new thermal paste soon, it's in the mail

Also here is my cpu box for anybody wondering the model, also I got the name wrong i think. I must have bought a different brand or sum cuz it's not even a Thermaltake lol.

 

[mäggäri]

Oh yes and if your RTX 3060 has 2x 6pin or 2x8pin, plug in two cables coming from PSU.

 

[Church]

Oh yes and if your RTX 3060 has 2x 6pin or 2x8pin, plug in two cables coming from PSU.

My GPU is the smaller 3060 model and only has 1 8pin input.

My GPU is the smaller 3060 model and only has 1 8pin input.

 

[Anonymous2630]

Did you fix it? I have the same issue...

 

[Jxsh18]

Any solutions? Got the same issue as well