Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP Home Edition Blue Screen when on the LAN

Status
Not open for further replies.

neilcorbett

Technical User
Apr 5, 2002
49
LU
Hi,

I have an XP Home Edition Laptop (Dell Inspiron 2200) it has worked fine on the LAN for ages but about 3 weeks ago it started to Blue Screen / Dumping Physical Memory within about 20 seconds of the LAN lead being attached.

It goes to Limited Connectivity to Connected to BSOD within 20 seconds, if I leave the LAN lead off it never Blue Screens, other laptops work fine when using the same lead so not a Lead / Router type issue.

I have reapplied SP2, updated the Drivers & the BIOS Version. Tried removing the drivers and they re applied when I rebooted but its still Blue Screening.

Short of a reload not sure what I can do :-(

Any thoughts anyone?

Many Thanks in Advance
 
1st thing to suspect is a hardware failure.
Try another network card. They are dead cheap. If using onboard LAB then disable it in the BIOS.

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]
 
Hi

I have just done exactly that - well kind of.

I have tested a connection to the net using the onboard Wireless and thats doing the same, the moment your connected bang its gone :-(

 
Onboard wireless and onboard ethernet - both fail? If so I would suspect they have components in common.

The cause could be a million and one things.

I suggest as your next step you try one or more of the following.

Set the machine to make a minidump and show the BSOD rather than auto re-boot (if you haven't already)
get windbg (windows dump file analyser) and analyse a dump (use another machine). The dump will be around 100MB so you could copy it via a CD or a USB stick?
The analysis may (hopefully) show you the driver or hardware that is failing.

Check you don't have any bad RAM - download memtest86 and make a bootable CD (you can get the iso to burn)

See if you have a restore point you can use to go back to when all was well. If you make a restore point now and then go back and it works then at least you know it's a software issue so you can return to your new restore point and then either try re-installing drivers, fixing winsock (google) or...

Backup any data you need to and do a repair install of windows. It will be quicker than messing around I suspect.

Scan for virus's etc.


you can google for memtest and windbg.


[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]
 
Download LSPFix from the following link

Download Winsock fix from the following link

Run LSPFix
Click the check box "I know what I am doing"
Remove every thing on left by moving to the right
Reboot the computer

Run winsock fix click the Fix button. When the repair is complete the program will prompt you to reboot.

When Windows loads the second time connect to the network, hopefully you will not get a Blue Screen
 
Hi Tektilityva

I have tried both of those Fixes and still doing the same :-(

Thanks though.
 
I'm not too busy as it happens so if you want, upload a minidump to a file hoster, like sendspace and I'll take a look at it. I still think it's hardware related though. You haven't changed any BIOS settings have you?

[navy]When I married "Miss Right" I didn't realise her first name was 'always'. LOL[/navy]
 
Hi stduc

To be honest I have pretty much given up now, spent too long on it. Going to try a reload and if that fails we know its hardware,

Thanks for the offer though appreciated

Neil
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top