DRIVER_NOT_LESS_OR_EQUAL BSOD Error

[MySelfLuls422]

After installing AVG and upgrading to the paid version. I restarted my computer, unexpected recieving BSOD error "DRIVER NOT LESS OR EQUAL" with the other error message "ndis.sys"

I tried to contact AVG but they are very slow at reacting to my so i see this as a hope for a response that works.

SYSTEM SPECS:

Operating System
Microsoft Windows 7 Home Premium 64-bit SP1
CPU
Intel Core i7 3930K @ 3.20GHz 46 °C
Sandy Bridge-E 32nm Technology
RAM
16,0 GB DDR3 @ 800MHz (11-11-11-28)
Motherboard
ASUSTeK COMPUTER INC. RAMPAGE IV EXTREME (LGA2011) 31 °C
Graphics
SyncMaster (1920x1080@59Hz)
P23T-6 LED (1920x1080@60Hz)
NVIDIA GeForce GTX 670
NVIDIA GeForce GTX 670
Hard Drives
932GB Seagate ST1000DM003-9YN162 ATA Device (SATA) 31 °C
112GB OCZ-AGILITY3 ATA Device (SSD) 30 °C
Optical Drives
Optiarc DVD RW AD-5280S ATA Device
DTSOFT Virtual CdRom Device
Audio
Realtek High Definition Audio

-------------------

This always occurs when I install AVG and restart.
I have no other choice but to use system restore before AVG was installed to solve the problem and make my computer available.


Best Regards and hopes of a solution.
MySelfLuls

 

[Faruk Aksamija]

Ok this bsod if coused becouse of outdated system or outdated drivers or conflict between drivers. I would suggest you to uninstall AVG and see weather you get BSOD if you still get BSOD for resolving it best way is to reinstall the whole system and do a clean driver instalation together with your AVG. This problem is not only happened to you, many people get same BSOD coused by AVG. Good Luck

 

[himnextdoor]

It is possible that a piece of malware has disguised itself with that file-name.

Do a search on your computer and look for ndis.sys.

There should be one in the Windows\System32\Drivers folder and others in the WinSX folder.

I would locate the one in the WinSX folder that has the same version number as the one in the Drivers folder and the copy and paste the WinSX version into the Drivers folder.

Does that help?

 

[MySelfLuls422]

Ok this bsod if coused becouse of outdated system or outdated drivers or conflict between drivers. I would suggest you to uninstall AVG and see weather you get BSOD if you still get BSOD for resolving it best way is to reinstall the whole system and do a clean driver instalation together with your AVG. This problem is not only happened to you, many people get same BSOD coused by AVG. Good Luck

As i posted in the message i did a system restore before AVG was installed so my computer works I am just without AVG that I paid for.

It is possible that a piece of malware has disguised itself with that file-name.

Do a search on your computer and look for ndis.sys.

There should be one in the Windows\System32\Drivers folder and others in the WinSX folder.

I would locate the one in the WinSX folder that has the same version number as the one in the Drivers folder and the copy and paste the WinSX version into the Drivers folder.

Does that help?

I am sorry, but when I search for ndis.sys nothing comes up sadly

 

[himnextdoor]

Open your C drive and then type 'ndis.sys' (without the quotes) into the search box at the top right of the explorer screen and press 'Enter'. Wait until the green line gets to the end of the address box.



Can you find them now?

 

[JDFan]

ndis.sys ( Network Driver Interface Specification ) is a network adapter driver file so try updating the network adapter driver that you have on your system (should be available from your MOBO manufacturers website if using the NIC interface built into the MOBO or the NIC card manufacturers site if using an add in card.)

 

[MySelfLuls422]

Open your C drive and then type 'ndis.sys' (without the quotes) into the search box at the top right of the explorer screen and press 'Enter'. Wait until the green line gets to the end of the address box.



Can you find them now?

I'll try tomorrow as I am really tired. It's 3 AM here. Been trying to fix this error for a while.
Thanks for trying to assist me.

 

[himnextdoor]

Okay dude. Keep us posted.

 

[MySelfLuls422]

I am really sorry, but I've found the files now. I am just unsure what you actually want me to do with them
I ain't quite experience on this part of a computer.

