Donanımsal olabilir. Sıcaklık değerleri nasıl?
Sıcaklıklar boşta ve oyunda gayet iyi, furmark ve occt gibi testlerde de ortalamanın üstünde ancak bu sorunu yaşarken sıcaklıklarla ilgili bir sorun olmuyor.
Donanımsal olabilir. Sıcaklık değerleri nasıl?
Eski bir sürücü versiyonu deneyin ya da Windows Update size bir sürücü bulur.
Bir minidump dosyası oluşmuş:
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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.
Eski bir sürücü yükledim ve anında ekran yine dondu. Emin oldum ki herhangi sürücü yükleyince oluyor bu sorun.
