BSOD repeatedly even after Clean Install Windows 10

[WREQD]

This is my system config just in case :
i7-2600k @3.6ghz CPUIntel® Desktop Board DH67BlGtx 1060 GPUDell D2215H monitor2 x 8gb DDR 3 1333mhz CL 9 rams 250gb HDD, Crucial MX 300 SSD 275GBAntec VP 500P PSU

I am facing severe BSOD issues since months now and i even bought a new motherboard, but the issue still persists .... I have all the drivers upto date and i have even clean installed Windows 10 but still the issue persists

So i came across the BlueScreenView app which enables me to share the data with you ... And EVERY BSOD in my history has been caused by ntoskrnl.exe which is a product of Microsoft .. here is the latest 3 BSOD details as per the app

==================================================
Dump File : 121516-9093-01.dmp
Crash Time : 15-12-2016 00:15:52
Bug Check String : SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x1000007e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff803`c8eecc10
Parameter 3 : ffff9b01`6921d4d8
Parameter 4 : ffff9b01`6921cd00
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+e3c10
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.576 (rs1_release_inmarket.161208-2252)
Processor : x64
Crash Address : ntoskrnl.exe+e3c10
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\121516-9093-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 14393
Dump File Size : 537,540
Dump File Time : 15-12-2016 00:20:39
==================================================

==================================================
Dump File : 121516-9937-01.dmp
Crash Time : 15-12-2016 00:11:38
Bug Check String : MEMORY_MANAGEMENT
Bug Check Code : 0x0000001a
Parameter 1 : 00000000`00041289
Parameter 2 : 00007ff6`b1235000
Parameter 3 : 00000000`0000076c
Parameter 4 : 000000f6`b1235005
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14a6f0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.576 (rs1_release_inmarket.161208-2252)
Processor : x64
Crash Address : ntoskrnl.exe+14a6f0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\121516-9937-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 14393
Dump File Size : 468,668
Dump File Time : 15-12-2016 00:12:15
==================================================

==================================================
Dump File : 121516-12640-01.dmp
Crash Time : 15-12-2016 00:10:34
Bug Check String : KMODE_EXCEPTION_NOT_HANDLED
Bug Check Code : 0x0000001e
Parameter 1 : ffffffff`c0000005
Parameter 2 : fffff803`33555257
Parameter 3 : 00000000`00000000
Parameter 4 : ffffffff`ffffffff
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14a6f0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.14393.576 (rs1_release_inmarket.161208-2252)
Processor : x64
Crash Address : ntoskrnl.exe+14a6f0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\121516-12640-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 14393
Dump File Size : 510,084
Dump File Time : 15-12-2016 00:11:14
==================================================


I have also run the sfc/scannow command and the Memory Management tools which was of no use

help me resolve the issue as it is out of my reach ... Hope i have provided all the information required

 

[cheese9k]

How frequent are these blue screens?

Have you tried running a single stick of memory/using a tool such as Memtest86+ to stess test your RAM?

Regards,
Cheese

 

[LukeFatwalker]

These BSOD's boil down to it either being RAM, Overclocking, or Out-of-date Drivers.

As was mentioned, test the RAM first. If that doesn't work, check if you're overclocking and disable if neccesary. Finally, if this doesn't work, try updating your drivers, particularly those tied to hardware.

If worse comes to worse, just re-format the machine.

You might also want to invest in a disk imager (i.e. Macrium Reflect) or a snapshot tool (i.e. RollBack Rx)

 

[WREQD]

How frequent are these blue screens?

Have you tried running a single stick of memory/using a tool such as Memtest86+ to stess test your RAM?

Regards,
Cheese

can u give me a proper link to it? I am coming across many apps from different sites when i google Memtest86+ ... i will surely try it out

 

[WREQD]

These BSOD's boil down to it either being RAM, Overclocking, or Out-of-date Drivers.

As was mentioned, test the RAM first. If that doesn't work, check if you're overclocking and disable if neccesary. Finally, if this doesn't work, try updating your drivers, particularly those tied to hardware.

If worse comes to worse, just re-format the machine.

You might also want to invest in a disk imager (i.e. Macrium Reflect) or a snapshot tool (i.e. RollBack Rx)

i have not Overclocked anything and i also made sure that every driver is up-to date by using apps like DriverEasy .... I ran the usual memory diagnostic tool provided in Windows 10 ... will try the memtest86+ one soon ... what do u make of the dump file data i have posted?

 

[LukeFatwalker]

These BSOD's boil down to it either being RAM, Overclocking, or Out-of-date Drivers.

As was mentioned, test the RAM first. If that doesn't work, check if you're overclocking and disable if neccesary. Finally, if this doesn't work, try updating your drivers, particularly those tied to hardware.

If worse comes to worse, just re-format the machine.

You might also want to invest in a disk imager (i.e. Macrium Reflect) or a snapshot tool (i.e. RollBack Rx)

i have not Overclocked anything and i also made sure that every driver is up-to date by using apps like DriverEasy .... I ran the usual memory diagnostic tool provided in Windows 10 ... will try the memtest86+ one soon ... what do u make of the dump file data i have posted?

You are getting BSOD's tied to ntoskrnl.exe which is ultimately tying to your RAM. So this is more than likely a hardware issue, but errors like this can occasionally be tied to Overclocking or driver updates.

Since you said it's not those last two, the likely culprit is your RAM. Back up your system beforehand and replace the RAM.

 

[WREQD]

I ran the driver verifier mentioned here https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983 and got a BSOD which said DRIVER_VERIFIED_DETECTED_VIOLATION iaStar.sys ..

What do u guys make of that?