PROBLEMA Blue screen SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

Pubblicità

Deliriox

Nuovo Utente
Messaggi
6
Reazioni
1
Punteggio
21
Ciao a tutti,mi compare spesso questo blue screen, inoltre anche molti dei giochi hanno continui crash.
Allego i report:
Codice:
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 25/05/2017 18:11:43 your computer crashed
crash dump file: C:\Windows\Minidump\052517-4765-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xDDDE4)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80250CEDDE4, 0xFFFFCA017905F6A8, 0xFFFFCA017905EED0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 25/05/2017 18:11:43 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, 0xFFFFF80250CEDDE4, 0xFFFFCA017905F6A8, 0xFFFFCA017905EED0)
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.



On Tue 23/05/2017 21:41:24 your computer crashed
crash dump file: C:\Windows\Minidump\052317-4718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14EC00)
Bugcheck code: 0x139 (0x3, 0xFFFF97816535F7A0, 0xFFFF97816535F6F8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 22/05/2017 18:41:48 your computer crashed
crash dump file: C:\Windows\Minidump\052217-4343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14EC00)
Bugcheck code: 0x50 (0xFFFFDD805E05DBC0, 0x0, 0xFFFFF8022A57389B, 0x1)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sat 20/05/2017 22:59:48 your computer crashed
crash dump file: C:\Windows\Minidump\052017-4125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14EC00)
Bugcheck code: 0x19 (0xE, 0xFFFFA00B4C0E1BB0, 0x0, 0x239BCDC4C1D63759)
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. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Qualcuno può aiutarmi?
Grazie in anticipo per la disponibilità.
 
Pubblicità
Pubblicità
Indietro
Top