BSOD DPC_WATCHDOG_VIOLATION + BUGCODE_NDIS_DRIVER

Dump File 17640

 

BUGCODE_NDIS_DRIVER (7c)

Arg1: 0000000000000014, NDIS_BUGCHECK_WAIT_EVENT_HIGH_IRQL
    A network driver called NdisWaitEvent at an illegal
    IRQL.
rtwlanu6.sys                                 - Realtek Driver   Still Wireless issue you got self into.

SYMBOL_NAME:  rtwlanu6+194a20

FAILURE_BUCKET_ID:  0x7C_14_rtwlanu6!unknown_function

 

@ubuysa will need to look at your Dump File Link in Post # 27

There is still a zero-byte length dump in there - that's a symptom of something that's not quite right here. Probably either RAM or system drive related.

 

The other dumps are identical to the others, the failing driver looks to be rtwlanu6.sys again.

 

Do note that just because this is a Realtek driver that doesn't mean it's for a Realtek device. Many wireless network adapters produced by named vendors are based on Realtek chipsets and use Realtek drivers. Drivers for these wireless adapters should of course be sourced from the wireless device vendor, not from Realtek.

 

I think we've established with the cable attachment tests earlier that this IS a problem wither with the wireless card or its driver.

 

That all said, I noticed this in your msconfig output...

USB xHCI Compliant Host Controller    PCI\VEN_10DE&DEV_1ADA&SUBSYS_12FD10DE&REV_A1\4&FA0C5&0&0208    This device cannot start.

If the network adapter is a USB attached adapter then this USB root hub issue may have an impact.
 

Edited by ubuysa, 09 April 2024 - 04:40 AM.

Thank you for the reply!
I did get the driver-update for my WiFi-USB-Adapter on the manufacturer's support page (ASUS).

About the USB root hub: To be honest I have no idea what that means. Could it be that one of the USB ports is not working? I did try to plug the adapter in another USB port some time ago, but it didn't change the fact that the PC crashed immediately at the start.

What do you suggest I do?

USB Drivers from your Support Page, just install all of them..............have done at 3pages.  Some sort of solution.conclusion should be decided.

As above. Check the driver downloads for your motherboard and update all where there is a more recent driver available.

• Have you ever used a driver search and install tool (like DriverEasy)?
• Have you ever performed a registry clean with a third-party product?
• Have you installed any apps or devices that are not fully Windows 10 compatible?

Edited by ubuysa, 10 April 2024 - 01:10 AM.

So today I updated all the drivers (didn't even know there were such programs as Easy driver, very helpful!) and I cleaned the registry.
As for the 3rd question: There's not really an app I can remember that wouldn't be Windows 10 compatible... maybe one which I downloaded like a year ago which is 20 years old (I used compatibility mode).

After following those steps I haven't had a BSOD for almost 3 hours (did a couple of reboots to test it).
Next time I can do a full-day-test is on Sunday, I will let you know how that went!

Note : Driver Easy will have inserted itself in to Task Scheduler.   Once drivers have been updated the do not need to continually be updated.  Suggest strongly to uninstall it now.

 

What did you use to clean the Registry ??   This maybe the whole issue.

Okay, I have uninstalled DriverEasy now.

I used Wise Registry Cleaner to clean it. Also this morning for like 30 mins no BSOD.

Will give another update on Sunday evening!

Edited by Ollowain1, 12 April 2024 - 12:26 AM.

I did NOT ask you to install DriverEasy! I only asked if you had such a tool. They are to be avoided like the plague.

 

Nor did I ask you to clean the registry, I only asked if you'd ever done it. Registry cleaning is also to be avoided because it causes more problems than it ever (allegedly) fixes.

 

My purpose in asking was to try and see why you might be having problems.

Edited by ubuysa, 12 April 2024 - 01:05 AM.

I'm sorry, I've misunderstood you there. I had not done any of these things before.

Unfortunately my PC still crashes.
Might have just been luck on Thursday...

I've checked my installed programs for anything that would maybe not be Windows 10 compatible and uninstalled it, yet the problem still stands.

I haven't gotten the Watchdog BSOD yet though, will keep watching that.

Edited by Ollowain1, 14 April 2024 - 05:38 AM.

We seem to be going round in circles here and it's getting tiresome. We established back in posts #17 and #19 that you do not get BSODs using cable connection to your router. The problem then is either the wireless adapter itself or the wireless driver. Get a cheap USB WiFi adapter and try that.

A cheap USB WiFi adapter was what I was using when I got the first BSOD. I did use that Adapter for years though and never changed anything. And I tried all the stuff with the driver before I decided to get a better one.

For some reason since I posted the last post I got no more BSODs. I used the PC all day on Sunday and a few hours yesterday. Restarted many times just to check if it works, but until now everything seems to be good.

I will be on vacation for a week now, so I won't be able to test it for longer.

Stuff breaks, so just because the USB WiFi has worked for years doesn't mean it's good now. Get another adapter - and you generally get what you pay for. An adapter from a known networking vendor is a better option than a no-name adapter, even if it is cheaper.