Question New PC build keeps crashing ?

[JacksonNewcrest]

Hi there,

I need your help. I built a new PC for the first time in 20 years and it keeps crashing, particularly during games. I have 2 recent minidumps that I am hoping someone can read to help me get to the bottom of my issues:

https://1drv.ms/f/s!AkUIIMPfeS8YgUsLRNbg_MqiShJ5

Symptoms: The screen cuts to black, my display says it lost signal, I can hear audio for a few seconds more, then the computer hangs. Sometimes it will BSOD, sometimes it won't and will restart itself, and sometimes I need to hard restart it.

System information:

• CPU: AMD Ryzen 7 7800X3D (stock, no overclocking)
• MB: ASRock B650E Taichi Lite on BIOS 2.08
• GPU: Nvidia RTX 4090 Founders Edition
• Memory: G.Skill Trident Z5 Neo 64GB (2x32GB) DDR5-6000 CL30. Stock, no EXPO enabled
• Storage: Crucial T700 TV M.2 PCIe 5.0 x 4 2TB drive (Windows 11 Pro installed on this drive)
• Storage: WD Black SN850X 4TB
• PSU: SeaSonic Vertex FX-1200 W 80+ Gold
• Display: Alienware AW3225QF

What I've tried:

• Clean install of Windows 11 Pro via Reset this PC, the installing minimal drivers
• Rolling back RTX 4090 drivers to a stable version (per reddit): 31.0.15.3758 from 10/4/23 using DDU
• Reseating GPU in Mobo and changing power cords from the single 600w 12VHPWR cord to the 3 separate PCI power cords to PSU
• Running Memtest86 via bootable USB to rule out any ram issues (came back with zero errors)
• Clean uninstalling and reinstalling AMD drivers from both AMD's site and ASRock's site
• CrystalDisk tests to validate both HDs are ok
• Loading GPU-Z and CPU-Z to see if any warnings signs arise while gaming before a crash (nothing I can tell)
• Rolling back windows updates

Error examples: I've been dealing with this on and off since the build was completed a couple weeks ago, and I've dealt with a number of different errors, some related to amd3dvcacheSvc, NvidiaOpen GL driver errors (DrvSetContext failed functionality indeterminant

(pid=4176 cncmd.exe 64bit)), and I still get several DistributedCOM and LSA system errors.

Error from amd3dvcacheSvc
The description for Event ID 1 from source amd3dvcacheSvc cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
amd3dvcacheSvc
CreateHelperUserProcess - WTSQueryUserToken Failed failed with 1008
The message resource is present but the message was not found in the message table

DistributedCOM Warning
Note: CLSID applies to Windows.SecurityCenter.WscDataProtection, Windows.SecurityCenter.SecurityAppBroker, Windows.SecurityCenter.WscBrokerManager, Windows.SecurityCenter.WscCloudBackupProvider

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscBrokerManager
and APPID
Unavailable
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

