Ntoskrnl.exe and memory related BSOD with new hardware

Hello there, I'm the new one and here's my story:

Since I switched to the new Skylake plattform, I've had multiple BSOD, which all related to my memory/ntoskrnl.exe. The system also worked poorly with a 1000hz polling rate on my mouse (every mouse movement would result in a massive FPS and GPU usage drop in many games). With 125hz these problems didn't occur.
I've performed a fresh WIndows 10 install and ran Memtest86+ and chkdsk, which didn't show any errors. The mouse problem and the BSOD stayed. The RAM analysis tool from Windows showed some errors, so I first swapped out my RAM (which didn't change a thing) and after that my mainboard. While my new mainboard was on it's way, I switched to my old mainboard, CPU and RAM and everything worked perfectly.

Now I've put in the new Hardware again and set up a dual boot with Win 8.1 and Win 10. Both versions worked fine at first, even without that strage mouse polling rate problem. Because I only have a key for Win. 8, I had to update the Win 8.1 install to Win 10. Trying this, I already got two new ntoskrnl.exe related BSOD, so the core issue still seems to exist.

I simply can't pin down the problem with BlueScreenView and excessive googling and I'm overwhelmed by the windows debugging tool.
The whole situation is driving me crazy and I sincerely think that this forum could be my last hope.

Could someone please have a look at my file down below?
View attachment 65942

Kind regards,
TheDestron

PS.: My RAM is officially compatible with my mainboard and the problem exists with and without the new mainboard drivers and BIOS.

Hi TheDestron,

Welcome to the 8forums.

Unfortunately, I cannot really find a possible cause as a possible solution.
I do find lots of files dating from 2014 and earlier where some might need updating.
Please visit Windows Update and install every update available, it may take a couple of times to get them all.
Please remove Google Chrome while troubleshooting, Chrome lately causes for some people crashes.
Please update the device drivers as far as you can, via the site of the manufacturer of the driver. Do not update through device manager as you'll get always the message that the drivers are up to date.

I would like you to try driver verifier and run some hardware tests so we can get a lead to the cause.

Please follow this tutorial to run driver verifier.


Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.


Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.


If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

Part One: CPU Stress Test
Part Two: MemTest86+ RAM Diagnostic
Part Three: Hard Drive Diagnostics
Part Four: GPU Stress Test

Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 7 Help Forums

Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 7 Help Forums

Run SeaTools to check the integrity of your HDD. SeaTools - HDD test - Windows 7 Help Forums

Run chkdsk Chkdsk - HDD Test - Windows 7 Help Forums

Run Furmark to stress test your GPU. FurMark - GPU Stress Test - Windows 7 Help Forums

Hi axe0
Thanks for your help. I've installed the newest drivers for my mainboard again and startet the verifier. Nothing has happened until now... How can I see that the verifier is running? I can't find any process running which would seem to match the verifier.
I also ran Prime for a few minutes, but it was using only 95% of my CPU. Is this normal?

Edit: Close to 2 hours of the verifier running, I've hat a new BSOD while browsing in IE. It was the "PFN_LIST_CORRUPT" this time. I've found this thread: Sporadische Bluescreens PFN_LIST_CORRUPT ntoskrnl.exe - Am Ende meiner Weisheit where a slight increase of the RAM voltage was the solution.

Edit 2: Increasing memory voltage of 0.1v didn't help either.

Edit 3: Sending the new dump package, with somehow already known BSOD. DRIVER_VERIFIER_DETECTED_VIOLATION is a new one which occured with the verifier DISABLED... While trying to start GTA V. View attachment 65944

Edit 4: Running the system 3 hours on integrated graphics now, no BSOD since I removed my GTX 970. Verifier is running again and didn't cause anything. I'll continue over night and going to try an old GTX 570 tomorrow. The GTX 970 ran just fine with my old system this weekend so my suspect are the Nvidia drivers or some communication/incompatibility issue between GPU and mainboard.$

Edit 5: Putting the GPU in again caused the typical memory_management BSOD after 1 minute idle on desktop. Going to try an other slot for the GPU.... Which didn't change a thing. Going to try the GTX 570 now... Aaaand still the same.

Edit 6: I've wiped the Nvidia drivers with DDU and installed them again, this time without the HD audio and 3D drivers. I even was able to play some BF4 without a crash yet. Let's see if my PC will behave this evening.

Edit 7: So... Last night I was able to use the system and play games without any hiccup. Today I tried to put my soundcard back, installed the drivers and after more or less 5 minutes of watching YT videos, one of the known bluescreens appeared. I removed the soundcard and the drivers and activated the onboard one in the windows sound settings... Same situation, slightly different BSOD. Now I've deactivated the onboard sound in windows and plugged in an external one, the same as I've used the night before. My conclusion at this moment: My setup just hates any sound device or drivers. I hope that it won't crash with the external sound, so my theory will be approved. Does somebody know a problem like this or a possible solution?

Please run the tool again and upload the zip file for the new BSOD's and up to date information about your system.

Here you go, those are the two BSOD I got today. I also finally managed to update to Win 10 without any problem yesterday.

In the case of Windows 10, you need to create a new thread at the sister forum tenforums.com
Eightforums.com is ONLY for windows 8 / 8.1 users.

Okay, thanks for your help so far, I'm going to continue my journey over there with my new insights.
May I post the link to the new thread right here for people who may be looking for answers to a similar problem?

That is not something I can decide if it is allowed, I am just a user of this forum like you.