debuglog.txt (problemas con el explorer)

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini070205-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:
C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Jul 2 02:26:40.875 2005 (GMT+2)
System Uptime: 0 days 13:34:51.438
Loading Kernel Symbols

Loading unloaded module list
...
Loading User Symbols

*
*
* Bugcheck Analysis
*
*
*

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8054aefc, b19a07f4, 0}

*** ERROR: Module load completed but symbols could not be loaded for

*** ERROR: Symbol file could not be found. Defaulted to export symbols

SYMEVENT.SYS -
Probably caused by : SAVRT.SYS ( SAVRT+2f219 )

Followup: MachineOwner


kd> !analyze -v;r;kv;lmtn;.logclose;q

*
*
* Bugcheck Analysis
*
*
*

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8054aefc, The address that the exception occurred at
Arg3: b19a07f4, Trap Frame
Arg4: 00000000

Debugging Details:



EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace
referencia a la memoria en "0x%08lx". La memoria no se puede "%s".

FAULTING_IP:
nt!ExAllocatePoolWithTag+772
8054aefc 8902 mov [edx],eax

TRAP_FRAME: b19a07f4 -- (.trap ffffffffb19a07f4)
.trap ffffffffb19a07f4
ErrCode = 00000002
eaxá0a46f0 ebx‚f0a050 ecx‚f0a0e8 edx350034 esiá0a4760

eip€54aefc esp±9a0868 ebp±9a08bc iopl=0 nv up ei pl nz na po

cs08 ss10 ds23 es23 fs30 gs00

nt!ExAllocatePoolWithTag+0x772:
8054aefc 8902 mov [edx],eax

.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from b2019219 to 8054aefc

STACK_TEXT:
b19a08bc b2019219 00000001 0013000f 53646152

WARNING: Stack unwind information not available. Following frames may be
wrong.
b19a08ec b1ff1253 fc415f88 b1ff1040 b19a0904 SAVRT+0x2f219
b19a0908 b1ff4c07 00000000 b19a09b0 b1ff4169 SAVRT+0x7253
b19a094c b2e2e268 e1068130 b19a09a8 00000001 SAVRT+0xac07
b19a0970 b2e30998 00000000 b19a09b0 b2e32426
SYMEVENT!SYMEvent_GetSubTask+0x1438
b19a09ec b2e2ad02 b19a0a30 e1cf702c b19a0a30

b2e254f4 b2e32660 b2e327f0 b2e327d0 00000000
SYMEVENT!SYMEvent_GetVMDataPtr+0x5562
b2e326e0 06c7384e b2e254f4 ff56018b c0331c50

b2e326e4 b2e254f4 ff56018b c0331c50 89384689 0x6c7384e
b2e326e8 ff56018b c0331c50 89384689 46894046 SYMEVENT+0x14f4
b2e326ec c0331c50 89384689 46894046 0446893c 0xff56018b
b2e326f0 89384689 46894046 0446893c 082444f6 0xc0331c50
b2e326f4 46894046 0446893c 082444f6 0c06c701 0x89384689
b2e326f8 0446893c 082444f6 0c06c701 74b2e244 0x46894046
b2e326fc 082444f6 0c06c701 74b2e244 15ff5607 0x446893c
b2e32700 0c06c701 74b2e244 15ff5607 b2e243e4 0x82444f6
b2e32704 74b2e244 15ff5607 b2e243e4 c25ec68b 0xc06c701
b2e32708 15ff5607 b2e243e4 c25ec68b 90900004 0x74b2e244
b2e3270c b2e243e4 c25ec68b 90900004 90909090 0x15ff5607
b2e32710 c25ec68b 90900004 90909090 8bf18b56 SYMEVENT+0x3e4
b2e32714 90900004 90909090 8bf18b56 0000808e 0xc25ec68b
b2e32718 90909090 8bf18b56 0000808e 74c98500 0x90900004
b2e3271c 8bf18b56 0000808e 74c98500 e8006a07 0x90909090
b2e32720 00000000 74c98500 e8006a07 ffffbc0c 0x8bf18b56


FOLLOWUP_IP:
SAVRT+2f219
b2019219 85f6 test esi,esi

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SAVRT+2f219

MODULE_NAME: SAVRT

IMAGE_NAME: SAVRT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3f6a141f

STACK_COMMAND: .trap ffffffffb19a07f4 ; kb

FAILURE_BUCKET_ID: 0x8E_SAVRT+2f219

BUCKET_ID: 0x8E_SAVRT+2f219

Followup: MachineOwner


eaxá0a46f0 ebx‚f0a050 ecx‚f0a0e8 edx350034 esiá0a4760

eip€54aefc esp±9a0868 ebp±9a08bc iopl=0 nv up ei pl nz na po

cs08 ss10 ds23 es23 fs30 gs00

nt!ExAllocatePoolWithTag+0x772:
8054aefc 8902 mov [edx],eax

ChildEBP RetAddr Args to Child
b19a08bc b2019219 00000001 0013000f 53646152

(FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be
wrong.
b19a08ec b1ff1253 fc415f88 b1ff1040 b19a0904 SAVRT+0x2f219
b19a0908 b1ff4c07 00000000 b19a09b0 b1ff4169 SAVRT+0x7253
b19a094c b2e2e268 e1068130 b19a09a8 00000001 SAVRT+0xac07
b19a0970 b2e30998 00000000 b19a09b0 b2e32426
SYMEVENT!SYMEvent_GetSubTask+0x1438
b19a09ec b2e2ad02 b19a0a30 e1cf702c b19a0a30

b2e254f4 b2e32660 b2e327f0 b2e327d0 00000000
SYMEVENT!SYMEvent_GetVMDataPtr+0x5562
b2e326e0 06c7384e b2e254f4 ff56018b c0331c50

b2e326e4 b2e254f4 ff56018b c0331c50 89384689 0x6c7384e
b2e326e8 ff56018b c0331c50 89384689 46894046 SYMEVENT+0x14f4
b2e326ec c0331c50 89384689 46894046 0446893c 0xff56018b
b2e326f0 89384689 46894046 0446893c 082444f6 0xc0331c50
b2e326f4 46894046 0446893c 082444f6 0c06c701 0x89384689
b2e326f8 0446893c 082444f6 0c06c701 74b2e244 0x46894046
b2e326fc 082444f6 0c06c701 74b2e244 15ff5607 0x446893c
b2e32700 0c06c701 74b2e244 15ff5607 b2e243e4 0x82444f6
b2e32704 74b2e244 15ff5607 b2e243e4 c25ec68b 0xc06c701
b2e32708 15ff5607 b2e243e4 c25ec68b 90900004 0x74b2e244
b2e3270c b2e243e4 c25ec68b 90900004 90909090 0x15ff5607
b2e32710 c25ec68b 90900004 90909090 8bf18b56 SYMEVENT+0x3e4
start end module name
804d7000 806eba80 nt ntoskrnl.exe Wed Mar 02 01:59:37 2005

806ec000 8070c380 hal halaacpi.dll Wed Aug 04 07:59:05 2004

b1ac1000 b1b01100 HTTP HTTP.sys Sat Oct 09 01:48:20 2004

b1e72000 b1e86400 wdmaud wdmaud.sys Wed Aug 04 08:15:03 2004

b1ed7000 b1efa000 Fastfat Fastfat.SYS Wed Aug 04 08:14:15 2004

b1f0a000 b1f18d80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004

b1fea000 b202a000 SAVRT SAVRT.SYS Thu Sep 18 22:22:55 2003

Opened log file 'c:\debuglog.txt'

Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini070205-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:
C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS\system32\drivers
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Sat Jul 2 02:26:40.875 2005 (GMT+2)
System Uptime: 0 days 13:34:51.438
Loading Kernel Symbols

Loading unloaded module list
...
Loading User Symbols

*
*
* Bugcheck Analysis
*
*
*

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8054aefc, b19a07f4, 0}

*** ERROR: Module load completed but symbols could not be loaded for

*** ERROR: Symbol file could not be found. Defaulted to export symbols

SYMEVENT.SYS -
Probably caused by : SAVRT.SYS ( SAVRT+2f219 )

Followup: MachineOwner


kd> !analyze -v;r;kv;lmtn;.logclose;q

*
*
* Bugcheck Analysis
*
*
*

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8054aefc, The address that the exception occurred at
Arg3: b19a07f4, Trap Frame
Arg4: 00000000

Debugging Details:



EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en "0x%08lx" hace
referencia a la memoria en "0x%08lx". La memoria no se puede "%s".

FAULTING_IP:
nt!ExAllocatePoolWithTag+772
8054aefc 8902 mov [edx],eax

TRAP_FRAME: b19a07f4 -- (.trap ffffffffb19a07f4)
.trap ffffffffb19a07f4
ErrCode = 00000002
eaxá0a46f0 ebx‚f0a050 ecx‚f0a0e8 edx350034 esiá0a4760

eip€54aefc esp±9a0868 ebp±9a08bc iopl=0 nv up ei pl nz na po

cs08 ss10 ds23 es23 fs30 gs00

nt!ExAllocatePoolWithTag+0x772:
8054aefc 8902 mov [edx],eax

.trap
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from b2019219 to 8054aefc

STACK_TEXT:
b19a08bc b2019219 00000001 0013000f 53646152

WARNING: Stack unwind information not available. Following frames may be
wrong.
b19a08ec b1ff1253 fc415f88 b1ff1040 b19a0904 SAVRT+0x2f219
b19a0908 b1ff4c07 00000000 b19a09b0 b1ff4169 SAVRT+0x7253
b19a094c b2e2e268 e1068130 b19a09a8 00000001 SAVRT+0xac07
b19a0970 b2e30998 00000000 b19a09b0 b2e32426
SYMEVENT!SYMEvent_GetSubTask+0x1438
b19a09ec b2e2ad02 b19a0a30 e1cf702c b19a0a30

b2e254f4 b2e32660 b2e327f0 b2e327d0 00000000
SYMEVENT!SYMEvent_GetVMDataPtr+0x5562
b2e326e0 06c7384e b2e254f4 ff56018b c0331c50

