Thanks for the quick answer! Here are the results:
--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-8G0QH34
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: MS-7798, MSI, B75MA-P45 (MS-7798)
CPU: GenuineIntel Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17111621632 bytes total
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sat 12.03.2016 12.15.40 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031216-12703-01.dmp
This was probably caused by the following module: hal.dll (hal!KeQueryPerformanceCounter+0x64)
Bugcheck code: 0xA (0xFFFFF803637EB1C4, 0xFF, 0x3D, 0xFFFFF80363FEB1C4)
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 Sat 12.03.2016 12.15.40 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: hal.dll (hal!KeQueryPerformanceCounter+0x64)
Bugcheck code: 0xA (0xFFFFF803637EB1C4, 0xFF, 0x3D, 0xFFFFF80363FEB1C4)
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 Sat 12.03.2016 11.42.44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031216-35171-01.dmp
This was probably caused by the following module: ndis.sys (ndis!guard_dispatch_icall_nop+0xD)
Bugcheck code: 0xD1 (0xFFFFF00573E3A180, 0x6, 0x0, 0xFFFFF80100AD6BED)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
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 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 12.03.2016 11.24.16 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031216-14234-01.dmp
This was probably caused by the following module: rt64.sys (rt640x64+0x13D3A)
Bugcheck code: 0xA (0xFFFFF801861C2770, 0x2, 0x8, 0xFFFFF801869C2770)
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: rt64.sys .
Google query: rt64.sys IRQL_NOT_LESS_OR_EQUAL
On Thu 10.03.2016 21.31.50 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\031016-15453-01.dmp
This was probably caused by the following module: ndis.sys (ndis!ndisInterruptDpc+0x2C8)
Bugcheck code: 0xA (0xFFFFF801826D1410, 0x2, 0x8, 0xFFFFF80182ED1410)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
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 Wed 09.03.2016 14.37.10 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030916-23312-01.dmp
This was probably caused by the following module: hal.dll (hal!HalBugCheckSystem+0xCF)
Bugcheck code: 0x124 (0x0, 0xFFFFE00070AF4028, 0xBE000000, 0x800400)
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 be caused by a 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 09.03.2016 02.40.25 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\030916-15625-01.dmp
This was probably caused by the following module: ndis.sys (ndis!guard_dispatch_icall_nop+0x1)
Bugcheck code: 0x1E (0xFFFFFFFFC000001D, 0xFFFFF8002FD26BE1, 0xFFFFF8018EB96740, 0xFFFFF8018EB26508)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
Bug check description: This indicates that a kernel-mode program 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 27.02.2016 14.05.51 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022716-12015-01.dmp
This was probably caused by the following module: hal.dll (hal!HalpProcessorResumeFromIdle+0xC)
Bugcheck code: 0xA (0xFFFFF803285E89A0, 0xFF, 0x0, 0xFFFFF80328DE899C)
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 Sat 27.02.2016 13.18.49 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022716-11875-01.dmp
This was probably caused by the following module: rt64.sys (rt640x64+0x13D3A)
Bugcheck code: 0xD1 (0x9E3F47BC, 0x2, 0x0, 0xFFFFF80082AEE57E)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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.
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: rt64.sys .
Google query: rt64.sys DRIVER_IRQL_NOT_LESS_OR_EQUAL
On Fri 26.02.2016 20.11.06 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\022616-15437-01.dmp
This was probably caused by the following module: ndis.sys (ndis!ndisReceiveWorkerThread+0xB7)
Bugcheck code: 0xFC (0xFFFFF800885A0EF7, 0x8000000411C47963, 0xFFFFD000873ED9B0, 0x2)
Error: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
file path: C:\WINDOWS\system32\drivers\ndis.sys
product: Operativsystemet Microsoft® Windows®
company: Microsoft Corporation
description: Network Driver Interface Specification (NDIS)
Bug check description: This indicates that an attempt was made to execute non-executable memory.
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. There is a possibility this problem was caused by a virus or other malware.
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.
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------
22 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has 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:
rt64.sys
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by 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 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.
I will look into updating the BIOS
Facebook
Twitter
Instagram