Ayuda reiterado pantallazo azul Windows 7 Kernel 41

Hola chicos, necesito vuestra ayuda porque no consigo solucionar este problema.
Mi equipo es el siguiente:

Campo Valor
Computadora
Tipo de computadora ACPI x64-based PC
Sistema operativo Microsoft Windows 7 Ultimate
Service Pack del sistema operativo -
Internet Explorer 8.0.7600.16385
DirectX DirectX 11.0
Nombre de la computadora SEVENT-PC
Nombre de usuario SEVENT
Dominio de inicio de sesión SEVENT-PC
Fecha / Hora 2010-04-19 / 13:11

Motherboard
Tipo de CPU QuadCore AMD Phenom II X4 810, 2600 MHz (13 x 200)
Nombre del motherboard Gigabyte GA-MA78LM-S2 (2 PCI, 1 PCI-E x1, 1 PCI-E x16, 2 DDR2 DIMM, Audio, Video, Gigabit LAN)
Chipset del motherboard AMD 760G, AMD K10
Memoria del sistema 4096 MB (DDR2-800 DDR2 SDRAM)
DIMM1: OCZ Reaper HPC OCZ2RPR800C42G 2 GB DDR2-800 DDR2 SDRAM (5-5-5-18 @ 400 MHz) (4-5-5-15 @ 333 MHz) (3-4-4-12 @ 266 MHz)
DIMM2: OCZ Reaper HPC OCZ2RPR800C42G 2 GB DDR2-800 DDR2 SDRAM (5-5-5-18 @ 400 MHz) (4-5-5-15 @ 333 MHz) (3-4-4-12 @ 266 MHz)
Tipo de BIOS Award Modular (03/18/10)
Puerto de comunicación Puerto de comunicaciones (COM1)

