Chassis intrusion

[jayjay66]

Hi,

I'm really hoping somebody can help with this one. I always leave my computer on (I never turn my computer off). I had a power failure during the night last night and when I started my computer up this morning it said "CHASSIS INTRUSION - Press F1 to continue". I pressed F1 and my computer booted-up but "Houston we have a problem". I don't have internet anymore. It says that the network cable is unplugged. But, it's not!!... Arggghhh, I've never seen "CHASSIS INTRUSION" before in my life. I've Googled the CHASSIS INTRUSION error and it says to replace the Jumper and reboot. I did that but I still get the same error. My mobo is Asus 7N8X-VM/400.

Can somebody please help me with this one.

Thanks,
JJ

 

[edfair]

This sounds more like an XP problem, not hardware.
This is XP, isn't it?

Next attempt is a repair installation. Then if that doesn't resolve it, a fresh install. And I would go back to the original network setup with on-board NIC.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[garebo]

I'm with edfair on the fresh install idea.

I know it doesnt help now, but can i suggest you get yourself even a lower priced UPS (uiniterruptible power supply. You can get them for under $100 at any computer place. Byt what you are saying i believe you should have one.
I keep about 2 to 4 pcs going almost all the time. And before i bought UPS's for my pc's i had the problems you are talking about and more and more still. Bad or dead motherboards, dead power supplies, vid cards, hard drives.
Since i have installed and use UPS's, almost no issues i cant handle and almost NO dead hardware! I'm a skeptic myself and thought it was a gimmick. Its not! Some areas have poor power and the public just doesnt know and likely never will find out. Power surges are bad but power brown-outs are even worse and they can happen in the blink of an eye.
More proof needed? Well, you can set the tolerance level on these UPS's and if i set mine to low tolerance levels, my UPS's will go off 10 to 20 times per day! I have to set the level to medium and they only go off maybe once every two months. So there is once every two months i don't lose any more hardware! I hum along, using my pc for 6 hours a day with the same win xp install i have had for years. No big windows probs no bad hardware.
By now i should be known for this rant, but its all true and if i can convince you or anyone else to buy a UPS then its worth it!


Good advice + great people = tek-tips

 

[smah]

What's at the other end of the network cable & are you sure that device is functioning properly?

 

[jayjay66]

I'm pretty sure it's not an XP problem. I'm gonna go buy a new motherboard tomorrow. I can't believe I have to do that. The repair in XP didn't work.

Anybody have ANY OTHER ideas before I go dish out money to buy a new mobo.

Please any help

Thanks,
JJ

 

[jayjay66]

Hi,

OK, so I'll sum this up. I've tried the onboard LAN it it says, "Network cable is unplugged. Acquiring network address. Network cable is unplugged. Acquiring network address. Network cable is unplugged. Acquiring network address." in a loop at the bottom in the WINXP taskbar.

I've tried disabling the onboard LAN and put in another NIC and it still says, " "Network cable is unplugged. Acquiring network address. Network cable is unplugged. Acquiring network address. Network cable is unplugged. Acquiring network address." in a loop at the bottom in the WINXP taskbar."

This all starting when I got a power failure and my mobo gave me the "Chassis Intrusion" error

I need to know how many people think it's the mobo the problem or it's WINXP.

My guess, mobo's shot. I really doubt it's an XP problem.

Anybody??

Please let me know your opinion and any help you can suggest.

Thanks,
JJ

 

[smah]

My guess is: neither. My first guess is a problem with the cable or the dhcp server (which might be broadband router -hence the reason that I asked: what's at the other end).

Next, once you have verified that the DHCP server is giving out addresses correctly, try the following command from the command prompt: netsh winsock reset catalog. Test your connectivity.

If you still have a problem, reset your TCP/IP stack using:

http://support.microsoft.com/default.aspx?scid=kb;en-us;299357

 

[jayjay66]

Hi,

I'm pretty sure it's not a problem with the cable. The cable is a cross-connect cable connected to another computer which the other computer works perfectly well (internet and all). I've resest the winsocks and tcp-ip's already. nothing worked.

Mobo problem since the problem only started when I had a power failure??

What's anybody's opinion.

Anybody?

Please let me know.

 

[jayjay66]

Again, I repeat. It's not the cable. The cable has been changed and tested.


Ughhhhh.... anybody, please help

Please help.

JJ

 

[KevinADC]

time for a new mother board?

 

[dglienna]

Have you deleted the network card and let Windows find it again? I faced the same problem the other night setting up a NEW Dell laptop. It would NOT connect to my router. Finally, I deleted it, and let Windows find it and reinstall the driver, which solved the issue.

David

 

[jayjay66]

Hi,

Yup, I've tried deleting the card and letting windows find it, but that still didn't work.

Anybody's help please?

Thanks,
JJ

 

[smah]

People have been giving you help. Just because the ICS machine is connecting to the internet, doesn't mean that it's correctly supplying an address to the 'problem' machine. Do you have another known working computer that you could borrow to test that connection? Or could you move the 'problem' computer to temporarily replace the ICS computer. Either of these tests will narrow down where the problem is.

 

[jurgen36]

I do believe it is not your computer at all. But on the other end of your networking cable. A faulty mobo would recognise another network card, if it works otherwise normally. The original error would be caused by a corrupt cmoss. This is easily fixed by resetting it. So look at the other end. That the other machine works on the internet does not mean that its networking setup is correct.
Regards

Jurgen