Hello,
I have a Pc with XP SP3 which is continously resetting. With windbg I have the following information,
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\mperez\Minidump\Mini050615-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.130307-0422
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed May 6 14:17:15.779 2015 (UTC + 2:00)
System Uptime: 0 days 6:38:12.092
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, f7717d70, 0, 0}
Unable to load image igxpmp32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpmp32.sys
*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for VIDEOPRT.SYS -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
*** WARNING: Unable to verify timestamp for igxpdx32.DLL
*** ERROR: Module load completed but symbols could not be loaded for igxpdx32.DLL
Probably caused by : igxpmp32.sys ( igxpmp32+44184 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f7717d70
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: iexplore.exe
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
TRAP_FRAME: a82df13c -- (.trap 0xffffffffa82df13c)
ErrCode = 00000002
eax=00000000 ebx=a82df2b8 ecx=e3fb3000 edx=0000000f esi=e3fb3000 edi=e3fb3000
eip=8056fc5c esp=a82df1b0 ebp=a82df1b4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!RtlCreateSecurityDescriptor+0x13:
8056fc5c ab stos dword ptr es:[edi] es:0023:e3fb3000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e9140 to 804e91b3
STACK_TEXT:
a82df004 804e9140 80567c80 00000000 c0c0003c nt!MiDoReplacement+0x13
a82df020 804ea77c c0c0003c 18820000 c038fecc nt!MiLocateAndReserveWsle+0xb1
a82df038 804ea959 e3fb3000 c038fecc 8128f300 nt!MiAddValidPageToWorkingSet+0x84
a82df060 804e936b e3fb3000 c038fecc 00000000 nt!MiResolveDemandZeroFault+0x150
a82df0d0 804ea305 00000001 e3fb3000 c038fecc nt!MiDispatchFault+0x129
a82df124 804e0956 00000001 e3fb3000 00000000 nt!MmAccessFault+0x642
a82df124 8056fc5c 00000001 e3fb3000 00000000 nt!KiTrap0E+0xd0
a82df1b4 80573624 e3fb3000 00000001 a82df2ec nt!RtlCreateSecurityDescriptor+0x13
a82df21c 805732bf a82df2b8 e3fb3000 a82df2bc nt!SeQuerySecurityDescriptorInfo+0x198
a82df234 80573280 e1024994 a82df2b8 e3fb3000 nt!CmpQuerySecurityDescriptorInfo+0x23
a82df280 806318d7 e7585838 00000001 a82df2b8 nt!CmpSecurityMethod+0x113
a82df2c0 8056dda4 e7585838 a82df2ec e7585834 nt!ObpGetObjectSecurity+0x99
a82df2f0 8057347c e7585838 8873e3a0 00000001 nt!ObCheckObjectAccess+0x2c
a82df33c 80572735 e1037b60 001e7818 d772881c nt!CmpDoOpen+0x2d5
a82df53c 8056d03b 001e7818 001e7818 8873e3a0 nt!CmpParseKey+0x5a6
a82df5b4 805701e7 00000000 a82df5f4 00000240 nt!ObpLookupObjectName+0x53c
a82df608 80572d08 00000000 89bc0860 00000000 nt!ObOpenObjectByName+0xea
a82df704 804dd99f a82dfa24 82000000 a82df7a8 nt!NtOpenKey+0x1c8
a82df704 804e3bff a82dfa24 82000000 a82df7a8 nt!KiFastCallEntry+0xfc
a82df788 8063d607 a82dfa24 82000000 a82df7a8 nt!ZwOpenKey+0x11
a82df9f8 8063d6c3 00000002 8063d718 00000000 nt!RtlpGetRegistryHandleAndPath+0x27a
a82dfa40 80609b64 a82dfa60 00000014 a82dfba0 nt!RtlpQueryRegistryGetBlockPolicy+0x2e
a82dfa68 8059a915 00000003 ea1d2bec 00000014 nt!RtlpQueryRegistryDirect+0x4b
a82dfab8 8059a82e ea1d2bec 00000003 a82dfb34 nt!RtlpCallQueryRegistryRoutine+0x369
a82dfb40 ba123184 00000001 00000084 a82dfba0 nt!RtlQueryRegistryValues+0x368
WARNING: Stack unwind information not available. Following frames may be wrong.
a82dfbe8 ba0e885b 00000005 883573fc 883574fc igxpmp32+0x44184
a82e0260 ba0e4a7b 89ab6358 a82e0290 00000000 igxpmp32+0x985b
a82e0274 ba0d9729 89ab6358 a82e0290 00000a0c igxpmp32+0x5a7b
a82e0338 804e13eb 89ab6040 889cac80 0000080c VIDEOPRT!VideoPortUnmapMemory+0x1441
a82e0348 bf877d24 a82e0610 bf6e6cdc 00000014 nt!IopfCallDriver+0x31
a82e0378 bf877d9e 89ab6040 00232150 a82e03f8 win32k!XLATEOBJ_iXlate+0xb185
a82e039c bf376769 89ab6040 00232150 a82e03f8 win32k!EngDeviceIoControl+0x1f
a82e1624 bf3b9f79 89ab6040 bf6a593c bf6a5960 igxpdx32+0x8769
a82e1670 8056d230 8873e3a0 00000240 89bc0860 igxpdx32+0x4bf79
a82e1708 8873e3a0 a82e17b0 80001120 8873e454 nt!ObpIncrementHandleCount+0x410
a82e174c 805512fa 8873e3a0 8873e430 00000000 0x8873e3a0
a82e1788 805702bb 8873e3a0 00000000 00000000 nt!ExFreePoolWithTag+0x664
a82e17b8 00000000 a82e17cc bf3a981c bf6f09b8 nt!ObOpenObjectByName+0x377
STACK_COMMAND: kb
FOLLOWUP_IP:
igxpmp32+44184
ba123184 ?? ???
SYMBOL_STACK_INDEX: 19
SYMBOL_NAME: igxpmp32+44184
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igxpmp32
IMAGE_NAME: igxpmp32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b47be93
FAILURE_BUCKET_ID: 0x7f_8_igxpmp32+44184
BUCKET_ID: 0x7f_8_igxpmp32+44184
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x7f_8_igxpmp32+44184
FAILURE_ID_HASH: {c5d53875-51aa-0095-320c-234c607d70d0}
Followup: MachineOwner
---------
Could anybody help me to knw what happened? I have minidums from 08/28/2013 until now but the PC was installed in 2010 and it was working well.
Best Regards and thanks in advance
I have a Pc with XP SP3 which is continously resetting. With windbg I have the following information,
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\mperez\Minidump\Mini050615-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.130307-0422
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed May 6 14:17:15.779 2015 (UTC + 2:00)
System Uptime: 0 days 6:38:12.092
Loading Kernel Symbols
...............................................................
...............................................................
Loading User Symbols
Loading unloaded module list
......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007F, {8, f7717d70, 0, 0}
Unable to load image igxpmp32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for igxpmp32.sys
*** ERROR: Module load completed but symbols could not be loaded for igxpmp32.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for VIDEOPRT.SYS -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for win32k.sys -
*** WARNING: Unable to verify timestamp for igxpdx32.DLL
*** ERROR: Module load completed but symbols could not be loaded for igxpdx32.DLL
Probably caused by : igxpmp32.sys ( igxpmp32+44184 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: f7717d70
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: iexplore.exe
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
TRAP_FRAME: a82df13c -- (.trap 0xffffffffa82df13c)
ErrCode = 00000002
eax=00000000 ebx=a82df2b8 ecx=e3fb3000 edx=0000000f esi=e3fb3000 edi=e3fb3000
eip=8056fc5c esp=a82df1b0 ebp=a82df1b4 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!RtlCreateSecurityDescriptor+0x13:
8056fc5c ab stos dword ptr es:[edi] es:0023:e3fb3000=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 804e9140 to 804e91b3
STACK_TEXT:
a82df004 804e9140 80567c80 00000000 c0c0003c nt!MiDoReplacement+0x13
a82df020 804ea77c c0c0003c 18820000 c038fecc nt!MiLocateAndReserveWsle+0xb1
a82df038 804ea959 e3fb3000 c038fecc 8128f300 nt!MiAddValidPageToWorkingSet+0x84
a82df060 804e936b e3fb3000 c038fecc 00000000 nt!MiResolveDemandZeroFault+0x150
a82df0d0 804ea305 00000001 e3fb3000 c038fecc nt!MiDispatchFault+0x129
a82df124 804e0956 00000001 e3fb3000 00000000 nt!MmAccessFault+0x642
a82df124 8056fc5c 00000001 e3fb3000 00000000 nt!KiTrap0E+0xd0
a82df1b4 80573624 e3fb3000 00000001 a82df2ec nt!RtlCreateSecurityDescriptor+0x13
a82df21c 805732bf a82df2b8 e3fb3000 a82df2bc nt!SeQuerySecurityDescriptorInfo+0x198
a82df234 80573280 e1024994 a82df2b8 e3fb3000 nt!CmpQuerySecurityDescriptorInfo+0x23
a82df280 806318d7 e7585838 00000001 a82df2b8 nt!CmpSecurityMethod+0x113
a82df2c0 8056dda4 e7585838 a82df2ec e7585834 nt!ObpGetObjectSecurity+0x99
a82df2f0 8057347c e7585838 8873e3a0 00000001 nt!ObCheckObjectAccess+0x2c
a82df33c 80572735 e1037b60 001e7818 d772881c nt!CmpDoOpen+0x2d5
a82df53c 8056d03b 001e7818 001e7818 8873e3a0 nt!CmpParseKey+0x5a6
a82df5b4 805701e7 00000000 a82df5f4 00000240 nt!ObpLookupObjectName+0x53c
a82df608 80572d08 00000000 89bc0860 00000000 nt!ObOpenObjectByName+0xea
a82df704 804dd99f a82dfa24 82000000 a82df7a8 nt!NtOpenKey+0x1c8
a82df704 804e3bff a82dfa24 82000000 a82df7a8 nt!KiFastCallEntry+0xfc
a82df788 8063d607 a82dfa24 82000000 a82df7a8 nt!ZwOpenKey+0x11
a82df9f8 8063d6c3 00000002 8063d718 00000000 nt!RtlpGetRegistryHandleAndPath+0x27a
a82dfa40 80609b64 a82dfa60 00000014 a82dfba0 nt!RtlpQueryRegistryGetBlockPolicy+0x2e
a82dfa68 8059a915 00000003 ea1d2bec 00000014 nt!RtlpQueryRegistryDirect+0x4b
a82dfab8 8059a82e ea1d2bec 00000003 a82dfb34 nt!RtlpCallQueryRegistryRoutine+0x369
a82dfb40 ba123184 00000001 00000084 a82dfba0 nt!RtlQueryRegistryValues+0x368
WARNING: Stack unwind information not available. Following frames may be wrong.
a82dfbe8 ba0e885b 00000005 883573fc 883574fc igxpmp32+0x44184
a82e0260 ba0e4a7b 89ab6358 a82e0290 00000000 igxpmp32+0x985b
a82e0274 ba0d9729 89ab6358 a82e0290 00000a0c igxpmp32+0x5a7b
a82e0338 804e13eb 89ab6040 889cac80 0000080c VIDEOPRT!VideoPortUnmapMemory+0x1441
a82e0348 bf877d24 a82e0610 bf6e6cdc 00000014 nt!IopfCallDriver+0x31
a82e0378 bf877d9e 89ab6040 00232150 a82e03f8 win32k!XLATEOBJ_iXlate+0xb185
a82e039c bf376769 89ab6040 00232150 a82e03f8 win32k!EngDeviceIoControl+0x1f
a82e1624 bf3b9f79 89ab6040 bf6a593c bf6a5960 igxpdx32+0x8769
a82e1670 8056d230 8873e3a0 00000240 89bc0860 igxpdx32+0x4bf79
a82e1708 8873e3a0 a82e17b0 80001120 8873e454 nt!ObpIncrementHandleCount+0x410
a82e174c 805512fa 8873e3a0 8873e430 00000000 0x8873e3a0
a82e1788 805702bb 8873e3a0 00000000 00000000 nt!ExFreePoolWithTag+0x664
a82e17b8 00000000 a82e17cc bf3a981c bf6f09b8 nt!ObOpenObjectByName+0x377
STACK_COMMAND: kb
FOLLOWUP_IP:
igxpmp32+44184
ba123184 ?? ???
SYMBOL_STACK_INDEX: 19
SYMBOL_NAME: igxpmp32+44184
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: igxpmp32
IMAGE_NAME: igxpmp32.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b47be93
FAILURE_BUCKET_ID: 0x7f_8_igxpmp32+44184
BUCKET_ID: 0x7f_8_igxpmp32+44184
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x7f_8_igxpmp32+44184
FAILURE_ID_HASH: {c5d53875-51aa-0095-320c-234c607d70d0}
Followup: MachineOwner
---------
Could anybody help me to knw what happened? I have minidums from 08/28/2013 until now but the PC was installed in 2010 and it was working well.
Best Regards and thanks in advance
