INTERRUPT_EXCEPTION_NOT_HANDLED BSOD, It is infuriating to fix

[mista.t007]

Hi, I have a BSOD that has come up in the past, it has driven me mad bonkers.
This Mostly Happens in game, but has come up in regular use


SPECS
----------
I'm Running Windows 10 Pro, fully Updated.
I have a Ryzen 1800x, at 4.0 (OC, before was stock 3.8)
I have 4 Sticks of 16 gb ram (64GB ~ 2100) Corsair
I have an RM 850i Powersupply with Corsair link enabled
I have Single 1080ti MSI
I have a MSI pro carbon gaming x370 mobo
I have a Corsairlink GTX AIO.
I have all Fans on my Rig Going 100%

Pherifhreals
---------------
Corsair K95 RGB / Corsair Utility Engine
Corsair VOID RGB Headset/ Corsair Utility Engine
Logitech G502 / Logitech Gaming Software
Occulus Rift/ Occulus Home.

The BSOD data from Blue Screen View HERE
And the Drivers that i have installed http://


Things I`ve done so far.
-----------------------------
Sfc/SCANNOW
Verifier.exe To locate faulty driver
MEMORY TESTING, USING Windows Memory Diag and Memtest86, passed on 8th pass.
Uninstalling all drivers in safe mode, and installing them
enabling/disabling driver enforcement bcdedit /set testsigning on
Replacing parts, Having guys test the Cpu, memory, Peripherals
Monitoring temps, at stable cpu is 34C, GPU is 35C, UNDER LOAD CPU 50C/GPU 55, sometimes hits 60-70C at max load.
Going back and resetting OC settings in BIOS, BSOD's Appeared even BEFORE I OC'D it.

What is the solution, I've almost tried everything.

 

[Colif]

That is an unusual Error

Bug Check 0x3D: INTERRUPT_EXCEPTION_NOT_HANDLED

The INTERRUPT_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000003D.

This bug check appears very infrequently.

- see, even Microsoft say so... though they could have given some clues.

remove overclock until we work out problem.

INTERRUPT_EXCEPTION_NOT_HANDLED is normally caused by incorrectly configured, old, or corrupted drivers, however, this can also be caused by driver conflicts after adding new hardware to your device, or that the memory (RAM) is corrupted.

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it