Pantalla azul windows 7 64 bits [Cerrado]

Denunciar
Message postés
3
Date d'inscription
martes, 22 de enero de 2013
Estatus
Miembro
Última intervención
martes, 26 de febrero de 2013
-
Log4n
Message postés
925
Date d'inscription
miércoles, 19 de noviembre de 2008
Estatus
Contribuidor
Última intervención
viernes, 26 de febrero de 2016
-
Hola,

Estoy teniendo problemas de pantalla azul he checado mis dos memorias ram de 4gb cada una por separado durante 7 horas con memtest y no dio ni un error y 0 errores.

Comprobé el estado del disco duro con crystaldiskinfo y es bueno.

Pasé antimalware y todo bien

Estos son los datos de windbg y pc wizard


Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\012213-55395-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 \SystemRoot\system32\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 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800'02c13000 PsLoadedModuleList = 0xfffff800'02e57670
Debug session time: Tue Jan 22 10:06:05.486 2013 (UTC - 6:00)
System Uptime: 0 days 0:23:52.015
*********************************************************************
* 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 \SystemRoot\system32\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
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffc000009d1eb, 2, 0, fffff80002d367ef}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : ntoskrnl.exe ( nt+1237ef )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffc000009d1eb, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002d367ef, 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: nt

FAULTING_MODULE: fffff80002c13000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 503f82be

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
fffffc000009d1eb

CURRENT_IRQL: 0

FAULTING_IP:
nt+1237ef
fffff800'02d367ef 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from fffff80002c91569 to fffff80002c91fc0

STACK_TEXT:
fffff880'085945a8 fffff800'02c91569 : 00000000'0000000a fffffc00'0009d1eb 00000000'00000002 00000000'00000000 : nt+0x7efc0
fffff880'085945b0 00000000'0000000a : fffffc00'0009d1eb 00000000'00000002 00000000'00000000 fffff800'02d367ef : nt+0x7e569
fffff880'085945b8 fffffc00'0009d1eb : 00000000'00000002 00000000'00000000 fffff800'02d367ef 00000000'00000000 : 0xa
fffff880'085945c0 00000000'00000002 : 00000000'00000000 fffff800'02d367ef 00000000'00000000 00000000'00000000 : 0xfffffc00'0009d1eb
fffff880'085945c8 00000000'00000000 : fffff800'02d367ef 00000000'00000000 00000000'00000000 00000000'00000000 : 0x2


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt+1237ef
fffff800'02d367ef 440fb6421b movzx r8d,byte ptr [rdx+1Bh]

SYMBOL_NAME: nt+1237ef

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------


PC Wizard 2010 Versión 1.961
------------------------------------------------------------------------------------------

Owner: CIBER
User: CIBER
Computer Name: CIBER-PC
Sistema Operativo: Windows 7 Ultimate Professional Media Center 6.01.7601 Service Pack 1
Report Date: martes 22 enero 2013at 10:58

------------------------------------------------------------------------------------------


<<< Resumen del Sistema >>>
> Mainboard : Gigabyte G41MT-S2
> Chipset : Intel G41
> Processor : Intel Core 2 Duo E7500 @ 2933MHz
> Physical Memory : 8192MB (2 x 4096 DDR3-SDRAM )
> Video Card : Intel(R) G41 Express Chipset
> Hard Disk : Hitachi HCT721016SLA380 ATA Device (160GB)
> DVD-Rom Drive : ATAPI iHAS122
> Monitor Type : AOC International 2243W - 22 inches
> Network Card : Attansic (Now owned by Atheros) AR8151 v1.0 Gigabit Ethernet
> Network Card : Atheros Communications AR5007G Wireless Network Adapter
> Sistema Operativo : Windows 7 Ultimate Professional Media Center 6.01.7601 Service Pack 1 (64-bit)
> DirectX : Versión 11.00
> Windows Performance Index : 3.5 on 7.9

A que se debe este pantallazo azul?

4 respuestas

Message postés
3
Date d'inscription
martes, 22 de enero de 2013
Estatus
Miembro
Última intervención
martes, 26 de febrero de 2013
1
Hola de nuevo, cambié el disco duro y la ram y durante unos 20 dias no dio problema alguno pero de nuevo desde ayer me esta volviendo a dar problemas
bug check code 0x00000109
caused by driver ntoskrnl.exe
caused by adress ntoskrnl.exe+7b580
ayer tambien me dio uno con el hal.dll
Porfavor alguien me puede ayudar? ya no se que pueda ser, no he instalado nada ultimamente salvo un quemador adicional pero durante muchos dias que ha estado instalado no ha dado problema. La mother tampoco puede ser porque probé con otra y me pasa lo mismo.
1
Gracias

Unas palabras de agradecimiento nunca están de más. Deja tu comentario

CCM 43779 usuarios nos han dicho gracias este mes

Message postés
925
Date d'inscription
miércoles, 19 de noviembre de 2008
Estatus
Contribuidor
Última intervención
viernes, 26 de febrero de 2016
2.059
Probaste actualizando los drivers y la bios de tu mother ? Otra opcion sería que pruebes win7 en 32 bits con solo 4 Gb de ram. Para ver si el problema persiste.
1
Gracias

Unas palabras de agradecimiento nunca están de más. Deja tu comentario

CCM 43779 usuarios nos han dicho gracias este mes

Message postés
3420
Date d'inscription
viernes, 12 de octubre de 2012
Estatus
Contribuidor
Última intervención
jueves, 29 de diciembre de 2016
1.208
Los pantallazos azules por lo general son causados por conflicto o incompatibilidad de drivers y aplicaciones.............Ten en cuenta si Instalaste o modificaste algo en el sistema antes de esto sucediera.
Hola, instalé una maquina virtual' ? será por eso ?
Message postés
3
Date d'inscription
martes, 22 de enero de 2013
Estatus
Miembro
Última intervención
martes, 26 de febrero de 2013
1
hace mucho que me esta pasando la verdad no se que pueda ser, no hay alguna manera de ver con algun programa o aplicacion cual es el que causa el problema?
Sirr
Message postés
3420
Date d'inscription
viernes, 12 de octubre de 2012
Estatus
Contribuidor
Última intervención
jueves, 29 de diciembre de 2016
1.208
En el reporte veo muchos errores de sistema lo cual indicaría sistema corrupto. Te sugiero que restaures sistema a la fecha más antigua.