SOLVED IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe, Windows 10 Blue Screen Error (Images provided)

[Shervin Grey]

Hi, I was watching a video on KMPlayer and listening to some music on Groove Music App at the same time and I wonder if it somehow caused a blue screen error.

I looked it up online and Installed BlueScreenView App and got a report back:
==================================================
Dump File : 102515-22093-01.dmp
Crash Time : 10/25/2015 5:49:14 PM
Bug Check String : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code : 0x0000000a
Parameter 1 : 00000000`00000038
Parameter 2 : 00000000`00000002
Parameter 3 : 00000000`00000000
Parameter 4 : fffff802`22223ad2
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+14e2e0
File Description : NT Kernel & System
Product Name : Microsoft® Windows® Operating System
Company : Microsoft Corporation
File Version : 10.0.10240.16545 (th1.150930-1750)
Processor : x64
Crash Address : ntoskrnl.exe+14e2e0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\Windows\Minidump\102515-22093-01.dmp
Processors Count : 4
Major Version : 15

I would really appreciate it if you guys could tell me what's causing this. Thank you in advance.

OH and since I suspect this error has got something to do with my one of drivers, I'm providing a complete list of my installed drivers in a txt file.

 

[Trouble]

Would you mind attaching the actual .dmp file. Just zip it up and attach it to your next post.
You may need to copy it to another folder first as Windows is finicky about what you can do inside C:\Windows\MiniDump
I'm no expert, but I'll have a look and see if I can see any glaring issues. Our resident BSOD guy is not currently around.

That particular issue can sometimes be a result of and older BIOS, so you might check and see if the computer manufacturer or the motherboard manufacturer has an update.
Additionally, if you are currently over clocking anything (CPU, GPU, memory) please return those setting to proper defaults.

 

[Shervin Grey]

Would you mind attaching the actual .dmp file. Just zip it up and attach it to your next post.
You may need to copy it to another folder first as Windows is finicky about what you can do inside C:\Windows\MiniDump
I'm no expert, but I'll have a look and see if I can see any glaring issues. Our resident BSOD guy is not currently around.

That particular issue can sometimes be a result of and older BIOS, so you might check and see if the computer manufacturer or the motherboard manufacturer has an update.
Additionally, if you are currently over clocking anything (CPU, GPU, memory) please return those setting to proper defaults.

Hey there, I highly appreciate your well-timed reply. I uploaded the zipped dmp file as you requested. I checked my BIOS version with ASUS's website and it seems that it's the latest version. I just bought this laptop. And honestly I don't remember doing a thing with overclocking stuff since I'm no PC gamer. But I remember AMD Catalyst driver had some over clocking options which I did not touch at all, however, I reset all settings.

Thank you for your kind help,
Grey.

 

[Trouble]

I don't see anything that actually looks scary.
A single driver that has been known to historically cause some problems at least since Windows 7
AODDriver2.sys 2/11/2014 (AMD Over Drive) it looks a little old and may need updating or even uninstalling.
As I said, I'm no expert, but it looks like it may have just been a one off.
Personally, I'd continue using it and see if a pattern develops or if you can replicate the problem. A single dump file is not much to go on.

If it continues do a couple of the normal diagnostics.
Use the native check disk utility from an elevated command prompt, simply type
chkdsk C: /R
hit enter
answer "Y"
type exit
reboot

Additionally run memtest86
You can get the ISO from here http://www.memtest86.com/download.htm
burn it to a CD or USB ThumbDrive and boot your machine let it run over night if possible unless it starts pitching errors right away, then you have some work to do.

I mention those two because basically it pitched a page fault.

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000038, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80222223ad2, address which referenced memory

STACK_TEXT:
fffff802`244fa5a8 fffff802`22374ca9 : 00000000`0000000a 00000000`00000038 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff802`244fa5b0 fffff802`223734c8 : 00000000`00000001 ffffe001`e42539d0 fffff802`244fa750 fffff800`5646a1a2 : nt!KiBugCheckDispatch+0x69
fffff802`244fa6f0 fffff802`22223ad2 : fffff802`2257f180 000000f2`b8805611 00000000`00000000 fffff802`2257f100 : nt!KiPageFault+0x248
fffff802`244fa880 fffff802`22222be3 : ffffe001`e41dbb70 000003e3`cbb03e0e 00000000`00000000 00000000`00000000 : nt!KiInsertTimer2WithCollectionLockHeld+0xc2
fffff802`244fa8c0 fffff802`222227bf : 00000000`00000002 000003e3`cbb03e0e ffffe001`e41dbb70 fffff802`22547bd8 : nt!KiExpireTimer2+0x283
fffff802`244fa9c0 fffff802`2226ca6e : fffff802`225f5740 00000000`00000001 00000000`00f8f2ed 00000000`00000000 : nt!KiTimer2Expiration+0xdf
fffff802`244faa10 fffff802`2236d03a : fffff802`2257f180 fffff802`2257f180 fffff802`225f5740 ffffe001`e1ede240 : nt!KiRetireDpcList+0x60e
fffff802`244fac60 00000000`00000000 : fffff802`244fb000 fffff802`244f5000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

And then blamed the kernel (ntoskrnl) which is pretty much a catch all.

It could still be a driver, either the one I mentioned above or looking at some further details I see some mention of

fffff802`244fa708 fffff800`5646a1a2 dxgkrnl!DXGADAPTER: PowerRuntimeComponentIdleStateCallback+0x16a

Which may indicate something going on with the GPU driver, although the actual GPU driver itself never shows in the stack.

 

[Shervin Grey]

I don't see anything that actually looks scary.
A single driver that has been known to historically cause some problems at least since Windows 7
AODDriver2.sys 2/11/2014 (AMD Over Drive) it looks a little old and may need updating or even uninstalling.
As I said, I'm no expert, but it looks like it may have just been a one off.
Personally, I'd continue using it and see if a pattern develops or if you can replicate the problem. A single dump file is not much to go on.

If it continues do a couple of the normal diagnostics.
Use the native check disk utility from an elevated command prompt, simply type
chkdsk C: /R
hit enter
answer "Y"
type exit
reboot

Additionally run memtest86
You can get the ISO from here http://www.memtest86.com/download.htm
burn it to a CD or USB ThumbDrive and boot your machine let it run over night if possible unless it starts pitching errors right away, then you have some work to do.

I mention those two because basically it pitched a page fault.

And then blamed the kernel (ntoskrnl) which is pretty much a catch all.

It could still be a driver, either the one I mentioned above or looking at some further details I see some mention of

Which may indicate something going on with the GPU driver, although the actual GPU driver itself never shows in the stack.

Thank you for your help and time. Would you suggest that I reinstall the GPU driver also?

 

[Trouble]

Would you suggest that I reinstall the GPU driver also?

It probably wouldn't hurt anything.
If it's something you wish to try, please uninstall it first. I like to use something like DDU from here http://www.wagnardmobile.com/forums/viewtopic.php?f=5&t=123 to tidy up before clean installing the latest driver.