Windows 10: BSOD Unexpected_kernel_mode_trap+system_check_exception+ several other

Hi,

Been having several bsod-incidents after putting together my new windows 10 skylake gaming pc. So far I've had maybe 2 days of joy of gaming in the last month or so. After that two days of use, I started to experience bsod every now and then and it seems that it's getting worse every day (today several crashes). So far I've had all the typical ones (irql_not_less_or_equal, system_service_exception, machine_check_exception and clock_watchdog_exception) and I'm running out of ideas what to do. So far I've updated bios, updated every single driver I could get my hands on, reconnecting every psu plug I could, downclocked my gfx-card, memory and cpu, reinstalled windows from scratch etc etc. I put a lot of money to this computer and I'm really getting frustrated with it. *Sad

Please, help this Finnish guy out. *cry
Attachment 36143

Edit:
Configuration of my pc:
i5 6600k
Asus Z170-a
16gb of kingston ddr4 2400mhz
kinston hyper-x 480gb ssd+crucial mx100 512gb ssd (pudated firmware)
Gigabyte 980ti g1 gaming
xfx 1050w black edition (gold)
Enermax liqtech 240x aio-cooler

win10 64

:)

 

BSOD - KMODE_EXCEPTION_NOT_HANDLED

Also, the most recent BSOD displayed a new error message: UNEXPECTED_KERNEL_MODE_TRAP

 

BSOD: UNEXPECTED_KERNEL_MODE_TRAP and other errors

Hi,

Link to your minidump leads to an error message at OSR. And on a new home build the issue is almost always hardware. Further indications are the re-installs did not help and that driver verifier found nothing.

Finding and correcting hardware issues at home can be very challenging since there usually is limited "known good" parts to swap in and out.

Remove ALL power. Then carefully remove the cards one at time and put them back in their slots. Do the same for the memory and then the cables. A loose or corroded connection point can cause strange issues.

Be sure you have the latest BIOS, chipset drivers, firmware (for SSD and others), and updated major drivers. New hardware almost always comes with out-of-date firmware and drivers.

Reduce the system down to as simple as possible including memory to see if that helps.

---------------------------------------------------------------------------------------

Just to be sure :

Memory tests do not catch all errors such as mismatched memory (possible

even for sticks that appear to be identical) and when faster memory is placed

in system behind slower memory. So it is best to also swap sticks in and out


to check for those even if all memory tests fail to show a problem.

To test RAM check here - let it run 4+ hours or so. <-- Use this method

www.memtest.org

For the Vista/Windows 7 Memory Diagnostic Tool

Start - type in Search box -> Memory - find Memory Diagnostics tool at top of list

- Right Click - RUN AS ADMIN follow the instructions

How to Run the Memory Diagnostics Tool in Windows 7

Memory Diagnostics Tool - Windows 7 Help Forums

---------------------------------------------------------------------------------------

Troubleshoot blue screen errors

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

Hope this helps.

--------------------------------------------------------------------------------------------

Rob Brown -
Microsoft MVP <- profile - Windows and Devices for IT : Bicycle - Mark Twain said it right.

 

Hi Pricez,

Welcome to the 10forums.

It seems that I cannot access a file that for my opinion is pretty important, the file is msinfo32.nfo.
This doesn't mean I cannot help you, but this file contains a lot of important information for the process of debugging.
I don't know if others are having the same problem as I do, but would you please upload a new zip file for me.

 

It seems that even I can't open it... Will try to make a new one.

I can only open it with text-editor, not sure if that's the right way to do it... Might be because of it's in Finnish?

 

The language doesn't matter at all, I am dutch and see regular german, brazillian, france and other languages in that file (although I can't read those languages)

It looks like you have some problems with your CPU






Diagnostic Test

CPU TEST


Run Prime95 - Stress Test Your CPU - Windows 10 Forums




Note If you're overclocking anything, please stop it and set everything back to default while troubleshooting


Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

Heard about prime now suitable with the latest cpu's so I prefer realbench, if that's ok for troubleshooting?

 

I don't think it is a problem, but be sure to try Prime95 too.

 

Running prime95 atm, temps at 51 celsius after 15 minutes... Let's see what happens.

Edit: After an hour still running at 52c and nothing seems to be going wrong.. Cpu is clocked to 4.4Ghz by motherboad (there's a switch for an automatic oc on this mobo that oc's the cpu suitable for the cooling installed).

 

17hr's later everything seems to be working fine and dandy. Will come back in a week to mark as solved, if everything goes well. *Smile

Thanks Axe0.

 

It seems that KB3081455 started to cause irql_not_less_or_equal-bsod again. Right after it installed, it made my computer crash with that error message and when my computer restarted it finished updating itself with windows is finalizing an update (or something like that)-message. Same exact thing happened the first time I started to have these bsod incidents. Long story short, after restarting the bloody thing, 15 minutes and again bsod, so I uninstalled that update and everything is ok for now. Newest report, I hope it confirms that it was that update and nothing else. Fingers crossed.

 

I can find nothing related to either hardware or drivers, so I guess you're correct.
Or you want to try driver verifier?

 

New day, new update... This time I can't even log to my computer without a crash. This time it's driver verifier that is causing it with a message about iomanager violation (iomap64.sys). So some update is causing some driver not to function right... This time I can't just go and delete it, since I can't even use the bloody thing atm.
Edit: hidclass.sys is another bsod reason I get.

 

Try to access the troubleshooting options.
From there open the command prompt and enter "verifier /reset" (without quotes)
Reboot and see if you can login.

 

No help.. Can't even return to a previous stable state, because it's giving me some sort of an error message.