Monitor
Placa de video ATI Radeon HD 5700 Series (1024 MB)
Placa de video ATI Radeon HD 5700 Series (1024 MB)
Placa de video ATI Radeon HD 5700 Series (1024 MB)
Aceleradora 3D ATI EG Juniper XT
Monitor LG W2261 (Digital) [22" LCD] (1910404150)

Multimedia
Placa de sonido Controladora de High Definition Audio [1002-AA58] [NoDB]
Placa de sonido Realtek ALC887 @ ATI SB750 - High Definition Audio Controller

Almacenamiento
Controlador IDE Controladora estándar PCI IDE de doble canal
Controlador IDE Controladora estándar PCI IDE de doble canal
Controlador de almacenamiento AF37H776 IDE Controller
Disco rígido ST31000528AS ATA Device (1000 GB, 7200 RPM, SATA-II)
Disco rígido ST3200822A ATA Device (200 GB, 7200 RPM, Ultra-ATA/100)
Disco óptico HKFAXKD 3OT6F05 SCSI CdRom Device
Disco óptico HL-DT-ST DVD-RAM GH22NS30 ATA Device (DVD+R9:16x, DVD-R9:12x, DVD+RW:22x/8x, DVD-RW:22x/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) 341.7 GB (237.8 GB libre)
D: (NTFS) 589.7 GB (548.1 GB libre)
E: (NTFS) 186.3 GB (66.7 GB libre)
Tamaño total 1117.7 GB (852.6 GB libre)

Dispositivos de entrada
Teclado Dispositivo de teclado HID
Teclado Dispositivo de teclado HID
Teclado Dispositivo de teclado HID
Teclado Dispositivo de teclado HID
Mouse Logitech HID-compliant G500 Gaming Mouse
Mouse Mouse compatible con HID

Red
Dirección IP primaria 192.168.1.100
Dirección MAC primaria 00-24-1D-5C-5F-E1
Placa de red Realtek PCIe GBE Family Controller (192.168.1.100)
Placa de red TAP-Win32 Adapter V9 (Tunngle)

Periféricos
Impresora hp psc 1310 series
Controlador USB1 ATI SB750 - OHCI USB Controller
Controlador USB1 ATI SB750 - OHCI USB Controller
Controlador USB1 ATI SB750 - OHCI USB Controller
Controlador USB1 ATI SB750 - OHCI USB Controller
Controlador USB1 ATI SB750 - OHCI USB Controller
Controlador USB2 ATI SB750 - EHCI USB 2.0 Controller
Controlador USB2 ATI SB750 - EHCI USB 2.0 Controller
Dispositivo USB Dispositivo compuesto USB
Dispositivo USB Dispositivo compuesto USB
Dispositivo USB Dispositivo de entrada USB
Dispositivo USB Dispositivo de entrada USB
Dispositivo USB Dispositivo de entrada USB
Dispositivo USB Dispositivo de entrada USB
Dispositivo USB Dispositivo de entrada USB
Dispositivo USB Generic USB Hub

DMI
DMI Fabricante del BIOS Award Software International, Inc.
DMI Versión del BIOS F8
DMI Fabricante del sistema Gigabyte Technology Co., Ltd.
DMI Nombre del sistema GA-MA78LM-S2
DMI Versión del sistema
DMI Número de serie del sistema
DMI UUID del sistema 30303234-31443543-35464531-FFFFFFFF
DMI Fabricante del motherboard Gigabyte Technology Co., Ltd.
DMI Nombre del motherboard GA-MA78LM-S2
DMI Versión del motherboard
DMI Número de serie del motherboard
DMI Fabricante del chasis Gigabyte Technology Co., Ltd.
DMI Versión del chasis
DMI Número de serie del chasis
DMI Identificador del chasis
DMI Tipo de chasis Desktop Case
DMI Sockets de memoria Total / Libres 4 / 2


Y este es el reporte del Debugger:

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


Loading Dump File [C:\Windows\Minidump\041910-17191-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03210000 PsLoadedModuleList = 0xfffff800`0344de50
Debug session time: Mon Apr 19 00:57:21.179 2010 (GMT+2)
System Uptime: 0 days 3:15:25.037
*********************************************************************
* 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 7F, {8, 80050031, 6f8, 6b732c85}

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

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: 000000006b732c85

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+ *
*********************************************************************

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: fffff80003210000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb

BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000327fb69 to fffff80003280600

STACK_TEXT:
fffff800`00ba4d28 fffff800`0327fb69 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt+0x70600
fffff800`00ba4d30 00000000`0000007f : 00000000`00000008 00000000`80050031 00000000`000006f8 00000000`6b732c85 : nt+0x6fb69
fffff800`00ba4d38 00000000`00000008 : 00000000`80050031 00000000`000006f8 00000000`6b732c85 00000000`00000000 : 0x7f
fffff800`00ba4d40 00000000`80050031 : 00000000`000006f8 00000000`6b732c85 00000000`00000000 00000000`00000000 : 0x8
fffff800`00ba4d48 00000000`000006f8 : 00000000`6b732c85 00000000`00000000 00000000`00000000 00000000`00000000 : 0x80050031
fffff800`00ba4d50 00000000`6b732c85 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6f8
fffff800`00ba4d58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6b732c85


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+70600
fffff800`03280600 48894c2408 mov qword ptr [rsp+8],rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+70600

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntoskrnl.exe

BUCKET_ID: WRONG_SYMBOLS

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

Muchas gracias de antemano y un cordial saludo para todos.
 
Bienvenid@ al foro, antchaiz :)

¿Bajo qué circunstancias te ocurre el pantallazo azul? ¿Tu Windows es original o has utilizado algún activador?

Saludos.
 
Ayax dijo:
Bienvenid@ al foro, antchaiz :)

¿Bajo qué circunstancias te ocurre el pantallazo azul? ¿Tu Windows es original o has utilizado algún activador?

Saludos.

Muchas gracias por tu interés.

Utilicé activador en octubre que es cuando me lo instalaron en la tienda donde lo compré pero sin licencia y el problema me viene la mayoría de las veces cuando llevo un rato jugando a Call Of Duty Modern Warfare 2 entre otros.

Saludos.
 
Probablemente el pantallazo te ocurra por usar un activador...

Intenta desinstalar por completo los drivers de tu tarjeta gráfica usando Driver Cleaner o Driver Sweeper e instalando los más recientes de la web de ATI.

Saludos.
 
Ayax dijo:
Probablemente el pantallazo te ocurra por usar un activador...

Intenta desinstalar por completo los drivers de tu tarjeta gráfica usando Driver Cleaner o Driver Sweeper e instalando los más recientes de la web de ATI.

Saludos.

Hola

Ya había reinstalado los drivers ATI CCC 10.3, pero no había utilizado ninguna de las herramientas que me indicas. Lo pruebo y os comento si queda solucionado.

Respecto a lo del activador no sé en qué medida crees que me pueda estar dando estos problemas, porque desde octubre lo uso pero los pantallazos son desde hace unos días.

Muchas gracias y saludos.
 
Te lo comento porque los activadores modifican ficheros del sistema, y puede que junto con alguna actualización reciente de Windows entre en conflicto.

Saludos.
 
Ayax dijo:
Te lo comento porque los activadores modifican ficheros del sistema, y puede que junto con alguna actualización reciente de Windows entre en conflicto.

Saludos.

Hola
Muchas gracias de nuevo.
He desinstalado los drivers de mi Ati HD 5770 con Driver Sweeper, después desinstalé el resto con la aplicación de Ati para volver a instalarlos nuevamente. Voy a darle caña al Call Of Duty y a ver si queda solucionado con esto.

Un saludo y ya te cuento mañana.
 
Por cierto, en el driver sweeper he visto que tenía instaladas algunas cosas de Nvidia, que supongo las habrá cargado algún juego.
¿Crees que puedan tener algún conflicto con mi gráfica ATI?
Por si acaso las he desinstalado.
Buenas noches.
 
Hasta ahora y gracias a tus consejos no se han vuelto a producir los pantallazos azules.

Añado que descubrí que LG también ha publicado unos drivers especiales para mi monitor y Windows 7, que arreglaban el bloqueo en el modo de ahorro de energía.

Esperemos que todo siga bien y podamos dar el asunto por solucionado.

Muchas gracias y saludos.
 
Curioso que tuvieras drivers de NVIDIA... Por cierto, acabo de ver que tu placa base tiene tarjeta gráfica integrada en placa, con lo que deberías asegurarte en la BIOS de tenerla deshabilitada (disabled) para que no haya conflictos con la tarjeta gráfica PCI-express.

Saludos.
 
Ayax dijo:
Curioso que tuvieras drivers de NVIDIA... Por cierto, acabo de ver que tu placa base tiene tarjeta gráfica integrada en placa, con lo que deberías asegurarte en la BIOS de tenerla deshabilitada (disabled) para que no haya conflictos con la tarjeta gráfica PCI-express.

Saludos.

Gracias por el aporte.

Voy a echar un vistazo a la BIOS a ver si encuentro esa opción.

Saludos.
 
He verificado la BIOS y en la opción de periféricos integrados me aparece la tarjeta de sonido, la de red y los USB, pero ni rastro de tarjeta gráfica integrada.

He revisado también el administrador de dispositivos de Windows y sólo me aparece la ATI HD 5770.

Saludos.
 
Hola

Ayer estuve probando el pc y afortunadamente tampoco me dio ningún tipo de problemas.

Supongo que todo ha quedado solucionado con la reinstalación de los drivers de la tarjeta gráfica desde 0 y demás posibles confilictos con otros drivers de Nvidia instalados por juegos.

Muchas gracias por la ayuda y si lo veis necesario, ya que está todo perfecto por ahora, proceded al cierre del tema.

Saludos
 
Esperemos que se haya solucionado el problema ;)

Lo dejamos abierto, no hay problema.

Recuerda visitarnos a diario en :arrow: SoftZone, donde podrás encontrar noticias, manuales, todo en uno, trucos, descargas gratuitas 100% seguras de software y mucho más...

Saludos.
 
Hola amigos.

Después de un par de días funcionando bien, continúan los problemas:

Recibí dos pantallazos azules por archivos distintos.
Después del primero procedí nuevamente a desinstalar los drivers de la tarjeta gráfica, los reinstalé, probé de nuevo y recibí otro pantallazo.
Aquí os dejo los minidumps por si podéis echarme una mano.

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


Loading Dump File [C:\Windows\Minidump\042310-18595-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 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03216000 PsLoadedModuleList = 0xfffff800`0344ee50
Debug session time: Fri Apr 23 23:24:38.807 2010 (UTC + 2:00)
System Uptime: 0 days 1:30:40.680
*********************************************************************
* 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 50, {fffff88007b9830f, 0, fffff88004b6bcc9, 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 ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\atipmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atipmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atipmdag.sys
*************************************************************************
*** ***
*** ***
*** 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 : atipmdag.sys ( atipmdag+289cc9 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88007b9830f, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004b6bcc9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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.

FAULTING_MODULE: fffff80003216000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b8ddbbc

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

FAULTING_IP:
atipmdag+289cc9
fffff880`04b6bcc9 413bc6 cmp eax,r14d

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000329a786 to fffff8000327e900

STACK_TEXT:
fffff880`0ac8cef8 fffff800`0329a786 : 00000000`00000050 fffff880`07b9830f 00000000`00000000 fffff880`0ac8d050 : nt+0x68900
fffff880`0ac8cf00 00000000`00000050 : fffff880`07b9830f 00000000`00000000 fffff880`0ac8d050 00000000`00000000 : nt+0x84786
fffff880`0ac8cf08 fffff880`07b9830f : 00000000`00000000 fffff880`0ac8d050 00000000`00000000 00000000`00000801 : 0x50
fffff880`0ac8cf10 00000000`00000000 : fffff880`0ac8d050 00000000`00000000 00000000`00000801 00000000`0000ffc0 : <Unloaded_spsys.sys>+0x2d30f


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atipmdag+289cc9
fffff880`04b6bcc9 413bc6 cmp eax,r14d

SYMBOL_NAME: atipmdag+289cc9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atipmdag

IMAGE_NAME: atipmdag.sys

BUCKET_ID: WRONG_SYMBOLS

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88007b9830f, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004b6bcc9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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.

FAULTING_MODULE: fffff80003216000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b8ddbbc

READ_ADDRESS: fffff88007b9830f

FAULTING_IP:
atipmdag+289cc9
fffff880`04b6bcc9 413bc6 cmp eax,r14d

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000329a786 to fffff8000327e900

STACK_TEXT:
fffff880`0ac8cef8 fffff800`0329a786 : 00000000`00000050 fffff880`07b9830f 00000000`00000000 fffff880`0ac8d050 : nt+0x68900
fffff880`0ac8cf00 00000000`00000050 : fffff880`07b9830f 00000000`00000000 fffff880`0ac8d050 00000000`00000000 : nt+0x84786
fffff880`0ac8cf08 fffff880`07b9830f : 00000000`00000000 fffff880`0ac8d050 00000000`00000000 00000000`00000801 : 0x50
fffff880`0ac8cf10 00000000`00000000 : fffff880`0ac8d050 00000000`00000000 00000000`00000801 00000000`0000ffc0 : <Unloaded_spsys.sys>+0x2d30f


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atipmdag+289cc9
fffff880`04b6bcc9 413bc6 cmp eax,r14d

SYMBOL_NAME: atipmdag+289cc9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atipmdag

IMAGE_NAME: atipmdag.sys

BUCKET_ID: WRONG_SYMBOLS

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff88007b9830f, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88004b6bcc9, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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.

FAULTING_MODULE: fffff80003216000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b8ddbbc

READ_ADDRESS: fffff88007b9830f

FAULTING_IP:
atipmdag+289cc9
fffff880`04b6bcc9 413bc6 cmp eax,r14d

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000329a786 to fffff8000327e900

STACK_TEXT:
fffff880`0ac8cef8 fffff800`0329a786 : 00000000`00000050 fffff880`07b9830f 00000000`00000000 fffff880`0ac8d050 : nt+0x68900
fffff880`0ac8cf00 00000000`00000050 : fffff880`07b9830f 00000000`00000000 fffff880`0ac8d050 00000000`00000000 : nt+0x84786
fffff880`0ac8cf08 fffff880`07b9830f : 00000000`00000000 fffff880`0ac8d050 00000000`00000000 00000000`00000801 : 0x50
fffff880`0ac8cf10 00000000`00000000 : fffff880`0ac8d050 00000000`00000000 00000000`00000801 00000000`0000ffc0 : <Unloaded_spsys.sys>+0x2d30f


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
atipmdag+289cc9
fffff880`04b6bcc9 413bc6 cmp eax,r14d

SYMBOL_NAME: atipmdag+289cc9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atipmdag

IMAGE_NAME: atipmdag.sys

BUCKET_ID: WRONG_SYMBOLS

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

Y DESPUÉS:


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


Loading Dump File [C:\Windows\Minidump\042410-21106-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
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.20655.amd64fre.win7_ldr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03268000 PsLoadedModuleList = 0xfffff800`034a0e50
Debug session time: Sat Apr 24 00:42:33.564 2010 (UTC + 2:00)
System Uptime: 0 days 0:45:20.047
*********************************************************************
* 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
*** 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 3B, {c0000005, fffff88004fcda05, fffff880078e0ae0, 0}

Unable to load image \SystemRoot\System32\drivers\dxgmms1.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgmms1.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
***** 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 : dxgmms1.sys ( dxgmms1+37a05 )

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

1: kd> !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: fffff88004fcda05, Address of the instruction which caused the bugcheck
Arg3: fffff880078e0ae0, 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 ***
*** ***
*************************************************************************

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: dxgmms1

FAULTING_MODULE: fffff80003268000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578

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:
dxgmms1+37a05
fffff880`04fcda05 488908 mov qword ptr [rax],rcx

CONTEXT: fffff880078e0ae0 -- (.cxr 0xfffff880078e0ae0)
rax=31327c6df5d5dc09 rbx=fffff8a000862720 rcx=1ea1f99cb2e31400
rdx=fffff8a000862700 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004fcda05 rsp=fffff880078e14b0 rbp=fffff8a000862700
r8=fffff880078e1510 r9=fffff880078e1518 r10=0000000000000080
r11=fffff880078e1180 r12=fffffa8006777010 r13=fffffa8006094000
r14=0000000000000000 r15=fffff8a00e5afd30
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010282
dxgmms1+0x37a05:
fffff880`04fcda05 488908 mov qword ptr [rax],rcx ds:002b:31327c6d`f5d5dc09=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff88004fcda05

STACK_TEXT:
fffff880`078e14b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1+0x37a05


FOLLOWUP_IP:
dxgmms1+37a05
fffff880`04fcda05 488908 mov qword ptr [rax],rcx

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: dxgmms1+37a05

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: dxgmms1.sys

STACK_COMMAND: .cxr 0xfffff880078e0ae0 ; kb

BUCKET_ID: WRONG_SYMBOLS

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

MUCHAS GRACIAS Y SALUDOS
 
Parece un problema de los controladores de la gráfica y de los directX

Desinstala los controladores e intala los más actuales y reinstala los últimos directx


Salu2


Gohuca
 
Muchas gracias por el consejo.

Después de un tedioso día te comento lo que he hecho y a ver si vale.

He particionado el disco duro y en una partición he puesto windows 7 32 bits y en la otra windows 7 64 bits con sus drivers correspondientes actualizados.

Sólo he podido probar la de 32 bits y corre a la perfección.

Ahora paso a probar la de 64 bits y mañana os comento si haciéndolo todo desde 0 da resultado.

Muchas gracias y saludos.
 
Sigo con los problemas, ahora también en 32 bits

Hola amigos, esto ya me empieza a desesperar...

Anoche jugando a Call Of Duty Modern Warfare 2 esta vez bajo Windows 7 32 bit, cuando llevaba una hora aproximadamente la pantalla se quedó en negro y el ordenador hizo un ruido muy extraño, se bloqueó y acto seguido el sonido seguía como si estuviese dentro del juego pero ya no pude recuperar la imagen de la partida y tuve que forzar el reinicio.

¿Qué me aconsejan que haga?

Son dos sistemas operativos recién instalados con los drivers actualizados a la última versión del fabricante de la tarjeta de video.

Las características de mi equipo están al principio del post.

Muchas gracias por vuestra inestimable ayuda.

Saludos.
 
Comprueba la temperatura de la gráfica y si esta está bien asentada


SAlu2


Gohuca
 
Arriba