| Snon |  |
|
2010-04-04 19:37 - Respuestas: 1 - Tema nº: 2675592
Windows 7 Windows 7 Ultimate 32 bit, 4GB RAM, 2 discos duros u.
Saludos, mi problema es que luego de cambiar de XP a 7, la computadora se reinicia automátiamente en cualquier momento, se traba o congela y no responde el mouse o teclado, o se reinicia y aparece la Blue Screen. Ya no sé qué hacer porque según estuve buscando podría ser muchas cosas, primero pensé que era la tarjeta de vídeo porque las primeras veces me pasó esto cuando estaba viendo videos online, videos guardados en la computadora y jugando. Ahora sucede en cualquier momento, pero más cuando veo los videos. Windows 7 Ultimate 32 bit, 4GB RAM, 2 discos duros uno de 111GB y otro de 298GB, tarjeta de vídeo de Nvidia GeForce 7300 SE/ 7200 GS, AMD Athlon 64x2 Dual Core Processor 5200+. Según ya actualicé los drivers de la tarjeta de memoria y desfragmenté los discos que necesitaban, también busqué errores en los discos y nada.
Lo que aparece luego de la Blue Screen es lo siguiente (pude copiar dos y los asteriscos los pongo para diferenciar):
***
Firma con problemas:
Nombre del evento de problema: BlueScreen
Versión del sistema operativo: 6.1.7600.2.0.0.256.1
Id. de configuración regional: 2058
Información adicional del problema:
BCCode: 19
BCP1: 00000003
BCP2: 81F78B78
BCP3: 43ACB826
BCP4: 1C00FFFF
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Archivos que ayudan a describir el problema:
C:\Windows\Minidump\040310-27877-01.dmp
C:\Users\GERAR\AppData\Local\Temp\WER-51589-0.sysdata.xml
***
Firma con problemas:
Nombre del evento de problema: BlueScreen
Versión del sistema operativo: 6.1.7600.2.0.0.256.1
Id. de configuración regional: 2058
Información adicional del problema:
BCCode: 1000007e
BCP1: C0000005
BCP2: 8AC25E37
BCP3: 8B983AEC
BCP4: 8B9836D0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Archivos que ayudan a describir el problema:
C:\Windows\Minidump\040410-20904-01.dmp
C:\Users\GERAR\AppData\Local\Temp\WER-33259-0.sysdata.xml
Comentarios adicionales: El problema surgió justo despues de instalar un programa. | |
|
|
| Snon | |
|
Re: Blue Screen en computadora recién instalado Windows7 - 2010-04-05 00:18 - Respuesta 2
Hola, primero que nada muchas gracias por tu ayuda, mira entré a la carpeta que según estaba el archivo *.dmp pero no hay nada! no recuerdo haberlos borrado porque ni los había buscado, de todas maneras busqué todos los archivos con esa extensión y me salieron varios, casi todos relacionados con el juego con el que probé la máquina: ANNO 1404. otro más me pareció diferente: 040410-20904-01.dmp
Hice lo que indicaste en tu manual y mira lo que me salió:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\GERAR\AppData\Local\Microsoft\Windows\WER\ReportQueue\Kernel_0_0_cab_04c5cd2d\040310-15880-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x82a0b000 PsLoadedModuleList = 0x82b53810
Debug session time: Sat Apr 3 14:31:54.662 2010 (UTC - 5:00)
System Uptime: 0 days 2:43:47.519
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
.........
..........
..
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {c, 4, 0, 8b3522bd}
***** 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 ***
*** ***
*************************************************************************
Probably caused by : ndis.sys ( ndis!ndisMiniportIsr+d )
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 too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000004, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8b3522bd, 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ndis
FAULTING_MODULE: 82a0b000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf58
READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
0000000c
CURRENT_IRQL: 0
FAULTING_IP:
ndis!ndisMiniportIsr+d
8b3522bd 8b7d0c mov edi,dword ptr [ebp+0Ch]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 8b3522bc to 82a5185b
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
807e0b70 8b3522bc badb0d00 00000052 8718a2d4 nt+0x4685b
807e0c44 82e2311d ffd080f0 807c4120 00000000 ndis!ndisMiniportIsr+0xc
807e0c64 868d5068 00000000 807c4120 ffffffff hal!HalpHpetQueryCount+0x4b
807e0c68 00000000 807c4120 ffffffff 017d7840 0x868d5068
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
ndis!ndisMiniportIsr+d
8b3522bd 8b7d0c mov edi,dword ptr [ebp+0Ch]
SYMBOL_NAME: ndis!ndisMiniportIsr+d
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ndis.sys
BUCKET_ID: WRONG_SYMBOLS
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 too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000004, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 8b3522bd, 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 ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: ndis
FAULTING_MODULE: 82a0b000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf58
READ_ADDRESS: 0000000c
CURRENT_IRQL: 0
FAULTING_IP:
ndis!ndisMiniportIsr+d
8b3522bd 8b7d0c mov edi,dword ptr [ebp+0Ch]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xD1
LAST_CONTROL_TRANSFER: from 8b3522bc to 82a5185b
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
807e0b70 8b3522bc badb0d00 00000052 8718a2d4 nt+0x4685b
807e0c44 82e2311d ffd080f0 807c4120 00000000 ndis!ndisMiniportIsr+0xc
807e0c64 868d5068 00000000 807c4120 ffffffff hal!HalpHpetQueryCount+0x4b
807e0c68 00000000 807c4120 ffffffff 017d7840 0x868d5068
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
ndis!ndisMiniportIsr+d
8b3522bd 8b7d0c mov edi,dword ptr [ebp+0Ch]
SYMBOL_NAME: ndis!ndisMiniportIsr+d
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ndis.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
-
1: kd>
1: kd> !IRP 0000000c
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
0000000c: Could not read Irp
1: kd> !IRP 0000000c
*************************************************************************
*** ***
*** ***
*** 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!_IRP ***
*** ***
*************************************************************************
0000000c: Could not read Irp
Haré lo mismo con los otros archivos porque en serio que no sé por qué no están los otros archivos. Por cierto, tiene algo que ver que me indique la compu que tengo 4GB en RAM pero sólo 3 GB utilizable??
| |
|
|
|
