BSOD CRITICAL_PROCESS_DIED

Could you drop me a link to a tutorial on how to do that?

Enable standard nvme controller in bios .

Or

Download kingston nvme driver, unzip file, copy driver files to usb pendrive, while installing windows, install nvme drivers

Okay so nothing is working and I’m trying to reinstall windows from a usb stick.

However, the windows installer is not picking up my SSD. What do I do here other than send it into an inspection service?

Thank you for the reply Mitchell. I will try the things you’ve mentioned to try and get a successful boot out of it.

I am currently waiting on a delivery for a usb stick that I can use to try and boot if nothing else works.

Hi SamTurner4,

Thank you for your additional message. I have also noticed that you are having an enthusiastic discussion with our volunteers on this issue.

From our point of view, the method of reinstalling the system using an ISO image file is actually different from the new installation system, because this way is not necessarily complete. What you can do with an ISO image file is to replace the system files on the entire computer, but this may not contain drivers or third-party software.

In general, to completely rule out the possibility of driver failure, we recommend that users update all drivers in the device as much as possible.

I noticed that you seem to have made a fix for "VirtualBox" in the past, but for now, I would probably advise you to uninstall it, as we have previously received reports of blue screens caused by VirtualBox.

In the absence of enough information at this time, I recommend that you try this by referring to the following instructions in the link:

As for the event viewer, what you really want to focus on is the error record corresponding to the point in time when the blue screen appears. You'll notice that errors are time-stamped (down to the second), and that only the point in time corresponding to the incident is the most specific:

According to the latest blue screen error message you provided, the error code is:

REGISTRY_FILTER_DRIVER_EXCEPTION

The following is the parsing information for this error code:

Bug Check 0x135 REGISTRY_FILTER_DRIVER_EXCEPTION - Windows drivers | Microsoft Learn

The directly directed process is:

WdFilter.sys

WdFilter.sys is the Windows Defender driver file, which is part of the Windows operating system. It is mainly used to monitor access to the file system and scan it if needed to ensure that the files do not contain malicious code.

If the error goes directly to WdFilter.sys, then I recommend that you try updating Windows Defender: Open the Windows Defender Security Center, click the "Virus and Threat Protection" TAB, and then click "Update Definition." This will help ensure that your Windows Defender always has the latest virus definitions and fixes.

But considering that the problem arises after you use an ISO image file, it makes me wonder if it's possible that the image file is incomplete.

From the latest screenshots, "No NVME Device Found," which means that your motherboard cannot recognize your SSD at this time. This is more troublesome because there is no way to back up even the data in the SSD.

Let's assume there are no hardware failures with your SSD. The general investigation process is as follows:

1. Ensure that csm support is enabled on the mainboard. In the boot menu, enable other PCI device items and disable all others.
2. If the fault persists, you may need to restore the motherboard to its default Settings.
3. On other devices, visit the official website of the mainboard, download the corresponding driver or firmware, and then update the driver or firmware for the mainboard with the help of the mainboard after-sales support.

But if no matter what you do, your SSD is still not recognized by your motherboard, then this may be an SSD hardware failure. In this case, do not hesitate to send your device to the after-sales service for inspection.

Best regards,

Mitchell - | Microsoft community support expert from MSFT