› Foros › PC › Software libre
Blue Ion escribió:Como recurso complicado pero extremadamente útil es examinar un volcado de memoria que hace el windows en esos casos. Te indica que driver es el que ha hecho el problema y puede ayudar a reinstalar o al menos evitar el problema.
Si quieres intentarlo dime y lo explico.
Debugger and Symbols Downloads
Download Windows Symbol Packages
Install Debugging Tools for Windows 32-bit Version
Install Debugging Tools for Windows 64-bit Versions
"C:\Archivos de programa\Debugging Tools for Windows\windbg" -y C:\WINDOWS\Symbols -i C:\WINDOWS\I386 -z %1
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, cd4, 142b0800, e1f4e008}
*** WARNING: Unable to verify timestamp for win32k.sys
Probably caused by : win32k.sys ( win32k!HeavyAllocPool+51 )
Followup: MachineOwner
: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 142b0800, Memory contents of the pool block
Arg4: e1f4e008, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: e1f4e008
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from 80551fc5 to 80537672
STACK_TEXT:
...
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 04030201, Memory contents of the pool block
Arg4: e3466a60, Address of the block of pool being deallocated
Debugging Details:
------------------
POOL_ADDRESS: e3466a60
FREED_POOL_TAG: pSsA
BUGCHECK_STR: 0xc2_7_pSsA
CUSTOMER_CRASH_COUNT: 5
DEFAULT_BUCKET_ID: COMMON_SYSTEM_FAULT
PROCESS_NAME: notepad++.exe
LAST_CONTROL_TRANSFER: from 80551fc5 to 80537672
STACK_TEXT:
b73c7b6c 80551fc5 000000c2 00000007 00000cd4 nt!MiRemoveUnusedSegments+0x3db
b73c7bbc b7b53a0a e3466a60 00000000 80569780 nt!KiProfileLock+0x1
WARNING: Stack unwind information not available. Following frames may be wrong.
b73c7be8 80635474 00001418 00000eb4 b73c7ce0 aswSP+0x5a0a
b73c7c08 805c062d b73c7c28 00000eb4 b73c7ce0 nt!RtlpSysVolAdminSid+0x2d
b73c7d0c 80586e4e 7c8106f5 00000000 00000000 nt!IoAssignDriveLetters+0x5cf
b73c7d50 804ec6c9 00000000 7c8106f5 00000001 nt!RtlOemStringToUnicodeString+0x49
00000000 00000000 00000000 00000000 00000000 nt!Magic86400000+0x1f1
STACK_COMMAND: kb
FOLLOWUP_IP:
aswSP+5a0a
b7b53a0a ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: aswSP+5a0a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswSP
IMAGE_NAME: aswSP.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4881fba3
FAILURE_BUCKET_ID: 0xc2_7_pSsA_aswSP+5a0a
BUCKET_ID: 0xc2_7_pSsA_aswSP+5a0a
Followup: MachineOwner
---------