I've been using my laptop and running skype having video call when suddenly my pc freezes and got blue screen with error message...at the end i saw memory dump file... so i have tried to debug my laptop and here's the result. i dont know what to do next please help:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:WindowsMinidumpMini111409-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18304.x86fre.vistasp1_gdr.090805-0102
Machine Name:
Kernel base = 0x82052000 PsLoadedModuleList = 0x82169c70
Debug session time: Sat Nov 14 21:46:50.618 2009 (GMT+8)
System Uptime: 0 days 4:57:57.771
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {84714510, 87959190, c00000b5, a}
Unable to load image SystemRootsystem32DRIVERSSISGRKMD.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SISGRKMD.sys
*** ERROR: Module load completed but symbols could not be loaded for SISGRKMD.sys
Probably caused by : SISGRKMD.sys ( SISGRKMD+c190 )
Followup: MachineOwner
---------
0: kd> .reload
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...........
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 84714510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 87959190, The pointer into responsible device driver module (e.g. owner tag).
Arg3: c00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000a, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image SystemRootsystem32DRIVERSSISGRKMD.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for SISGRKMD.sys
*** ERROR: Module load completed but symbols could not be loaded for SISGRKMD.sys
FAULTING_IP:
SISGRKMD+c190
87959190 8bff mov edi,edi
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
8c03aa8c 8ac7fd76 00000116 84714510 87959190 nt!KeBugCheckEx+0x1e
8c03aab0 8ac80a68 87959190 c00000b5 0000000a dxgkrnl!TdrBugcheckOnTimeout+0x8d
8c03aad0 8ac1ded1 c00000b5 00000000 8c03ab84 dxgkrnl!TdrIsRecoveryRequired+0xa1
8c03ab38 8ac2f2d0 8622a668 0011731c 00000000 dxgkrnl!VidSchiReportHwHang+0x2f5
8c03ab64 8ac75b3b 8622a668 8c03ab84 00000102 dxgkrnl!VidSchWaitForCompletionEvent+0x160
8c03abe4 8ac28c73 8439c000 8622a668 b1c69518 dxgkrnl!VidSchiWaitForCompletePreemption+0x54
8c03ac60 8ac291c9 8439c9d8 00000001 b1c69518 dxgkrnl!VidSchiSendToExecutionQueueWithWait+0xc2
8c03ad44 8ac26930 00c69518 87725710 8c03ad68 dxgkrnl!VidSchiSubmitRenderCommand+0x51c
8c03ad54 8ac2efb0 b1c69518 820a3645 8622a668 dxgkrnl!VidSchiSubmitQueueCommand+0x61
8c03ad68 8ac6c053 8622a668 00000000 8613bd78 dxgkrnl!VidSchiRun_PriorityTable+0x24
8c03ad7c 82227b22 8622a668 54251430 00000000 dxgkrnl!VidSchiWorkerThread+0x62
8c03adc0 82080a2e 8ac6bff1 8622a668 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
SISGRKMD+c190
87959190 8bff mov edi,edi
SYMBOL_NAME: SISGRKMD+c190
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SISGRKMD
IMAGE_NAME: SISGRKMD.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 49ab8f3d
FAILURE_BUCKET_ID: 0x116_IMAGE_SISGRKMD.sys
BUCKET_ID: 0x116_IMAGE_SISGRKMD.sys
Followup: MachineOwner
---------
The first cause can be fixed rather easily. Simply run fewer programs or buy additional RAM or processor upgrades. Your computer is running past its specified limits. But remember that in this case the blue screen of death should happen extremely infrequently. If you see the physical memory dump blue screen much more often then the issue is clearly...!..
The first cause can be fixed rather easily. Simply run fewer programs or buy additional RAM or processor upgrades. Your computer is running past its specified limits. But remember that in this case the blue screen of death should happen extremely infrequently. If you see the physical memory dump blue screen much more often then the issue is clearly...!..
click start right click on my computer,properties advanced scroll down to system and recovery open settings write and debugging information the drop down button select none
ideally, it should already be the default debugger for your system.
The Dr. Watson debugger program logs all information related to failed processes to the Drwtsn32.log file. In addition to this, the debugger program can be configured to create memory dump files related to the failed processes. You can refer these dump files to analyze the reason behind a process failure.
Perform the following steps to configure Dr. Watson as the default debugger program to record user-mode program errors:
377 views
Usually answered in minutes!
×