Misc Stangest Wifi issue EVER!

[zone97]

Here is the situation. Here i am at work, about to take lunch and play some club house games with mmy wife via WFC.. Well I connect and create a room and wait... Mean while, a fellow tech came into the break room and told me his laptop just went BSOD, as did mine. At the same time.. Well we check the rest of the office and it only effected ours.. Now neither laptop is connected wirelessly. My tech had complained about having a virus he had issues with a week ago but had said nothing sence. I checked my system and also had nothing...

What we discovered was very strange. The DSL was causing the BSOD's.. If i turned the DSL off and back on and went to the WFC the second it connected, both laptops would die.

Now the DSL has a static IP from set, 1 laptop does and the other doesnt. I even changed the IP of the DSL and no change still BSOD... Anyone ever heard of anthing like that?

 

[Rayder]

That is strange. Maybe the router is limiting the amount of simultaneous connections. As soon as you connect with the DS, the PC's get cut off......though I'm not sure why both PC's would crash.....unless the 2 PC's rely on each other somehow and if one crashes, they both do.

Maybe it's a combination of connection limiting and a MAC address issue. See if your DS has the same MAC address as one of the PC's.

Otherwise, I couldn't say what the heck is going on.

 

[zone97]

Both laptops are wired, not wireless. The wireless router is not being used, other than by the DSL. Now this recently stated happening and I do rember upgrading the firmware for the router recently. It is a USR router configured as an access point only. no DHCP. humm wonder if i need to back the firmware back.

 

[cory1492]

Dig around for crash logs on the affected PCs. Usually with a blue screen it gives a memory dump and mentions what program caused the exception somewhere. On a side note, my brother has one of those cable modem phones, if we have it hooked to any PC and the phone rings, one of the modules creates an unhandled exception (write to protected memory IIRC) which causes a bluescreen (and due to the settings of the PC, immediate reboot), though outgoing calls work 100%... it's about the only thing hardware related that I have ever seen which comes close to what you are experiencing.

At a guess though, DS wifi has to use a specific/slower mode than most PC's do... perhaps when it is telling the connected PCs that it is going into a different mode things go bonkers. It's a good bet that it has something to do with the udpate, if it has never done it before (they didn't by chance produce a changelog with your recent upgrade that mentions any changes to how wireless b/g etc are handled, did they? You might also look into the wireless drivers on both affected PC's, maybe they need an update too, and happen to be the same drivers?

 

[zone97]

Laptops are not using wireless..

man you guys read the post!!!!

also there are 27 other PCs on this network, servers workstations.. Only these 2 laptops were effected? This is what makes it even more of a mystery.

This is what was in the system event log at the time of the crash..

The computer has rebooted from a bugcheck. The bugcheck was: 0x1000000a (0xffffff9a, 0x00000002, 0x00000000, 0x80533281). A dump was saved in: C:\WINDOWS\Minidump\Mini030807-01.dmp.

 

[Little]

While the laptops aren't wireless, they must be in someway, at some point, connected to the same network, where the wired and wireless meets up. Its there that your problem is going to be.

 

[Digeman]

That IS the stangest issue ever!

Sorry man couldn't resist

Oh and I don't know squat about computers so can't help ya there but wish you the best of luck!