ayuda con pantalla azul

tengo esta pc y tenia el xp 2009 desde hace 2 años que comenzo a tener pantallazo azules quedando sin respuesta(solo con reset); instale el expertos y me sigue el mismo problema.(no instale ningun nuevo hard)
Agradeceria si alguien me puede ayudar.
Gracias

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\Mini072110-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 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 XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0
Debug session time: Wed Jul 21 20:43:59.828 2010 (GMT+2)
System Uptime: 0 days 0:08:35.500
*********************************************************************
* 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 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 1000000A, {98dc9bdc, 1c, 1, 804e1642}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+a642 )

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: 98dc9bdc, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, 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: 804e1642, 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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+ *
*********************************************************************
*********************************************************************
* 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+ *
*********************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b7a9491

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
98dc9bdc

CURRENT_IRQL: 1c

FAULTING_IP:
nt+a642
804e1642 095154 or dword ptr [ecx+54h],edx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 804e5e2c to 804e1642

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
a7fc47f0 804e5e2c 00000001 00000000 00000000 nt+0xa642
a7fc480c 8057069b 89a8fd48 00000001 00000000 nt+0xee2c
a7fc4864 804dd99f 00000e74 00000000 016cda7c nt+0x9969b
a7fc493c 804e1454 fe38ad80 00001fa1 00000fd6 nt+0x699f
a7fc4940 fe38ad80 00001fa1 00000fd6 00000001 nt+0xa454
a7fc4944 00000000 00000fd6 00000001 0000001f 0xfe38ad80


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+a642
804e1642 095154 or dword ptr [ecx+54h],edx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+a642

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

MI PC

Versión EVEREST v5.50.2100/es
Módulo de rendimiento 2.5.292.0
Página Web http://www.lavalys.com/
Tipo de informe Informe rápido
Computadora DESKTOP
Generador Usuario
Sistema operativo Microsoft Windows XP Professional 5.1.2600 (WinXP RTM)
Fecha 2010-07-21
Hora 21:45


--------[ Resumen ]-----------------------------------------------------------------------------------------------------

Computadora:
Tipo de computadora Equipo multiprocesador ACPI
Sistema operativo Microsoft Windows XP Professional
Service Pack del sistema operativo Service Pack 3
Internet Explorer 8.0.6001.18702 (IE 8.0)
DirectX 4.09.00.0904 (DirectX 9.0c)
Nombre de la computadora DESKTOP
Nombre de usuario Usuario
Dominio de inicio de sesión DESKTOP
Fecha / Hora 2010-07-21 / 21:45

