Ah you get off to sleep. These tests can wait. Did the machine come with a list of settings they used to overclock. If so seeing that would be out interest to me being an overclocker and all.
Sent from my Nexus 6 using Tapatalk
No, only the BIOS profile. I can have a look at that and let you know anything but can only compare default and that. I know the CPU was taken from 3.5ghz to 4.5ghz but it's the memory timings etc that's probably of more interest.
No problem although I would test for longer when you get chance. Simply because 4 hours isn't long enough.
I thought the blue screens had stopped after you removed the driver specified by the C4 dump?
And yes your overclock settings would be interesting as most of us have at one time or another overclocked something or other although nowadays it's nothing like the dark art it used to be..
It's been quite a few years since I overclocked myself. With family taking up time and not having the spare money to replace things if I break them I don't generally experiment like I used to
.
I've copied the crash dump analysis from whocrashed, the BSODS relating to
gpcidrv64.sys stopped when I removed the gigabyte program but I continued to get the other kind relating to
ntoskrnl.exe
Crash Dump Analysis
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Mon 12/12/2016 18:06:26 your computer crashed
crash dump file: C:\Windows\Minidump\121216-6593-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x139 (0x3, 0xFFFFE001E3A3EB60, 0xFFFFE001E3A3EAB8, 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 12/12/2016 18:06:26 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module:
nvlddmkm.sys (nvlddmkm+0x9742C)
Bugcheck code: 0x139 (0x3, 0xFFFFE001E3A3EB60, 0xFFFFE001E3A3EAB8, 0x0)
Error:
KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7bb3101ce32915cc\nvlddmkm.sys
product:
NVIDIA Windows Kernel Mode Driver, Version 376.19
company:
NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 376.19
Bug check description: The kernel has detected the corruption of a critical data structure.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 376.19 , NVIDIA Corporation).
Google query:
NVIDIA Corporation KERNEL_SECURITY_CHECK_FAILURE
On Mon 12/12/2016 16:44:48 your computer crashed
crash dump file: C:\Windows\Minidump\121216-5828-01.dmp
This was probably caused by the following module:
gpcidrv64.sys (GPCIDrv64+0x1851)
Bugcheck code: 0xC4 (0xF6, 0x430, 0xFFFFD380A6D07080, 0xFFFFF80AFDCC1851)
Error:
DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. 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: gpcidrv64.sys .
Google query:
gpcidrv64.sys DRIVER_VERIFIER_DETECTED_VIOLATION
On Mon 12/12/2016 16:43:22 your computer crashed
crash dump file: C:\Windows\Minidump\121216-11859-01.dmp
This was probably caused by the following module:
gpcidrv64.sys (GPCIDrv64+0x1851)
Bugcheck code: 0xC4 (0xF6, 0x4A8, 0xFFFFD38EF9C1E780, 0xFFFFF80ABE191851)
Error:
DRIVER_VERIFIER_DETECTED_VIOLATION
Bug check description: This is the general bug check code for fatal errors found by Driver Verifier.
A driver references a user-mode handle as kernel mode. 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: gpcidrv64.sys .
Google query:
gpcidrv64.sys DRIVER_VERIFIER_DETECTED_VIOLATION
On Mon 12/12/2016 16:39:46 your computer crashed
crash dump file: C:\Windows\Minidump\121216-7250-01.dmp
This was probably caused by the following module:
ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0x139 (0x3, 0xFFFFB800CF1A4440, 0xFFFFB800CF1A4398, 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.
Hope that helps, off to sleep now. As before thanks for the replies.