Ho fatto già memtest con i blocchinsingoli e non ci sono errori,con crystaldisk mi.dice che l hdd è a rischio.
https://imageshack.us/i/pmd74Wmgp scannow su cmd
https://imageshack.us/i/plgnJVBPp crystaldisk
Non faccio oc,inoltre ho visto altri con la mia stessa gpu e alimentatori da 500w
- - - Updated - - -
On Sun 10/07/2016 12:29:17 GMT your computer crashed
crash dump file: C:\Windows\Minidump\071016-12078-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80125D4B6F8, 0xFFFFD00024BA6460, 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 Sun 10/07/2016 12:29:17 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: 0x3B (0xC0000005, 0xFFFFF80125D4B6F8, 0xFFFFD00024BA6460, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 Sat 09/07/2016 20:24:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070916-12781-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFC92F658, 0x1000000000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.
On Sat 09/07/2016 20:23:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070916-12890-02.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1427A0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68115F17FF8, 0x200, 0x1FF)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.
On Sat 09/07/2016 20:15:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070916-12875-01.dmp
This was probably caused by the following module: ci.dll (CI+0x32B2C)
Bugcheck code: 0x7F (0x8, 0xFFFFD000E3CBDA30, 0x42024, 0xFFFFF80166AB2B2C)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\ci.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Code Integrity Module
Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap.
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 Sat 09/07/2016 16:24:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070916-26796-01.dmp
This was probably caused by the following module: acpi.sys (ACPI+0x7165C)
Bugcheck code: 0x1000007E (0xFFFFFFFFC000001D, 0xFFFFF8004129165C, 0xFFFFD001B63297C8, 0xFFFFD001B6328FE0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\acpi.sys
product: Sistema operativo Microsoft® Windows®
company: Microsoft Corporation
description: Driver ACPI per NT
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 that cannot be identified at this time.
On Sat 09/07/2016 16:19:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070916-12203-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142760)
Bugcheck code: 0x1A (0x3F, 0x4F13, 0xE79E3246, 0xA79E3246)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.
On Sat 09/07/2016 12:31:34 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070916-15687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142760)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68000019E50, 0x150, 0x14F)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.
On Fri 08/07/2016 20:31:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070816-12968-01.dmp
This was probably caused by the following module: hal.dll (hal+0x2949)
Bugcheck code: 0xA (0x10A, 0x2, 0x1, 0xFFFFF800238F23A4)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 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 Fri 08/07/2016 19:07:05 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070816-11875-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142760)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000024780, 0x400000000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.