DistributedCOM Warning 2
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Bugcheck
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000133 (0x0000000000000001, 0x0000000000001e00, 0xfffff8022771c340, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 18767be2-2116-4687-8716-68fd2bb8312d.

LSA Error
LSA package is not signed as expected. This can cause unexpected behavior with Credential Guard.
PackageName: schannel

(this also happens with PackageName: sfapm, msv1_0, wdigest, cloudap, pku2u, tspkg, kerberos, negoexts

Critical Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Error from nvlddmkm
The description for Event ID 0 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\Video3
UCodeReset TDR occurred on GPUID:100
The message resource is present but the message was not found in the message table

My theory is that there is a graphic driver conflict that is causing the system to fail. My fear is that two or more of the components are not playing nicely together or need to be RMA'd. I'm hoping someone out there can help and restore confidence in my attempt to get back into PC gaming.

Thank you in advance!

 

[Roland Of Gilead]

Hey there,

Have you updated the bios? What's your current one?

 

[JacksonNewcrest]

I am currently on Bios 2.08, which was the newest at the time of my build. On the 3/21/24 ASRock posted 2.10 (Description: Update AGESA to ComboAM5 1.1.0.3) which I haven't updated to yet but absolutely can.

Over in the Microsoft support forums someone just replied:

According to our analysis of the dmp file you submitted, the reason for your blue screen is nvlddmkm, which is the NVIDIA graphics card driver, indicating that the problem may be related to issues such as incompatible graphics card drivers or errors.

recommended to roll back an NVIDIA driver (which I've tried but will happily try again), and trying to Repair System via the following command lines:

DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /RestoreHealth
SFC /Scannow

Then, if that doesn't work they recommended using the media creation tool for the repair.

 

[Roland Of Gilead]

I am currently on Bios 2.08, which was the newest at the time of my build. On the 3/21/24 ASRock posted 2.10 (Description: Update AGESA to ComboAM5 1.1.0.3) which I haven't updated to yet but absolutely can.

Over in the Microsoft support forums someone just replied:

According to our analysis of the dmp file you submitted, the reason for your blue screen is nvlddmkm, which is the NVIDIA graphics card driver, indicating that the problem may be related to issues such as incompatible graphics card drivers or errors.

recommended to roll back an NVIDIA driver (which I've tried but will happily try again), and trying to Repair System via the following command lines:

DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /RestoreHealth
SFC /Scannow

Then, if that doesn't work they recommended using the media creation tool for the repair.

The problem could very well lie there. Update the bios, and then clear CMOS. Once done, default the bios, and then go onto Windows. See if the problem persists.

Often bios updates bring fixes for bugs, mem compatibility, security updates and more.

 

[JacksonNewcrest]

Thank you for your quick replies! I've updated the BIOS and cleared the CMOS, but unfortunately am still getting hard crashes. I've been trying to stress the GPU using 3DMark and sure enough it led to the same type of cash – video signal shots off, computer hangs, and then either stalls out and I need to hard reboot or it restarts itself. Still throwing these amd3dvcacheSvc errors in Event Viewer. I also tried all the command line prompts from the MS forum but that didn't help anything. As a next step I was going to reseat all the HW components and power cables in the hope that helps, and then from there do (another) clean install of Windows 11.

Any other advice before I go down RMA territory? Any theories if it's just a bad 4090 GPU, CPU, Motherboard, etc?

 

[bajadera]

W

I am currently on Bios 2.08, which was the newest at the time of my build. On the 3/21/24 ASRock posted 2.10 (Description: Update AGESA to ComboAM5 1.1.0.3) which I haven't updated to yet but absolutely can.

Over in the Microsoft support forums someone just replied:

According to our analysis of the dmp file you submitted, the reason for your blue screen is nvlddmkm, which is the NVIDIA graphics card driver, indicating that the problem may be related to issues such as incompatible graphics card drivers or errors.

recommended to roll back an NVIDIA driver (which I've tried but will happily try again), and trying to Repair System via the following command lines:

DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /RestoreHealth
SFC /Scannow

Then, if that doesn't work they recommended using the media creation tool for the repair.

We have the same Memory: G.Skill Trident Z5 Neo 64GB (2x32GB) DDR5-6000 CL30
I also have the same error after I ran stability/stress tests in prime95.

 

[JacksonNewcrest]

I am almost certain my issue was a bad 4090. I've been dealing with Nvidia to run tests and whatnot and it got to the point my rig wouldn't even post to BIOS or boot into windows unless the card was removed.

I even went out and bought another GPU (with the intent to return) to see if that was the issue and I've had ZERO issues with installed. RMA'ing the 4090 with the hopes that fixes it.

I ran memtest on the RAM and it came back with zero errors. Not ruling our your issue isn't RAM, but for me it looks like it's just a bad GPU.

 

[bajadera]

I am almost certain my issue was a bad 4090. I've been dealing with Nvidia to run tests and whatnot and it got to the point my rig wouldn't even post to BIOS or boot into windows unless the card was removed.

I even went out and bought another GPU (with the intent to return) to see if that was the issue and I've had ZERO issues with installed. RMA'ing the 4090 with the hopes that fixes it.

I ran memtest on the RAM and it came back with zero errors. Not ruling our your issue isn't RAM, but for me it looks like it's just a bad GPU.

I have a rx6800xt.
Thats why I suspected ram as they are identical .
Many cpu related errors are caused by ram but the majority of people blame the cpu.

I was doing stability /stress tests when the error occurred.

 

[JacksonNewcrest]

Updating this thread to provide a conclusion to the story. I RMA'd the 4090, it was replaced with a brand new one from Nvidia, I installed it with zero issues, updated to the latest drivers, and have had zero issues.

As many others have documented and recommended... if you know your components are compatible and something just seems off, it probably is and RMA the component.

I was able to get another, lower-end GPU to test in my system (that I will now need to return) to rule out anything else was going on. That GPU installed easily and everything ran perfectly so I was able to confirm my suspicion it was a 4090 GPU hardware issue, not something else.

Good luck all, and RMA those faulty components when you need to!

 

[Roland Of Gilead]

Excellent. Result! Happy gaming