[SOLVED] IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe+150aa0 - Windows 8.1 x64

[shawkynasr]

Dear sysnative Teams,

Could you please help me solve this problem with my PC?

OS: Win 8.1

This problem almost from 3 months ago, my PC forced to restart when opining Google Chrome.

"IRQL_NOT_LESS_OR_EQUAL" ntoskrnl.exe+150aa0

I guess this RAM, I'll change it, I'll uprgarde to 2 RAM (4G+4G), but first want to make sure this problem realte with RAM not other thing?

Many thanks!


View attachment SHAWKY-2015_02_07_??_204133_91.zip

 

[Jared]

Your .zip folder is empty.
Follow these instructions: https://www.sysnative.com/forums/bs...ons-windows-10-8-1-8-7-and-windows-vista.html

Please don't post the same topic on multiple different forums, it won't help us, or you. You can receive conflicting information that just slows down the process of us helping you.

 

[shawkynasr]

Please find attached file, it's damp files:

Your app "Sysnative BSOD Dump + System File Collection App " take a long time, till now can't export any report.

Just say "Waiting for systeminfo", it's like hanging!


View attachment Minidump.rar

 

[Jared]

2: kd> .bugcheck
Bugcheck code 0000000A
Arguments ffffc000`39f0bc08 00000000`00000002 00000000`00000001 fffff803`432d2937

2: kd> kn
 # Child-SP          RetAddr           Call Site
00 ffffd000`23f538f8 fffff803`433d55e9 nt!KeBugCheckEx [COLOR="#800080"]//BSOD[/COLOR]
01 ffffd000`23f53900 fffff803`433d3e3a nt!KiBugCheckDispatch+0x69 [COLOR="#800080"]//Execute KeBugCheckEx[/COLOR]
02 ffffd000`23f53a40 fffff803`432d2937 nt!KiPageFault+0x23a [COLOR="#800080"]//Page fault[/COLOR]
03 ffffd000`23f53bd0 fffff801`7c616119 nt!KeWaitForSingleObject+0x137 [COLOR="#800080"]//Wait for object[/COLOR]
04 ffffd000`23f53c60 ffffc000`39f0bc08 GUBootStartup+0x1119 [COLOR="#800080"]//Glary Utilities Startup Manager Tool driver[/COLOR]
05 ffffd000`23f53c68 ffffe001`00000000 0xffffc000`39f0bc08 [COLOR="#800080"]//Context not saved[/COLOR]
06 ffffd000`23f53c70 ffffe001`b413d500 0xffffe001`00000000
07 ffffd000`23f53c78 00000000`00000000 0xffffe001`b413d500

2: kd> lmvm GUBootStartup
start             end                 module name
fffff801`7c615000 fffff801`7c61e000   GUBootStartup T (no symbols)           
    Loaded symbol image file: GUBootStartup.sys
    Image path: GUBootStartup.sys
    Image name: GUBootStartup.sys
    Timestamp:        Wed Jul 30 06:39:32 2014 (53D88514) [COLOR="#800080"]//Possible update?[/COLOR]
    CheckSum:         000078E4
    ImageSize:        00009000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Glary utilities startup manager has a bug in the driver, it's unnecessary anyway... I highly recommend you rid the software, but if you must keep it, then you need to update it.

Technical information:

Read More:

The cause is due to the violation of a rule which Windows implements, the rule states that when the IRQL is at DPC/Dispatch level (2), you cannot wait for an object. If the thread waits for an object, a context switch occurs, thus requiring the thread scheduler to execute another thread. The problem is that because DPC routines are used execute deferred work, and thus to schedule threads from previous routines, the DPC routines would never be able to schedule threads for execution, creating lots of problems later on; therefore, Windows creates the rule that you can never wait for objects at this IRQL.
Secondly, only nonpaged system memory can be accessed at IRQL 2 or above, therefore page faults aren't allowed to be incurred.
Pagable memory can be, as suggested, paged out to disk when not in use, as a result a disk I/O operationg performed by a file system driver at IRQL APC_LEVEL level (1) is required. An IRQL cannot be lowered when there is work required at any levels above; because there is work being done at IRQL 2, the disk I/O cannot complete to bring the memory in, yet the wait cannot be satisfied because it's waiting on the disk I/O. As a result, this creates an infinite loop that can never be broken, so a bugcheck is initiated.
I won't go into anymore detail unless requested, but the point being is that this is a driver bug; so the only option is to update the driver or remove the software.

 

[shawkynasr]

This is new analyze, as attached file.

Many thanks!

View attachment 10761

 

[Jared]

Exactly the same problem, caused by the same driver.

 

[shawkynasr]

Many thanks!

But I do'nt have this software now (Glary utilities startup manager) , one year age uninstall it!

How delete this Glary utilities startup manager driver?

 

[Jared]

I don't believe it's associated with any other programs, so you should just be able to rename it directly.

c:\windows\system32\drivers\gubootstartup.sys

It's probably best to create a restore point prior to renaming it.

 

[Patrick]

And as far as renaming it goes, just change the extension from .sys to .bak and then restart.

 

[shawkynasr]

Well done, Many thanks!

 

[shawkynasr]

Exactly the same problem, caused by the same driver.

Dear Jared,
My problem not solve.... already remove "Glary utilities startup manager driver" file ..

But till now, when open Google Chrome, just 5 mic and then blue screen forced PC restart


Please check this new file

View attachment 020815-39781-01.rar

View attachment 10763

 

[Jared]

Same problem...
That driver is still causing the issue.

 

[shawkynasr]

But I already delete it! How I can solve this problem?

 

[Patrick]

Can you elaborate on how you are "deleting" the driver? We're telling you to rename, not delete. If you're deleting, it'll just be remade upon reboot.

 

[shawkynasr]

Just delete it. but i can't found this file after restart!

 

[Patrick]

Again, I don't understand what you mean by "deleting". Are you literally deleting the file, or renaming and restarting.

 

[shawkynasr]

use Shift+delete, that is

 

[Patrick]

Okay, well, I told you to rename the file, not delete it.

And as far as renaming it goes, just change the extension from .sys to .bak and then restart.​

 

[shawkynasr]

use Shift+delete, How I can now resolve this?

 

[Jared]

Patrick, has quoted twice to rename that driver from GUBootStartup.sys to GUBootStartup.bak, then restart.
Do not delete the driver as it will just reload from the program that uses it.