Windows 7: DRIVER_IQRL_NOT_LESS_OR_EQUAL Usbport.sys and ntkrnl.exe

Arc · 22 Nov 2013

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 · 22 Nov 2013

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 · 22 Nov 2013

OK, go for it

surge411 · 23 Nov 2013

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 · 23 Nov 2013

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 · 23 Nov 2013

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 · 23 Nov 2013

Why not?

surge411 · 23 Nov 2013

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 · 23 Nov 2013

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

Code:

*******************************************************************************
*                                                                             *
*                        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 · 23 Nov 2013

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