BSOD when Ethernet Plugged In

Forums › Desktop computing › BSOD when Ethernet Plugged In

MallAudio

95 posts

Master Geek

#29930 23-Jan-2009 15:46

Having trouble with a 2.1GHz Intel P4, 500MB RAM, Running embedded XP SP2...

Will run as happy as larry until you plug in the Ethernet Cable... as soon as it finds and connects to the network, it goes to the BSOD for maybe 1/2 a second and then reboots itself...

Was infected with a program called 'Spyware Guard 2009'
Have run MalwareBytes Anti-Malware, scanned with NOD32 etc and cleaned it all off...
Updated Network drivers, Chipset etc

Still no luck...

Any Ideas firstly - why its happening?
secondly - how to fix it?

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#191594 23-Jan-2009 15:51

If that spyware changed anything in the network configuration it could be causing this... Best option would be to reinstall the OS in my opinion... Then make sure you have all drivers up-to-date.

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

bazzer

3438 posts

Uber Geek
+1 received by user: 267

Trusted

#191602 23-Jan-2009 16:13

I'd try a new NIC if I could. I had the same problem and it came down to a faulty card.

MallAudio

95 posts

Master Geek

#191619 23-Jan-2009 16:39

have pulled apart another pc so i could try its network card in the faulting PC...
seemed to have resolved the issue.. was connected for 10mins or so and then it faulted...

STOP: 0x0000007A (0xCO201884, OxC0000156, Ox80621EA2, 0x181B88CO)

so... neither the D-link Network Card or the built in network adapter work...

Am going to reload our base image onto it on monday anyway, so will know then whether it's the adapter or some internal settings...

If its still happening after then, does that mean faulty mobo?

MallAudio

95 posts

Master Geek

#192127 26-Jan-2009 14:54

Re-imaged the machine just now... rebooted... it loads up the bios screen etc, then when it starts windows it pauses for 2-3 seconds then flashes the BSOD then reboots... so wont start at all now... tried the drive in another pc and it works fine... tried another drive in the problem PC and it does the same thing (faults then reboots)

Faulty MOBO????

Zeon

3926 posts

Uber Geek
+1 received by user: 759

Trusted

#192195 26-Jan-2009 23:57

Most likely a faulty MOBO. Onboard NIC was pro bably part of the southbridge and it is getting mroe and more sick. Maybe take back for Warranty?

Speedtest 2019-10-14

MallAudio

95 posts

Master Geek

#192254 27-Jan-2009 13:24

Have been playing around with this some more...

Have tried 2 different IDE drives and neither of them would boot... The problem SATA drive still wouldnt boot (cloned drive)
Tried a different SATA drive from one of my other servers and its booting fine repeatedly in the problem PC...

When its operating, plug in the IDE drive and it autoplays... plug in the problem SATA drive and it autoplays...

Try the problem drive in a pc i know is working, and it still wont boot on that machine either...

So... to me it looks like the drive is at fault... but if that was the case, how come i cant get IDE drives booting on the problem PC? but i can get the SATA drive booting on it...

Why would one drive work in the problem PC, but not the other... and why would the original drive from the 'problem PC' not work in another PC if it was just the MOBO?

sounds like both MOBO and HD are faulting??... but why would another drive work fine in the PC with "faulty" MOBO?

Confused?? Me too!!!

Lenovo

Shop now for Lenovo laptops and other devices (affiliate link).

DrGr33n

57 posts

Master Geek

#192354 27-Jan-2009 19:10

Have tried 2 different IDE drives and neither of them would boot... The problem SATA drive still wouldnt boot (cloned drive)
Tried a different SATA drive from one of my other servers and its booting fine repeatedly in the problem PC...

May need to change the SATA Raid/AHCI Mode in bios, and the bad sata drive may need a low level format. (there could still be remnants of the virus left.)

Also try resetting the CMOS and a different stick of ram for the bluescreen problem..

Cheers ;-)

Only dead fish go with the flow...