New PC build is experiencing frequent crashes?
New PC build is experiencing frequent crashes?
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!
I'm currently using Bios 2.08, the latest version available at the time of my build. On March 21, 2024, ASRock released an update (version 2.10, ComboAM5 1.1.0.3), which I haven't applied yet but can do. In the Microsoft support forums, someone shared that based on the dmp file you provided, the blue screen issue is linked to nvlddmkm, the NVIDIA graphics driver, suggesting potential problems with incompatible drivers or errors. It was suggested to revert an NVIDIA driver (which I attempted but am open to trying again) and to repair the system using these commands: DISM /Online /Cleanup-Image /ScanHealth, DISM /Online /Cleanup-Image /CheckHealth, DISM /Online /Cleanup-Image /RestoreHealth, followed by SFC /Scannow. If those steps fail, using the media creation tool for repair is recommended.
The issue might be in that area. Modify the bios, reset CMOS, then restart. After that, set the bios to default and proceed to Windows. Check if the problem continues.
Thank you for your updates! The BIOS was updated and the CMOS cleared, but crashes persist. Stressing the GPU with 3DMark caused similar issues like video signal drops, hangs, and restarts. The Event Viewer shows errors, and MS forum commands didn’t resolve the problem. I’m considering a hardware reset and a fresh Windows 11 install. Any other suggestions before reaching RMA? Are there any other potential causes like GPU, CPU, or motherboard issues?
I'm pretty sure the problem was with the 4090. I've been working with Nvidia to run tests and it became so bad my system wouldn't even connect to BIOS or start Windows unless the card was taken out.
I even bought another GPU (planning to bring it back) to check if that was the cause, but I didn't have any issues with the one I had installed. I'm sending it back through RMA hoping it gets fixed.
My RAM passed memtest with no errors, so it doesn't seem like the memory is the problem, but it still looks like the GPU is faulty.
Updating this thread to offer a conclusion to the story. I returned the 4090 and received a replacement from Nvidia without any problems. Following the advice of others, I checked my components and confirmed compatibility. Testing another lower-end GPU helped eliminate other possibilities, solidifying my belief it was indeed a 4090 issue. Good luck everyone, and please RMA any faulty parts when necessary!