Error encountered during startup: new BSOD.
Error encountered during startup: new BSOD.
Hello, I recently assembled a new PC and have encountered several issues. The specifications are: Asus TUF B650-PLUS RTX 3080, Aorus WaterForce, Ryzen 7 7700X, Kingston Fury Beast, DDR5 16GB, 5200mhz. I noticed that when using two RAM sticks together, my system would bluescreen and display typical RAM error codes. Even though each stick functions correctly when used alone, the problem persists. After a bluescreen, I manually entered BIOS, adjusted RAM settings, and booted again—everything worked smoothly. It remains unclear whether changing the settings each time prevents crashes or if it’s related to booting from BIOS. Once I rebooted through BIOS, there were no crashes, unusual temperatures, stutters, or BSODs. This seems strange because I’m unsure what exactly is causing the issue. Something so small seems to have a major effect.
Yes, all drivers are current and Windows is also up to date. (WIN10)
Open event viewer, navigate to Windows Logs -> System. Apply filters for 'Critical', 'Warning' and 'Error'. Check logs near the crash time, verify if any entries contain error codes.
The specific permission settings do not allow Local Activation for the COM Server app with the given CLSID and APPID to the user DESKTOP-*****\docen at LocalHost using LRPC. This restriction can be adjusted via the Component Services admin tool. Additional permissions are available through the following IDs: +permission for COM Server with Windows.SecurityCenter.SecurityAppBroker, +permission for COM Server with Windows.SecurityCenter.WscBrokerManager. Windows encountered a failure during fast startup with error code 0xC00000D4. The driver WudfRd could not load for the specified device, and the State Repository Service stopped unexpectedly. The SysMain service ended due to an error, and a dump was created at C:\Windows\MEMORY.DMP. The system has rebooted from a bugcheck, but it remains stable after recent restarts. For troubleshooting, refer to the CBS log at windir\Logs\CBS or use the provided offline repair files.