BSOD from ntoskrnl when explorer.exe is open

Update the display driver to the latest.

And, Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Various different BSODs head to head.

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
________________________________________________

Code:

BugCheck 1A, {41284, 7379001, 5469, fffff70001080000}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

Followup: MachineOwner
---------------------------------------------------------
BugCheck 24, {1904fb, fffff8800db19ce8, fffff8800db19540, fffff880012a8317}

Probably caused by : Ntfs.sys ( Ntfs!NtfsFindPrefixHashEntry+1fe )

Followup: MachineOwner
---------------------------------------------------------
BugCheck 3B, {c0000005, fffff960002ff016, fffff88009847c90, 0}

Probably caused by : win32k.sys ( win32k!RBRUSH::vRemoveRef+12 )

Followup: MachineOwner
---------

Before checking the dumps, I will ask for the result of memtest 86+. :)

Because DV applies here only if memtest did not show any error.

Checked the BSODs of 17/02 .... they all nor not providing any sufficient information, rather than some hints of memory corruption. Though the memory corruption can be caused by some misbehaving drivers too.

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

So when you enabled Driver Verifier, it did not cause any BSOD at all? And you noticed screen glitches only?

Your last three crash dumps are all different within a very small period.

Code:

BugCheck 4E, {99, 35b4aa, 0, fffffa800a11dfe0}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

Code:

BugCheck 1000007E, {ffffffffc0000005, fffff8800f1ab151, fffff880059b3ef8, fffff880059b3750}

Probably caused by : atikmdag.sys ( atikmdag+110151 )

Followup: MachineOwner
---------

Code:

BugCheck 1A, {41284, ef20001, 1d669, fffff70001080000}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+4ad3 )

Followup: MachineOwner
---------

Uninstall your installed latest version of the display driver.

• How-To Uninstall AMD Catalyst Drivers From A Windows Based System

Then clean up any possible leftover.

• Drivers - Clean Left over Files after Uninstalling

Then install version 13.9 WHQL only.

• Previous AMD Catalyst? Display Drivers

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

How many passes you ran memtest? Run memtest again. Let us see a camera snap of the computer screen when it is completing 8 passes.