Vista - the problem with ndis.sys Blue Screen of Death problem solved?

there are many ndis.sys Blue Screen of Death postings on the net, but
none of them seem to suggest that it is solved. Can it be solved? Or
can someone point to a solution? Thanks very much!


the blue screen shows
DRIVER_IRQL_NOT_LESS_OR_EQUAL

and I am using an onboard LAN card by Intel, with IRQ -3 (minus 3),
the model is 82562-V2 10/100

It is on Vista SP1, with every possible upgrade installed.

In article <8f1cba24-124b-4347-b45a-bc741f212ebf@xxxxxx>,
liketofindoutwhy <liketofindoutwhy@xxxxxx> wrote:-3??? Hmmmmm

irq not less than is usually a driver issue. I'd start by making sure
any of my third party drivers (video drivers are a likely culprit) are
up to date.

It can also be hardware but if it is we'll have to get a shotgun
so I hope you don't live in a liberal state.

On May 22, 8:45*pm, w...@xxxxxx (the wharf rat) wrote:
the error seems to occur when my network is busy... so i was thinking
of the LAN / NIC card at first, but can the video card be affecting it
as well? thanks.

In article <0aee5312-17c5-4da3-b3e7-214980a863b0@xxxxxx>,
liketofindoutwhy <liketofindoutwhy@xxxxxx> wrote:Sorry, can't tell from here :-) If you think it's the NIC and
the thing is a plug in card (even though it wil REAAAALLLY piss of that
westom guy) just replace it with a different card, used 100bt cards
are a dime a dozen.

Maybe westom can diagnose the logic of a lan card with a multimeter.

--

Richard Urban
Microsoft MVP
Windows Desktop Experience


"the wharf rat" <wrat@xxxxxx> wrote in message
news:gv7uts$b2p$1@xxxxxx

In article <Oqit$R22JHA.5816@xxxxxx>,
Richard Urban <richardurbanREMOVETHIS@xxxxxx> wrote:Come on, you know better than that. You use a ***HAIR DRYER***
to diagnose lan cards.

On May 22, 11:34*pm, liketofindoutwhy <liketofindout...@xxxxxx>
wrote:The error message says software has executed incorrectly and was
detected by hardware. The message has additional information (ie such
as the file name of software that failed). Trace the problem to
either hardware or software. Suspects are either a software driver
(rarely) or is hardware such as defective power system or memory
circuits.

Verify voltages on the red, orange, yellow, and purple wires with a
3.5 digit multimeter when the system is multitasking to all
peripherals simultaneously. However this suspect is less likely if
your error message is always to one location or in a software driver.

Problem more likely can be found with a good diagnostic such as the
one provided for free by better computer manufacturers (that also
tests the NIC), or by a third party such as Memtst64. Execute this
diagnostic once. Then repeat it with memory heated with a hairdryer
on highest heat settings. Intermittent memory is often found
conclusively by a diagnostic when memory is happy and hot. So hot as
to be uncomfortable to touch is an ideal testing temperatures.

Meanwhile, a complete message with software driver and numbers may
have resulted in a better answer. Also look for an Intel diagnostic
for their NIC chip. That might provide useful information if the above
tests do not identify a failure. IRQ 3 is not relevant.