Hola amigos vacunos. Ya he leído varios temas sobre pantalla azul, pero no he podido solucionar mi problema. Tengo una pc que acabo de armar hace como 3 meses y al principio le instale Windows xp pero seguido se me ponía la pantalla negra y ni reiniciando se recuperaba, solamente quitándole la corriente al pc y volviendo a prenderla. Así que le instale Windows 7x64 y todo muy bien durante un tiempo, pero un día de repente que me sale una pantalla azul que decía algo del ntoskrnl.exe, así que reemplace el ntoskrnl.exe y todo siguió bien, pero a la semana volvió la pantalla azul con el mismo problema. Así que formatie el disco duro e instale de ceros el Windows 7 x64 sp1. Una semana después al querer quemar un cd cuando inserte el disco virgen y la pc lo reconoció me salió la pantalla azul nuevamente así que le pase el memtest y lo deje 2 pasadas pero no me salió ningún error, luego le pase el HD regenerator al disco duro y por ultimo le hice una prueba de stress a la tarjeta de video para ver si con al calentarse me volvía a salir la pantalla azul, pero nada, entonces pensé que era por el software que uso para quemar disco así que lo cambie por nero y queme en un par de ocasiones en días distintos algunos cds y dvds sin problema pero hace dos días al querer quemar un cd con nero cuando inserte el cd virgen y que la pc lo reconoció nuevamente la pantalla azul. Así que no tengo ni la más remota idea de que es lo que causa esta pantalla azul ya me tiene desesperado y no encuentro solución, espero me puedan ayudar con mi problema.
Estas son las especificaciones de mi pc:
Tarjeta madre: Asus M5A99X EVO
Procesador: AMD FX 8150
Fuente de poder: Cooler Master Extreme 600W
Memoria: DDR3 KINGSTON HYPERX 4 GB 1600MHZ (KHX1600C9D3/4G)
Quemador: LG GH22NS70
Disco Duro: Seagate 1TB Sata II

Pego abajo el último volcado de memoria:

Kernel Summary Dump File: Only kernel 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 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Kernel base = 0xfffff800`02c0f000 PsLoadedModuleList = 0xfffff800`02e54e90
Debug session time: Wed Oct 3 21:35:45.179 2012 (GMT-6)
System Uptime: 0 days 9:33:48.506
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
.................................................................................................................................Page 973bf not present in the dump file. Type ".hh dbgerr004" for details
.Page 945ae not present in the dump file. Type ".hh dbgerr004" for details
.........................
Loading User Symbols

Loading unloaded module list
........
The context is partially valid. Only x86 user-mode context is available.
The wow64exts extension must be loaded to access 32-bit state.
.load wow64exts will do this if you haven't loaded it already.
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80002c87565, fffff8800af56990, 0}

***** 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 ***
*** ***
*************************************************************************
*********************************************************************
* 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 : ntkrnlmp.exe ( nt!ExpInterlockedPopEntrySList+25 )

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

16.0: kd:x86> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80002c87565, Address of the exception record for the exception that caused the bugcheck
Arg3: fffff8800af56990, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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 ***
*** ***
*************************************************************************
*********************************************************************
* 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: fffff80002c0f000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - La instrucci n en 0x%08lx hace referencia a la memoria en 0x%08lx. La memoria no se pudo %s.

FAULTING_IP:
nt!ExpInterlockedPopEntrySList+25
fffff800`02c87565 49 dec ecx

CONTEXT: fffff8800af56990 -- (.cxr 0xfffff8800af56990)
Unable to read context, HRESULT 0x80004002

DEFAULT_BUCKET_I WRONG_SYMBOLS

BUGCHECK_STR: 0x3B

LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0


STACK_COMMAN .bugcheck ; kb

FOLLOWUP_IP:
nt!ExpInterlockedPopEntrySList+25
fffff800`02c87565 49 dec ecx

SYMBOL_NAME: nt!ExpInterlockedPopEntrySList+25

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrnlmp.exe

BUCKET_I WRONG_SYMBOLS

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