Hi Trouble,
Thanks for your swift response. I've upgraded all the drivers you suggest except the Atheros one (the download link you suggested gave me a zipped archive,
but I'm unsure how best to go about installing the drivers contained within (there doesn't seem to be any kind of installer attached).
In any case, I will monitor my system (ie. play more games
) and let you know if the problem persists.
Cheers,
Sir Thursday
I suspect that your network devices are still involved and according to your latest dump files three of the five files that I suggested updating in my original post are still reflecting the same dates
hamachi.sys 2/19/2009 update, uninstall or rename to hamachi.OLD you can always rename back to hamachi.sys if it proves not to be at fault.
netr28ux.sys 5/24/2009 Wireless Network Adapter (Possibly Linksys with RaLink Chipset) update from here
https://sites.google.com/site/linksy...river/download
L1E62x64.sys 8/23/2009 Atheros Ethernet Adapter update from here
Link Removed
DUMP FILE:
Code:
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {fffff88002f94040, 2, 0, fffff80002ceb6f6}
Probably caused by : ntkrnlmp.exe ( nt!KiSetTimerEx+86 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. [COLOR=#ff0000][U][B]This is usually
caused by drivers using improper addresses.[/B][/U][/COLOR]
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffff88002f94040, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ceb6f6, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f12100
fffff88002f94040
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiSetTimerEx+86
fffff800`02ceb6f6 488b8c2498000000 mov rcx,qword ptr [rsp+98h]
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: League of Lege
TRAP_FRAME: fffff88002f93e10 -- (.trap 0xfffff88002f93e10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880080e8be0 rbx=0000000000000000 rcx=0000000036117fb0
rdx=00000000727448cd rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ceb6f6 rsp=fffff88002f93fa8 rbp=fffff880080e8ca0
r8=0000000000001cf1 r9=0000000000000000 r10=fffffa8007150060
r11=0000000000000246 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up di pl nz na pe nc
nt!KiSetTimerEx+0x86:
fffff800`02ceb6f6 488b8c2498000000 mov rcx,qword ptr [rsp+98h] ss:fffff880`02f94040=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002cdf1e9 to fffff80002cdfc40
STACK_TEXT:
fffff880`02f93cc8 fffff800`02cdf1e9 : 00000000`0000000a fffff880`02f94040 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`02f93cd0 fffff800`02cdde60 : fffffa80`0834fd28 fffffa80`0834f1a0 fffffa80`077d6402 fffff880`02f64180 : nt!KiBugCheckDispatch+0x69
fffff880`02f93e10 fffff800`02ceb6f6 : fffff800`02ce2765 00000000`00000000 fffffa80`06cc6060 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02f93fa8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSetTimerEx+0x86
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSetTimerEx+86
fffff800`02ceb6f6 488b8c2498000000 mov rcx,qword ptr [rsp+98h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiSetTimerEx+86
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3
FAILURE_BUCKET_ID: X64_0xA_nt!KiSetTimerEx+86
BUCKET_ID: X64_0xA_nt!KiSetTimerEx+86
Followup: MachineOwner
As far as installing driver files that are contained within zipped archives, first you have to extract them, I personally use a piece of software called 7zip, but you can use anyone you are comfortable with including the built in windows 7 extractor.
Once extracted you need to force the install by using device manager.
Locate the device you wish to update
Right click it and choose properties
Select the driver tab
click the update driver button
Browse my computer for driver software
Let me pick from a list of device drivers on my computer
Have disk button
Browse button
Use the Locate File dialog box to browse to the folder where you have downloaded and extracted the files to, in the case of the Atheros driver you'll be looking for netL1e64.inf (3/29/2010), double click it and OK and next until finished.
NOTE: To answer your other question
As I mentioned in my previous post, I was unable to install the Atheros
drivers...
how likely is it that those are the problem?
I would think, quite probable. Since your dump files are still reflecting problems with drivers and all your most recent dumps reflect "League of Lege" which I assume is the online game you are having issues with.... unless of course there is something inherently wrong with the game itself and you need some updates and patches to correct it, in which case I might suggest checking their forum boards and see if there are any other players with similar issues. But if it's happening with other online games as well, then it's still likely a driver issue.
Regards
Randy