Servicio a la orden, hardware, software, internet y de todo un poco ;)

Ver más
  • 110,927 Miembros
  • 177,478 Temas
  • 33,593 Seguidores
  • 0

Pido ayuda con pantallazos azules (BSoD) con Windows 7

Estoy desesperado, reinicio la PC unas 10 veces diarias. Hay veces que me sale la pantalla azul con las letras blancas, se me reinician y ya está, y otras se me bloquea el ordenador con la pantalla azul, pero sin letras ni nada.
Con el programa WhoCrashed he obtenido la siguiente información, pero como no tengo ni idea de informatica, no se que quiere decir.
También aclarar que el WIndows 7 es pirata (sacado de Taringa!, XD) y tambien decir que con otro programa llamado Memtest86 le hice un análisis a mi memoria Ram, la cual resulto que estaba al 100%

PORFAVOR SI ALGUIEN ME PUEDE APORTAR ALGO DE AYUDA, POR POCA QUE SEA, LE ESTARE MUY AGRADECIDO.

Información de errores:

On Fri 15/10/2010 14:31:21 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xD1 (0x6E6F4356, 0x2, 0x0, 0x6E6F4356)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\101510-14265-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 15/10/2010 14:25:41 your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF88003E3796E, 0xFFFFF88002185668, 0xFFFFF88002184ED0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\101510-13890-01.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 14/10/2010 20:34:01 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E16FD1, 0xFFFFFFFFFFFFFFFF, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
Dump file: C:\Windows\Minidump\101410-16531-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 13/10/2010 16:44:51 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x18 (0xFFFFFA8002ACA570, 0xFFFFFA8004663490, 0x1, 0x400000000000000)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\101310-14812-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 12/10/2010 20:42:25 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800315D868, 0xFFFFF8800315D0D0, 0xFFFFF88001357B39)
Error: NTFS_FILE_SYSTEM
Dump file: C:\Windows\Minidump\101210-13875-01.dmp
file path: C:\Windows\system32\drivers\ntfs.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador del sistema de archivos NTFS
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Tue 12/10/2010 22:24:37 your computer crashed
This was likely caused by the following module: dxgmms1.sys
Bugcheck code: 0x10E (0x16, 0xFFFFFA8004E28BF0, 0x400000000020000, 0x200)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
Dump file: C:\Windows\Minidump\101210-17312-01.dmp
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 11/10/2010 18:56:03 your computer crashed
This was likely caused by the following module: atikmdag.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF88004B09FEE, 0xFFFFF880021859B8, 0xFFFFF88002185220)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\101110-14500-01.dmp
file path: C:\Windows\system32\drivers\atikmdag.sys
product: ATI Radeon Family
company: ATI Technologies Inc.
description: ATI Radeon Kernel Mode Driver



