Overclock.net banner

Windows 7 BSOD While Gaming

642 Views 9 Replies 3 Participants Last post by  Raptor_Jesus
Hey guys,

Well I've been getting BSODs while playing BF2. Randomly they will pop up, and its getting really annoying. BCcode 50. This is what windbg says about it. Any help is greatly appreciated!

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\\Windows\\Minidump\\120609-16660-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02853000 PsLoadedModuleList = 0xfffff800`02a90e50
Debug session time: Sun Dec 6 11:40:50.361 2009 (GMT-5)
System Uptime: 0 days 11:23:53.890
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
Loading User Symbols
Loading unloaded module list
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff89f8951bd38, 1, fffff800029d3193, 5}

Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!EmpEvaluateUpdateRuleEvalState+3 )

Followup: MachineOwner

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

Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arg1: fffff89f8951bd38, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800029d3193, If non-zero, the instruction address which referenced the bad memory
Arg4: 0000000000000005, (reserved)

Debugging Details:

Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002afb0e0

fffff800`029d3193 48895808 mov qword ptr [rax+8],rbx





PROCESS_NAME: explorer.exe


TRAP_FRAME: fffff88003fdc130 -- (.trap 0xfffff88003fdc130)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88003fdc2c8 rbx=0000000000000000 rcx=fffff8a00009b4e0
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800029d3193 rsp=fffff88003fdc2c8 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=0000000000000000
r11=fffffa8005c4cad0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
fffff800`029d3193 48895808 mov qword ptr [rax+8],rbx ds:c300:fffff880`03fdc2d0=fffff88003fdc3b8
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002942b91 to fffff800028c4f00

fffff880`03fdbfc8 fffff800`02942b91 : 00000000`00000050 fffff89f`8951bd38 00000000`00000001 fffff880`03fdc130 : nt!KeBugCheckEx
fffff880`03fdbfd0 fffff800`028c2fee : 00000000`00000001 fffff8a0`00097890 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40f5b
fffff880`03fdc130 fffff800`029d3193 : fffff800`029d33f5 fffff880`03fdc3b8 fffff880`03fddd00 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`03fdc2c8 fffff800`029d33f5 : fffff880`03fdc3b8 fffff880`03fddd00 00000000`00000000 fffff880`03fdc3a0 : nt!EmpEvaluateUpdateRuleEvalState+0x3
fffff880`03fdc2d0 fffff800`02cd242e : ffffffff`ffffffff 00000000`00000000 fffff8a0`00097890 fffff880`03fdc3a8 : nt!EmpUpdateRuleState+0xe5
fffff880`03fdc300 fffff800`02cfd0d0 : fffff880`03fdc420 fffff880`03fddd00 00000000`00000001 00000000`00000000 : nt!EmClientQueryRuleState+0x8e
fffff880`03fdc330 fffff800`02b82efa : 00000000`00000000 00000000`00000001 fffff880`03fddd60 00000000`00000000 : nt!PopFilterCapabilities+0x1b0
fffff880`03fdc3a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtPowerInformation+0x6ba


fffff800`029d3193 48895808 mov qword ptr [rax+8],rbx


SYMBOL_NAME: nt!EmpEvaluateUpdateRuleEvalState+3



IMAGE_NAME: ntkrnlmp.exe


FAILURE_BUCKET_ID: X64_0x50_nt!EmpEvaluateUpdateRuleEvalState+3

BUCKET_ID: X64_0x50_nt!EmpEvaluateUpdateRuleEvalState+3

Followup: MachineOwner
See less See more
1 - 10 of 10 Posts

Originally Posted by grunion
View Post

Run system at stock for troubleshooting purposes?

Memtest would be my second step.

I am running at stock. I will give memtest a shot.
See less See more
page fault in nonpaged area (50) is generally memory corruption. have you run memtest already?

EDIT grunion beat me to it
  • Rep+
Reactions: 1
How many passes should I run?

And page file is enabled.
Okay, so I think it might be a bad slot. I removed one of the sticks, leaving just one in slot 0. I tested this for ~3 passes. No errors. Then I removed the one in slot 0, and replaced it with the other stick, and tested that. ~3 passes no error. I moved them both into slots 1 and 3, and now I am not getting BSODs. I will run a memtest tonight on slots 0 & 2, and slots 1 & 3 together. I know now for sure its not a bad DIMM.
This has happened to me before also. It ended up being the northbridge overheating, you may want to check that out, although with the P45 it wouldnt get as hot as the P35 I had before. Eventually I had to replace the motherboard because it started happening across all 4 of my DIMM slots randomly.
Hopefully this wont happen to my remaining slots. I don't think I will go to 8gb of memory, and if I do, I'm probably going i7. But thanks for the help!
1 - 10 of 10 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.