| pumuki713 |  |
|
2007-01-08 15:55 - Respuestas: 2 - Tema nº: 2430644
Características: Windows XP Profesional, amd sempron 3000+ , 1gb de ram ,160 gb de HD.
Buenas,
hace 15 días me tuvieron que cambiar el procesador porque peto. Me han colocado un amd seprom 3000+. ´Lo que me pasa es que sin hacer nada , es decir, dejando el ordenado encendido sin más se me queda colgado error grave pantalla azul y a reiniciar, pero no sigue un patrón determinado porque pensaba que era solo cuando jugaba a juegos pero no, también cuando solo navego por internet.
No se que hacer , lo unico que puedo poneros es los detalles del error sacados con el windbg.Gracias de antemano:
Microsoft (R) Windows Debugger Version 6.6.0007.5
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: *** 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 tosymbol 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlpa.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Jan 8 14:36:21.687 2007 (GMT+1)
System Uptime: 0 days 2:04:38.255
*********************************************************************
* 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 argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlpa.exe -
Loading Kernel Symbols
...........
Loading User Symbols
Loading unloaded module list
...........
*** ERROR: Symbol file could not be found. Defaulted to export symbols for tcpip.sys -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {6dfb63f8, 2, 0, aaf782b6}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for psched.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for NDIS.sys -
*** ERROR: Module load completed but symbols could not be loaded for ndiswan.sys
*** ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
Probably caused by : ndiswan.sys ( ndiswan+dc59 )
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: 6dfb63f8, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: aaf782b6, address which referenced memory
Debugging Details:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
MODULE_NAME: ndiswan
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 41107ec6
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
6dfb63f8
CURRENT_IRQL: 2
FAULTING_IP:
tcpip!IPTransmit+678
aaf782b6 ff5608 call dword ptr [esi+8]
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from aaf782b6 to 8053f853
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
80548868 aaf782b6 badb0d00 8054891c 805488d4 nt!Kei386EoiHelper+0x27db
80548a14 aaf795f8 aafb6698 00000000 8575d9c0 tcpip!IPTransmit+0x678
80548a60 aaf7d247 026b3c10 00000000 00000000 tcpip!IPTransmit+0x19ba
80548a80 aaf75a08 00000002 00000002 80548aac tcpip!ARPRcv+0x2dd4
80548ab4 aaf7594f 00000002 aaf75901 aaf753d6 tcpip!ARPRcvPacket+0x20e
80548b20 ef40c01d 00620208 864a2548 00000001 tcpip!ARPRcvPacket+0x155
80548b34 ef40c1b4 86460130 864a2548 00000001 psched!RegisterPsComponent+0x6cef
80548b58 ef40c5f9 86393c38 00000000 86460130 psched!RegisterPsComponent+0x6e86
80548b70 f733ed40 86393c30 85742988 8647f888 psched!RegisterPsComponent+0x72cb
80548bc0 ef422c59 00620208 80548c00 00000001 NDIS!FddiFilterDprIndicateReceive+0xb48
80548bf4 ef422f15 0247f888 8584e9a0 8647f888 ndiswan+0xdc59
80548c28 ef4233c2 8647f888 858e6008 000004b2 ndiswan+0xdf15
80548c44 ef420e51 859489f0 858e6008 8643c618 ndiswan+0xe3c2
80548c68 f73398f5 00000001 861e5d8e 000004b2 ndiswan+0xbe51
80548c8c f29ca979 80548cb4 024ff130 00000001 NDIS!NdisMWanIndicateReceive+0x54
80548cc4 f29cfe9d 85852d50 85852ac8 00000000 raspppoe+0x1979
80548ce4 804ff234 f29d2028 f29d1fe0 fbf09ff8 raspppoe+0x6e9d
80548e00 804ff34b 80551b80 80551920 ffdff000 nt!ZwYieldExecution+0xa08
80548e2c 80540d5d 80551f80 00000000 00074d8f nt!ZwYieldExecution+0xb1f
80548e50 80540cd6 00000000 0000000e 00000000 nt!KiDispatchInterrupt+0x35d
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2d6
STACK_COMMAND: kb
FOLLOWUP_IP:
ndiswan+dc59
ef422c59 8a4d0b mov cl,byte ptr [ebp+0Bh]
SYMBOL_STACK_INDEX: a
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ndiswan.sys
SYMBOL_NAME: ndiswan+dc59
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
-
Comentarios adicionales: El problema surgió justo despues de agregar o quitar hardware en el PC. | |
|
|
| pumuki713 | |
|
Re: Error pantalla azul error grave - 2007-01-08 16:18 - Respuesta 2
Ahora tampoc me deja jugar a los juegos. Cuando estoy unos 5 minutos me dice que un error grave se ha producido y el programa debe cerrarse. Por lo menos no se queda colgado el ordenador solo me echa del juego.
Ah por cierto he formateado el ordenador por si era eso pero no ha funcionado. gracias | |
|
|
| caterpilar |  |
|
Re: Error pantalla azul error grave - 2007-01-08 16:48 - Respuesta 3
Hola pumiki713, puede que el problema se encuentre en la configuración de la bios, al cambiar el micro usando la misma placa base, hay configuraciones que deben respetarse para que todo funcione correctamente, consulta con tu técnico de confianza..............Un abrazo. | |
|
|
|
