ayuda con pantallazo azul win 7 ultimate

[DarkSun]

hola gracias por las respuestas

 

 

 

instale drivers de audio pero los desinstale cuando me empezo a dar el error , fue lo primero que se me ocurrio pero ya no esta instalado

 

no caxo que otra wea pueda ser

[ExtreemD4t4]

entra en modo a prueba de fallos (modo seguro) y pasa el ccleaner y desinstala otra vez el driver de sonido

[DarkSun]

Saludos hace tiempo que no salia el pantallazo azul

 

pero estos dias ya a aparecido 4 o 5 veces... incluso cuando reincio despues de pantallazo azul , inicia windows y vuelve otro pantallazo azul , la lista es variada asi que voy a pegar lo que saque de mes drivers...

 

actualize driver de bios y tarjeta de video pero sigue igual

 

IRQL_NOT_LESS_OR_EQUAL

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

CACHE_MANAGER

BAD_POOL_HEADER

VIDEO_SCHEDULER_INTERNAL_ERROR

IRQL_NOT_LESS_OR_EQUAL

SYSTEM_SERVICE_EXCEPTION

DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

lo que dice whocrashed

salen 12 pantallazos azules listados..

 

System Information (local)

computer name: KOMOGATOPALAGUA
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel® Core i5-2310 CPU @ 2.90GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4294967295 total tengo 8 GB de memoria RAM sera que una ram ta mala???
VM: 2147352576, free: 1932447744

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Fri 14-06-2013 4:35:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061413-40154-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xA (0x402C, 0x2, 0x0, 0xFFFFF8000300E977)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 14-06-2013 4:35:12 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: sptd.sys (sptd+0x4B5FC)
Bugcheck code: 0xA (0x402C, 0x2, 0x0, 0xFFFFF8000300E977)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\sptd.sys
product: SCSI Pass Through Direct
company: Duplex Secure Ltd.
description: SCSI Pass Through Direct Host
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: sptd.sys (SCSI Pass Through Direct Host, Duplex Secure Ltd.).
Google query: sptd.sys Duplex Secure Ltd. IRQL_NOT_LESS_OR_EQUAL




On Fri 14-06-2013 4:33:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061413-35817-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CF7)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF88002F61CF7, 0xFFFFF880061B1568, 0xFFFFF880061B0DC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Fri 14-06-2013 3:13:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061313-65380-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800767D5F8, 0xFFFFF8800767CE50, 0xFFFFF80003109AB7)
Error: CACHE_MANAGER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 14-06-2013 2:33:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061313-30498-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x19 (0x3, 0xFFFFF8000325CAC0, 0xFFFFF8000325B0C0, 0xFFFFF80003250FC0)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a pool header is corrupt.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Fri 14-06-2013 2:30:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061313-29421-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x119 (0x7000000, 0xFFFFFA80094DB010, 0xFFFFFA800D4EB010, 0xFFFFFA800C321410)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.


On Thu 13-06-2013 5:09:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061313-34975-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF800030E0FC0)
Bugcheck code: 0xA (0x12F8, 0x2, 0x1, 0xFFFFF800030EF468)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: Unknown .
Google query: Unknown IRQL_NOT_LESS_OR_EQUAL




On Wed 12-06-2013 16:09:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061213-33353-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030F5D6C, 0xFFFFF8800BBFCEE0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Wed 12-06-2013 15:27:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061213-33930-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xD1 (0x830, 0x2, 0x0, 0xFFFFF880047BA01D)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 10-06-2013 19:28:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\061013-27440-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800033DFD42, 0xFFFFF88008C17EF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 10-06-2013 3:46:55 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060913-27955-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0)
Bugcheck code: 0xD1 (0x57FFFB, 0x2, 0x0, 0xFFFFF88001464D14)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Mon 10-06-2013 3:40:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060913-27549-01.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1+0x20CF7)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800475FCF7, 0xFFFFF880053CD568, 0xFFFFF880053CCDC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

Conclusion

12 crash dumps have been found and analyzed. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

sptd.sys (SCSI Pass Through Direct Host, Duplex Secure Ltd.)

unknown

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

 

Ojala me puedan ayudar.

 

saludos.

 

Intente quitar el dirver de sonido otra vez entrando al modo aprueba de fallos pero no existe el driver , que se puede hacer??

 

 

Edited June 14, 2013 by DarkSun

[baltinino]

Unos de los errores que muestra el archivo DMP está relacionado con el programa Daemon Tools, desinstalalo o desactiva que se ejecute desde el inicio. Puede ser la causa de los demás errores.

[ExtreemD4t4]

segun puedo leer, windows tiene un problema para menejar los accesos a la ram por problemas de software o drivers instalados, yo recomendaria formatear

[DarkSun]

ya desintale el alcohol (daemon tools)

 

voy a probar antes de formatear

 

saludos

 

 

editado: volvio aparecer pantalla azul , cual win 7 es mejor?

 

Como puedo saber que placa o que drivers necesito tener antes de formatear??

 

saludos,

Edited June 16, 2013 by DarkSun