Author Topic: IQRL_NOT_EQUAL_OR_LESS errors and FNETDEVI.SYS ? (Read 11822 times)

DrSatanDracula · « **on:** May 20, 2009, 09:23:45 PM »

I received a BSOD stating IQRL_NOT_EQUAL_OR_LESS and I found this in my event log:

\??\C:\Windows\SysWow64\drivers\FNETDEVI.SYS has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

Considering these errors are supposedly related to driver issues, could this be what is causing my problem? If so, where can I find this? I am doing a search and not finding much info on FNETDEVI.SYS

I did a windows memory test and it said my memory was fine. Should I do any other memory tests just to rule out that the memory itself isn't the problem?

EDIT: Note I am using Windows Vista 64-Bit.

iamtonsoffun247 · « **Reply #1 on:** May 20, 2009, 09:26:07 PM »

I am searching it but to no avail. Possibly a virus.... Hmmmmmmm part of something called Fnet Co. Sound familiar at all?

Broni · « **Reply #2 on:** May 20, 2009, 09:32:12 PM »

Is the computer bootable?
If so...

Navigate to: C:\Windows\Minidump folder.
If you see any .dmp files, zip all of them, and attach zipped file to your next reply.

DrSatanDracula · « **Reply #3 on:** May 20, 2009, 09:37:42 PM »

Quote from: iamtonsoffun247 on May 20, 2009, 09:26:07 PM

I am searching it but to no avail. Possibly a virus.... Hmmmmmmm part of something called Fnet Co. Sound familiar at all?

I think it is a legitimate driver. Possibly for my USB drive (which is not powered on right now) which contains my old computer data.

DrSatanDracula · « **Reply #4 on:** May 20, 2009, 09:38:56 PM »

Quote from: Broni on May 20, 2009, 09:32:12 PM

Is the computer bootable?
If so...

Navigate to: C:\Windows\Minidump folder.
If you see any .dmp files, zip all of them, and attach zipped file to your next reply.

Here you go:

[attachment deleted by admin]

Broni · « **Reply #5 on:** May 20, 2009, 09:48:19 PM »

IRQL_NOT_LESS_OR_EQUAL error points to ohci1394.sys problem.
ohci1394.sys is 1394 OpenHCI Port Driver (firewire).
Check Device Manager for errors.

DrSatanDracula · « **Reply #6 on:** May 20, 2009, 09:54:03 PM »

Quote from: Broni on May 20, 2009, 09:48:19 PM

IRQL_NOT_LESS_OR_EQUAL error points to ohci1394.sys problem.
ohci1394.sys is 1394 OpenHCI Port Driver (firewire).
Check Device Manager for errors.

Once I am in Device Manager, where should I go to check for errors on this?

Broni · « **Reply #7 on:** May 20, 2009, 09:59:49 PM »

If there ARE any errors, you should see some yellow "?", or "!" marks.
If you don't see any, let me know.

DrSatanDracula · « **Reply #8 on:** May 20, 2009, 10:02:52 PM »

Quote from: Broni on May 20, 2009, 09:59:49 PM

If there ARE any errors, you should see some yellow "?", or "!" marks.
If you don't see any, let me know.

I just went to Device Manager, clicked on everything, and saw no ? or ! marks.

Also, thanks so much.

You've been extremely helpful so far.

Broni · « **Reply #9 on:** May 20, 2009, 10:04:18 PM »

Please download SystemLook from one of the links below and save it to your Desktop.
Download Mirror #1
Download Mirror #2

Double-click SystemLook.exe to run it.
Vista users:: Right click on SystemLook.exe, click Run As Administrator
Copy the content of the following box into the main textfield:
Quote
:file
C:\Windows\System32\drivers\ohci1394.sys
Click the Look button to start the scan.
When finished, a notepad window will open with the results of the scan. Please post this log in your next reply.

Note: The log can also be found on your Desktop entitled SystemLook.txt

DrSatanDracula · « **Reply #10 on:** May 20, 2009, 10:09:55 PM »

Quote from: Broni on May 20, 2009, 10:04:18 PM

Please download SystemLook from one of the links below and save it to your Desktop.
Download Mirror #1
Download Mirror #2
Double-click SystemLook.exe to run it.
Vista users:: Right click on SystemLook.exe, click Run As Administrator
Copy the content of the following box into the main textfield:
Click the Look button to start the scan.
When finished, a notepad window will open with the results of the scan. Please post this log in your next reply.
Note: The log can also be found on your Desktop entitled SystemLook.txt

Right-o, my good man. I shall do that right this second.

