Question Error_code: 0xc000000d and Stop code: DPC_WATCHDOG_VIOLATION ?

[thee_unknown]

Hello all I'm currently stumped at what is wrong with my pc. I've tried SFC scan and trying to repair my boot drive/windows 10 file and it still is running into errors on bootup. The 2 blue screen errors I run into are Recovery Your PC Couldn't Start Properly A required device isn't connected or be accessed error_code: 0xc000000d and Stop code: DPC_WATCHDOG_VIOLATION. It's odd because maybe out of like 6 attempts to boot up, 1 will go through successfully and start up properly. I've also tried doing a windows 10 re-install via USB. It will get to the 3rd page of where I activate a key and freeze.

My current specs are

Processor : AMD Ryzen 3950X
Motherboard: Asus TUF GAMING X570-PLUS (WI-FI) ATX AM4 Motherboard
SSD (used for boot drive): Samsung 970 Evo 1 TB M.2-2280 PCIe 3.0 X4 NVME Solid State Drive
Graphics Card: NVIDIA Founders Edition GeForce RTX 3080 10GB 10 GB Video Card
HDD: Seagate Barracuda Compute 2 TB 3.5" 7200 RPM Internal Hard Drive



Any help is greatly appreciated, TIA

 

[ubuysa]

The 0xC000000D exception code indicates that an invalid parameter was passed to a function. The DPC_WATCHDOG_VIOLATION bugcheck indicates that a DPC (the back-end of device interrupt processing) ran for too long.

The conclusion must be that a boot loaded driver is misbehaving and causing both these issues. First try starting Windows in Safe Mode - that's a stripped down system with only critical services and no third party drivers loaded. If it boots consistently into Safe Mode then that would confirm a rogue boot-loaded driver.

If it boots in Safe Mode then next try a Clean Boot of Windows. This loads a complete Windows system but you can select which third-party drivers are loaded at boot time. Start with no third-party drivers and if that boots reliably then use a binary sort technique to add in third-party drivers until you find the culprit. Bear in mid that there may be more than one.

 

[thee_unknown]

The 0xC000000D exception code indicates that an invalid parameter was passed to a function. The DPC_WATCHDOG_VIOLATION bugcheck indicates that a DPC (the back-end of device interrupt processing) ran for too long.

The conclusion must be that a boot loaded driver is misbehaving and causing both these issues. First try starting Windows in Safe Mode - that's a stripped down system with only critical services and no third party drivers loaded. If it boots consistently into Safe Mode then that would confirm a rogue boot-loaded driver.

If it boots in Safe Mode then next try a Clean Boot of Windows. This loads a complete Windows system but you can select which third-party drivers are loaded at boot time. Start with no third-party drivers and if that boots reliably then use a binary sort technique to add in third-party drivers until you find the culprit. Bear in mid that there may be more than one.

Thanks for the reply, I tried getting into Windows in Safe Mode but ultimately it just ended up blue screening again with error code 0xc000000d and it saying Your PC/Device needs to be repaired A required device isn't connected or can't be accessed.

 

[ubuysa]

Can you boot the Windows installation media?

 

[thee_unknown]

Can you boot the Windows installation media?

So I recently tried isolating the problem (i disconnected all other ssd/hdd from the pc and had the bare minimum mouse and keyboard only plugged in) but ultimately it still freezes when trying to boot from the USB. I also tried swapping my boot ssd with a new one to see if its just an issue with the ssd but it still also freezes with the ssd.

 

[ubuysa]

That doesn't sound good. Try removing all drives and see whether the Windows install USB will boot.

 

[thee_unknown]

That doesn't sound good. Try removing all drives and see whether the Windows install USB will boot.

just attempted to boot via the USB with no ssd/hdds attached but it still froze. its starting to make me think it might be a hardware issue rather than a software issue

 

[ubuysa]

Oh, it's most definitely a hardware issue. There is NO doubt about that. The question is what hardware....

 

[thee_unknown]

Oh, it's most definitely a hardware issue. There is NO doubt about that. The question is what hardware....

gave up unfortunately and caved in to going to a pc repair store. They said they have isolated it down to the CPU or Motherboard. I wonder what the issue lies after finding which hardware part is the problem.