driver_irql_not_less_or_equal

  • Thread starter Thread starter Agnostic
  • Start date Start date
A

Agnostic

Can anyone solve this riddle for me?

I bought an HP desktop a few weeks ago. It is a s3700y (pavilion
slimline). The only thing installed on it was a wireless network
adapter driver Belkin G F5D7050 for wireless internet. The system
keeps crashing with the blue screen of death labelling the error

driver_irql_not_less_or_equal

and it says something about disabling bios memory options such as
caching and shadowing if this keeps happening. I have tried doing a
system recovery multiple times but after reinstalling the Belkin
driver, the system crashes again with the same error. I have tried
downloading a Belkin driver for the same adapter model from the Belkin
website onto a CD, and then installing it from the CD onto the
desktop, but the system kept crashing. I can only conclude that the
driver for this Belkin adapter is what is causing the system to crash.
The HP tech support guy really ran my patience out without coming to a
solution.



Rather than having to buy a new wireless network adapter and go
through trial and error of whether it is compatible with the system,
is there a way of overcoming this.

I have no idea of how to disable caching or shadowing, so I would
appreciate guidance through it.

Thank you.
 
Agnostic said:
Can anyone solve this riddle for me?

I bought an HP desktop a few weeks ago. It is a s3700y (pavilion
slimline). The only thing installed on it was a wireless network
adapter driver Belkin G F5D7050 for wireless internet. The system
keeps crashing with the blue screen of death labelling the error

driver_irql_not_less_or_equal

and it says something about disabling bios memory options such as
caching and shadowing if this keeps happening. I have tried doing a
system recovery multiple times but after reinstalling the Belkin
driver, the system crashes again with the same error. I have tried
downloading a Belkin driver for the same adapter model from the Belkin
website onto a CD, and then installing it from the CD onto the
desktop, but the system kept crashing. I can only conclude that the
driver for this Belkin adapter is what is causing the system to crash.
The HP tech support guy really ran my patience out without coming to a
solution.



Rather than having to buy a new wireless network adapter and go
through trial and error of whether it is compatible with the system,
is there a way of overcoming this.

I have no idea of how to disable caching or shadowing, so I would
appreciate guidance through it.

Thank you.
Click to expand...

Have you read the reviews on Newegg for the product ?

http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16833314011

One poster mentions there are multiple versions of the same product.
It is possible they use different chipsets. Is there something on
the label that identifies the version ?

If it is an Ralinktech chipset, you may be able to get drivers from them.
Identifying the design, is all part of the fun of using Wireless.

http://www.ralinktech.com/ralink/Home/Support/Windows.html

Paul
 
Agnostic said:
Can anyone solve this riddle for me?

I bought an HP desktop a few weeks ago. It is a s3700y (pavilion
slimline). The only thing installed on it was a wireless network
adapter driver Belkin G F5D7050 for wireless internet. The system
keeps crashing with the blue screen of death labelling the error

driver_irql_not_less_or_equal

and it says something about disabling bios memory options such as
caching and shadowing if this keeps happening. I have tried doing a
system recovery multiple times but after reinstalling the Belkin
driver, the system crashes again with the same error. I have tried
downloading a Belkin driver for the same adapter model from the Belkin
website onto a CD, and then installing it from the CD onto the
desktop, but the system kept crashing. I can only conclude that the
driver for this Belkin adapter is what is causing the system to crash.
The HP tech support guy really ran my patience out without coming to a
solution.



Rather than having to buy a new wireless network adapter and go
through trial and error of whether it is compatible with the system,
is there a way of overcoming this.

I have no idea of how to disable caching or shadowing, so I would
appreciate guidance through it.

Thank you.
Click to expand...

Every time I've seen this message, it was bad memory. Before anything else,
check your memory sticks with Memtest. Dollars to donuts you've got a bad
one. Hope this helps you. JG
 
JFG said:
Every time I've seen this message, it was bad memory. Before anything else,
check your memory sticks with Memtest. Dollars to donuts you've got a bad
one. Hope this helps you. JG
Click to expand...

I'll add a little anecdotal evidence to this statement as well. 2 of
the 3 times I've fought this BSoD, it's been bad memory.
 
Thanks guys, I will do a memtest and see the results before getting
back to you.
Click to expand...

In at least one (maybe both) of the cases I refer to, memtest did not
reveal any errors.
 
