Windows 10: ntoskrnl bsods on fresh install

Hello,

I've recently update to x99 platform and I've freshly installed Windows 10 Pro
I'm having all sorts of issue with it.

I ended up reading all sorts of threads regarding bsods in Windows 10 etc (things that didn't happen on the old x79 platform)

Before posting here I've:
- Updated to the latest bios for my board
- Tested Memory via memtest, 1 pass (it took quite a lot for 32gigs)
- Tested Memory via build in testing tools ( Windows Memory Diagnostic )
- Tested CPU: prime small ffts (1h) occt - both standard and linpack (30min)

All tests pass and no issue. The parts are new, no issues durring setup, no issues on other os (let's say ubuntu)
The thing is that all of these BSODs (that are included) are somewhat related to ntoskrnl
The bsods are random and can sometimes occur out of thin air *Smile

My setup should appear in my info I guess.

:)

 

DRIVER_POWER_STATE_FAILURE stop error every boot

In my fresh windows 10 installation after a week of flawless operation I started to get this BSOD every time I boot up: system let's me log in and after ~1 minute it drops with the bsod - the interesting thing is that it happens only on first boot attempt;
when system automatically restarts, everything works properly and I am not getting bsod anymore.

Minidump points to ntoskrnl as the cause of the error so I am frustrated: initially I assumed some upgraded driver (like nvidia geforce) to cause this since there were no bsods for a week after fresh install, but it apparently turns out to be windows components,
probably introduced with some windows update.

Please suggest.

regards,

Pavel

 

BSOD Driver IRQL, NETIO.sys

Recently I installed a new GPU. I reinstalled drivers, but continued to have nvidia-driver related BSODs. A couple days ago, I did a complete fresh install of the nvidia drivers. Since then, I have been getting regular BSODs with a different message, "Driver
IRQL not less or equal error: netio.sys." For some reason I can't read the dump file either, something about ntoskrnl not being valid or working when trying to read the symbols.

How can I fix the constant blue screens? I know I could reinstall windows, but I'd really rather not... I uploaded the most recent .dmp at the link below.

Dump Files

 

Hi mehusername,

Welcome to the 10forums *Smile

There are some different crashes, but it looks like you may have some faulty memory given that most bugchecks are having pretty much the same causes and there is a hardware crash in the different crashes.
Lets first test your memory to see if a test can confirm it, please note that a test isn't always 100% meaning that if the test doesn't find any problem it could be the test is incorrect.
Please follow the instructions carefully.





Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

Thanks,

Glad to be here.
I will run memtest tonight and will get back with a report etc.

In the mean time, I've restored my old image of Windows 10 on another drive:
- Installed chipset drivers only for the x99 platform.
- Removed ai suite and that's about it... I'm guessing it might be a driver issue
- It has roughly around 8h of uptime without any bsods (which is more than strange)

I will reply later on with the memtest results.

 

OK,

This took quite awhile to complete, but here are the results.

 

OK, this might be useful or not for people that experienced this.

In my case, the issues were all related to Intel Networking drivers.
After restoring my old backup and using that one, I did not install any other drivers besides the chipset driver.

I've used it for two weeks and counting without any issues until, yesterday when I've decided to update my networking drivers.
Intel(R) Ethernet Connection (2) I218-V, was using the driver that came either with Windows or with my old x79
networking drivers (the x79 platform, p9x79 pro had also an intel nic)

So, after updating the NIC driver, more exactly to version 6420.7.68.0 I had my first BSOD in two weeks
Download Network Adapter Driver for Windows® 10

Code: ================================================== Dump File : 050916-17859-01.dmp Crash Time : 09.05.2016 00:49:41 Bug Check String : IRQL_NOT_LESS_OR_EQUAL Bug Check Code : 0x0000000a Parameter 1 : 00003799`40df8740 Parameter 2 : 00000000`00000002 Parameter 3 : 00000000`00000000 Parameter 4 : fffff803`c9e621d6 Caused By Driver : ntoskrnl.exe Caused By Address : ntoskrnl.exe+142760 File Description : NT Kernel & System Product Name : Microsoft® Windows® Operating System Company : Microsoft Corporation File Version : 10.0.10586.212 (th2_release_sec.160328-1908) Processor : x64 Crash Address : ntoskrnl.exe+142760 Stack Address 1 : Stack Address 2 : Stack Address 3 : Computer Name : Full Path : C:\windows\Minidump\050916-17859-01.dmp Processors Count : 12 Major Version : 15 Minor Version : 10586 Dump File Size : 275.511 Dump File Time : 09.05.2016 00:51:51 ==================================================[/quote] Since I'm backing up on a weekly base, I do have a backup prior to updating my networking drivers.

 

Glad to hear your issue is resolved, thanks for sharing your solution *Smile