Motherboard:
Tipo de CPU DualCore Intel Core 2 Duo E4600, 2400 MHz (12 x 200)
Nombre del motherboard ECS 945GCT-M (2 PCI, 2 PCI-E x16, 2 DDR2 DIMM, Audio, Video, LAN)
Chipset del motherboard Intel Lakeport-G i945GC
Memoria del sistema 2039 MB (DDR2-667 DDR2 SDRAM)
DIMM1: Kreton 516245223681351400 2 GB DDR2-667 DDR2 SDRAM (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz) (3-3-3-9 @ 200 MHz)
Tipo de BIOS AMI (03/28/0:cool:
Puerto de comunicación Puerto de comunicaciones (COM1)
Puerto de comunicación Puerto de impresora (LPT1)

Monitor:
Placa de video Intel(R) 82945G Express Chipset Family (224 MB)
Aceleradora 3D Intel GMA 950
Monitor BenQ G900W (Analog) [19" LCD] (L3809753SL0)
Monitor BenQ G900W (Analog) [19" LCD] (L3809753SL0)

Multimedia:
Placa de sonido SigmaTel STAC9221 A2 @ Intel 82801GB ICH7 - High Definition Audio Controller [A-1]

Almacenamiento:
Controlador IDE Intel(R) 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF
Controlador IDE Intel(R) 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0
Disco rígido Generic USB CF Reader USB Device
Disco rígido Generic USB MS Reader USB Device
Disco rígido Generic USB SD Reader USB Device
Disco rígido Generic USB SM Reader USB Device
Disco rígido WDC WD2500AAJS-00B4A0 (232 GB, IDE)
Disco óptico HL-DT-ST DVDRAM GH20NS10 (DVD+R9:10x, DVD-R9:10x, DVD+RW:20x/8x, DVD-RW:20x/6x, DVD-RAM:12x, DVD-ROM:16x, CD:48x/32x/48x DVD+RW/DVD-RW/DVD-RAM)
Estado SMART de los discos rígidos OK

Particiones:
C: (NTFS) 232.9 GB (180.4 GB libre)
Tamaño total 232.9 GB (180.4 GB libre)

Dispositivos de entrada:
Teclado Teclado estándar de 101/102 teclas o Microsoft Natural PS/2 Keyboard
Mouse Mouse compatible con HID

Red:
Dirección IP primaria 192.168.1.103
Dirección MAC primaria 00-1E-90-9A-D2-5E
Placa de red Realtek RTL8139/810x Family Fast Ethernet NIC (192.168.1.103)

Periféricos:
Impresora Microsoft XPS Document Writer
Controlador USB1 Intel 82801GB ICH7 - USB Universal Host Controller [A-1]
Controlador USB1 Intel 82801GB ICH7 - USB Universal Host Controller [A-1]
Controlador USB1 Intel 82801GB ICH7 - USB Universal Host Controller [A-1]
Controlador USB1 Intel 82801GB ICH7 - USB Universal Host Controller [A-1]
Controlador USB2 Intel 82801GB ICH7 - Enhanced USB2 Controller [A-1]
Dispositivo USB Dispositivo de almacenamiento masivo USB
Dispositivo USB Dispositivo de interfaz humana USB

DMI:
DMI Fabricante del BIOS American Megatrends Inc.
DMI Versión del BIOS 080012
DMI Fabricante del sistema ECS
DMI Nombre del sistema 945GCT-M
DMI Versión del sistema 2.0
DMI Número de serie del sistema 1131
DMI UUID del sistema 00020003-00040005-00060007-00080009
DMI Fabricante del motherboard Intel
DMI Nombre del motherboard 945GCT-M
DMI Versión del motherboard 2.0
DMI Número de serie del motherboard To be filled by O.E.M.
DMI Fabricante del chasis ECS
DMI Versión del chasis To Be Filled By O.E.M.
DMI Número de serie del chasis To Be Filled By O.E.M.
DMI Identificador del chasis To Be Filled By O.E.M.
DMI Tipo de chasis Desktop Case
DMI Sockets de memoria Total / Libres 4 / 3
 
Antes de nada pasa memtest86+ a tu memoria RAM y HDD Regenerator a tu disco duro, para ver si tienen problemas o no.

Saludos.
 
HDD no arroja ningun error.
siguo teniendo pantallazos azules solo cuando ejecuto algun juego por ejemplo, sino no.
gracias
 
¿y el memtest86+ que te dice, lo has pasado?
Parece un problema de RAM.
Saludos..
 
¿solo te ocurre cuando juegas??
¿cuanta memoria virtual tienes asignada?, supongo que tendrás el archivo de paginación en el sistema activo.
Saludos..
 
intel core 2 2394
L1 cache 32
L2 cache 2048
memory 2039 2386
chipset intel i945G ECC DISAMBLED
setting RAM 332 MHZ (DDR 665) CAS 5-5-5-15 single channel (64 bits)
slot 0 2048 MB DDR2-333 - kreton xxxx
le cambio algo? y como
gracias
 
si solo cuando corre cualquier juego
no tengo ninguna particion del disco

c : 2046-4092
tamaño personalizado
tamaño inicial 2046
tamaña maximo 4092


minimo 2MB
recomendado 3058
actual 2046

gracias
 
Actualiza los controladores a la última versión sobre todo los de la gráfica y de paso los directX


Salu2


gohuca
 
Para hacer lo que te ha comentado gohuca, bájate los drivers más actuales de tu tarjeta gráfica desde la web del fabricante (si el PC es de marca, bájalos de la web del fabricante del ordenador), luego desinstala los drivers actuales de tu tarjeta gráfica, después elimina rastros del driver usando Driver Cleaner o Driver Sweeper, reinicia e instala por último los drivers descargados.

Saludos.
 
Arriba