BSOD Watchdog_timeout in WIFI driver after switching to WI-Fi 6 router

[Miha3]

After switching my router to a new model supporting Wi-Fi 6 I somtimes get BSOD at Windows 10 startup. The cause of the problem is:

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8046dcfa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding this single DPC timeout

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\drivers\rtwlane02.sys, Win32 error 0n2

SYMBOL_NAME:  rtwlane02+3cd6e0

MODULE_NAME: rtwlane02

IMAGE_NAME:  rtwlane02.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  3cd6e0

FAILURE_BUCKET_ID:  0x133_DPC_rtwlane02!unknown_function

OS_VERSION:  10.0.19041.1

If the system starts up correctly, then the WiFi functions without problems.

I also have the latest HP Pavilion network drivers installed and have reinstalled them trying to fix this problem.

[Miha3]

Bump.

[Miha3]

I was really hoping to get at least some response here...

[Betty0610]

@Miha3

Welcome to the HP Support Community.

Please help us with the product number of the Laptop. Also, not all Wi-Fi adapter will support 6g.

Let us know 🙂

Thanks!

[Miha3]

First, thank you for responding.

The product number is V2H47EA#BED.

Also, I understand that it's unreasonable to expect 6g  in an old laptop. I was hopingto at least get rid of the crashes, I don't need the latest features.

Br, Miha

[Betty0610]

Try the steps from here: https://support.hp.com/in-en/document/c04593971

Let me know if this helps.

If the information I've provided was helpful, give us some reinforcement by clicking the "Accept as solution" button, that'll help us and others see that we've got the answers!

Thanks!

Have a great day!

[Miha3 · Accepted solution]

In the end it turned out it was a bit-rot issue. Reinstalling Windows was the solution that helped.

[Betty0610]

I'm glad to hear that. Do get back to us in the future for further assistance.

Have a nice day!:)