Windows 10: Irql_not_less_or_equal

Good evening,

First post here. BSOD twice for same error. Not sure if this will help but ever since the upgrade to 10 from 8, DVD-RW drive does not work (it works prior to 10 loading), hard drive seems to be running a bit slow (time for a SSD), and battery in laptop is poor and may be contributing to the problem. I took the battery out and have not have the BSOD since.

Thanks in advance.

:)

 

IRQL_NOT_LESS_OR_EQUAL

IRQL_NOT_LESS_OR_EQUAL blue screen

 

Cant get my pc to quit bluescreening

and the error code is always irql_not_less_or_equal

 

Hi whereisroger,

Welcome to the 10forums *Smile

I've had a look at the support page of Gateway for your laptop and there are a few things we could try for now.
Note that Gateway supports software, updates and such for Windows 7 only according to the support page, correct me if I'm wrong please.Option 1. Starting with driver verifier, the problem is that if driver verifier shows a driver that Gateway provides and reinstalling the driver doesn't help it appears that your system may become incompatible with Windows 10. Note that the installation date doesn't matter at this sight.

Option 2. A clean install, a clean install solves many problems that may occur when upgrading. If however a BSOD occurs again, depending on the situation, we may need to go back to option 1.I'll leave the decision to you for where to start with *Smile

 

Thanks for the quick reply. You are correct, I do not see Gateway providing support beyond Windows 7, but I have been using Windows 10 since the day they made the upgrade available. The upgrade from Windows 8.1 to 10 went well. This was the first BSOD I have run into. Also, I had not used the laptop in over a month so it seem to run very slow then I got the BSOD. I have been running the laptop for 1+ day now with no BSOD. Hopefully I will not run into anymore issues.

I take it from your reply the zip file I provided told you there was a driver error. If so could you expand?

Thanks again.

 

Not exactly, the dumps show memory corruption. Memory corruption knows a few variation of causes where drivers causing memory corruption is the most occuring. However I am not 100% certain if it is a driver that is causing it, but it can be verified using driver verifier.
If I go to the stack of the dumps they show calls to the internal memory management, what exactly happens I'm not sure of but this could again go a few ways.
Code: STACK_TEXT: ffffd001`c3d54318 fffff800`339ccfe9 : 00000000`0000000a fffff6bf`bf62cb50 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffd001`c3d54320 fffff800`339cb7c7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 ffffd001`c3d54460 fffff800`338cc5c2 : 00000003`00000000 ffffe001`10225cc0 00000000`00000000 00000000`0000048f : nt!KiPageFault+0x247 ffffd001`c3d545f0 fffff800`338b165a : ffffe001`10221cc0 ffffe001`0d0163c0 ffffe001`10221cc0 00000000`00000000 : nt!MiAgeWorkingSet+0x302 ffffd001`c3d54940 fffff800`338b10ab : ffffd001`00000000 ffffd001`c3d54bc0 ffffd001`c3d54af0 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0x15a ffffd001`c3d549f0 fffff800`33925b2b : fffff800`00000000 00000000`00000000 00000000`000000ac 00000000`00000002 : nt!MiProcessWorkingSets+0x1fb ffffd001`c3d54ba0 fffff800`339a5e8d : 00000000`00000003 00000000`00000003 00000000`ffffffff 00000000`00000001 : nt!MiWorkingSetManager+0xa7 ffffd001`c3d54c60 fffff800`33963585 : ffffe001`0d142040 00000000`00000080 fffff800`339a5d3c 87840ff6`85f18b56 : nt!KeBalanceSetManager+0x151 ffffd001`c3d54d50 fffff800`339c75f6 : fffff800`33b9d180 ffffe001`0d142040 fffff800`33963544 8b00003c`ffe85a18 : nt!PspSystemThreadStartup+0x41 ffffd001`c3d54da0 00000000`00000000 : ffffd001`c3d55000 ffffd001`c3d4f000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_TEXT: ffffd000`25014408 fffff801`60dbffe9 : 00000000`0000000a fffff580`50809d98 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx ffffd000`25014410 fffff801`60dbe7c7 : 00000000`00000000 00000000`00000010 00000000`00000100 00000000`00000000 : nt!KiBugCheckDispatch+0x69 ffffd000`25014550 fffff801`60cbcd7f : 00000000`000006bd 00007fff`2333f001 ffffe000`19f0c580 00000000`00000000 : nt!KiPageFault+0x247 ffffd000`250146e0 fffff801`60cbc78d : 00000000`00000aa3 00000000`00000aa4 00000000`00000000 000000b4`b0001692 : nt!MiUpdateWsle+0x48f ffffd000`25014790 fffff801`60cbb83c : fffff6bf`ff919080 00000000`00000000 00000000`00000001 00000000`00000000 : nt!MiAllocateWsle+0x29d ffffd000`250147f0 fffff801`60cb0ce8 : ffffe000`19f0c580 ffffe000`163c9b00 00007fff`23210fd0 7fffffff`ffffffff : nt!MiCompleteProtoPteFault+0x29c ffffd000`250148d0 fffff801`60cae2d9 : fffff6e0`00ee1cc0 00007fff`23210fd0 fffff6bf`ff919080 ffffe000`19f0c580 : nt!MiResolveProtoPteFault+0x4d8 ffffd000`25014980 fffff801`60cabbeb : 00000000`00000000 00007fff`23210fd0 00000000`00000000 fffff801`00000000 : nt!MiDispatchFault+0x3a9 ffffd000`25014ae0 fffff801`60dbe6bc : ffffe000`19f57800 00000000`00000000 00000000`00000000 ffffe000`19f21800 : nt!MmAccessFault+0x34b ffffd000`25014c40 00007fff`23210fd0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x13c 00000001`4dd9e128 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`23210fd0[/quote]

 

Okay I will run the program tonight and let you know. I'm going to order a ninjabatt to replace oem which essential can no longer hold a charge. I was fixing an old IBM thinkpad that would crash a few years back and as soon as I took out the battery it would run just fine. I'll let you know the results after I run it.