up vote 3 down vote favorite
1
share [g+] share [fb]

I have a laptop that works fine everywhere. But when the user gets home and tries to start it it gets a BSOD. I said start it up and then go home and see what happens. Even though it is already started as soon as get gets home it stops working with a BSOD. When the user gets back in the car and goes out a few miles it reboots fine. I know this is more than a coincidence. This has happened over and over with various combinations. It only hoses up at his house.

The wireless is suspected. I am having him turn if all of on his laptop and the routers to see what happens.

Has anyone ever seen anything like this before where it is the wireless? I am out of ideas.

It is an IBM Thinkpad about 5+ years old. XP Pro., SP3, fully updated, all the latest drivers. Works great everywhere, even in other wireless networks, but just not at his home location. I have not read the BSOD dump for the latest incident but last one was an IRQ error 0xA, nothing that was obvious.\

EDIT: clarify - the BSOD is upon boot up and never gets to the logon for XP. The other BSOD was when it was already booted up an running, desktop showing, etc. and when he got out at his house it went BSOD and then BSOD upon boot up. Few miles from home no BSOD.

EDIT: forgot to say the system was completely restored before all the updates...everything fresh.

EDIT: further research shows it may hose up because of the N band only coming from the router or a neighbors router.

link|improve this question
35% accept rate
Have you tried disabling the wireless on the laptop, or many laptops have the wireless cards easily accessible from underneath, you could try removing the card. – heavyd Feb 11 '10 at 15:34
That's what's next. But if it is what could be causing it? – johnny Feb 11 '10 at 15:41
+1 for the phrase hoses up – eleven81 Feb 11 '10 at 15:46
Faulty hardware can cause any kind of very difficult to debug issues, including unexpected BSOD or reboots. Especially with the a wireless card that is always listening for incoming traffic, if there is a problem any wireless signal could trigger it. – heavyd Feb 11 '10 at 15:51
1  
I would suggest using Nirsoft Bluescreen View to see if you can look at the minidump file and see exactly which driver/file is cause the BSOD. Link: nirsoft.net/utils/blue_screen_view.html – commradepolski Feb 11 '10 at 17:37
show 1 more comment
feedback

2 Answers

up vote 1 down vote accepted

Yes - I have seen this lots on some of the early Intel Wireless Pro based cards when connecting to secure networks - I forget now, but I think the card came out before AES or TKIP (whichever is newer) became widespread and whenever you attempt to connect to one of these, it either hangs or causes a BSOD.

They released a driver update that fixed it though. Based on the age of the laptop, I would guess it was this, but it has been some time since I last came across this problem.

link|improve this answer
i updated the driver no more bsod. apparently it didn't like getting an n type signal without dying. – johnny Mar 1 '10 at 20:32
feedback
up vote 1 down vote

Hows the leccy?

Some places have more dodgy power than others.. What happens when its running on batteries to boot?

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.