Upgraded from Win 7 to Win 10. BSOD ntoskrnl IRQL_NOT_LESS_OR_EQUAL

axe0 · 14 Nov 2015

Keep the clean install in mind and let me know how it goes :)

demoncamber · 16 Nov 2015

Ugh.. Just got another ntsokrnl bsod IRQL

Is there any way to find the root cause of this issue?

==================================================
Dump File : 111615-43093-01.dmp
Crash Time : 11/16/2015 1:11:37 AM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000039
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff803`b6499690
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14f4d0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+14f4d0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\111615-43093-01.dmp
Processors Count : 6
Major Version : 15
Minor Version : 10240
Dump File Size : 145,177
Dump File Time : 11/16/2015 1:21:56 AM
==================================================

axe0 · 16 Nov 2015

Hi demoncamber,

I don't know what program you have used, but I assure you that the data we need isn't available in the program.

When you get another BSOD, we need you to run the DM Log Collector tool, upload the zip and give some description so we can analyse the files and try to find a patern using the files and your description.

The ntoskrnl.exe is a Windows file, blamed when no other file can be blamed. If it is indeed the cause, one would have so much more problems. The point: a Windows file is rarely the real cause and I have yet to see it happen for the first time.

demoncamber · 17 Nov 2015

I ran the tool, refreshed the upload in the first post, that's got a few bsod's in there. Should I run another?

axe0 · 17 Nov 2015

Please run DM again, this zip is from 3 days ago and thus wouldn't contain anything regarding the new bluescreen.

demoncamber · 17 Nov 2015

There you go, all up to date. Since then, I've removed all old and uninstalled drivers from previous devices and refreshed all my hardware drivers as well. So far so good no BSOD yet today.

axe0 said:

Please run DM again, this zip is from 3 days ago and thus wouldn't contain anything regarding the new bluescreen.

axe0 · 18 Nov 2015

I suggest you check Creative and Unified for updates.

Creative driver

Code:

*** WARNING: Unable to verify timestamp for ha20x2k.sys
*** ERROR: Module load completed but symbols could not be loaded for ha20x2k.sys

Unified driver

Code:

*** WARNING: Unable to verify timestamp for uvhid.sys
*** ERROR: Module load completed but symbols could not be loaded for uvhid.sys

Also check Windows Update for the new Windows 10 10586 update. It may help with your problem.