Every time I've seen this message, it was bad memory.  Before anything else,
check your memory sticks with Memtest.  Dollars to donuts you've got a bad
one.  Hope this helps you.  JG- Hide quoted text -

- Show quoted text -
Click to expand...

Ok, I ran the memtest and there were no errors. Here are the details
of the blue screen

Stop: 0x0000001 (0xE041C8BF, 0x00000002, 0x00000000, 0x894BC341)

ndis.sys Address 894BC341 base at 894B7000, Datestamp 479190e7

Does that clarify anything?

Thanks
 
Agnostic said:
Ok, I ran the memtest and there were no errors. Here are the details
of the blue screen

Stop: 0x0000001 (0xE041C8BF, 0x00000002, 0x00000000, 0x894BC341)

ndis.sys Address 894BC341 base at 894B7000, Datestamp 479190e7

Does that clarify anything?
Click to expand...

I still think it could be a bad memory module. Is it likely to BSoD at
any time? Or, is it just at startup? How often? Is it random, or can
you specify steps that will make it crash?

Strip your system down to a minimum and see if it stops crashing. Add
parts back in until the crashes come back.
 
I still think it could be a bad memory module.  Is it likely to BSoD at
any time?  Or, is it just at startup?  How often?  Is it random, orcan
you specify steps that will make it crash?

Strip your system down to a minimum and see if it stops crashing.  Add
parts back in until the crashes come back.- Hide quoted text -

- Show quoted text -
Click to expand...

Is it really simple to strip it down? I really don't want to be
messing with it if it's not especially while it's new and I still have
the warranty. I don't have experience in disassembling electronics. It
BsoDs anytime while the wireless adapter is plugged in. Sometimes it
takes minutes, sometime longer. There are no steps that lead to it
BSoDing, just surfing the net has been causing it. When the wireless
adapter is not plugged in, I noticed that this doesn't happen, but
again I haven't done much work without the internet.


There was a post here that seemed to have been removed. It was the
earliest post of someone asking me about the details of the error. It
didn't seem illegitimate so I'm not sure who removed it.

I found a webpage about that same error involving ndis.sys and it says
that it could very possibly be the NIC. But I can never find the same
error with the same 0x0 numbers posted.
 
Agnostic said:
Is it really simple to strip it down? I really don't want to be
messing with it if it's not especially while it's new and I still have
the warranty. I don't have experience in disassembling electronics. It
BsoDs anytime while the wireless adapter is plugged in. Sometimes it
takes minutes, sometime longer. There are no steps that lead to it
BSoDing, just surfing the net has been causing it. When the wireless
adapter is not plugged in, I noticed that this doesn't happen, but
again I haven't done much work without the internet.
Click to expand...

That would be a good datapoint to have. If you have some extended work
without the internet, see if the machine with BSoD without the wireless
adapter.
 
That would be a good datapoint to have.  If you have some extended work
without the internet, see if the machine with BSoD without the wireless
adapter.
Click to expand...

I'll try to find something to do without the internet. Would just
running virus scan be good enough?
 
Agnostic said:
I'll try to find something to do without the internet. Would just
running virus scan be good enough?
Click to expand...

Have you identified the chip inside the Wifi adapter yet ?
And verified the correct driver is being used ?

NDIS is related to networking, so my guess is, the problem BSOD
is directly related to your networking solution.

There are five versions of F5D7050 shown here. Take a look.

http://www.belkin.com/support/ab/d/

Since the device is USB, you can get ID info for the MAC chip
using UVCView. Click one of the dated links here, to download
a copy. This one runs in a 32 bit Windows OS.

http://web.archive.org/*/http://dow...f-a31d-436b-9281-92cdfeae4b45/UVCView.x86.exe

Vendor and device numbers are documented here.
For example "148f Ralink Technology, Corp." is the
start of some Ralinktech parts. It is also possible for
USB devices to have custom IDs, which defeats the value
of plug and play. "IDvendor" and "IDproduct" in
UVCView details for the USB device, are what you'd compare
to the numbers in this document.

http://www.linux-usb.org/usb.ids

Once you know what device it is, if you cannot get the
Belkin provided driver to work, you can look for
other sources of drivers.

Paul
 
I am not sure why I keep seeing messages by me and other people
deleted from here, but anyhow.

I replaced the wireless adapter, recovered the system and installed
from scratch. The system keeps crashing, although less often now. It
always crashes when I leave the PC idle for a while and come back to
it and move the mouse. The error varies between driver irql not less
or equal, USBPort.sys, and WUSB54GSCV2.SYS which again indicates a
wireless adapter issue. I don't know if I should go on replacing
wireless adapters. It seems to be a windows problem and a
compatibility issue that should be addressed.

