Hola randomize
Ahora si te entendí.
Estuve depurando un poco mejor los DMP con WinDbg y el resultado que obtuve es:
-----------------------------------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\DMP PC de Omar\031814-13494-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02817000 PsLoadedModuleList = 0xfffff800`02a5ce90
Debug session time: Mon Mar 17 18:55:21.533 2014 (GMT-3)
System Uptime: 0 days 0:07:00.969
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80043844e0, fffff88005182694, ffffffffc000009a, 4}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : nvlddmkm.sys ( nvlddmkm+97e694 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80043844e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005182694, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: fffff80002817000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 52f651cf
FAULTING_IP:
nvlddmkm+97e694
fffff880`05182694 803d6ea7eeff00 cmp byte ptr [nvlddmkm+0x868e09 (fffff880`0506ce09)],0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`045e5b88 fffff880`04302000 : 00000000`00000116 fffffa80`043844e0 fffff880`05182694 ffffffff`c000009a : nt+0x80640
fffff880`045e5b90 00000000`00000116 : fffffa80`043844e0 fffff880`05182694 ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5d000
fffff880`045e5b98 fffffa80`043844e0 : fffff880`05182694 ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
fffff880`045e5ba0 fffff880`05182694 : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`043844e0 : 0xfffffa80`043844e0
fffff880`045e5ba8 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`043844e0 fffff880`042d5867 : nvlddmkm+0x97e694
fffff880`045e5bb0 00000000`00000004 : 00000000`00000001 fffffa80`043844e0 fffff880`042d5867 fffff880`05182694 : 0xffffffff`c000009a
fffff880`045e5bb8 00000000`00000001 : fffffa80`043844e0 fffff880`042d5867 fffff880`05182694 fffffa80`05980000 : 0x4
fffff880`045e5bc0 fffffa80`043844e0 : fffff880`042d5867 fffff880`05182694 fffffa80`05980000 00000000`00000000 : 0x1
fffff880`045e5bc8 fffff880`042d5867 : fffff880`05182694 fffffa80`05980000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`043844e0
fffff880`045e5bd0 fffff880`05182694 : fffffa80`05980000 00000000`00000000 ffffffff`c000009a fffffa80`0597f410 : dxgkrnl+0x30867
fffff880`045e5bd8 fffffa80`05980000 : 00000000`00000000 ffffffff`c000009a fffffa80`0597f410 ffffffff`feced300 : nvlddmkm+0x97e694
fffff880`045e5be0 00000000`00000000 : ffffffff`c000009a fffffa80`0597f410 ffffffff`feced300 fffffa80`059e46f0 : 0xfffffa80`05980000
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+97e694
fffff880`05182694 803d6ea7eeff00 cmp byte ptr [nvlddmkm+0x868e09 (fffff880`0506ce09)],0
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nvlddmkm+97e694
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
-----------------------------------------------------------------------------------------------------------
Aca aparece un nuevo modulo como causante del problema (nvlddmkm.sys), y buscando en internet encontré esto:
http://es.kioskea.net/faq/4212-error-nvlddmkm-sys-la-solucionLos sintomas que ahi detalla son los mismos que tiene mi PC, asi que voy a probar con ese metodo y veo que pasa, sino se corrige voy por el zerofill.
Esta tarde lo pruebo y les comento como me fue.
Muchas gracias
Autor
En línea
