BSOD while rendering in Adobe Premiere

Hi,

I have a problem with system crashing while rendering movie (Adobe Premiere).

Since I'm using this PC (around 2 years) I've never had system crash.
I don't know what changed today but I had 2 BSOD and every time I'm rendering big project it happens again. Yesterday I was rendering project and it was done smooth. Today same project is crashing to blue screen.

Can anyone tell me whats wrong with my PC?

Here is some information provided by WhoCrashed:

--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

Computer name: MARCIN-PC
Windows version: Windows 7 Service Pack 1, 6.1, build: 7601
Windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., P8P67 REV 3.1
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17145413632 bytes total

MY NOTE:
GPU - NVIDIA GTX970 4G
CPU - Overclocked to 4.3GHz (cooling is working well)

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Wed 2018-07-18 12:52:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071818-69872-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70400)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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 can be caused by non-responding hardware or by a overheated CPU (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 Wed 2018-07-18 12:52:49 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: hal.dll (hal!halreturntofirmware+0xb2d)
Bugcheck code: 0x101 (0x19, 0x0, 0xFFFFF880009B3180, 0x4)
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 can be caused by non-responding hardware or by a overheated CPU (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 Wed 2018-07-18 11:15:15 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071818-50372-01.dmp
This was probably caused by the following module: hal.dll (hal+0x12A3B)
Bugcheck code: 0x124 (0x0, 0xFFFFFA80106A0028, 0xBE200000, 0x5110A)
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.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



EDIT 1:



I've turned Driver Verifier on to check the drivers and after a minute of turning PC on crash occurred.
Then I've turned Driver Verifier off using Safe Mode to use computer.

Dumps (OneDrive):

https://1drv.ms/f/s!AmnkftOjZ2pNv38XNYRGnix9Q6QX

There is 2 dumps of BSOD's occurred when rendering and 2 after Driver Verifier.

That's all dumps I have in directory.



EDIT 2:



MemTest86 shows everything fine with memory.
Prime95 causing BSOD after 30 seconds. Dump added to OneDrive.