DrSatanDracula · « **Reply #11 on:** May 20, 2009, 10:12:06 PM »

SystemLook v1.0 by jpshortstuff (18.05.09)
Log created at 00:10 on 21/05/2009 by James Rowe (Administrator - Elevation successful)

No Context: C:\Windows\System32\drivers\ohci1394.sys

-=End Of File=-

Should I try looking merely for ohchi1394.sys ? As I am running 64 bit Windows Vista.

Broni · « **Reply #12 on:** May 20, 2009, 10:17:13 PM »

Look manually into C:\Windows\System32\drivers folder, and see, if you have ohci1394.sys file there.
If it's not there, search entire computer. You should have backup copy somewhere.

DrSatanDracula · « **Reply #13 on:** May 20, 2009, 10:23:23 PM »

Quote from: Broni on May 20, 2009, 10:17:13 PM

Look manually into C:\Windows\System32\drivers folder, and see, if you have ohci1394.sys file there.
If it's not there, search entire computer. You should have backup copy somewhere.

No results.

I also made sure to put the search parameters on everywhere so as to make sure it wasn't just showing me indexed areas. No results.

What the fudge? I can't stand Windows Vista search. It apparently doesn't understand "look everywhere" because right there in Windows32 is the ohci1394.sys file.

DrSatanDracula · « **Reply #14 on:** May 20, 2009, 10:29:33 PM »

C:\Windows\winsxs\amd64_1394.inf_31bf3856ad364e35_6.0.6001.18000_none_574df222be456348

Another ochi is found there as well.

However, I don't have a AMD processor. I have an Intel. My last computer has a AMD. Could this by any chance be checking my drive-image file that I made of my last computer which did have a AMD processor? I made a drive image I haven't deleted from Acronis.

I also just found the original file in my OP that said was having some trouble at:

C:\Windows\SysWOW64\drivers

Broni · « **Reply #15 on:** May 20, 2009, 10:36:50 PM »

You know, Windows search is horrible.
Get Super Finder: http://download.cnet.com/Super-Finder/3000-2248_4-10454472.html
It'll install itself as an option under right click menu in Windows Explorer.
When you open it, make sure, under "Advanced" tab, all file types are selected.
Using this tool, search for ohci1394.sys again.

DrSatanDracula · « **Reply #16 on:** May 20, 2009, 10:39:02 PM »

Quote from: Broni on May 20, 2009, 10:36:50 PM

You know, Windows search is horrible.
Get Super Finder: http://download.cnet.com/Super-Finder/3000-2248_4-10454472.html
It'll install itself as an option under right click menu in Windows Explorer.
When you open it, make sure, under "Advanced" tab, all file types are selected.
Using this tool, search for ohci1394.sys again.

Thank you again. Let me install this, as yeah, Windows Search -is- horrible. That was pathetic.

Broni · « **Reply #17 on:** May 20, 2009, 10:39:58 PM »

You found ohci1394.sys file in C:\Windows\SysWOW64\drivers folder?

DrSatanDracula · « **Reply #18 on:** May 20, 2009, 10:42:24 PM »

In Super Find:

ohci1394.sys

C:\Windows\winsxs\amd64_1394.inf_31bf3856ad364e35_6.0.6001.18000_none_574df222be456348

Broni · « **Reply #19 on:** May 20, 2009, 10:44:30 PM »

Is that the only location?
What did you say about C:\Windows\SysWOW64\drivers folder?

DrSatanDracula · « **Reply #20 on:** May 20, 2009, 10:44:57 PM »

Quote from: Broni on May 20, 2009, 10:39:58 PM

You found ohci1394.sys file in C:\Windows\SysWOW64\drivers folder?

No. Ohci1394 is in:

C:\Windows\System32\drivers

And:

C:\Windows\winsxs\amd64_1394.inf_31bf3856ad364e35_6.0.6001.18000_none_574df222be456348

The Fnetdevi.sys was in the C:\Windows\SysWOW64\drivers

Broni · « **Reply #21 on:** May 20, 2009, 10:54:26 PM »

Go Start>Run ("Start Search" in Vista), type in:
sfc /scannow
Click OK (hold CTRL, and SHIFT, hit Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) will find any errors, it may ask you for the CD/DVD.
If sfc won't find any errors in Windows XP, it'll simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

DrSatanDracula · « **Reply #22 on:** May 20, 2009, 11:01:09 PM »

Quote from: Broni on May 20, 2009, 10:54:26 PM

