What's new

Win8 BSOD

beigemonkey

New Member
Getting BSOD with Windows 8 and i can't tell what is causing it from debug.

https://docs.google.com/file/d/0BzbiFaNMfn1QYWM3Zm5FV0JsYjA/edit?usp=sharing
Have to remove some the items for confidentiality.

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000000780, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000


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




DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED


CUSTOMER_CRASH_COUNT: 1


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT


BUGCHECK_STR: 0x133


PROCESS_NAME: System


CURRENT_IRQL: d


LAST_CONTROL_TRANSFER: from fffff801e7fea747 to fffff801e7e91040


STACK_TEXT:
fffff880`03c14208 fffff801`e7fea747 : 00000000`00000133 00000000`00000001 00000000`00000780 00000000`00000000 : nt!KeBugCheckEx
fffff880`03c14210 fffff801`e7ebcf06 : fffff880`009f1180 00000000`003627cb fffff880`03c14390 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x13cdc
fffff880`03c14290 fffff801`e8581eca : 00000580`00000000 fffff880`0b847000 00000580`00000005 fffff880`0b8470c8 : nt!KeUpdateTime+0x41b
fffff880`03c14480 fffff801`e7e8a4de : 00000081`1ddbc96e fffffa80`1214a980 fffff801`e85ab9a0 fffffa80`1214a980 : hal!HalpTimerClockInterrupt+0x86
fffff880`03c144b0 fffff801`e7ec7df7 : fffff801`e7e564e0 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x1ce
fffff880`03c14648 fffff801`e7e564e0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MI_IS_PFN+0x37
fffff880`03c14650 fffff801`e7e59cb4 : 0000075f`face5000 fffff8a0`0531bff0 fffff8a0`0531b0c8 fffffa80`03a88400 : nt!MiLockLeafPageWorker+0x80
fffff880`03c14690 fffff801`e7e57b82 : 00000000`00002018 fffff880`03c14880 00000000`00000000 a0200001`382c0943 : nt!MiReplacePageOfProtoPool+0x384
fffff880`03c14780 fffff801`e7fa5b2b : 00000000`00000000 00000000`00000008 00000000`00000000 00000000`00000000 : nt!MiStealPage+0x162f
fffff880`03c14a80 fffff801`e838f178 : fffffa80`00000001 fffffa80`00000003 00000000`00000000 00000000`00000001 : nt!MiScrubNode+0x427
fffff880`03c14b10 fffff801`e7ec9951 : fffffa80`0a4c3780 fffffa80`08d444f8 fffff801`e80b3a00 fffff801`e809a200 : nt!MiScrubMemoryWorker+0x40
fffff880`03c14b80 fffff801`e7e393d5 : fffff880`01865180 00000000`00000080 fffff801`e7ec9810 fffffa80`0a4c3780 : nt!ExpWorkerThread+0x142
fffff880`03c14c10 fffff801`e7e77116 : fffff880`01865180 fffffa80`0a4c3780 fffff880`01870e40 fffffa80`066d7700 : nt!PspSystemThreadStartup+0x59
fffff880`03c14c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16




STACK_COMMAND: kb


FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+13cdc
fffff801`e7fea747 cc int 3


SYMBOL_STACK_INDEX: 1


SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+13cdc


FOLLOWUP_NAME: MachineOwner


MODULE_NAME: nt


IMAGE_NAME: ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP: 50ecec77


BUCKET_ID_FUNC_OFFSET: 13cdc


FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_


BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
 
Last edited:

My Computer

System One

  • OS
    Windows 8

Arc

New Member
Team Member
VIP Member
It is a stop 0x133.
Code:
1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[URL="http://www.carrona.org/bsodindx.html#0x00000133"]DPC_WATCHDOG_VIOLATION (133)[/URL]
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
[COLOR=#008000]Arg1: 0000000000000001[/COLOR], The system cumulatively spent an extended period of time at
    DISPATCH_LEVEL or above. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000000780, The watchdog period.
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------
Determining the cause of a stop 0x133 with a first parameter of 1 is a bit more difficult because the problem is a result of DPCs running from multiple drivers, so the call stack is insufficient to determine the culprit. (Source: Ntdebugging Blog)

So let us enable Driver Verifier to monitor the drivers as a first attempt.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

information   Information
Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.


warning   Warning
Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.


Tip   Tip


Let us know the results, with the subsequent crash dumps, if any.
 

My Computer

Top