|
hola a todos alguien me ayuda con el resultado de windbg,
en la maquina aparece la pantalla azul de stop, al conectarme tarda unas horas en apagarse pero si me conecto con cualquier descargador de sp2( emule, utorrent, azureus, cualquiera.), se apaga a los minutos.
Microsoft ® Windows Debugger Version 6.9.0003.113 X86
Copyright © Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini070808-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 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 XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Tue Jul 8 01:29:09.890 2008 (GMT-3)
System Uptime: 0 days 0:06:34.577
*********************************************************************
* 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 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 NDIS.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for NDIS.sys
*** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
Unable to load image Sacm2A.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Sacm2A.sys
*** ERROR: Module load completed but symbols could not be loaded for Sacm2A.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000D1, {6, 2, 0, f7a25504}
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : Sacm2A.sys ( Sacm2A+cd8 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is todo high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000006, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f7a25504, address which referenced memory
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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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+ *
*********************************************************************
MODULE_NAME: Sacm2A
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 40c8573c
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000006
CURRENT_IRQL: 2
FAULTING_IP:
NDIS+3504
f7a25504 f6460605 test byte ptr [esi+6],5
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from a919acd8 to f7a25504
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f78ae8f0 a919acd8 00000000 f78ae910 f78ae930 NDIS+0x3504
f78ae914 a919ac46 897be248 890567d8 0000003e Sacm2A+0xcd8
f78ae954 a919ab2d 00000003 898ccb60 00000103 Sacm2A+0xc46
f7a25edd 084d8bec ff04518a a27e5415 04c25df7 Sacm2A+0xb2d
f7a25ee1 ff04518a a27e5415 04c25df7 90909000 0x84d8bec
f7a25ee5 a27e5415 04c25df7 90909000 ff8b9090 0xff04518a
f7a25ee9 04c25df7 90909000 ff8b9090 56ec8b55 0xa27e5415
f7a25eed 90909000 ff8b9090 56ec8b55 8b08758b 0x4c25df7
f7a25ef1 ff8b9090 56ec8b55 8b08758b f815ffce 0x90909000
f7a25ef5 56ec8b55 8b08758b f815ffce c6f7a27d 0xff8b9090
f7a25ef9 8b08758b f815ffce c6f7a27d 5e020446 0x56ec8b55
f7a25efd f815ffce c6f7a27d 5e020446 0004c25d 0x8b08758b
f7a25f01 c6f7a27d 5e020446 0004c25d 90909090 0xf815ffce
f7a25f05 5e020446 0004c25d 90909090 55ff8b90 0xc6f7a27d
f7a25f09 0004c25d 90909090 55ff8b90 4d8bec8b 0x5e020446
f7a25f0d 90909090 55ff8b90 4d8bec8b fc15ff08 0x4c25d
f7a25f11 55ff8b90 4d8bec8b fc15ff08 5df7a27d 0x90909090
f7a25f15 4d8bec8b fc15ff08 5df7a27d 900004c2 0x55ff8b90
f7a25f19 fc15ff08 5df7a27d 900004c2 90909090 0x4d8bec8b
f7a25f1d 5df7a27d 900004c2 90909090 8b55ff8b 0xfc15ff08
f7a25f21 900004c2 90909090 8b55ff8b 25ff5dec 0x5df7a27d
f7a25f25 90909090 8b55ff8b 25ff5dec f7a27e1c 0x900004c2
f7a25f29 8b55ff8b 25ff5dec f7a27e1c 90909090 0x90909090
f7a25f2d 25ff5dec f7a27e1c 90909090 55ff8b90 0x8b55ff8b
f7a25f31 f7a27e1c 90909090 55ff8b90 8b56ec8b 0x25ff5dec
f7a25f35 90909090 55ff8b90 8b56ec8b 8b570875 NDIS+0x5e1c
f7a25f39 55ff8b90 8b56ec8b 8b570875 c0330c7d 0x90909090
f7a25f3d 8b56ec8b 8b570875 c0330c7d 1c74f83b 0x55ff8b90
f7a25f41 8b570875 c0330c7d 1c74f83b 050646f6 0x8b56ec8b
f7a25f45 c0330c7d 1c74f83b 050646f6 468b0574 0x8b570875
f7a25f49 1c74f83b 050646f6 468b0574 ff0feb0c 0xc0330c7d
f7a25f4d 050646f6 468b0574 ff0feb0c 50501475 0x1c74f83b
f7a25f51 468b0574 ff0feb0c 50501475 5650016a 0x50646f6
f7a25f55 ff0feb0c 50501475 5650016a 7c7015ff 0x468b0574
f7a25f59 50501475 5650016a 7c7015ff 0789f7a2 0xff0feb0c
f7a25f5d 5650016a 7c7015ff 0789f7a2 8b14468b 0x50501475
f7a25f61 7c7015ff 0789f7a2 8b14468b 895f104d 0x5650016a
f7a25f65 0789f7a2 8b14468b 895f104d c25d5e01 0x7c7015ff
f7a25f69 8b14468b 895f104d c25d5e01 90900010 0x789f7a2
f7a25f6d 895f104d c25d5e01 90900010 8b909090 0x8b14468b
f7a25f71 c25d5e01 90900010 8b909090 ec8b55ff 0x895f104d
f7a25f75 90900010 8b909090 ec8b55ff 5608458b 0xc25d5e01
f7a25f79 8b909090 ec8b55ff 5608458b 8508708b 0x90900010
f7a25f7d ec8b55ff 5608458b 8508708b 0c458bf6 0x8b909090
f7a25f81 5608458b 8508708b 0c458bf6 35743089 0xec8b55ff
f7a25f85 8508708b 0c458bf6 35743089 050646f6 0x5608458b
f7a25f89 0c458bf6 35743089 050646f6 468b0574 0x8508708b
f7a25f8d 35743089 050646f6 468b0574 6a09eb0c 0xc458bf6
f7a25f91 050646f6 468b0574 6a09eb0c 15ff5600 0x35743089
f7a25f95 468b0574 6a09eb0c 15ff5600 f7a27c44 0x50646f6
f7a25f99 6a09eb0c 15ff5600 f7a27c44 8b104d8b 0x468b0574
f7a25f9d 15ff5600 f7a27c44 8b104d8b 01891455 0x6a09eb0c
f7a25fa1 f7a27c44 8b104d8b 01891455 8b14468b 0x15ff5600
f7a25fa5 8b104d8b 01891455 8b14468b 0189184d NDIS+0x5c44
f7a25fa9 01891455 8b14468b 0189184d 05eb0289 0x8b104d8b
f7a25fad 8b14468b 0189184d 05eb0289 0114468b 0x1891455
f7a25fb1 0189184d 05eb0289 0114468b 85368b01 0x8b14468b
f7a25fb5 05eb0289 0114468b 85368b01 ebf575f6 0x189184d
f7a25fb9 0114468b 85368b01 ebf575f6 10458b12 0x5eb0289
f7a25fbd 85368b01 ebf575f6 10458b12 8b002083 0x114468b
f7a25fc1 ebf575f6 10458b12 8b002083 20831445 0x85368b01
f7a25fc5 10458b12 8b002083 20831445 18458b00 0xebf575f6
f7a25fc9 8b002083 20831445 18458b00 5e002083 0x10458b12
f7a25fcd 20831445 18458b00 5e002083 0014c25d 0x8b002083
f7a25fd1 18458b00 5e002083 0014c25d 90909090 0x20831445
f7a25fd5 5e002083 0014c25d 90909090 55ff8b90 0x18458b00
f7a25fd9 0014c25d 90909090 55ff8b90 458bec8b 0x5e002083
f7a25fdd 90909090 55ff8b90 458bec8b 708b5608 0x14c25d
f7a25fe1 55ff8b90 458bec8b 708b5608 0c458b08 0x90909090
f7a25fe5 458bec8b 708b5608 0c458b08 3bff3357 0x55ff8b90
f7a25fe9 708b5608 0c458b08 3bff3357 743089f7 0x458bec8b
f7a25fed 0c458b08 3bff3357 743089f7 0046f63b 0x708b5608
f7a25ff1 3bff3357 743089f7 0046f63b 00000000 0xc458b08
f7a25ff5 743089f7 0046f63b 00000000 00000000 0x3bff3357
3bff3357 00000000 00000000 00000000 00000000 0x743089f7
STACK_COMMAND: kb
FOLLOWUP_IP:
Sacm2A+cd8
a919acd8 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: Sacm2A+cd8
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: Sacm2A.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
1: kd> lmvm Sacm2A
start end module name
a919a000 a919d800 Sacm2A T (no symbols)
Loaded symbol image file: Sacm2A.sys
Image path: Sacm2A.sys
Image name: Sacm2A.sys
Timestamp: Thu Jun 10 09:42:36 2004 (40C8573C)
CheckSum: 0000EFC0
ImageSize: 00003800
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
|
reinicio de winxp_ windbg, alguien me ayuda con el resultado del windbg
Jul 9 2008, 05:03 PM