Go Start>Run ("Start Search" in Vista), type in:
sfc /scannow
Click OK (hold CTRL, and SHIFT, hit Enter in Vista).
Have Windows CD/DVD handy.
If System File Checker (sfc) will find any errors, it may ask you for the CD/DVD.
If sfc won't find any errors in Windows XP, it'll simply quit, without any message.
In Vista you will receive the following message: "Windows resource protection did not find any integrity violations".

I will have to wait till tomorrow for the second step. I don't have the recovery CDs on hand. HP is a friggin' idiotic company that sent me the wrong recovery CDs, so I don't have Vista on CD right now.

Should I try the scan just to see if I get any errors anyway?

Broni · « **Reply #23 on:** May 20, 2009, 11:04:16 PM »

sfc will rarely ask for DVD in Vista, because usually backup files are found right on hard drive.
You can simply start running it, just to see, if it'll complain about any file(s).

DrSatanDracula · « **Reply #24 on:** May 20, 2009, 11:25:09 PM »

Just did it.

No problems found. It also just closed after verifiying. No report or anything afterwards.

Broni · « **Reply #25 on:** May 20, 2009, 11:28:46 PM »

OK. Was the BSOD one-time occurrence, or it happens all the time?
You provided only 1 dmp file. Were there more of them?

DrSatanDracula · « **Reply #26 on:** May 20, 2009, 11:31:58 PM »

Quote from: Broni on May 20, 2009, 11:28:46 PM

OK. Was the BSOD one-time occurrence, or it happens all the time?
You provided only 1 dmp file. Were there more of them?

There was only one dump file.

I've had another BSOD (I believe with the same error message) last week.

My computer has been freezing up routinely. Here is a thread regarding that: http://www.computerhope.com/forum/index.php/topic,83436.0.html

Broni · « **Reply #27 on:** May 20, 2009, 11:35:08 PM »

Well, I'm sorry, but we've been wasting our time here, since it's 3 weeks old computer.
Take it back to the store before 30 days pass by.

DrSatanDracula · « **Reply #28 on:** May 20, 2009, 11:37:19 PM »

Quote from: Broni on May 20, 2009, 11:35:08 PM

Well, I'm sorry, but we've been wasting our time here, since it's 3 weeks old computer.
Take it back to the store before 30 days pass by.

You really think that ist he most effective solution?

Do you think that instead of actually sending it back I could try reinstalling Windows? Or what?

Because I seriously do not want to be deprived of access to a computer for two weeks. I have business to tend to that I can't put off during the period.

Broni · « **Reply #29 on:** May 20, 2009, 11:40:01 PM »

Trying to fix 3 weeks old computer would be highly un-wise.
If it's acting up now, what will happen 2, 6, 15 months from now, especially when the warranty is out.
I'd insist not on fixing it, but on replacing it.

DrSatanDracula · « **Reply #30 on:** May 20, 2009, 11:42:27 PM »

Quote from: Broni on May 20, 2009, 11:40:01 PM

Trying to fix 3 weeks old computer would be highly un-wise.
If it's acting up now, what will happen 2, 6, 15 months from now, especially when the warranty is out.
I'd insist not on fixing it, but on replacing it.

This is true. But I do have a there-year service plan on this and if the problem is reasonably fixable, I would prefer to fix it then send it in. Again, because business wise, I don't think I can tolerate a two week period with no access to my computer and no alternatives.

Again: Do you think a reinstall of Windows would be appropriate here? Or what?

Broni · « **Reply #31 on:** May 20, 2009, 11:44:28 PM »

You can give it a shot, but you may be having some hardware problems, and those are hard to detect through some computer forum.

DrSatanDracula · « **Reply #32 on:** May 20, 2009, 11:49:43 PM »

Quote from: Broni on May 20, 2009, 11:44:28 PM

You can give it a shot, but you may be having some hardware problems, and those are hard to detect through some computer forum.

Shouldn't the windows hardware scans catch those?

DrSatanDracula · « **Reply #33 on:** May 21, 2009, 12:37:56 AM »

Here's my hardware report zipped up:

[attachment deleted by admin]

Broni · « **Reply #34 on:** May 21, 2009, 05:47:11 PM »

I don't know what else to tell you except for what I already told you.

Computer Hope Forum

News:

Author Topic: IQRL_NOT_EQUAL_OR_LESS errors and FNETDEVI.SYS ? (Read 11822 times)

DrSatanDracula

iamtonsoffun247

Broni

DrSatanDracula

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

DrSatanDracula

Broni

DrSatanDracula

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

Broni

DrSatanDracula

DrSatanDracula

Broni