PC New Condition BSOD - Kernel Security Check Failed
PC New Condition BSOD - Kernel Security Check Failed
Specifications: Ryzen 5 7600X3D, NVIDIA GeForce RTX 4070 Ti Super, G.Skill Flare X5 32GB, SK Hynix Platinum P41 NVMe SSD. I also installed BlueScreenView and observed that all BSODs were linked to the driver ntoskrnl.exe. Only three BSODs had bug check string details: MEMORY_MANAGEMENT and INTERNAL_POWER_ERROR.
After rebooting from the BSOD KERNEL_SECURITY_CHECK_FAILURE, I checked Event Viewer. The system rebooted due to a bugcheck with ID 0x00000139. A dump was saved at C:\WINDOWS\Minidump\021925-13609-01.dmp.
Additionally, I enabled EXPO I during initial PC setup. I ran a malware scan using Malwarebytes. All checks passed: no malware detected.
The disk check (chkdsk C
, SFC scan, and DISM integrity verification showed no issues. If anyone can assist with this problem, I would be very grateful.
Edgecrusher2kX
01-31-2024, 08:19 AM #1I constructed my PC a month ago and have been experiencing BSODs occasionally. They seem to appear without any clear trigger, just randomly. The last time it happened was while typing in a Google document.
Specifications: Ryzen 5 7600X3D, NVIDIA GeForce RTX 4070 Ti Super, G.Skill Flare X5 32GB, SK Hynix Platinum P41 NVMe SSD. I also installed BlueScreenView and observed that all BSODs were linked to the driver ntoskrnl.exe. Only three BSODs had bug check string details: MEMORY_MANAGEMENT and INTERNAL_POWER_ERROR.
After rebooting from the BSOD KERNEL_SECURITY_CHECK_FAILURE, I checked Event Viewer. The system rebooted due to a bugcheck with ID 0x00000139. A dump was saved at C:\WINDOWS\Minidump\021925-13609-01.dmp.
Additionally, I enabled EXPO I during initial PC setup. I ran a malware scan using Malwarebytes. All checks passed: no malware detected.
The disk check (chkdsk C, SFC scan, and DISM integrity verification showed no issues.
If anyone can assist with this problem, I would be very grateful.
PSU: make, model, wattage? New?
New build:
Power down, unplug, open the case.
Check that all connectors, cards, RAM, jumpers, and case connections are securely in place.
Keep the CPU untouched.
You might need to carefully plug in or remove a few components several times to ensure everything fits properly.
Inspect for twisted or pinched wires, cracks, loose pins or ports.
A new build shouldn’t require forcing anything; if it looks fully connected, it’s likely just something loose needs fixing.
AEnglander5
01-31-2024, 09:45 AM #2Motherboard?
PSU: make, model, wattage? New?
New build:
Power down, unplug, open the case.
Check that all connectors, cards, RAM, jumpers, and case connections are securely in place.
Keep the CPU untouched.
You might need to carefully plug in or remove a few components several times to ensure everything fits properly.
Inspect for twisted or pinched wires, cracks, loose pins or ports.
A new build shouldn’t require forcing anything; if it looks fully connected, it’s likely just something loose needs fixing.
TheNiggaGamer
02-01-2024, 06:19 PM #4I've started my PC and inspected all the cables connected to the motherboard and PSU. Everything looks fine, not twisted or pinched. I tried to be as careful as possible during the wiring process for this build. The BSODs don't occur when performing specific actions; they happen randomly, so I'll have to wait until it happens again before informing you. I also set EXPO to auto at startup to check if that resolves any issues.
YoungAriesArt
02-04-2024, 05:47 PM #5Random issues are actually hard to identify and fix. Examine Reliability History/Monitor and Event Viewer more closely. Search for any error messages, alerts, or data logs that occurred right before or during the BSODs.
Error: The previous system shutdown at 1:22:14 PM on 2/19/2025 was unexpected.
Error: Dump file generation succeeded.
Critical: The system restarted without a clean shutdown. This issue might stem from the system failing to respond, crashing, or losing power suddenly.
Warning: The driver Driver\WUDFRd failed to load.
Device: HID\VID_3329&PID_4B19&Col03\9&2d53b0a8&0&0002
Status: 0xC0000365
Warning: Disk 3 shares identifiers with one or more connected disks. Visit Microsoft's support site (http://support.microsoft.com) and search for KB2983588 to fix the problem.
Error: The computer restarted due to a bugcheck. The associated bugcheck ID is 0x00000139 (details provided). A dump was saved at C:\WINDOWS\Minidump\021925-13609-01.dmp.
Then there are just a few warnings.
In Event Viewer the only information visible before the incident is a warning that appeared nearly an hour prior to the final BSOD. Following the BSOD, the displayed entries are (earliest to latest):
Error: The previous system shutdown at 1:22:14 PM on 2/19/2025 was unexpected.
Error: Dump file generation succeeded.
Critical: The system restarted without a clean shutdown. This issue might stem from the system failing to respond, crashing, or losing power suddenly.
Warning: The driver Driver\WUDFRd failed to load.
Device: HID\VID_3329&PID_4B19&Col03\9&2d53b0a8&0&0002
Status: 0xC0000365
Warning: Disk 3 shares identifiers with one or more connected disks. Visit Microsoft's support site (http://support.microsoft.com) and search for KB2983588 to fix the problem.
Error: The computer restarted due to a bugcheck. The associated bugcheck ID is 0x00000139 (details provided). A dump was saved at C:\WINDOWS\Minidump\021925-13609-01.dmp.
Then there are just a few warnings.
= = = =
Concerning the Driver WUDFRd issue, it requires more steps but here is an older resource that could assist—useful for your build and gaming setup.
Reattempt running "dism" and "sfc /scannow".
Take your time, read thoroughly, and proceed methodically. Document your findings.
Observe the Disk 3 Warning and look for the specified KB. Launch the Disk Management window and ensure it displays all items. Capture a screenshot and share it via imgur (www.imgur.com).
= = = =
Concerning the Driver WUDFRd issue, it requires more steps but here is an older resource that could assist—useful for your build and gaming setup.
Reattempt running "dism" and "sfc /scannow".
Take your time, read thoroughly, and proceed methodically. Document your findings.
Error message: The driver failed initialization, causing a list entry to be corrupted or deleted twice. A minidump file would help identify the issue. You may need to check the control panel, device manager, and remove the faulty driver to install the correct one for your motherboard.
davidspyro
02-09-2024, 09:38 AM #87: kd> !error 0xC0000365
Error message: The driver failed initialization, causing a list entry to be corrupted or deleted twice. A minidump file would help identify the issue. You may need to check the control panel, device manager, and remove the faulty driver to install the correct one for your motherboard.
I went to my BIOS and removed the EXPO I option that I set when I first built the PC. It has been two months and I have not had any BSODs since. What do you think the problem was? I haven't had EXPO on since and I know that it is recommended to make the PC faster. Is it a PSU issue or a RAM issue? I want to know so I can get a replacement and enable EXPO.
@Ralston18
Just an update for you since it has been a while.
I went to my BIOS and removed the EXPO I option that I set when I first built the PC. It has been two months and I have not had any BSODs since. What do you think the problem was? I haven't had EXPO on since and I know that it is recommended to make the PC faster. Is it a PSU issue or a RAM issue? I want to know so I can get a replacement and enable EXPO.
@Ralston18