On Mon 11/10/2010 17:24:57 your computer crashed
This was likely caused by the following module: dxgmms1.sys
Bugcheck code: 0x10E (0x16, 0xFFFFFA8004EDCA10, 0x400000000020000, 0x200)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
Dump file: C:\Windows\Minidump\101110-14921-01.dmp
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Mon 11/10/2010 16:48:17 your computer crashed
This was likely caused by the following module: dxgmms1.sys
Bugcheck code: 0x10E (0x16, 0xFFFFFA80034F4610, 0x1000000000020000, 0x200)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
Dump file: C:\Windows\Minidump\101110-17359-01.dmp
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 07/10/2010 13:46:41 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x18 (0xFFFFFA8002AC8100, 0xFFFFFA8004A55750, 0x1, 0x1400000000000000)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\100710-13000-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sun 26/09/2010 20:57:59 your computer crashed
This was likely caused by the following module: dxgmms1.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF88004FC524C, 0xFFFFF88006D31E60, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\092610-17250-01.dmp
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Sat 25/09/2010 10:43:25 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x18 (0xFFFFFA8002AC8100, 0xFFFFFA8004AE5DD0, 0x1, 0x400000000000000)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\092510-13109-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Fri 24/09/2010 20:53:51 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x18 (0xFFFFFA8002AE3100, 0xFFFFFA8002CE5E90, 0x1, 0x400000000000000)
Error: REFERENCE_BY_POINTER
Dump file: C:\Windows\Minidump\092410-14437-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Thu 23/09/2010 15:42:50 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x3B (0xC0000005, 0x3, 0xFFFFF88002514AC0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\092310-12406-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 22/09/2010 16:32:40 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF9600018B36C, 0xFFFFF88007319FD0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
Dump file: C:\Windows\Minidump\092210-13406-01.dmp
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 multiusuario
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.



On Wed 22/09/2010 16:18:47 your computer crashed
This was likely caused by the following module: rt64win7.sys
Bugcheck code: 0xD1 (0xFFFFFA80080D1560, 0x2, 0x0, 0xFFFFF8800466F42A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Dump file: C:\Windows\Minidump\092210-13531-01.dmp
file path: C:\Windows\system32\drivers\rt64win7.sys
product: Realtek 8101E/8168/8169 PCI/PCIe Adapters
company: Realtek Corporation
description: Realtek 8101E/8168/8169 NDIS 6.20 64-bit Driver



On Sat 18/09/2010 10:50:30 your computer crashed
This was likely caused by the following module: dxgkrnl.sys
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF88004E6B96E, 0xFFFFF8800217E8A8, 0xFFFFF8800217E110)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file: C:\Windows\Minidump\091810-15968-01.dmp
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
The crash took place in a standard Microsoft module. Your system configuration may be incorrect, possibly the culprit is in another driver on your system which cannot be identified at this time.
---------------------------------------------------------------------------------------------------------------------------------------------------


Muchas Gracias de antemano, ya que cualquier ayuda me servira de algo.

Un saludo. DaniWeaver
  • 0
  • 0Calificación
  • 1Seguidores
  • 4.658Visitas
  • 0Favoritos

18 comentarios

@adjaca03
resumiendo todo esto ..!! con tantas reiniciadas que le distes al PC hicistes pelota el SO
1) ya ..!! ase una particion desde otra PC (obiamente sacando el rigido)para pasar el backub
2) no reinstales << ( este paso solamente si NO tienes otra PC para lebantar el backup)
3) Forma C : %( formatia ) <[sulucion]
@diegodequil
podes tmb chequear el rigido a ver si tiene algun sector malo, o el mother. si tenes otro rigido aunque sea chico proba de instalarle el win de nuevo a ver si sufre los mismos cuelgues
@jecbanjo
De casualidad intalaste el remove WAT??? ultimamente las nuevas versiones me han dado problemas, ademas deberias subir la config de tu pc

Actualiza tu directX y si tu tarjeta es ATI actuliza drivers y nos cuentas como te fue
@jecbanjo
ahi esta el problema, primero descarga la ultima version del 7loader de orbit o hazar, luego utiliza de nuevo el remove wat para RESTAURAR EL WAT, reinicia, luego ejecutas el 7 loader para validar tu windows, actualiza tu directx a la ultima revision y tus catalyst de ati.

Prueba y nos comentas como te fue.
@moebius17 +1
Disculpame, ando buscando solucion para el error de System_service_exception. Vos decis que el error salta por una validacion equivocada de Windows? Me darias una gran mano si sabes resolverlo
@jecbanjo
yo tube el mismo problema, antes me funcionaba bien, pues siempre habia utilizado los 7 loader, pero en una maquina que tengo no habia usado ningun activador y cuando se me acabaron los dias de prueba, utilice el remove wat 2.25 o 26 y desde que lo instale comenzaron los problemas de pantallas azules con ntfs.sys y win32k entre otros. el error se debe a que existe algun error en los ultimos remove wat. entonces lo elimine y utilice el 7 loader y se solucionaron los problemas.
@jecbanjo
al parecer el error en el remove wat solo afecta las versiones de windows 7 de 64 bits
@jecbanjo
ya RESTAURASTE el wat con el remove wat? porque si el 7 loader no te funciona es porque no encuentra el WAT en el equipo.

usaste el 7Loader v1.6.1d by Hazar? sino te funciono entonces utiliza el Windows 7 Loader v1.9.2 by Daz.

Si ninguna te funciona significa que el remove wat corrompió el wat del equipo, inténtalo de nuevo en una instalación limpia.
@jecbanjo
cuando usas el remove WAT te da dos opciones una de eliminar el WAT y otra de restor WAT.
usa la de restore WAT

Te recomiendo el 1.9.2 by Daz
@jecbanjo
bueno, cuando restauras el wat te sale que windows no es original, pero ¿incluso en ese estado recibes pantallazos azules?, si es asi lo mejor es reinstalar pero NO USAR REMOVE WAT, usar de una ves el 7LOADER
@simiolas11
yo tengo este maldito error ya e probado cambiar de hadwares y todo , grrr

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


Loading Dump File [C:WindowsMinidump30611-16536-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 SystemRootsystem32ntoskrnl.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 x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Kernel base = 0x8303c000 PsLoadedModuleList = 0x8317c5b0
Debug session time: Sun Mar 6 18:13:15.063 2011 (GMT-3)
System Uptime: 0 days 7:17:56.811
*********************************************************************
* 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 SystemRootsystem32ntoskrnl.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
.....
Tienes que ser miembro para responder en este tema