bsod/dpc_watchdog mainly among others

Hello there!

Seems like the dump file didn't catch the bugcheck exception in dump file. We may need to wait for another crash and use that minidump to get more information.

Update the following drivers:
Code: 
ASMMAP64.sys Thu Jul 02 14:43:26 2009

Bugcheck:

Code: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Unknown bugcheck code (133)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000000
Arg2: 0000000000000281
Arg3: 0000000000000280
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x133

PROCESS_NAME:  System

CURRENT_IRQL:  d

LAST_CONTROL_TRANSFER:  from fffff801f27ebad7 to fffff801f266c240

STACK_TEXT:  
fffff801`f3da09c8 fffff801`f27ebad7 : 00000000`00000133 00000000`00000000 00000000`00000281 00000000`00000280 : nt!KeBugCheckEx
fffff801`f3da09d0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1459a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+1459a
fffff801`f27ebad7 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+1459a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  513814ba

FAILURE_BUCKET_ID:  X64_0x133_nt!_??_::FNODOBFM::_string_+1459a

BUCKET_ID:  X64_0x133_nt!_??_::FNODOBFM::_string_+1459a

Followup: MachineOwner
 

My Computer

System One

  • OS
    Windows 7
ckaracay said:
bump! very frustrating and still persistant would love a check on the files. thanks!
Click to expand...

Hello there!

Sorry for the late response. Seems like it's your Display drivers i.e. nVidia that's crashing you system. I would recommend to download the latest drivers and installed it. Use the driver cleanup software to remove the left over files as well. Also look for any BIOS update.

Check out this articles : nVidia Driver Cleanup Guide | Captain Debugger

Bugcheck:

Code: 
0: kd> !analyze -vERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************


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


TAG_NOT_DEFINED_c000000f:  FFFFF803ED33AFB0


LAST_CONTROL_TRANSFER:  from fffff803ee24ab2f to fffff803ee0cb240


STACK_TEXT:  
fffff803`ed333aa8 fffff803`ee24ab2f : 00000000`00000133 00000000`00000001 00000000`00000780 00000000`00000000 : nt!KeBugCheckEx
fffff803`ed333ab0 fffff803`ee110001 : 00000000`00000000 fffff803`ee369180 fffff803`ed333c10 fffff780`00000320 : nt! ?? ::FNODOBFM::`string'+0x145f6
fffff803`ed333b30 fffff803`ee027e94 : ffffffff`ffd0dc08 fffff803`ee051502 fffff880`00000000 00000000`000000a0 : nt!KeUpdateRunTime+0x51
fffff803`ed333b60 fffff803`ee0c3e5e : 00000000`00000000 fffffa80`12ffb000 fffff803`ee051580 00000000`00000000 : hal!HalpTimerClockInterrupt+0x50
fffff803`ed333b90 fffff880`04a2ae98 : fffff803`ed333d50 fffff880`04a4c504 00000000`00000000 fffffa80`12ffb000 : nt!KiInterruptDispatchLBControl+0x1ce
fffff803`ed333d20 fffff803`ed333d50 : fffff880`04a4c504 00000000`00000000 fffffa80`12ffb000 fffff803`ed333e60 : nvlddmkm+0x1dfe98
fffff803`ed333d28 fffff880`04a4c504 : 00000000`00000000 fffffa80`12ffb000 fffff803`ed333e60 00000000`00000000 : 0xfffff803`ed333d50
fffff803`ed333d30 00000000`00000000 : fffffa80`12ffb000 fffff803`ed333e60 00000000`00000000 fffff803`ed333d80 : nvlddmkm+0x201504




STACK_COMMAND:  kb


FOLLOWUP_IP: 
nvlddmkm+1dfe98
fffff880`04a2ae98 ??              ???


SYMBOL_STACK_INDEX:  5


SYMBOL_NAME:  nvlddmkm+1dfe98


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nvlddmkm


IMAGE_NAME:  nvlddmkm.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  505793aa


FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm+1dfe98


BUCKET_ID:  0x133_ISR_nvlddmkm+1dfe98


Followup: MachineOwner
---------
 

My Computer

System One

  • OS
    Windows 7
You must log in or register to reply here.
Back
Top