Windows 10: multiple BSODs caused by Watchdog.sys

I bought a new notebook witch 7940hs and rtx 4060 therefore i have amd and vidia drivers. Sometimes i face BSODS caused by watchdog.sys regarding to BlueScreenViewer. Ive already tried Reinstalling Graphics Drivers with DDU in safe mode and ran multiple commands like DISM.exe and chkdsk to fix everything. But still this is happening and i cant identify the issue. Ive also read that this issue can be caused by hardware errors. OneDrive - BSOD

:)

 

QCAMAIN1.SYS CAUSING BSOD

This was probably caused by the following module:
qcamain1.sys (Qcamain10x64+0x108678)

Bugcheck code: 0x1D3 (0x333, 0x0, 0x0, 0x0)

Error: CUSTOM_ERROR

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: qcamain1.sys .

Google query: qcamain1.sys CUSTOM_ERROR

Using WhoCrashed I found this thread: Redirecting however without
solution, locked.

I did get BSOD almost everytime I moved the laptop.

This worked for me:

unscrew wifi module, push a little into the socket. Screw in. DONE

 

DPC Watchdog Violation BSOD

Dear Bill F Curtis,

Welcome to the Microsoft Community



Thank you for reaching out about the recurring DPC Watchdog Violation BSOD error you've been experiencing. I understand how frustrating it can be to encounter such issues regularly. Based on the information you've provided, it seems like the error is related to the ACPI.sys driver, specifically pointing to ACPIInterruptEventCompletion.



The DPC Watchdog Violation error typically occurs when a Deferred Procedure Call (DPC) exceeds the permitted time limit, leading to a system crash (Blue Screen of Death or BSOD). The ACPI.sys driver manages Advanced Configuration and Power Interface functionalities in Windows, which are critical for power management and device enumeration.



To further diagnose and resolve this issue, I recommend the following steps:



Steps to Resolve DPC Watchdog Violation Error:

1. Update Drivers: Ensure all your drivers, especially the ACPI-related ones, are up to date. Outdated or corrupted drivers can often cause such errors. Please download the latest adapted driver from the hardware manufacturer's website and install it.
   
2. Check for BIOS Update: Sometimes, BIOS updates include fixes for ACPI-related issues. Visit your computer manufacturer's website to check if there's a BIOS update available for your specific model. Follow the manufacturer's instructions carefully when updating the BIOS.
   
3. Run Windows Memory Diagnostic: Memory issues can also contribute to DPC Watchdog Violation errors. Run the Windows Memory Diagnostic tool to check for memory problems:
   
   • Press Windows key + R, type mdsched.exe, and press Enter.
     
   • Choose to restart and check for problems.
     
4. Disable Overclocking (if applicable):If you've overclocked your CPU or GPU, revert to default settings temporarily. Overclocking can sometimes destabilize system components and lead to BSOD errors.
   

If the issue continues despite these steps, it might be beneficial to consult with a qualified technician who can perform more in-depth diagnostics.

Please let me know how these steps work for you or if you have any further questions. We're here to assist you further.

Best Regards,

Martin | Microsoft Community Support Specialist

 

Multiple BSODS with different errors, caused by ntoskrnl.exe

Wow thats a lot of usual causes!

Just to clarify / remove some things of that list, as mentioned the RAM has passed memtest multiple times, none of my hardware is OC'd, BIOS is fully up to date.

As far as I'm aware this is because its the single ram speed, and with it being DDR its 800*2=1600, I could be mistaken though?

As for the slots basically I was having BSOD's whenever any module was installed in one of the channels, so I had to move both modules over to the other channel, and this seemed to fix it, however I can move them back around to see what happens.

As for the memory I could have sworn I saw it on the supported list a while ago, ill check with the vendor of my PC.

Thanks for all the help

So whats the next step?