Pantallazos azules!

Grun está baneado por "clon brasa de usaurio baneado"
Despues de un tiempo (y sin antivirus instalado) me ha vuelto a salir pantallazos azules, uno ayer y otro hoy

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 19/08/2014 8:47:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081914-59810-01.dmp
This was probably caused by the following module: Unknown (0x00000001)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x1, 0xFFFFF880031C5818, 0xFFFFF880031C5070)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M



On Tue 19/08/2014 8:47:33 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0x1, 0xFFFFF880031C5818, 0xFFFFF880031C5070)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed.
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.
Mira en el administrador de dispositivos si tienes todos los controladores actualizados o hay alguno con problemas.
Grun está baneado por "clon brasa de usaurio baneado"
Y como se actualizan?
Grun escribió:Y como se actualizan?


Si ves alguno con una señal amarilla de advertencia, clic derecho y Propiedades.
Grun está baneado por "clon brasa de usaurio baneado"
Whispers_v2 escribió:
Grun escribió:Y como se actualizan?


Si ves alguno con una señal amarilla de advertencia, clic derecho y Propiedades.


A ver, no si he echo bien, he ido en administrador de dispositivos y ahi todos no me aparece ninguna advertencia, excpeto en Adaptadores de red desplegable Broadcom Netlink (TM) Ethernet aparece una flechita pa abajo, que hago? yo le he dado, click derecho Actualizar software de controlador, se me abierto un asistente Buscar automaticamente software de controlador actualizado y me ha dicho que ya esta instalado la actualizacion mas reciente

veo en google en este link: http://www.driveridentifier.com/scan/br ... S_06011025 que hay una actualizacion mas reciente de este controlador, lo descargo? mi sitema operativo es windows 7 64bit y mi portatil Acer Aspire 5733Z cual diriver me tengo que descargar?

______________________________

me ha vuelto a salir una pantallazo azul:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 20/08/2014 13:53:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\082014-28438-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002C8DCA3, 0xFFFFF880043F4070, 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 that cannot be identified at this time.



On Wed 20/08/2014 13:53:33 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xDCCE)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF80002C8DCA3, 0xFFFFF880043F4070, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Controlador Win32 multiusuario
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 19/08/2014 8:47:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\081914-59810-01.dmp
This was probably caused by the following module: Unknown (0x00000001)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0x1, 0xFFFFF880031C5818, 0xFFFFF880031C5070)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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.
A third party driver was identified as the probable root cause of this system error.
Google query: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

3 crash dumps have been found and analyzed.
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.
4 respuestas