Various BSOD in games

Hello!

I'm going to try to make the most detailed post about my problem, but if you need anymore information please don't hesitate to ask!

For starter here is my configuration (I've built the PC myself like 4-5 years ago):

MB: ASUS A8R32MVP Deluxe
CPU: AMD Athlon X2 3800+
GPU: ATI RADEON HD4850 (1 year old, failry new compared to the rest of the system)
RAM: 4*1 Go of Corsair DDR2 400 Cas 3
PSU: Seasonic SS-600HT 12V1:18A 12V2:18A
HDD: 250Go WD (System)
1To Samsung (Data)
OS: W7 Professional x64
AV: MSE

Nothing is over-clocked or ever was, I just don't play with OC

Now let me go on with the battery of tests I've run so far:

Memory:
I've run Memtest86+ for more than 24hours straight without a single error.
Furthermore, I've try every combination of my sticks, the BSOD never stopped.
I can fairly say I'm pretty sure my RAM is OK.

Overheating:
Like I said the configuration is 4-5 year old, build by myself, and the case is a really well ventilated (3x12cm fans) Thermaltake case which never suffered any heat. That said my temperatures are as follow on heavy game load (after a few hours of crysis for exemple):
CPU 1&2: 68° Max
GPU: 80°C max
With my limited knowledge of hardware stuff I can fairly say these are normal temperatures, nothing to worry about here.

CPU/GPU/PSU load:
I've run all of OCCT tests (CPU OCCT, CPU LINPACK, GPU OCCT, and POWER SUPPLY) and everything passed without any problem.

HDD:
I've run all the tests of SeaTools & WD Diagnostic on both HDD and everything passed green, so no problem there.

OS&Drivers:
I've done a fresh install this week end, of a legit MSDNAA (I'm a student) Windows 7 Professional copy, installed ATI and integrated sound latest drivers, and a few games to test the system stability.

Now, with all that said (which I hope will help and not just waste your time), and if you're still reading, let me explain what exactly my problem is:
My system is having randomly reboot, ONLY WHILE PLAYING GAMES, most of the time showing a BSOD, sometimes just rebooting, a few times just crashing to desktop (may be games crash, not sure if it's related to my problem). The thing is I'm a heavy gamer, or was for the past years, and this system always performed like a charm, and now since a few months ago I've been experiencing freezes/reboot in certain games, while I could play some other for hours. I found it weird but it didn't happen on a lot of games so I ignored it or some time. But lately, in almost every single game I try to run, it crash to a BSOD &/or reboot after a few min or less than an hour. But some game I can still play for hours straight without problem, like Aion, which is a huge load on the system, but these games are becoming rare.

All that said, I've been looking at hundred of posts trying to pinpoint the problem and I've lately learned to analyse minidumps and such, but after trying almost everything I though it was time I requested some help on the matter. I've seen you guys get conclusion out of minidumps like you could read memory adress stuff and know exactly what happened in there, which is impressive

So here are some of my latest minidumps since I reinstalled my system last week-end, the error are almost all the time different, I was getting a lot of IRQ_NOT_LESS_OR_EQUAL stuff, but lately I've got some MEMORY_MANAGEMENT, or PAGE_FAULT_IN_NON_PAGED_AREA, ATTEMPT_TO_WRITE_IN_READ_ONLY_MEMORY or some BAD_POOL_CALLER, etc. If you need me to produce more minidumps, just ask me I'll go play Civilization V for a few mins and come back to you guys :-(

Anyway, you are my last hope, thanks in advance for any help!!!


Edit: Sorry I forgot to talk about the outdated drivers that the minidumps may list, but theree is a few I identified:

SI3132.sys
SiRemFil.sys
SiWinAcc.sys
These 3 are Silicon Image drivers and there seem to be no drivers more recent than those, even on Asus official website, the driver for my motherboard are older than those, probably fetched by W7.

RT2500.sys
This one is a Ralink driver for my wireless adapter, because Linksys never published x64 compatible drivers for this card, but since the internal chip is a Ralink, this driver if fully compatible, and I've been using it since forever, I'd give my hand this one is safe :)

Every other driver seems to be recent enough, at least from 2009.

First thing that struck me are the temps.
68C is getting warm for a Intel CPU, but really HOT for a AMD. Especially if Not OCing.
What were load temps in Prime like?

I believe ideally they are supposed to be around 55ish or so at full load .. (I could be wrong on temps here however, as i havent dealt with many AMD builds, just going by a failing memory)

I didn't see mention if you cleaned out the case.
Do you have a can of compressed air to blow out everthing real well, especially the CPU Heatsink?


AS far as MEMtest passing, please remember, this is only showing the RAM modules themselves are OK.
If youv'e tested individual sticks in the various slots, we can also assume the motherboard DIMM slots are OK as well.

But, that doesnt mean you can not get memory errors. you still can relating to the NB or Memory Controller itself when everything is under load.

IRQ_NOT_LESS_OR_EQUAL can be memory related, or even driver related.

PAGE_FAULT_IN_NON_PAGED_AREA - This means a program is attempting to write outside its allocated space. Often, just sloppy coding.

MEMORY_MANAGEMENT : The culprit here could be the memory controller. Being AMD its intergrated into the CPU.
Although it could be something else entirely. Just some thoughts as to "possible" culprits.

(Im guessing you already know this though :) )


