Windows 7 BSOD Team Fortress 2

I've never had a problem with Team Fortress 2, even back when I had my terrible laptop. I built a computer back in March 2012, and it's been (almost) perfect until now.

For some reason, it seems to BSOD randomly when playing TF2. I don't know why, my drivers are up to date, as is my BIOS.

Here's a recent minidump.

Please help! Thank you very much!

View attachment 090712-19328-01.dmp

I use AVG. I hear it can mess with games sometimes, what Antivirus should I use? Thanks.

Last edited:


Windows Forum Admin
Staff member
Premium Supporter
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

Use !analyze -v to get detailed debugging information.

BugCheck A, {26, d, 0, fffff8000307a7e0}

Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+150 )

Followup: MachineOwner

0: kd> !analyze -v
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

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 a kernel debugger is available get the stack backtrace.
Arg1: 0000000000000026, memory referenced
Arg2: 000000000000000d, 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: fffff8000307a7e0, address which referenced memory

Debugging Details:

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b3100


fffff800`0307a7e0 488b4618        mov     rax,qword ptr [rsi+18h]




PROCESS_NAME:  hl2.exe

TRAP_FRAME:  fffff880055e1460 -- (.trap 0xfffff880055e1460)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8006b0b320 rbx=0000000000000000 rcx=fffff800031f4f18
rdx=00000000031f6e80 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000307a7e0 rsp=fffff880055e15f0 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000002 r10=0000000000000008
r11=fffff880055e16b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
fffff800`0307a7e0 488b4618        mov     rax,qword ptr [rsi+18h] ds:0200:00000000`00000018=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003083769 to fffff800030841c0

fffff880`055e1318 fffff800`03083769 : 00000000`0000000a 00000000`00000026 00000000`0000000d 00000000`00000000 : nt!KeBugCheckEx
fffff880`055e1320 fffff800`030823e0 : 00000000`00017710 fffff880`055e1610 fffffa80`0b797160 fffff800`031f4f18 : nt!KiBugCheckDispatch+0x69
fffff880`055e1460 fffff800`0307a7e0 : fffffa80`06aa4a40 00000000`00000001 00000000`00000001 00000000`00000000 : nt!KiPageFault+0x260
fffff880`055e15f0 fffff800`0308dcd7 : 00000000`00000002 fffff800`031f4f18 fffff800`031f6e80 fffff800`033785ec : nt!KeAccumulateTicks+0x150
fffff880`055e1680 fffff800`035f7895 : fffff800`0361d460 fffff880`055e1830 fffff800`0361d460 fffffa80`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`055e1780 fffff800`03080713 : fffffa80`091cc2d0 fffff800`03094f5c 73500001`2aec2867 fffffa80`0c906b50 : hal!HalpHpetClockInterrupt+0x8d
fffff880`055e17b0 fffff800`0309476d : fffff680`002416b0 fffffa80`07459d78 fffffa80`0c906b50 ffffffff`ffffffff : nt!KiInterruptDispatchNoLock+0x163
fffff880`055e1940 fffff800`03090e6d : fffffa80`038839e0 fffff880`055e1a00 fffff700`01080000 00000000`00000000 : nt!MiInitializePfn+0x11d
fffff880`055e1980 fffff800`030822ee : 00000000`00000001 00000000`482d7000 fffff880`055e1a01 00000000`00000e44 : nt!MmAccessFault+0xa7d
fffff880`055e1ae0 00000000`722d4aa7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`003adb88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x722d4aa7


fffff800`0307a7e0 488b4618        mov     rax,qword ptr [rsi+18h]


SYMBOL_NAME:  nt!KeAccumulateTicks+150

FOLLOWUP_NAME:  MachineOwner


IMAGE_NAME:  ntkrnlmp.exe


FAILURE_BUCKET_ID:  X64_0xA_nt!KeAccumulateTicks+150

BUCKET_ID:  X64_0xA_nt!KeAccumulateTicks+150

Followup: MachineOwner

The IRQL_NOT_LESS_OR_EQUAL bug check has a value of 0x0000000A. This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.

[h=3]Cause[/h]This bug check is issued if paged memory (or invalid memory) is accessed when the IRQL is too high.
The error that generates this bug check usually occurs after the installation of a faulty device driver, system service, or BIOS.
If you encounter bug check 0xA while upgrading to a later version of Windows, this error might be caused by a device driver, a system service, a virus scanner, or a backup tool that is incompatible with the new version.

Your bios is out of date:

BiosVersion = F9
BiosReleaseDate = 05/11/2012
Please update to the latest version: GIGABYTE - Motherboard - Socket AM3+ - GA-970A-D3 (rev. 1.0/1.1)

You are also running certain drivers which are known to cause issues:

AppleCharger.sys Wed Nov 02 02:46:00 2011: May cause BSOD's on Win7 systems - uninstall to test

As you mention in your post, please uninstall AVG and try MSE instead: Microsoft Security Essentials - Free Antivirus for Windows

Please update:
ae1000w7.sys Fri Jan 15 08:15:48 2010: Linksys AE1000
Rt64win7.sys Tue Aug 23 14:55:41 2011: Realtek
RTKVHD64.sys Tue Oct 18 12:48:20 2011: Realtek

Once you've completed the above and bsod still persists check your RAM using this app: Memtest86+ - Advanced Memory Diagnostic Tool
Only test one stick at a time and for at least 7/8 passes.

Thank you very much for the quick and organized response. I am now going through the checklist, and will check back when the problem seems to have stopped.

Again, thank you very much. I should report back in a day or so.

This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.