NetSetMan Support

Critcho

Member

Registered: 2012-11-26

Posts: 3

Win7-64bit Blue Screen Of Death when ethernet cable unplugged

Software: NetSetMan Pro V3.5.1 (says it's the latest).
System: Windows 7 Pro, SP1, 64 bit.

I can unplug and replug the ethernet cable as often as I want when NetSetMan is not running (e.g. NSM is not restarted after a laptop sleep??). However, as soon as I unplug the cable when NSM is running, my laptop crashes to Blue Screen Of Death.

This is repeatable every single time, so let me know what crash files you want me to send and I can do that to assist.

Thanks.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,899

Re: Win7-64bit Blue Screen Of Death when ethernet cable unplugged

Well, that sounds really strange. I never heard of that problem before. However, taking into account how NetSetMan works the only reason this might happen is if you're using AutoSwitch. Because that's the only method where NetSetMan reacts on changes in your network. Could you tell me if you're using that feature and if by deactivating it the problem is gone?
Of course deactivating that feature isn't a "real" solution. A blue screen in Windows mostly appears if some driver or hardware is malfunctioning. The blue screen usually gives some hint on where the problem might be found. You can use a tool like BlueScreenView to analyze the problem. That way you'll get more information on what the source of the problem might be. I'd recommend to update or reinstall the network drivers (both for wired and wireless adapters) and then to try again.

Critcho

Member

Registered: 2012-11-26

Posts: 3

Re: Win7-64bit Blue Screen Of Death when ethernet cable unplugged

Hi Ilja, That problem hasn't happened for a while (last one 28/01/13), not sure if the IT guys did something to my laptop when they had it. I had one autoswitch set to make my home printer the default when the home wifi came into range, but the crashes never coincided with the presence or lack thereof of that wifi connection.

The process that was crashing was ntoskrnl.exe, every time:
012813-14196-01.dmp    28/01/2013 19:17:44    WORKER_THREAD_RETURNED_AT_BAD_IRQL    0x000000e1    fffff800`03587560    00000000`00000002    fffffa80`0cc86e20    fffffa80`0cc86e20    ntoskrnl.exe    ntoskrnl.exe+7efc0    NT Kernel & System    Microsoft® Windows® Operating System    Microsoft Corporation    6.1.7601.18044 (win7sp1_gdr.130104-1431)    x64    ntoskrnl.exe+7efc0                    C:\Windows\Minidump\012813-14196-01.dmp    8    15    7601    299,448   

At the moment, when I have the ethernet cable plugged into one local device only (PLC), all traffic is routed through the ethernet cable instead of the WIFI, so I have no internet access. I'm not sure if this is related, when the IT guys fix this, I'll make sure this BSOD doesn't come back.

Thanks again for your help. I've got several other annoyances with NSM (forgetting settings, forgetting WIFI saved profiles, taking forever to open the tray) that I'll search the forums for.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,899

Re: Win7-64bit Blue Screen Of Death when ethernet cable unplugged

"IRQL"-problems are always very annoying. As to my knowledge they all have in common that some drivers interfere with each other. Sometime that only happens with some certain trigger. So for example if NetSetMan hooks to the change events of your WiFi adapter and this event handling is coliding with the event handling of some other driver (simply because one of those two drivers is faulty) then it might result in such a problem.
Please have a look at all the different issues that are related to the error that you pointed out:
https://www.google.de/search?q=WORKER_T … T_BAD_IRQL
I'd highly recommend to update or completely reinstall all network related drivers if that happens again.

Thanks again for your help. I've got several other annoyances with NSM (forgetting settings, forgetting WIFI saved profiles, taking forever to open the tray) that I'll search the forums for.

I'm sure you'll find some answers here but you're welcome to ask if you're stuck with some problem.

Here are some quick replies:
forgetting settings -> need more details...
forgetting WIFI saved profiles -> WiFi settings are managed by Windows. NetSetMan only accesses them to provide an easier management system.
taking forever to open the tray -> the reason is probably a problem with updating the public IP address; try deactivating this feature in the preferences.