I get a BSOD thread_stuck_in_device_driver while playing SOME games, the screen freezes for a split second and then it knocks me to the blue screen; it also keeps looping the same small bit of audio (which sounds very annoying.) it only happens in a few of the games I play such as: Minecraft Windows 10 edition, Euro Truck Simulator 2, War thunder etc. Here is the dump file of the most recent crash:
Bugcheck Analysis *
The device driver is spinning in an infinite loop, most likely waiting for
hardware to become idle. This usually indicates problem with the hardware
itself or with the device driver programming the hardware incorrectly.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including bugcheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines (OS builds <= 3790) it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the bugcheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arg1: ffff800e1271c080, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.
* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
Key : Analysis.CPU.mSec Value: 108 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on LAPTOP-E9017ADL Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 109 Key : Analysis.Memory.CommitPeak.Mb Value: 44 Key : Analysis.System Value: CreateObject Key : WER.CorruptModuleList Value: 1
STACK_COMMAND: .thread ; .cxr ; kb
OSNAME: Windows 10
I had a read through myself but I'm that technical, I have a suspicion some module has been corrupted.
I put it under the tag windows-10-hardware-performance because I couldn't find anything that suited my problem; besides, I think BSOD's often have to do with hardware problems too.