Hola
Últimamente estoy sufriendo algunos pantallazos azules aleatoriamente,
y siempre es al inicio, cuando se está cargando Windows xp, pero
repito que son aleatorios, hay veces que no salen y el sistema inicia
bién. Me explico. No siempre salen, pero de 10 veces que enciendo el
ordenador, 7 sale la pantalla azul. Los errores que me indica la
pantalla no son siempre los mismos y eso es lo que me despista.
Otra cosa que también me despista es que siempre es al iniciarse
windows, y una vez reiniciado, el sistema trabaja perfectamente,
pudiéndolo reiniciar las veces que quiera sin que de error. Osea,
apago el ordenador y al día siguiente en frío, es cuando sale el error
de pantalla azul, pero si reinicio, va muy bien y no me da ningún
problema durante todo el día...
Siguiendo las indicaciones de José Manuel Tella Llop en
http://multingles.net/docs/jmt/bsod.htm
esto es lo que me sale al analizar MEMORY.DMP :
(Aclaro que posteriormente he tenido un par más de pantallazos pero no
me ha hecho el volcado de memoria a MEMORY.DMP...)
Muchísimas gracias y saludos.
Microsoft (R) Windows Debugger Version 6.5.0003.7
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available
Symbol search path is: SRV*c:\simbolos*
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.051011-1528
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a520
Debug session time: Fri Feb 16 13:42:59.717 2007 (GMT+1)
System Uptime: 0 days 0:27:12.289
Loading Kernel Symbols
...
Loading unloaded module list
.
Loading User Symbols
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 8E, {c0000005, 8058b991, f31b08bc, 0}
Probably caused by : ntoskrnl.exe ( nt!CmpGetNameControlBlock+a6 )
Followup: MachineOwner
kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
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: 8058b991, The address that the exception occurred at
Arg3: f31b08bc, 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!CmpGetNameControlBlock+a6
8058b991 3b07 cmp eax,[edi]
TRAP_FRAME: f31b08bc -- (.trap fffffffff31b08bc)
ErrCode = 00000000
eaxE2ea87a ebx=f31b0968 ecx=e100b000 edx 000686 esi=e14efb99
edi000000
eip58b991 esp=f31b0930 ebp=f31b0950 iopl=0 nv up ei pl nz
na po nc
cs 08 ss 10 ds 23 es 23 fs 30 gs 00
efl 010206
nt!CmpGetNameControlBlock+0xa6:
8058b991 3b07 cmp eax,[edi] ds:
0023:08000000=????????
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
LOCK_ADDRESS: 80558560 -- (!locks 80558560)
Resource @ nt!PiEngineLock (0x80558560) Available
Contention Count = 1
1 total locks
PNP_TRIAGE:
Lock address : 0x80558560
Thread Count : 0
Thread address: 0x00000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from 8058b7b1 to 8058b991
STACK_TEXT:
f31b0950 8058b7b1 011b0968 e1bd5170 e140c008 nt!CmpGetNameControlBlock
+0xa6
f31b0974 8058b440 e140c008 00bf3998 c36b499c nt!
CmpCreateKeyControlBlock+0x1be
f31b09c4 8058af86 e140c008 00bf3998 c36b499c nt!
CmpAddInfoAfterParseFailure+0x2ff
f31b0ba0 8056326c 00bf3998 ffffffff ffb594b0 nt!CmpParseKey+0x646
f31b0c28 8056739a 00000000 f31b0c68 00000040 nt!ObpLookupObjectName
+0x56a
f31b0c7c 80567cfd 00000000 81340040 ffffff01 nt!ObOpenObjectByName
+0xeb
f31b0d50 804de7ec 00bbdee0 80000000 00bbdbd0 nt!NtOpenKey+0x1af
f31b0d50 7c91eb94 00bbdee0 80000000 00bbdbd0 nt!KiFastCallEntry+0xf8
00bbdbb0 7c91dd48 7c92d284 00bbdee0 80000000 ntdll!KiFastSystemCallRet
00bbdbb4 7c92d284 00bbdee0 80000000 00bbdbd0 ntdll!ZwOpenKey+0xc
00bbdec4 7c92d369 00bbe264 00bbdee0 00000800 ntdll!
LdrpOpenImageFileOptionsKey+0xf7
00bbded8 7c8190e9 00000000 7c81a1dc 00000001 ntdll!
LdrQueryImageFileExecutionOptions+0x12
00bbe91c 77dc7838 00000430 00000000 00bbf0e4 kernel32!
CreateProcessInternalW+0xfe0
00bbe970 7dbc073c 00000430 00000000 00bbf0e4 ADVAPI32!
CreateProcessAsUserW+0x153
00bbf358 7dbc0b7a 00000000 00bbf38c 003b5d70 umpnpmgr!
CreateDeviceInstallClient+0x383
00bbf3ac 7dbc1314 003b5d70 00bbf4a0 00000005 umpnpmgr!
DoDeviceInstallClient+0xc9
00bbff18 7dbb9cf9 003b5d70 7dbcc1dc 00bbff64 umpnpmgr!
InstallDeviceServerSide+0x12b
00bbffb4 7c80b683 00000000 7c9263a8 00b7feb8 umpnpmgr!
ThreadProc_DeviceInstall+0x45f
00bbffec 00000000 7dbb5d5b 00000000 00000000 kernel32!BaseThreadStart
+0x37
FOLLOWUP_IP:
nt!CmpGetNameControlBlock+a6
8058b991 3b07 cmp eax,[edi]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!CmpGetNameControlBlock+a6
MODULE_NAME: nt
IMAGE_NAME: ntoskrnl.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 434c56bb
STACK_COMMAND: .trap fffffffff31b08bc ; kb
FAILURE_BUCKET_ID: 0x8E_nt!CmpGetNameControlBlock+a6
BUCKET_ID: 0x8E_nt!CmpGetNameControlBlock+a6
Followup: MachineOwner
Últimos mensajes - Powered by IBM
Palabras claves
Hacer una pregunta
Siga el debate
Tengo una respuesta
Busqueda sugerida
Martes 14 de mayo - 07:32
Registrar
Leer las respuestas