b2e326e4 b2e254f4 ff56018b c0331c50 89384689 0x6c7384e
b2e326e8 ff56018b c0331c50 89384689 46894046 SYMEVENT+0x14f4
b2e326ec c0331c50 89384689 46894046 0446893c 0xff56018b
b2e326f0 89384689 46894046 0446893c 082444f6 0xc0331c50
b2e326f4 46894046 0446893c 082444f6 0c06c701 0x89384689
b2e326f8 0446893c 082444f6 0c06c701 74b2e244 0x46894046
b2e326fc 082444f6 0c06c701 74b2e244 15ff5607 0x446893c
b2e32700 0c06c701 74b2e244 15ff5607 b2e243e4 0x82444f6
b2e32704 74b2e244 15ff5607 b2e243e4 c25ec68b 0xc06c701
b2e32708 15ff5607 b2e243e4 c25ec68b 90900004 0x74b2e244
b2e3270c b2e243e4 c25ec68b 90900004 90909090 0x15ff5607
b2e32710 c25ec68b 90900004 90909090 8bf18b56 SYMEVENT+0x3e4
b2e32714 90900004 90909090 8bf18b56 0000808e 0xc25ec68b
b2e32718 90909090 8bf18b56 0000808e 74c98500 0x90900004
b2e3271c 8bf18b56 0000808e 74c98500 e8006a07 0x90909090
b2e32720 00000000 74c98500 e8006a07 ffffbc0c 0x8bf18b56


FOLLOWUP_IP:
SAVRT+2f219
b2019219 85f6 test esi,esi

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: SAVRT+2f219

MODULE_NAME: SAVRT

IMAGE_NAME: SAVRT.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3f6a141f

STACK_COMMAND: .trap ffffffffb19a07f4 ; kb

FAILURE_BUCKET_ID: 0x8E_SAVRT+2f219

BUCKET_ID: 0x8E_SAVRT+2f219

Followup: MachineOwner


eaxá0a46f0 ebx‚f0a050 ecx‚f0a0e8 edx350034 esiá0a4760

eip€54aefc esp±9a0868 ebp±9a08bc iopl=0 nv up ei pl nz na po

cs08 ss10 ds23 es23 fs30 gs00

nt!ExAllocatePoolWithTag+0x772:
8054aefc 8902 mov [edx],eax

ChildEBP RetAddr Args to Child
b19a08bc b2019219 00000001 0013000f 53646152

(FPO: [Non-Fpo])
WARNING: Stack unwind information not available. Following frames may be
wrong.
b19a08ec b1ff1253 fc415f88 b1ff1040 b19a0904 SAVRT+0x2f219
b19a0908 b1ff4c07 00000000 b19a09b0 b1ff4169 SAVRT+0x7253
b19a094c b2e2e268 e1068130 b19a09a8 00000001 SAVRT+0xac07
b19a0970 b2e30998 00000000 b19a09b0 b2e32426
SYMEVENT!SYMEvent_GetSubTask+0x1438
b19a09ec b2e2ad02 b19a0a30 e1cf702c b19a0a30

b2e254f4 b2e32660 b2e327f0 b2e327d0 00000000
SYMEVENT!SYMEvent_GetVMDataPtr+0x5562
b2e326e0 06c7384e b2e254f4 ff56018b c0331c50

b2e326e4 b2e254f4 ff56018b c0331c50 89384689 0x6c7384e
b2e326e8 ff56018b c0331c50 89384689 46894046 SYMEVENT+0x14f4
b2e326ec c0331c50 89384689 46894046 0446893c 0xff56018b
b2e326f0 89384689 46894046 0446893c 082444f6 0xc0331c50
b2e326f4 46894046 0446893c 082444f6 0c06c701 0x89384689
b2e326f8 0446893c 082444f6 0c06c701 74b2e244 0x46894046
b2e326fc 082444f6 0c06c701 74b2e244 15ff5607 0x446893c
b2e32700 0c06c701 74b2e244 15ff5607 b2e243e4 0x82444f6
b2e32704 74b2e244 15ff5607 b2e243e4 c25ec68b 0xc06c701
b2e32708 15ff5607 b2e243e4 c25ec68b 90900004 0x74b2e244
b2e3270c b2e243e4 c25ec68b 90900004 90909090 0x15ff5607
b2e32710 c25ec68b 90900004 90909090 8bf18b56 SYMEVENT+0x3e4
start end module name
804d7000 806eba80 nt ntoskrnl.exe Wed Mar 02 01:59:37 2005

806ec000 8070c380 hal halaacpi.dll Wed Aug 04 07:59:05 2004

b1ac1000 b1b01100 HTTP HTTP.sys Sat Oct 09 01:48:20 2004

b1e72000 b1e86400 wdmaud wdmaud.sys Wed Aug 04 08:15:03 2004

b1ed7000 b1efa000 Fastfat Fastfat.SYS Wed Aug 04 08:14:15 2004

b1f0a000 b1f18d80 sysaudio sysaudio.sys Wed Aug 04 08:15:54 2004

b1fea000 b202a000 SAVRT SAVRT.SYS Thu Sep 18 22:22:55 2003