BSOD happens randomly, random computer freezing occurs as well.

[derekimo]

This time it's your wireless driver,

Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
 athurx+0x9d35

Driver Reference Table - athurx.sys

 Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:        [COLOR="Red"]Wed Apr 20 03:07:45 2011 [/COLOR](4DAEB071)
    CheckSum:         001E1C78
    ImageSize:        001DE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Try updating it here,

Download - Welcome to TP-LINK

 

[weilun]

wow thanks! really appreciate your help and replies to my situation! I just updated the driver for the wireless adapter now . hopefully nothing bad will happen again ....

 

[derekimo]

You're welcome, hope it goes well.

 

[weilun]

Hi all, actually I've had multiple BSODs since my last post but I didn't have much time to try and fix the problem due to school commitments .. The random computer freezing still happens but really i have no idea how to fix or log the activities right up before the freezing occurs.

as attached is the zipped folder for the crash logs!

cheers for helping me. thanks ~

 

[weilun]

Hi anyone can help me?

recently got a lot more bsods

 

[derekimo]

Sorry about that, don't know how I lost track of this thread.

This is still your wireless driver being flagged,

Unable to load image \SystemRoot\system32\DRIVERS\athurx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athurx.sys
*** ERROR: Module load completed but symbols could not be loaded for athurx.sys
 athurx+0x34bd

Same version,

Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:        [COLOR="Red"]Wed Apr 20 03:07:45 2011[/COLOR] (4DAEB071)
    CheckSum:         001E1C78
    ImageSize:        001DE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Did you try updating the driver?

TL-WN721N - Welcome to TP-LINK

Do you have a different adapter to test? Does this happen with it plugged in to a different USB port?

 

[weilun]

yes I did download the latest version TL-WN721N_V1_131113 but it seems that the driver date didn't change.
I even re-installed just moments ago just to be sure.

Should I move the wireless adaptor to the port behind just to try out?

Anyway, don't worry about losing track >.< you're already doing me a huge favour by advising me what to do!!! *bow*

EDIT:
I've looked into the .inf file of the top 2 latest drivers stated in the website.

TL-WN721N_V1_Win7_Beta
[version]
Signature = "$Windows NT$"
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %ATHEROS%
LayoutFiles = layout.inf
CatalogFile = athurext.cat
DriverVer = 10/06/2011,2.0.0.64

TL-WN721N_V1_131113
[version]
Signature = "$Windows NT$"
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %ATHEROS%
LayoutFiles = layout.inf
CatalogFile = athurextx.cat
DriverVer = 04/20/2011,2.0.0.62

 

[derekimo]

Yeah, try a different port to see if that helps.

It would be nice if you had a different adapter to try as well just to make sure if it's the adapter or the port.

 

[weilun]

Noted. Will shift the adaptor to the back usb port for now >.<

 

[Layback Bear]

Just a thought.
Your motherboard has usb 3.0 and 2.0.
Sometimes things will not work well in usb 3.0 for what ever reason.
Try both and see if it helps.

 

[weilun]

Just a thought.
Your motherboard has usb 3.0 and 2.0.
Sometimes things will not work well in usb 3.0 for what ever reason.
Try both and see if it helps.

hihi! you mean to not use usb 3.0 ports at all for now?

 

[derekimo]

Just a thought.
Your motherboard has usb 3.0 and 2.0.
Sometimes things will not work well in usb 3.0 for what ever reason.
Try both and see if it helps.

hihi! you mean to not use usb 3.0 ports at all for now?

No, just that they may not work as well, so try the others.