Random BSOD. ndis.sys

Question

The driver \Driver\WUDFRd failed to load.

Device: USB\VID_2808&PID_A99A\1234567890ABCDEF

Status: 0xC0000365

All drivers and windows update are up to date.
Please help

Answer 1

Your data indicates two separate problems which are most likely unrelated.

1

The Device ID you list (USB\VID_2808&PID_A99A\1234567890ABCDEF) resolves to a FocalTech Fingerprint reader driver, do you have that type of device on your system?

2

For the system crashes, please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

Answer 2

The crash dump shows a bug check in ndis.sys, which is the Windows network driver framework used by miniport/network drivers. BSODs involving ndis.sys are commonly caused by faulty or incompatible network adapter drivers or by issues fixed in Windows updates that include an updated ndis.sys.

For similar issues on supported Windows versions, Microsoft has provided fixes that update ndis.sys to newer builds to address stop errors and power‑state failures involving network drivers. In those cases, the resolution is to install the corresponding Windows update or hotfix that contains the updated ndis.sys file.

Given that the dump points to ndis.sys and there is also a WUDFRd (user‑mode driver framework reflector) load failure for a USB device, the recommended approach is:

1. Ensure the system has all current cumulative and driver updates installed, especially those that update ndis.sys.
2. Update or reinstall the network adapter drivers (Wi‑Fi and Ethernet) from the system or adapter manufacturer so they are built and tested for the current Windows 11 build.
3. If BSODs continue, check for vendor guidance or firmware/driver updates for any Wi‑Fi or network‑related hardware, as similar ndis.sys stop errors have been confirmed and fixed via updated drivers/Windows updates on earlier Windows versions.

If, after updating Windows and all network/USB‑related drivers from the hardware manufacturer, the issue persists, contact the device or PC manufacturer with the minidump for further analysis, as they may need to provide an updated miniport or USB driver.

---

References:

• STOP Error 0x0000009F in DRIVER_POWER_STATE_FAILURE on Windows 8.1 when your computer resumes from sleep mode
• FIX: A stop error 0x50 in NDIS.sys occurs when any sleep state is entered and then resumed on a computer that is running Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1
• "0x0000009F" Stop error when you restart a Windows 7-based or Windows Server 2008 R2-based computer that has certain Wi-Fi drivers installed
• Minidrivers, Miniport drivers, and driver pairs