High CPU load (or maybe RAM) causes display driver to crash and recover !

First my PC specs : CPU : i7 2600K RAM : HyperX FURY Black 8Go DDR3 160 HX316C10FB/8 CL10 (10-10-10-30) and 1600 MHz (PC3-12800) + 2*4Go Corsair Vengeance Low Profile 8 Go (2 x 4 Go) - DDR3 1600 MHz Cas 9 PSU : Cooler Master V750 80 PLUS Gold GPU : MSI GTX 1070 Armor OC Motherboard : Asrock Z77 Extreme 4 SSD : Samsung 850 Evo HDD : Hitashi 1To 7200rpm

Speecy : http://speccy.piriform.com/results/q4UBxPXFO8ZU0bRfHEGrBe8

First the issue happened two ago when I was browsing the web with Firefox Nightly 57 and used Molotov (to watch TV). The first time I didn't noticed it beacause I was eating but found it in the event viewer... The second time (doing the same thing with my computer) i saw the screen goes black and back fully responsive with the infamous "Nvidia driver didn't respond and have been recovered". So I thought maybe it's beacause of Nightly Firefox and Hardware Acceleration that might be buggy, but didn't be able to recreate like this !

So I perform to passes of memtest86+ (not in a single row) with no error and I re-dl Nvidia latest driver the DDU then reinstall.

I noticed that while stress test my CPU with IntelBurnTest that the issue occurs one more time (before reinstalling the driver).

The next day I tried to overclock my RAM (because maybe it's the "weakest point" of my PC and raise my FPSMIN on Witcher 3 GOTY by 5) and test it with memtest86+ (the second pass) with no error. But... Someone told that HCI memtest can detect more error than memtest86+ so I tried it.

What I did : desactivate the paging file so I will test only the RAM, and as I have 8 Treads and 12GB free RAM in W10 I set 8 instances of HCI memtest testing each one 1500Mb of RAM. But I noticed there was 970Mb of free (not reserved or wainting) ram so I run an other intance testing 960MB. HWMonitor was open to check CPU temp and it was something like 60-65°C so didn't worry at all. And the issue occurs again (black screen then recover) so I openend event viewer to search for event 4101 (the event corresponding). But the software was complaining that no ram is aviable bla bla and the screen froze ! Waited few minutes, computer was not responsive so I press power button and the computer shut off like a half second after.

Did an overclocked RAM (1600Mhz > 1866Mhz around 1.585V) and no RAM aviable (because no pagning file and opended event viewer with barely no RAM) can cause a computer to freeze ?

So I tried again to run HCI memtest without overclocking my RAM and CPU and trying to not use so much RAM and I found that under 100% CPU load I can recreate the event 4101 aka "Display driver didn't respond and have been recoverd"

EXTRA : When I bought my MSI GTX 1070 Armor OC I had to send it back : It was causing VIDEO_TDR_ERROR on boot (loading Windows). They give me a new one with the same problem and I call then and they told me to desactivate Fast Startup. I did and I have no problem since. I say that because event 4101 is related to TDR !

Thank for reading !

UP : The system froze like previous and this time the minidump was saved so what is taht whocrased said :

On Fri 25/08/2017 15:23:35 your computer crashed crash dump file: C:\Windows\Minidump\082517-10343-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560) Bugcheck code: 0xA (0x30, 0x2, 0x1, 0xFFFFF8018006AC4F) Error: IRQL_NOT_LESS_OR_EQUAL 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 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 the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

On Fri 25/08/2017 15:23:35 your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: bdfwfpf.sys (bdfwfpf+0x3BBE) Bugcheck code: 0xA (0x30, 0x2, 0x1, 0xFFFFF8018006AC4F) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Program Files\Common Files\Bitdefender\Bitdefender Firewall\bdfwfpf.sys product: BitDefender Firewall company: BitDefender LLC description: BitDefender Firewall WFP Filter Driver 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: bdfwfpf.sys (BitDefender Firewall WFP Filter Driver, BitDefender LLC)

So the issue started the 08/23/2017 and I install two things : LG United mobile Drivers and Firefox Alpha 57. Maybe try a system restore.

I was wondering... IRQL_NOT_LESS_OR_EQUAL means to me BAD RAM, but who crashed didn't say so.

EDIT : just lost my activation with no reason. And my PC is still listed on my microsoft account !

EDIT : just solved the activation issue ONLY. Had to reinstall Windows 10 again ! But before installing ANY driver, I get a BSOD BAD_POOL_HEADER

On Fri 25/08/2017 23:37:58 your computer crashed crash dump file: C:\Windows\Minidump\082517-5843-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x16BFD0) Bugcheck code: 0x19 (0xE, 0xFFFFC58A5192A9E0, 0x19013CFFFF8D46E0, 0xB1948C1BD5C21F41) Error: BAD_POOL_HEADER 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 a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. 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 25/08/2017 23:37:58 your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Bugcheck code: 0x19 (0xE, 0xFFFFC58A5192A9E0, 0x19013CFFFF8D46E0, 0xB1948C1BD5C21F41) Error: BAD_POOL_HEADER Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. 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. 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.

Both time (because Whocrashed sees two crashes for one) the software says "it's not likely to be caused by a hardware problem". I don't think so...

Annnnd can't make the (KB4034674) update with windows update beacuse it fails...