Jump to content

Hello, I built a new PC just the other day and have had nothing but problems.

SPECS:
Asus TUF B650-PLUS
RTX 3080 auros waterforce
Ryzen 7 7700x 
Kingston Fury Beast DDR5 16GB DDR5 5200mhz 

So. I've figured out that when I run my PC with two ram sticks my PC bluescreens and give the typical RAM error BS codes. 
(Both sticks of ram is fine, Nothing wrong with them I have ran both sticks solo and they work just fine)

But here's the weird part. After I bluescreen, I manually boot into bios, Change some RAM settings and boot from there and it works fine. The thing is, I can't tell if it's me changing the settings each time that keeps my PC from crashing or if it's booting from BIOS, Cause after I change the bios settings, Make sure the PC runs fine and reboot I bluescreen.

It's like initial boot fails cause of something, But once it's booted from BIOS it works just fine, No weird temps, No stutters, No BSOD, No nothing. 

I am dumbfounded cause I have no clue what is wrong and something so minuscule has such a big impact.  

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

EDIT: Booting from BIOS works, It doesn't bluescreen.

I have tried setting my ram to both the intended speed of 5200mhz and 4800 mhz nothing changes the outcome on the cold boot where it gets me into windows, Runs for 30 seconds then bluescreens.
I have also tried undervolting the RAM both at 5200mhz and 4800mgz, Same outcome as above.

Gonna do something stupid and update to WIN11 and see if that fixes it. I doubt it but maybe I'll edit this part if it fixes it or not.

I have ran MC FRT and it was unable to resolve a couple of issues they are listed below in comment same with windows logs right before bluescreen. But the only error I get before BS is:

permission settings do not grant local activation permission for the COM Server application with CLSID 
The driver \Driver\WudfRd failed to load for the device HID\VID_046D&PID_0AAA&MI_03&Col02\8&35c17930&0&0001.
The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000008887, 0xffff808006a5f8d0, 0xffff8080069f0420, 0x0000000000000504).

Link to comment
https://linustechtips.com/topic/1462737-bsod-new-build/
Share on other sites

Link to post
Share on other sites

In event viewer -> Windows Logs -> System, filter by 'Critical', 'Warning' & 'Error'.

Look for around the time of the crash, are the any logs with error codes ?

CPU: Ryzen 5900x | GPU: RTX 3090 FE | MB: MSI X470 Gaming Pro Carbon | RAM: 32gb Ballistix | PSU: Corsair RM750 | Cooler: Sythe Fuma 2 | Case: Phanteks P600s | Storage: 2TB WD Black SN 750 & 1TB Sabrent Rocket | OS: Windows 11 Pro & Linux Mint

Link to comment
https://linustechtips.com/topic/1462737-bsod-new-build/#findComment-15618725
Share on other sites

Link to post
Share on other sites

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
and APPID
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
to the user DESKTOP-*****\docen SID (S-1-5-21-1683805387-1439082028-1471246537-1001) from address LocalHost (with LRPC) running in the application container Not available SID (Not available). This security permission can be modified using the Component Services administrative tool.

+permission for the COM Server application with CLSID 
Windows.SecurityCenter.SecurityAppBroker

+permission for the COM Server application with CLSID 
Windows.SecurityCenter.WscBrokerManager
+Windows failed fast startup with error status 0xC00000D4.

+The driver \Driver\WudfRd failed to load for the device HID\VID_046D&PID_0AAA&MI_03&Col02\8&35c17930&0&0001.

+The State Repository Service service terminated unexpectedly.  

+The SysMain service terminated with the following error: 
The parameter is incorrect.

+SecurityCenter.WscCloudBackupProvider

+The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000000403, 0xffff83000011f4a0, 0x8100000135754c66, 0xffff83008011f4a0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: c38bc2e4-4569-4310-a507-0352712f02df.

+The computer has rebooted from a bugcheck.  The bugcheck was: 0x0000001a (0x0000000000000403, 0xffff83000011f4a0, 0x8100000135754c66, 0xffff83008011f4a0). 

+The AppX Deployment Service (AppXSVC) service depends on the State Repository Service service which failed to start because of the following error: 
The operation completed successfully
+The State Repository Service service terminated unexpectedly.  It has done this 2 time(s).  The following corrective action will be taken in 300000 milliseconds: Starta om tjänsten.
+The server Windows.Internal.StateRepository.ApplicationExtension did not register with DCOM within the required timeout.


I have done two fresh installs of windows and two fresh windows boot device. after all of this my pc has been running fine for the past 3 hours without any issues what so ever. But I can bet if I restart it it will bluescreen as it did last time


CMD Sfc /scannow
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Microsoft framework repair tool unable to resolve:
C:\Windows\windowsupdate.log

C:\Windows\logs\cbs\cbs.log

C:\Users\docen\AppData\Local\Temp\FixDotNet.log

C:\Users\docen\AppData\Local\Temp\NetFxSetupEvents.txt

C:\Users\docen\AppData\Local\Temp\dd_NetFxRepairTool_decompression_log.txt

C:\Users\docen\AppData\Local\Temp\dd_vcredistMSI5131.txt

C:\Users\docen\AppData\Local\Temp\dd_vcredistUI5131.txt

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022004659.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022004853.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022004853_0_vcRuntimeMinimum_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022004853_1_vcRuntimeAdditional_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022033143.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022033143_000_vcRuntimeMinimum_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022033143_001_vcRuntimeAdditional_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022033147.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022110420.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022110420_000_vcRuntimeMinimum_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022110420_001_vcRuntimeAdditional_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022110421.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022115817.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022230802.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022230802_000_vcRuntimeMinimum_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022230802_001_vcRuntimeAdditional_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022230809.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022231833.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022231833_0_vcRuntimeMinimum_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_amd64_20221022231833_1_vcRuntimeAdditional_x64.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022004854.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022004854_0_vcRuntimeMinimum_x86.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022004854_1_vcRuntimeAdditional_x86.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022110418.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022110418_000_vcRuntimeMinimum_x86.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022110418_001_vcRuntimeAdditional_x86.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022110419.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022115818.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022231835.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022231835_0_vcRuntimeMinimum_x86.log

C:\Users\docen\AppData\Local\Temp\dd_vcredist_x86_20221022231835_1_vcRuntimeAdditional_x86.log

C:\Users\docen\AppData\Local\Temp\Microsoft Visual C++ 2010  x64 Redistributable Setup_20221022_231837322-MSI_vc_red.msi.txt

C:\Users\docen\AppData\Local\Temp\Microsoft Visual C++ 2010  x86 Redistributable Setup_20221022_231841026-MSI_vc_red.msi.txt

C:\Users\docen\AppData\Local\Temp\Microsoft Visual C++ 2010  x64 Redistributable Setup_20221022_231837322.html

C:\Users\docen\AppData\Local\Temp\Microsoft Visual C++ 2010  x86 Redistributable Setup_20221022_231841026.html

C:\Users\docen\AppData\Local\Temp\FixDotNet_HKCR_Installer.regdump

C:\Users\docen\AppData\Local\Temp\FixDotNet_HKLM_Installer.regdump








Link to comment
https://linustechtips.com/topic/1462737-bsod-new-build/#findComment-15618814
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×