OK, this might be useful or not for people that experienced this.
In my case, the issues were all related to Intel Networking drivers.
After restoring my old backup and using that one, I did not install any other drivers besides the chipset driver.
I've used it for two weeks and counting without any issues until, yesterday when I've decided to update my networking drivers.
Intel(R) Ethernet Connection (2) I218-V, was using the driver that came either with Windows or with my old x79
networking drivers (the x79 platform, p9x79 pro had also an intel nic)
So, after updating the NIC driver, more exactly to version 64220.127.116.11 I had my first BSOD in two weeks
Download Network Adapter Driver for WindowsÂ® 10
Since I'm backing up on a weekly base, I do have a backup prior to updating my networking drivers.
Dump File : 050916-17859-01.dmp
Crash Time : 09.05.2016 00:49:41
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00003799`40df8740
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff803`c9e621d6
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+142760
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10586.212 (th2_release_sec.160328-1908)
Processor : x64
Crash Address : ntoskrnl.exe+142760
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\windows\Minidump\050916-17859-01.dmp
Processors Count : 12
Major Version : 15
Minor Version : 10586
Dump File Size : 275.511
Dump File Time : 09.05.2016 00:51:51