Ayuda con WinDbg, auxiliooooo Por favor Tengo pantallazos azules, que por motivo de seguridad Win se apagara,
les dejo el WinDbg, para ver que ven y me ayudan:
Gracias y saludos.
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp.050301-1521
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed May 21 21:06:58.968 2008 (GMT-5)
System Uptime: 0 days 3:34:43.533
Loading Kernel Symbols
.................................................. .................................................. .................
Loading unloaded module list
.................
Loading User Symbols
.................................................. .................................................. ..............
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {f9c46328, 2, 0, f9c46328}
*** ERROR: Module load completed but symbols could not be loaded for alcaudsl.sys
*** ERROR: Module load completed but symbols could not be loaded for alcan5wn.sys
Probably caused by : alcaudsl.sys ( alcaudsl+2f14 )
Followup: MachineOwner
---------
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 too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: f9c46328, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f9c46328, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: f9c46328
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_ComputeAllocatedBandwidth+0
f9c46328 ?? ???
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from f9c2b12a to f9c46328
TRAP_FRAME: fa2c7cf4 -- (.trap fffffffffa2c7cf4)
ErrCode = 00000000
eax=00002ee0 ebx=81211028 ecx=812322e0 edx=00000000 esi=812110ec edi=fa2c7da8
eip=f9c46328 esp=fa2c7d68 ebp=fa2c7d84 iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00210246
USBPORT!USBPORT_ComputeAllocatedBandwidth:
f9c46328 ?? ???
Resetting default scope
STACK_TEXT:
fa2c7d64 f9c2b12a 81211028 81166618 ff9bab38 USBPORT!USBPORT_ComputeAllocatedBandwidth
fa2c7d84 fa0fef14 81166618 00000000 3176656c USBPORT!USBPORT_BusQueryBusInformation+0x15a
WARNING: Stack unwind information not available. Following frames may be wrong.
fa2c7dc4 fa0fef7f ff9b1030 ff94d044 ff94d000 alcaudsl+0x2f14
fa2c7de0 fa10dcb6 ff9b1030 00000001 fa10dcbe alcaudsl+0x2f7f
fa2c7e08 fa10e5d1 ff94d000 00000001 fa10e5d6 alcan5wn+0x1cb6
fa2c7e20 fa10e6bd ff94d000 ff94d3e8 ff94d3e8 alcan5wn+0x25d1
fa2c7e3c fa10e421 ff94d000 ffaef9f0 ff94d000 alcan5wn+0x26bd
ff94d000 ff94d000 ff94d000 fa116c80 fa10c3d8 alcan5wn+0x2421
ffaef9f0 00000000 ffac68a0 ff94d000 005e005c 0xff94d000
FAILED_INSTRUCTION_ADDRESS:
USBPORT!USBPORT_ComputeAllocatedBandwidth+0
f9c46328 ?? ???
FOLLOWUP_IP:
alcaudsl+2f14
fa0fef14 8b45e4 mov eax,[ebp-0x1c]
SYMBOL_STACK_INDEX: 2
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: alcaudsl+2f14
MODULE_NAME: alcaudsl
IMAGE_NAME: alcaudsl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 3fd45837
STACK_COMMAND: .trap fffffffffa2c7cf4 ; kb
FAILURE_BUCKET_ID: 0xD1_CODE_AV_BAD_IP_alcaudsl+2f14
BUCKET_ID: 0xD1_CODE_AV_BAD_IP_alcaudsl+2f14
Followup: MachineOwner
---------
Este es otro el mini dump:
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\Administrador\Mis documentos\Mini052108-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \WINDOWS\system32\TUKERNEL.EXE, Win32 error 2
*** WARNING: Unable to verify timestamp for TUKERNEL.EXE
*** ERROR: Module load completed but symbols could not be loaded for TUKERNEL.EXE
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a420
Debug session time: Wed May 21 21:06:58.968 2008 (GMT-5)
System Uptime: 0 days 3:34:43.533
Unable to load image \WINDOWS\system32\TUKERNEL.EXE, Win32 error 2
*** WARNING: Unable to verify timestamp for TUKERNEL.EXE
*** ERROR: Module load completed but symbols could not be loaded for TUKERNEL.EXE
Loading Kernel Symbols
.................................................. .................................................. .................
Loading unloaded module list
.................
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {f9c46328, 2, 0, f9c46328}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
Probably caused by : USBPORT.SYS ( USBPORT!USBPORT_ComputeAllocatedBandwidth+0 )
Followup: MachineOwner
---------
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 too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: f9c46328, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f9c46328, address which referenced memory
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: USBPORT
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
f9c46328
CURRENT_IRQL: 2
FAULTING_IP:
USBPORT!USBPORT_ComputeAllocatedBandwidth+0
f9c46328 8bff mov edi,edi
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 00000000 to 804e187f
STACK_TEXT:
fa2c7cd8 00000000 f9c46328 00000002 00000000 nt+0xa87f
STACK_COMMAND: .bugcheck ; kb
FAILED_INSTRUCTION_ADDRESS:
USBPORT!USBPORT_ComputeAllocatedBandwidth+0
f9c46328 8bff mov edi,edi
FOLLOWUP_IP:
USBPORT!USBPORT_ComputeAllocatedBandwidth+0
f9c46328 8bff mov edi,edi
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: USBPORT!USBPORT_ComputeAllocatedBandwidth+0
IMAGE_NAME: USBPORT.SYS
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
