Har testat att köra med ett ramminne åt gången, men datorn hänger sig fortfarande. Köpte ytterliggare några minnen som var med på QVL och dessa är 3000Mhz men i listan ska de gå att köra i 2400MHz men det crashar även där.
Fick upp denna informationen i Whocrashed:
On Fri 2017-07-07 21:51:08 your computer crashed
crash dump file: C:\Windows\Minidump\070717-7015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14CC20)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFFD000F9DAE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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 Fri 2017-07-07 21:51:08 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalPerformEndOfInterrupt+0x86)
Bugcheck code: 0x101 (0xC, 0x0, 0xFFFFD000F9DAE180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware 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.