This post is more than 5 years old
3 Posts
0
33451
February 4th, 2014 09:00
SOLVED -- BSOD - Win7 - hostednetwork
Hi there,
I am one of those guys who knows enough to be dangerous.
My machine is a Vostro 1015, with a very fresh and fully updated Win 7 Pro x86
I was researching a mysterious paper that was spit of my printer, which contained some networking info. It referenced IP 192.168.137.1...
My research led me to the command:
netsh wlan
Which of course, being the adventerous type, continued the command with:
netsh wlan start hostednetwork
Immediately followed by BSOD.
I cannot enter safemode with networking(without further BSOD's), and so I cannot follow up with the command:
netsh wlan stop hostednetwork
Which I presume would undo my foolish decision to START it in the first place.
Entering that last command, from "safe mode without networking", gets me:
Wireless AutoConfig Service (wlansvc) is not running. The hosted network could not be stopped. Reason code is 0.
Further research into this problem, led me to more than one forum that discussed wifi adapter driver problems... But i'm not sure how that applies to me, or what to do about it.
Also, I had no intentions of setting up a Virtual Network, which I now understand that is what I was inadvertantly doing.
Any suggestions or ideas on undoing this would be helpful.
Thanks, Kris
PS, I can provide the BSOD dump files if that would be helpful.
PudgyOne
9 Legend
•
30.3K Posts
0
February 4th, 2014 09:00
Kris,
Restart the computer and run the full diagnostics, press F12 at startup. report back any error codes.
Download and install Resplendence Software - WhoCrashed
Click on analyze and see what caused the crash.
Rick
BigSmellyMonkey
3 Posts
0
February 4th, 2014 15:00
Hi Rick,
Thanks so much for your reply.
I ran the WhoCrashed software, and it pointed me to the problem driver.
With a little googling, I found a updated driver that solved my problem.
I was my Athero (qualcom) wireless adapter driver.
Thanks again,
Kris
BigSmellyMonkey
3 Posts
0
February 4th, 2014 16:00
Hey Rick,
Thanks for your reply,
I had no errors with the Diagnostics, so I ran WhoCrashed.
It identified my wireless adapters driver as the culprit.
Downloaded a new version of my driver, and it works great.
Thanks again,
Kris
PudgyOne
9 Legend
•
30.3K Posts
0
February 4th, 2014 17:00
Kris,
Glad you got it working! :emotion-21: Thanks for posting back.
Take care,
Rick