ndis.sys ( Network Driver Interface Specification ) is a network adapter driver file so try updating the network adapter driver that you have on your system (should be available from your MOBO manufacturers website if using the NIC interface built into the MOBO or the NIC card manufacturers site if using an add in card.)

So, what you do want me to do is to update my network driver on the computer?

I'll try to figure that out soon.

 

[JDFan]

That would be the easiest method since reinstalling the network driver package will replace that file with the correct version for your network adapter card which seems to be where the conflict is (seems that the AV program is trying to use the internet connection (probably to update itself or check their database to see if the files are safe to run) and for some reason the version of the NDIS file that you currently have does not support a portion of what the AV program is trying to do thus they are conflicting with each other causing the problem (and since the AV program is the latest version it is most likely an older version of that NDIS file that is the problem. SO downloading and installing the latest version from your MOBO manufacturer should correct the problem.

So go to the mobo manufacturers website and look up the MOBO model that you have and under the downloads section look for the network or LAN driver - download it and install and hopefully that will correct the problem.

 

[himnextdoor]

Browse to your Windows\System32\Drivers folder and locate the ndis.sys file that is there.

Hover your mouse over the file and make a note of the version number. (Or right click and choose Properties to find the version number.)

Now go to your search results window and hover your mouse over the ndis.sys files that are in the WinSX folder.

Locate the file that has the same version number as the one you noted.

Copy that file and paste it onto your 'C' drive.

Now, restart the computer and press F8 to bring up start options.

Select 'Repair my computer' from the top of the list.

When the files are loaded, log into your account.

On the screen that follows, choose 'Command Prompt'.

Now type the following line:

Copy d:\ndis.sys d:\Windows\System32\Drivers

(Note, there is a space between '.sys' and 'd'.)

Press 'Enter'.

Press 'y' and 'Enter' to overwrite the file.

Close the dos window and restart.

Does that help?

 

[MySelfLuls422]

Browse to your Windows\System32\Drivers folder and locate the ndis.sys file that is there.

Hover your mouse over the file and make a note of the version number. (Or right click and choose Properties to find the version number.)

Now go to your search results window and hover your mouse over the ndis.sys files that are in the WinSX folder.

Locate the file that has the same version number as the one you noted.

Copy that file and paste it onto your 'C' drive.

Now, restart the computer and press F8 to bring up start options.

Select 'Repair my computer' from the top of the list.

When the files are loaded, log into your account.

On the screen that follows, choose 'Command Prompt'.

Now type the following line:

Copy d:\ndis.sys d:\Windows\System32\Drivers

(Note, there is a space between '.sys' and 'd'.)

Press 'Enter'.

Press 'y' and 'Enter' to overwrite the file.

Close the dos window and restart.

Does that help?

I have to admit i don't quite like to fiddle around in the BIOS and with such important files.
Would this be the only solution?

 

[himnextdoor]

I have to admit i don't quite like to fiddle around in the BIOS and with such important files.
Would this be the only solution?

You won't be fiddling around in BIOS.

All that we will achieve by doing this is to replace the 'faulty' file with a backed up version of in that is kept in the WinSX folder precisely in case of situations like this. SFC, the file scanner, basically does the same thing.

If this works then it doesn't matter whether this is the only solution or not.

If it doesn't then you could repeat the process but with a newer version of ndis.sys if you have one.

However, I can assure you that I have never given advice that has caused a machine to be bricked so have a little faith.

If you need walking through the process the just let me know but I think my instructions are quite simple to follow.

If it would make you feel better, you can always copy and paste the original 'faulty' file onto your desktop so that you can put it back later if this doesn't work.

Besides, we are not 'fiddling', we are fixing and we may have all the tools we need at our disposal.

For my part though, I'd rather do without AVG.

 

[MySelfLuls422]

I am sorry if I offended you. I know you gave me a precise and what should be easy to solve solution. he fact is just that i don't like to touch such files in the cause of not knowing what could happend in return of it.

I have my full trust to you, may i ask why this happens when I install AVG and upgrade to the paid version?

I would like you to walk me through the process if you have time for that please.

Best Regards
MySelfLuls

 

[MySelfLuls422]

I havn't recieved a response and updating my internet driver did not solve the error as it re-occured.

Could anyone be to assistance for me?