Solved DRIVER_IQRL_NOT_LESS_OR_EQUAL Usbport.sys and ntkrnl.exe

[Arc]

As the present installation is fruunin faulty, it would be better to start afresh. If you opt for an upgrade installation, it will keep "most of" your stuff intact, may be including the problematic elements too.

 

[surge411]

Ok. Maybe I'm a bit stubborn but ill try out the update first . I think that, if it won't fix the drivers (hopefully it will), maybe at least it will fix the dump issue. Also if it won't work after that ill just install fresh and use my time over the weekend. I'll post back when the "reinstall" is done.

 

[Arc]

OK, go for it

 

[surge411]

Ok, great! I reinstalled windows clean (with format) and 5 minutes after entering the desktop, guess what? B S O D. it zoomed past real fast, it said something about fault in non pages area, and the driver was, I think "win32k". I don't have any debugger installed and can't download the SF_DIAGNOSTIGS because I didn't install Ethernet drivers. I hope you can tell me at least what sort of error it was and turn me into the right direction.

EDIT: The error seems to be PAGE_FAULT_IN_NONPAGED_AREA win32k.sys. Found that by doing a google search. I will try removing a ram stick and see if it works better.

 

[Arc]

From what you are saying, it appears to be a STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA.

Possible causes are:

• Antivirus
• Device Driver
• RAM/GPU/CPU
• BIOS (may be overlooked in this case, at least upto now)
• Disc issue.

Provided the motherboard/BIOS is not faulty.

If you can upload the crash dump after installing the network driver, it will be easier to decide about it.

 

[surge411]

Yes. I removed a stick of ram and will wait 10 minutes incase. Then I will start first with the LAN driver and, with sf diag I will retrieve the data and ill upload it. So far it's been 5 minutes and it hasn't blue screened.hopefully it will work!
Btw if I am not able to do anything can I just upload the dumps with a Linux live USB or something?

 

[Arc]

Why not?

 

[surge411]

Alright, hasn't crashed since i removed the ram stick. Also I noticed the rams sticks are different timings one is 6-6-6-24 and one is 9-9-9-24. I removed the 6-6-6-24 one. Anyways dumps are attached, and mean while i will install drivers one by one.

 

[Arc]

The crash dump is not saying any more that you have already told.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffffff83c03a6, 1, fffff96000180cb6, 2}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!PostMessageCheckIL+8e )

Followup: MachineOwner
---------

But, it is certain that RAMs with different timings can cause this issue for sure. As it is detected, you have removed one rightly. Now it is time for observation.

After the drivers, get the windows updates too

 

[surge411]

Absolutely. I am installing drivers one by one with driver verifier to see if any of the drivers (from manufacturer's website) are perhaps faulty. Also when I'm done that I'll put the other ram stick in and see if it will crash. Too bad though, 4gb of ram wasted

 

[Arc]

Dont put the other RAM. As it is with different timings, it is almost sure that it will cause system instability. When you buy new RAM, make it sure that the new stick matches the specs of the existing one.

 

[surge411]

Ok, new bsod, verifier enabled. The driver is Asushwio.sys.it happened when I tried to open the setup from the ASUS Disk that comes with the mobo.

 

[surge411]

Ok, It seems to be the install disc that keeps giving me BSODs when I try to open it. I will never use it again. Also there is no Asushwio.sys in my sys32 folder so yeah. I'm currently installing software as I'm done with drivers! I'll post back soon.

 

[Arc]

It is ASUS driver system driver file, that runs the driver installer disc. May be it will not cause any error if you disable Driver Verifier.

 

[surge411]

Yeah I know but I won't run it for safety. Anyways with driver verifier now I got the same bsod with aswSnx.sys. Ugh! Corrupt drivers everywhere! Just as I thought I had solved everything!

 

[Arc]

Lol

aswSnx is Avast antivirus. It contributes in all types of memory management BSODs, but it is not a BSOD causer everywhere necessarily. The necessary knowledge before deciding about it is that .... does avast cause BSOD there without DV enabled or not.

I think you should use the computer normally for a few hour and see how the new installation (without the mismatch RAM) works.

 

[surge411]

Oh crapulous! I uninstalled avast and installed mse, I actually installed avast before because I wanted to try it out (I had mse before) but it hasn't given me the best experience… perhaps after I can be sure evrything is fixed ill try to install it. Anyways does what you said mean both my ram sticks could be faulty? Ugh that sucks! I am going to run memtest over night with both sticks installed.

EDIT: I didn't understand what DV meant at first lol. Anyways yeah ill play games without it tomorrow and see…

 

[Arc]

DV = Driver Verifier

Dont put both the RAM sticks together, as you know that they are not matching. It will make the system unstable by its own virtue, but memtest may not find it as an error, as it tests for the memory errors, not the compatibility thing.

If you want to run memtest, do it individually on each stick.

 

[surge411]

I actually forgot to install the second stick before starting so I'm running it on one stick right now . Anyways it's done 4 passes so I think it's kinda enough, anyways I thought of running a not so demanding game or benchmarker, or something that would test the four important parts of a computer (RAM, GPU, CPU, HDD) to see if I can reproduce a bsod (no DV) and hopefully analyze the dump. Do you perhaps know something that I can run overnight?

 

[Arc]

Download a big file?