Do you have you Pagefile disabled by chance? if so, re-enabled it.
Although this should usually give a error something like "Virtual Memory"



Few questions:

What PSU do you have? Wattage and 12V rail amperage?

What does your bios report in "System Health" for voltages? (12V etc)

What Antivirus are you running?

What tests did you run with OCCT? Small FFT or blend?

Can you try running Prime 95 and see what results you get?
Prime is a bit more accurate in my experience.
Start with a blend test.
If it fails, try a Small FFT (which is just the CPU)


Also, please upload a dmp file, so those more experienced in debugging can have a look while running a Prime test.

Of the dumps you uploaded, the two most recent are Driver Verifier enabled dumps. One blames a Windows core system file the other blames Direct X. The only dump not Driver Verifier enabled also blames Direct X. It shows a stop error code of BE, ATTEMPTED_WRITE_TO_READONLY_MEMORY , usually caused by a device driver or memory.

Since Driver Verifier is pointing to Windows files, I suggest you turn it off.

Code:

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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_minidumps.zip\092610-19968-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a5e000 PsLoadedModuleList = 0xfffff800`02c9be50
Debug session time: Sun Sep 26 11:36:44.540 2010 (GMT-4)
System Uptime: 0 days 0:15:17.712
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck BE, {fffff9600025c594, 6cc000005a24b021, fffff880057569e0, b}

Probably caused by : dxgkrnl.sys ( dxgkrnl!DxgkCheckVidPnExclusiveOwnership+2bb )

Followup: MachineOwner
---------

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

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: fffff9600025c594, Virtual address for the attempted write.
Arg2: 6cc000005a24b021, PTE contents.
Arg3: fffff880057569e0, (reserved)
Arg4: 000000000000000b, (reserved)

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xBE

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880057569e0 -- (.trap 0xfffff880057569e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880044c3fcf rsp=fffff88005756b70 rbp=fffff88005756ca0
 r8=fffff8a00752a000  r9=0000000000000011 r10=fffff9600025c594
r11=fffff900c0662250 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgkrnl!DxgkCheckVidPnExclusiveOwnership+0x2bb:
fffff880`044c3fcf 498bd5          mov     rdx,r13
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b4eae2 to fffff80002ace740

