Windows 10: BSOD and restarts after bug control 0x0000000a and more random errors

Hello everyone.

I'm getting desperate.

After abandoning Mac, I bought a 4k € desktop last year (Jan 2016) for 3D modelling and rendering, and also for flightsimming. Initially, it was an MSI X99A with a i5930 processor and an Nvidia 980Ti, but it seemed to be insufficiënt for Fsimming. So I bought an ASUS z270f mobo with an i7700k and an nVidia 1080 as replacement.

Since I place the mobo myself - I am a PC noob, but I can read manuals very well - I get constant BSOD, random system restarts, with all different error codes. I know where to find the logs, I know where the .dmp files are, but I don't know anybody who can help me. I'm getting desperate, after years of struggling with Fsims on poor Mac-power, I was so happy to gotten to save money for finally able to buy a decent Sim-PC... but now this *cry

Could it be a faulty Mobo? Did I screw up stuff? How should I proceed from this point on?

Thank you in advance for your helpful replies!!!!!

Kind regards,

bob

:)

 

I've been having BSOD errors with my Lenovo Yoga 2 13 over the past few weeks, BSOD IRQL_NOT_LESS_OR_EQUAL.

* Original Title: BSOD IRQL_NOT_LESS_OR_EQUAL

I've been having BSOD errors with my Lenovo Yoga 2 13 over the past few weeks with some freezing happening the other day (unresponsive to mouse and keyboard, hard shutdown required). Most of the BSODs have displayed a IRQL_NOT_LESS_OR_EQUAL error with the
bugcheck code 0x0000000a. Just trying to get some ideas here on whether it may be a faulty driver or hardware. I did a complete reset and fresh install of Windows 10 yesterday and it had been working fine until today when the same BSOD came up. After the reset,
I updated the following drivers: Intel HD Graphics version 20.19.15.4331, Lenovo ACPI-Compliant Virtual Power Controller version 13.52.34.549, BIOS build 96CN31WW(V1.17)

System Specs:

Lenovo Yoga 2 13"

Windows 10 Home

OS build 10586.218

Intel Core i5 4210U CPU

8 GB RAM

Here is the most recent BSOD dump file (Created from BlueScreenView)

Bug check string: IRQL_NOT_LESS_OR_EQUAL

BCC: 0x0000000a

Parameter 1: 00000000`00000008

Parameter 2: 00000000`00000002

Parameter 3: 00000000`00000000

Parameter 4: fffff803`2e9e9675

Caused by driver: hal.dll

Caused by address: hal.dll+1b675

Crash address: ntoskrnl.exe+142760

Any help is greatly appreciated, thanks.

 

Windows 10 fall Creators Update crashing 55%

Hi Auggy

Sorry for the delay.

I made the changes you suggested, I did indeed have a VPN installed which I have removed, and turned fast boot off however the update still failed. Possibly with the same error. I was troubleshooting some more but now I have developed another issue, every
shutdown/restart is causing a BSOD. with

IRQL_NOT_LESS_OR_EQUAL 0x0000000a

It is saying that ntoskrnl.exe is causing the issue, which is like the other error im getting with the update. So something must not be right with this driver?

Edit: I have fixed IRQL error - Turning fast boot back on stops it from BSOD when shutting down or restarting. Will try update again.

 

We will be happy to help! *Smile Please upload the logfiles as instructed at the top of the page: Posting Instructions

 

Wow, thanx for the fast reply.

This should be the logfile

 

There are no crash dump files recorded. I'm wondering if you have accidentally deleted them with CCleaner. You can alter the settings in CCleaner so that it does not delete mini-dump files. If this is the problem wait for as few more BSOD events and re-post the logfiles.

 

Thank you. That may be possible. I'm going to alter my CCleaner now, and will come back to this post later.

Have a nice evening!

 

Aaah, no, I moved my dumps to the desktop, I wanted to post them on my dropbox. I'll put them back and recollect the info. Silly me

 

Here they are. Sorry for that.

 

I've looked at the two crash dumps - both make reference to memory corruption and one highlights the graphics driver as being faulty. I'm not convinced these are the real causes but for completeness I suggest you start with the following.

1. Please reinstall the NVidia driver. The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.

2 Run a memory test. In your case this is going to take a very long time to get through 8 or more passes. You could test the modules separately if you wanted by removing them all and testing just one at a time.





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.

Make a photo of the result and post it.

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.

 

Thank you!

I know what to do this weekend. I really hope I can find the faulty hardware this way.
At least I finally have a starting point after all these weeks. Great forum.

Enjoy your weekend!

 

One other thing I noticed in your error log. You have several errors for fast start-up failing:

Windows kan niet snel worden opgestart met de foutstatus 0xC00000D4.

You can temporarily turn off this feature and see if it makes a difference.
Turn On or Off Fast Startup in Windows 10

 

I'll try that as well. Thank you. I decided to test the 4 modules together. When one fails, can I see which one, and also, in which slot? Maybe the slot can be faulty as well?

 

Yes, the slot could also be faulty so it is important after testing all four together and if you find errors you will need to repeat the tests with individual modules until you find either the faulty RAM or slot. Unfortunately it is not possible to identify exactly which RAM is faulty when testing them all together.

 

Okay, will run a full system test. My gut says its my nvidia card somehow. I'll keep you posted. Thanks man