BSOD while Quad-Boxing Wakfu Game.

[lealr]

Hi Guys,

It's been a long time since I last posted on here. But I have ran into a BSOD on my brothers computer today. I am not too sure what the cause is, but I have gotten the necessary info to see if you guys can help me out. He mentioned that this was the 2nd time it has happened, where the first time was about 2 weeks ago.

Check attached for the debug info.

He was playing the MMO Wakfu, and he was running 4 (Quad-boxing) instances of the game on his machine, so I am assuming it took a strain on the video-card, but I could be wrong. When the computer restarted the wireless card was disabled, and so I had to go to the adapter option and re-enable it so it was working again. I think these are all the info I gathered. I would greatly appreciate any help on this issue.

The computer specs are: AMD Phenon II X6 1090T Processor 3.20 GHz | 8gb Ram | ASUS M4A79XTD EVO AM3 AMD 790X ATX AMD | W7-sp1 64bit

You guys are always amazing when it comes to helping people with such issues.

Thanks,
Leal

 

[Thedoctor44]

Your Atheros network driver is causing problems. Please update it from this link.

Download - Welcome to TP-LINK

I think you may appear to have the wrong driver installed for your network card. The one you have installed is for Atheros.

Remove the old Atheros network driver from the control panel, then find your wireless network card for TP-LINK in the URL above. Install the latest correct driver for your network card. If you have any more BSODs post back.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000020, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88001840580, address which referenced memory

fffff880`02600000 fffff880`027de000   athurx   T (no symbols)           
    Loaded symbol image file: athurx.sys
    Image path: \SystemRoot\system32\DRIVERS\athurx.sys
    Image name: athurx.sys
    Timestamp:        [COLOR="red"]Wed Apr 20 11:07:45 2011[/COLOR] (4DAEB071)
    CheckSum:         001E1C78
    ImageSize:        001DE000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

 

[lealr]

Thanks for the help Thedoctor44. I will be sure to update those drivers, and see how it holds up. I'll check back at the end of the week, and if everything is working fine I will mark this thread as solved.