Solved Random BSOD while running common tasks

[skipbr]

I've been having some random BSOD with this computer. Sometimes it work for the whole day, sometimes it crashes in 10 minutes. It happens when browsing using IE/Chrome, using Explorer or using Word.

I did noticed several errors in Windows Events log, but don't know how to isolate some of them, so I could test it properly.

Just a note, I ran memtest (about 2 hours only) and it gave me nothing. I'd be running a second time and will keep for at least 24 hours just to make sure memory isn't the culprit.

Any help is more than welcome.

Note: Im posting it from my main computer (the one in my system specs) and not from the one with BSOD.

 

[HonorGamer]

Hello,

Event[421]:
  Log Name: System
  Source: Microsoft-Windows-WLAN-AutoConfig
  Date: 2011-10-05T13:55:18.186
  Event ID: 10000
  Task: N/A
  Level: Erro
  Opcode: Informações
  Keyword: N/A
  User: S-1-5-18
  User Name: AUTORIDADE NT\SISTEMA
  Computer: Secretaria1-WIN
  Description: 
Falha na inicialização do Módulo de Extensibilidade de WLAN.

Caminho do Módulo: C:\Windows\system32\athExt.dll
Código de Erro: 126

Thanks to Google translator i was able to figure out what this meant lol. But make sure you have the latest WLAN drivers. Are you using a USB wifi adapter by any chance?

jswpslwf.sys Thu May 15 05:28:43 [B][COLOR="Red"]2008 [/COLOR][/B](482C105B)

Drivers before 2009 are known to cause problems such as BSODs. Please update: D-Link - Tech Support Product List

some of the dumps are showing memory corruption. Please run a http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html to be safe.

Post back results.

-Justin

 

[skipbr]

That was fast, thanks.

Yes, this computer uses an usb wifi dongle. It's an TP-Link adapter.
I just updated my first post with the system specs.

As soon as memtest finishes the 24 hours test I'll update the driver and see how it goes.

Thanks again!

 

[HonorGamer]

Win7 does not like USB wireless devices. Unplug, and uninstall all the drivers. Then just connect via ethernet cable. Then test that out.

-Justin

 

[skipbr]

Win7 does not like USB wireless devices. Unplug, and uninstall all the drivers. Then just connect via ethernet cable. Then test that out.

-Justin

Ok, thanks for the advice.

I'll test it and report back asap.

 

[Poimetheus]

You could also download "bluescreenview", which analyzes the memory dump made you blue-screened. Use that to retrieve the stop code and provide it to us, or look it up online.

 

[HonorGamer]

You could also download "bluescreenview", which analyzes the memory dump made you blue-screened. Use that to retrieve the stop code and provide it to us, or look it up online.

With the program I have there is no need. As I am able to see all the codes.

-Justin

 

[skipbr]

Ok, ran memtest and found that someone restart the computer after the 24 hours test

So I just uninstalled the TP-Link driver and also an utility called QSS (from TP-Link as well). Installed the latest driver and so far, no BSOD.

The file described early (jswpslwf.sy) belongs to this utility. Since it's not supported in Windows 7 (had to force uninstall) I believe it was the culprit here.

Hope it won't crash anymore.

Thanks once again.

 

[HonorGamer]

If it does crash please post back and we will try to get it solved. But glad we got it figured out!

-Justin

 

[Poimetheus]

You could also download "bluescreenview", which analyzes the memory dump made you blue-screened. Use that to retrieve the stop code and provide it to us, or look it up online.

With the program I have there is no need. As I am able to see all the codes.

-Justin[/QUT

This suggestion wasn't for you. It was for the gent with BSOD problems. Did I miss where you posted a problem and not a suggestion? (not sarcasm)

 

[HonorGamer]

i know this, but the gent with the BSOD problems is giving me the files that I need to find out the problem. The stop code DOESN'T ALWAYS provide the answer. Not to mention, if he is already giving me the crash files that are needed then I can analyze the problem. It may take a few steps though. And this is why we have troubleshooting. To narrow it down to the answer.

-Justin