STACK_TEXT:  
fffff880`05756878 fffff800`02b4eae2 : 00000000`000000be fffff960`0025c594 6cc00000`5a24b021 fffff880`057569e0 : nt!KeBugCheckEx
fffff880`05756880 fffff800`02acc82e : 00000000`00000001 fffffa80`04480060 fffffa80`04480100 fffff800`02ad5992 : nt! ?? ::FNODOBFM::`string'+0x4237e
fffff880`057569e0 fffff880`044c3fcf : fffffa80`04480060 00000000`00000000 fffffa80`0436b000 fffff960`001c56ff : nt!KiPageFault+0x16e
fffff880`05756b70 fffff960`0025c5a6 : 00000000`00000000 00000000`00000000 00000000`0000080a 00000000`40000080 : dxgkrnl!DxgkCheckVidPnExclusiveOwnership+0x2bb
fffff880`05756bf0 fffff800`02acd993 : fffffa80`04480060 00000000`0203f4d0 000007fe`f726d610 fffffa80`00000000 : win32k!NtGdiDdDDICheckVidPnExclusiveOwnership+0x12
fffff880`05756c20 000007fe`fee7137a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0203efd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fee7137a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgkrnl!DxgkCheckVidPnExclusiveOwnership+2bb
fffff880`044c3fcf 498bd5          mov     rdx,r13

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgkrnl!DxgkCheckVidPnExclusiveOwnership+2bb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgkrnl

IMAGE_NAME:  dxgkrnl.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac5509e

FAILURE_BUCKET_ID:  X64_0xBE_dxgkrnl!DxgkCheckVidPnExclusiveOwnership+2bb

BUCKET_ID:  X64_0xBE_dxgkrnl!DxgkCheckVidPnExclusiveOwnership+2bb