If anyone has a suggestion different from the ones addressed, please
let me know. Thanks.
 
Agnostic said:
I am not sure why I keep seeing messages by me and other people
deleted from here, but anyhow.

I replaced the wireless adapter, recovered the system and installed
from scratch. The system keeps crashing, although less often now. It
always crashes when I leave the PC idle for a while and come back to
it and move the mouse. The error varies between driver irql not less
or equal, USBPort.sys, and WUSB54GSCV2.SYS which again indicates a
wireless adapter issue. I don't know if I should go on replacing
wireless adapters. It seems to be a windows problem and a
compatibility issue that should be addressed.

If anyone has a suggestion different from the ones addressed, please
let me know. Thanks.
Click to expand...

http://aumha.org/a/stop.htm

"0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article.)

The system attempted to access pageable memory using a kernel process
IRQL that was too high. The most typical cause is a bad device driver
(one that uses improper addresses). It can also be caused by
faulty or mismatched RAM, or a damaged pagefile."

You could give memtest86+ a try, and test the memory. Let it run for
two full passes, before pressing <esc> to reboot the computer back
to your regular OS. No errors are acceptable. If the same memory
location shows an error for the different tests, you could have
a "stuck" memory bit.

http://www.memtest.org/

As for the pagefile, I think I've deleted that while booted with
a Linux LiveCD (and the system will create a new one). I can do that,
if I want to move the files around. Otherwise, if you try to
fool around with "pagefile.sys" or "hiberfil.sys" which stores
RAM contents during hibernation, they may be marked busy. So
if the memory thing doesn't work out, for fun, you can try
making changes to pagefile.sys. You should be able to see
its relative position on disk, using the defrag report (as
the system defragmenter will class those files as something
which cannot be moved). I think this is a long shot, and not worth
wasting time on.

Other than that, it could be some other weird piece of software,
which is upsetting things. Is there anything about your setup
you consider unique or out of the ordinary ?

HTH,
Paul
 
http://aumha.org/a/stop.htm

    "0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
     (Click to consult the online Win XP Resource Kit article.)

     The system attempted to access pageable memory using a kernel process
     IRQL that was too high. The most typical cause is a bad devicedriver
     (one that uses improper addresses). It can also be caused by
     faulty or mismatched RAM, or a damaged pagefile."

You could give memtest86+ a try, and test the memory. Let it run for
two full passes, before pressing <esc> to reboot the computer back
to your regular OS. No errors are acceptable. If the same memory
location shows an error for the different tests, you could have
a "stuck" memory bit.

   http://www.memtest.org/

As for the pagefile, I think I've deleted that while booted with
a Linux LiveCD (and the system will create a new one). I can do that,
if I want to move the files around. Otherwise, if you try to
fool around with "pagefile.sys" or "hiberfil.sys" which stores
RAM contents during hibernation, they may be marked busy. So
if the memory thing doesn't work out, for fun, you can try
making changes to pagefile.sys. You should be able to see
its relative position on disk, using the defrag report (as
the system defragmenter will class those files as something
which cannot be moved). I think this is a long shot, and not worth
wasting time on.

Other than that, it could be some other weird piece of software,
which is upsetting things. Is there anything about your setup
you consider unique or out of the ordinary ?

HTH,
      Paul- Hide quoted text -

- Show quoted text -
Click to expand...

Thanks again, Paul. I was with HP support and he said it's an
incompatibility issue with the drivers of Belkin and Linksys.
Ofcourse, he put the blame on Belkin and Linksys, and said that since
my memory tests passed, both through hardware diagnostics and memtest,
that there is nothing wrong with the PC itself. He suggested buying an
HP wireless adapter, so I will try that as a last resort in deciding
whether my computer is the culprit. It certainly is an error that has
been going around with windows vista in come computers. As for the
pagefile,if it was damaged would it remain damaged even after I run
system recoveries?, because I have many times and it hasn't solved the
problem.

There's nothing out of the ordinary. When the wireless adapter is not
plugged the system does not crash. Like I said, the crashes are
significantly less often with Linksys than with the Belkin, where I
can actually get some work done. So maybe there is a compatibility
issue that needs to be addressed for s3700y HPs. Thanks.
 
Back
Top