Re: [foxboro] Blue Screen NDIS.sys

  • From: "William C Ricker" <wcricker@xxxxxxxxxxxxxxx>
  • To: <foxboro@xxxxxxxxxxxxx>
  • Date: Tue, 7 Sep 2010 12:57:22 -0400

Update on these processors, anecdotal info, for what it's worth ...

We recently have had some problems with the T-3500 motherboard failures.
Of 3 brand new machines last month, one motherboard failed.

On the other side of the house folks dealing with "Brand Y" indicate that
they, too, are seeing above average motherboard failures on this same 
processor.


True, failure in 'ndis.sys' sounds like network, but don't forget to look 
at the motherboard.

When troubleshooting remember that in the MESH P92 the slot location and 
Ethernet address is each MESH network card is critical to the system.  As
I understand it, if a card is replaced or moved, either an edit to the 
registry of a reinstall of IA is required to make the system run.

Regards,
William C Ricker



-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Tadeo Armenta
Sent: Saturday, August 28, 2010 10:25 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Blue Screen NDIS.sys

Hey william
Its a P92 Dell 3500, it has IA 8.5, its the host of the system, and hosts
the 
AIM historian.

Its the original box.

Regards




________________________________
De: William C Ricker <wcricker@xxxxxxxxxxxxxxx>
Para: foxboro@xxxxxxxxxxxxx
Enviado: vie, agosto 27, 2010 5:28:19 PM
Asunto: Re: [foxboro] Blue Screen NDIS.sys

You didn't recently change machines, did you ?
Also, what version is it ?  what Hardware ?

WCR

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Tadeo Armenta
Sent: Friday, August 27, 2010 4:57 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Blue Screen NDIS.sys

Hello list
Yep, your eyes didnt deceive you, neither did mine...

Blue Screen

STOP: 0x0000007E (0xC0000005,0xB7D2591B,0x9B217C94,0x9B217990)

NDIS.sys   - Address B7D2591B base at B7D25000, Datestamp 48025d03

Normally, these type of erros are hardware related. So I'm gonna open de box
and 
give it some love in case something is lose... I read something about virus 
messing with the NDIS.sys file.

Does anything like this happened to you? Did you found a solution? Dont you
love 
Windows?

Please dont tell me this involves the NIC's

Thanx for any clue you can provide

Regards


 

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: