- 17,011
- 5,013
- CPU
- Intel® Core™ i7-920 Processor - @3.33GHz
- Dissipatore
- Stock Intel
- Scheda Madre
- Asus P6T - socket LGA 1366
- HDD
- Samsung 830 128GB + Samsung Spinpoint F4 320GB + Seagate Barracuda 1,5 TB
- RAM
- Corsair DDR3 1333MHz CL9 XMS3 DHX (3x2GB) - @1674MHz
- GPU
- MSI R6970 Lightning
- Audio
- Realtek ALC 1200
- Monitor
- HP 2310i
- PSU
- XFX Pro 750W Core Edition
- Case
- Cooler Master HAF 922
- Periferiche
- R.A.T. 5 Cyborg Mad Catz - Keycool KC84
- OS
- Arch Linux + Windows 10 Pro
no fede, tranquillo, con lele si scherza :)
ecco il report che mi avevi chiesto. c'è altro di cui hai bisogno?
Codice:
System Information (local)
Computer name: DESKTOP-67UJ40E
Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P6T
CPU: GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 4284600320 bytes total
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Tue 07/03/2017 12:15:11 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF8010008005F)
Bugcheck code: 0x50 (0xFFFFF8010008005F, 0x0, 0xFFFFF80A27AE21DC, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
A third party driver was identified as the probable root cause of this system error.
Google query: PAGE_FAULT_IN_NONPAGED_AREA
On Mon 06/03/2017 17:51:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030617-21062-01.dmp
This was probably caused by the following module: hal.dll (hal!memcpy+0x40)
Bugcheck code: 0xA (0xFFFFCE155760CC70, 0x2, 0x0, 0xFFFFF80390236880)
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 Mon 06/03/2017 15:56:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\030617-19984-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFF800E864AE70, 0x400A02, 0xFFFFF800E688FA92)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Mon 20/02/2017 16:43:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\022017-19828-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFF801F164AE70, 0xFFFFF801F1634F31, 0xFFFFF801EF961BD0)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Fri 17/02/2017 16:47:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021717-20609-01.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFA28DE9B44028, 0xBE000000, 0x300152)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might also be caused because of overheating (thermal issue).
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 Wed 08/02/2017 18:57:46 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020817-19718-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpDmaNextContiguousPieceV3+0x18D)
Bugcheck code: 0x7F (0x8, 0xFFFFF80009C4AE70, 0xFFFFF80009C34EC0, 0xFFFFF80007F2AE19)
Error: UNEXPECTED_KERNEL_MODE_TRAP
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
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 Thu 02/02/2017 11:19:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020217-9218-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!WheapCreateLiveTriageDump+0x7B)
Bugcheck code: 0x124 (0x0, 0xFFFFAF8806D7D8F8, 0x0, 0x0)
Error: WHEA_UNCORRECTABLE_ERROR
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. 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.
On Sat 28/01/2017 14:10:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012817-16515-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFA5000A9ABB30, 0xFFFFA5000ED21010, 0xFFFFF803610CCCDE)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
On Tue 24/01/2017 16:09:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012417-15953-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x1E5, 0x2, 0x0, 0xFFFFF8025B0FD254)
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.
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 13/01/2017 17:50:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011317-16125-01.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7F (0x8, 0xFFFFD680A25E8B30, 0x4A2BF760, 0xA82782)
Error: UNEXPECTED_KERNEL_MODE_TRAP
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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
Conclusion
14 crash dumps have been found and analyzed. Only 10 are included in this report.
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 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.
