Windows 10: Couple of BSODs in the last day. No clear idea how to proceed. KMODE_EXCEPTION_NOT_HANDLED...

So this is my daughters' box.

A hand-me-down as the base from a friend of mine with a couple of upgrades.


i5-2500k
ASrock p67 pro3

4x4GB DDR3 1333
Geforce GTX 980

2 SSDs 256 GB, one of them completely new, second at 91% health.


There have been BSODs in the past. I got a new SSD and installed a fresh copy of Win 10. That fixed most of that and things were okayish still 1-2 BsoD per month.

Now for whatever reason, they started appearing much more frequent again in very short succession 4 alone yesterday, some just 5 mins after restarting, and I'm lost at this point.


Most of the dumps point to clipsp.sys which is often!? a driver issue, but I can't identify the culprit.
Coupled with the old hardware, there are just no drivers newer than 2015 for the mainboard/bios.


But maybe those are not even the faulty ones.


She had one crash again today while playing overcooked, which is also noted in the dmp, indicating a catastrophic memory failure. Maybe the memory is faulty? I ran Memtest for 2h and that looked fine. Running a longer period has to wait until the weekend as she needs the box for online school right now.


One thing that I noted today is that HWInfo is showing the Ram only running at 667Mhz despite all 4 being capable of 1333Mhz. That nudges me into thinking that maybe one of the slots is faulty.

If someone can get more information out of the minidumps or has another tip for me, that would really be appreciated.


Minidumps.zip ~1 Mb

:)

 

Windows 10 - KMODE_EXCEPTION_NOT_HANDLED netio.sys BSOD

So after I had updated Windows I decided to play a game and after aprox. 10-15 minutes, I got a "kmode_exception_not_handled" BSOD.

So I let it restart and do its thing. Later I get a different BSOD (which I can't remember.) Then the same day I get "kmode_exception_not_handled" BSOD again.

I wait for it to do its thing again and then after it's done I update drivers and such. It works fine for the next couple of days.

But today when I had just started the computer and was just was about to type in my pincode, it gave me "kmode_exception_not_handled" BSOD.

I honestly don't know what to do anymore so I'll just upload the .dmp and hope that someone can figure this out.

Here is the .dmp file.

 

BSOD - KMODE_EXCEPTION_NOT_HANDLED

A couple (1-3) times a day my W540 laptop will display a blue screen of death with the error message KMODE_EXCEPTION_NOT_HANDLED. The machine then restarts and works fine until the next iteration. The specific cause (which I understand is sometimes displayed
under this error) is not listed. The machine restarts and then later on that day will do the same. I am trying to determine the cause of the error. I haven't installed any new hardware or software recently, Windows 10 is up to date, and the BSOD troubleshooter
didn't find anything wrong. I looked at the Event Viewer to try and determine the cause (Event Viewer>Windows Logs>System) but all I could find was a list of "Event 6008" entries that each read "The previous system shutdown at 6:39:26 AM on ‎1/‎23/‎2018 was
unexpected." Here's a list of the recent unexpected restarts:

Restart at 3:10AM on 23 January 2018

Restart at 6:39AM on 23 Jan

Restart at 6:25AM on 22 Jan

Restart at 5:12AM on 22 Jan

Restart at 8:24PM on 21 Jan

Restart at 5:01PM on 21 Jan

Restart at 4:10PM on 21 Jan

Restart at 12:10AM on 20 Jan

Restart at 3:02AM on 20 Jan

 

Kmode_exception_not_handled BSOD in Windows 10

Hi Lucas,



Thank you for posting your query in Microsoft Community. I regret the inconvenience caused to you. Let me help you.

• 
  When did the BSOD screen appeared?
  
• 
  Have you made any changes in settings or installed any third party software prior to the issue?
  

I would suggest you to refer to the troubleshooting steps suggested by
Babu V in the link below and check if it helps:

How to troubleshoot blue screen
errors in Windows 10

For more information regarding this error code, you can refer to the link below:

Bug Check 0x1E: KMODE_EXCEPTION_NOT_HANDLED

Check if it helps.



If you need any further assistance, please feel free to contact us again. We will be happy to assist you further.