Followup: MachineOwner
---------


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_minidumps.zip\092710-77484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c04000 PsLoadedModuleList = 0xfffff800`02e41e50
Debug session time: Mon Sep 27 12:52:38.295 2010 (GMT-4)
System Uptime: 0 days 0:10:09.483
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41201, fffff68000183a40, 884000008c2a8867, fffffa8003149d70}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13bb2 )

Followup: MachineOwner
---------

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041201, The subtype of the bugcheck.
Arg2: fffff68000183a40
Arg3: 884000008c2a8867
Arg4: fffffa8003149d70

Debugging Details:
------------------


BUGCHECK_STR:  0x1a_41201

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  game.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002cd2b3e to fffff80002c74740

STACK_TEXT:  
fffff880`05f629b8 fffff800`02cd2b3e : 00000000`0000001a 00000000`00041201 fffff680`00183a40 88400000`8c2a8867 : nt!KeBugCheckEx
fffff880`05f629c0 fffff800`02c42b6e : fffff880`05f62a90 fffff800`02c7293d 00000000`00000008 88400000`8c2a8867 : nt! ?? ::FNODOBFM::`string'+0x13bb2
fffff880`05f62a00 fffff800`02c4280a : fffffa80`03149d70 fffffa80`0417a6e0 fffffa80`0417a6e0 00000000`30748000 : nt!MiQueryAddressState+0x2ae
fffff880`05f62a50 fffff800`02f5bc38 : 00000000`00000004 00000000`30749000 fffffa80`03149d70 00000000`00000000 : nt!MiQueryAddressSpan+0xaa
fffff880`05f62ac0 fffff800`02c73993 : ffffffff`ffffffff fffffa80`0487c660 00000000`0479fd20 00000000`0479e798 : nt!NtQueryVirtualMemory+0x386
fffff880`05f62bb0 00000000`7744ff8a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0479e778 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7744ff8a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13bb2
fffff800`02cd2b3e cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13bb2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x1a_41201_VRF_nt!_??_::FNODOBFM::_string_+13bb2

BUCKET_ID:  X64_0x1a_41201_VRF_nt!_??_::FNODOBFM::_string_+13bb2

Followup: MachineOwner
---------


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


Loading Dump File [C:\Users\Owner\AppData\Local\Temp\Temp1_minidumps.zip\092910-88000-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e49e50
Debug session time: Wed Sep 29 14:51:39.796 2010 (GMT-4)
System Uptime: 0 days 2:15:21.671
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 1500743, fffffa80045d0400}

GetPointerFromAddress: unable to read from fffff80002eb40e0
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264 )

Followup: MachineOwner
---------

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

BAD_POOL_CALLER (c2)
The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000001500743, Memory contents of the pool block
Arg4: fffffa80045d0400, Address of the block of pool being deallocated

Debugging Details:
------------------


POOL_ADDRESS:  fffffa80045d0400 

FREED_POOL_TAG:  Ntfx

BUGCHECK_STR:  0xc2_7_Ntfx

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME:  CivilizationV.

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002daf60e to fffff80002c7c740

STACK_TEXT:  
fffff880`0723a558 fffff800`02daf60e : 00000000`000000c2 00000000`00000007 00000000`00001097 00000000`01500743 : nt!KeBugCheckEx
fffff880`0723a560 fffff880`03d5f5ec : 00000000`00000000 00000000`00000001 fffff8a0`0ad133b0 00000000`00000001 : nt!ExDeferredFreePool+0x11eb
fffff880`0723a610 fffff880`03d45ecc : 00000000`00000000 fffff8a0`00000000 fffffa80`029eaa00 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+0x264
fffff880`0723a6e0 fffff880`03c87c10 : 00000000`00000000 fffff8a0`0b26a000 fffff8a0`0b26a000 00000000`00000001 : dxgmms1!VidMmCloseAllocation+0x44
fffff880`0723a710 fffff880`03c8754b : fffff8a0`0b26a000 fffff8a0`0b26b300 fffff8a0`00000000 00000000`00000000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x248
fffff880`0723a800 fffff880`03c87825 : 00000000`00000010 fffff8a0`0b26a000 00000000`00000001 00000000`00000000 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0xa3
fffff880`0723a850 fffff880`03c8b6e0 : fffff8a0`0a69e600 fffff880`0723aca0 fffffa80`043fa000 fffff880`03c523af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`0723a8a0 fffff880`03c8dd9b : fffff8a0`0b26a000 fffff880`0723a9b0 00000000`fdf92001 fffffa80`0444a001 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x448
fffff880`0723a930 fffff960`001bb3a2 : 00000000`00000000 fffffa80`0477c810 00000000`00000020 00000000`74af5f08 : dxgkrnl!DxgkDestroyAllocation+0x9bf
fffff880`0723abf0 fffff800`02c7b993 : 00000000`00000000 fffff800`032173c0 00000000`0ec1ef90 00000000`00000000 : win32k!NtGdiDdDDIDestroyAllocation+0x12
fffff880`0723ac20 00000000`74b1120a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0a55e7e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74b1120a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264
fffff880`03d5f5ec 488b4b20        mov     rcx,qword ptr [rbx+20h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc578

FAILURE_BUCKET_ID:  X64_0xc2_7_Ntfx_VRF_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264

BUCKET_ID:  X64_0xc2_7_Ntfx_VRF_dxgmms1!VIDMM_GLOBAL::CloseOneAllocation+264

Followup: MachineOwner
---------

I would not be surprised if this driver was not a large part of your problem; it is an almost guaranteed cause of BSOD's:

ASACPI.sys Sun Mar 27 22:30:36 2005

The 2005 version of this driver is a known BSOD cause.
Please visit this link: ASUSTeK Computer Inc.-Support- download_item_mkt
Scroll down to the Utilities category, then scroll down to the "ATK0110 driver for WindowsXP/Vista/Windows 7 32&64-bit " (it's about the 8th item down).
Download and install it.
Go to C:\Windows\System32\drivers to check and make sure that the ASACPI.sys file is date stamped from 2009 or 2010 (NOT 2005).

Let's see how your system does with that driver updated.

I find another badly out of date driver as well as the outdated Silicon drivers you mentioned:

RT2500.sys Thu Jun 01 10:39:06 2006 - RaLinkTech/Linksys WMP54G wireless network adapter driver Ralink corp.

SI3132.sys Wed Oct 03 14:39:29 2007
SiRemFil.sys Wed Jun 20 15:42:10 2007
SiWinAcc.sys Thu Jun 14 20:02:02 2007

I suggest you upgrade your wireless adapter to one compatible with Win 7.