Question Brand New PC BSOD - KERNEL_SECURITY_CHECK_FAILURE

[fundip88192]

I've built my PC last month and I have been getting BSODs every once in a while. It doesn't seem to occur whenever I do something specific, it just happens out of no where. Completely random. This time I was just typing in a google doc and it happened.

SPECS:
Ryzen 5 7600X3D
NVIDIA GeForce RTX 4070 Ti Super
G.Skill Flare X5 32GB
SK Hynix Platinum P41 NVMe SSD

I also downloaded BlueScreenView and ran it to see that all of my BSODs were "Caused By Driver: ntoskrnl.exe"
Only 3 of the BSODs have values for Bug Check Strings which are: MEMORY_MANAGEMENT and INTERNAL_POWER_ERROR

After my PC rebooted from the BSOD KERNEL_SECURITY_CHECK_FAILURE, I went to Event Viewer and saw:
The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xfffff80548ae7e70, 0xfffff80548ae7dc8, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\021925-13609-01.dmp.

To add, I have enabled EXPO I in the bios when I first put together my PC.
I have scanned for malware using Malwarebytes.
I have ran chkdsk C: which there were no problems found.
I have ran sfc /scannow which the Windows Resource Protection did not find any integrity violations.
I have ran DISM /Online /Cleanup-Image /CheckHealth which there was no component store corruption detected.

If anyone could help me resolve this issue I would greatly appreciate it.

 

[Ralston18]

Motherboard?

PSU: make, model, wattage? New?

New build:

Power down, unplug, open the case.

Verify by sight and feel that all connectors, cards, RAM, jumpers, and case connections are fully and firmly in place.

Leave the CPU alone.

You may need to carefully unplug/replug or unseat/reseat a few times in order to ensure a smooth firm connection.

Look for kinked or pinched wires, cracks, loose pins or ports.

No one wants to force anything with a new build so what seems to be fully connected or seated is really not so.

Hopefully the problem is just a matter of finding and fixing something a bit loose.

 

[fundip88192]

Motherboard?

PSU: make, model, wattage? New?

New build:

Power down, unplug, open the case.

Verify by sight and feel that all connectors, cards, RAM, jumpers, and case connections are fully and firmly in place.

Leave the CPU alone.

You may need to carefully unplug/replug or unseat/reseat a few times in order to ensure a smooth firm connection.

Look for kinked or pinched wires, cracks, loose pins or ports.

No one wants to force anything with a new build so what seems to be fully connected or seated is really not so.

Hopefully the problem is just a matter of finding and fixing something a bit loose.

I apologize, here is the requested information:

Motherboard: ASUS B650-E TUF Gaming
PSU: Corsair RM850x 850 Watt Cybenetics Gold, New

I will check now and get back to you. Thanks for the help.

 

[fundip88192]

@Ralston18 I've opened up my PC. Checked all the cables connected to the motherboard and PSU, they all seem like they're in properly and they're not twisted or pinched. I tried to be as careful as possible when doing the wiring on this build.

Like I said, the BSODs aren't happening when I do something specific. They occur randomly, so I will have to wait until it happens again to let you know.

When starting up my PC, I also set EXPO to auto to see if it fixes anything.

 

[Ralston18]

Random problems are indeed difficult to diagnose and solve.

Take a closer look at what may be happening via Reliability History/Monitor and Event Viewer.

Look for any error codes, warnings, or even informational events being logged just before or at the time of the BSODs.

 

[fundip88192]

Random problems are indeed difficult to diagnose and solve.

Take a closer look at what may be happening via Reliability History/Monitor and Event Viewer.

Look for any error codes, warnings, or even informational events being logged just before or at the time of the BSODs.

In Event Viewer the only thing I see before it happened is a warning that occurred almost an hour before the last BSOD.

After the BSOD occurred the only things I see are (From earliest to latest):

Error: The previous system shutdown at 1:22:14 PM on ‎2/‎19/‎2025 was unexpected.
Error: Dump file generation succeded.
Critical: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Warning: The driver \Driver\WUDFRd failed to load.
Device: HID\VID_3329&PID_4B19&Col03\9&2d53b0a8&0&0002
Status: 0xC0000365
Warning: Disk 3 has the same disk identifiers as one or more disks connected to the system. Go to Microsoft's support website (http://support.microsoft.com) and search for KB2983588 to resolve the issue.
Error: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000139 (0x0000000000000003, 0xfffff80548ae7e70, 0xfffff80548ae7dc8, 0x0000000000000000). A dump was saved in: C:\WINDOWS\Minidump\021925-13609-01.dmp.

Then theres just a bunch of warnings

 

[Ralston18]

Note the Disk 3 Warning:

Search for the mentioned KB as directed.

Open the Disk Management window and expand so all can be seen.

Take a screenshot and post the screenshot here via imgur (www.imgur.com).

= = = =

Regarding: \Driver\WUDFRd

That is more involved but here is a year old link that may be helpful - either directly or as a lead into other possible reasons and fixes. As applicable to your build and gaming environment.

= = = =

Try running "dism" and "sfc /scannow" again.

Take your time, read carefully, be methodical. Keep notes.

 

[johnbl]

7: kd> !error 0xC0000365
Error code: (NTSTATUS) 0xc0000365 (3221226341) - The driver was not loaded because it failed its initialization call.


the bugcheck code indicated a driver error where a list entry was corrupted or deleted twice by a driver

we would have to have the actual minidump file to see what the driver was.
for the error code indicated we would need a kernel dump to list the plug and play drivers that did not load.

you should be able to go in to control panel, device manager and look for a driver that is not loading and fix the problem. (delete the bad driver and install the correct driver for your motherboard.)

 

[ubuysa]

Can you upload the actual dump files produced please?

 

[fundip88192]

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

 

[Ralston18]

Not an overclocker (full disclosure) so I will defer to those who do such things.

Overall though, I would suspect that there was some issue with EXPO and/or support for related components.

Per @ubuysa: the dump files may prove helpful.