New
#21
Hi DaTa82. I looked at all five of your dumps and I see five different error codes. all five indicate memory corruption and two directly blame memory corruption. Unfortunately, they do not give us the specific cause of the memory corruption. The five different error codes or bugcheck codes generally indicate a hardware or hardware related problem. You stated your BSOD's only seem to occur when you are running games. This plus the the fact the two dumps blamed the Windows system Direct X driver and one blamed your video driver lead me to believe you definitely have a conflict.
I agree with The Howling Wolves suggestion to enable Driver Verifier. Carefully follow the instructions in this tutorial: Driver Verifier - Enable and Disable. If Driver Verifier encounters a faulty driver, it will trigger a BSOD. Use your computer normally while Verifier is running and upload any and all Verifier enabled dumps.
What firewall are you running and do you have any other security programs running besides your firewall and MSE? This would include any banking security program, gaming security program, etc.
Since one dump blames the Direct X Driver and one blames atikmpag.sys, your video driver, you might try removing the Catalyst Control Center and only install the Display Driver.
Let's see Driver Verifier shows and we will go from there.
Code:Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`0301f000 PsLoadedModuleList = 0xfffff800`03264e90 Debug session time: Fri Apr 15 13:10:51.220 2011 (GMT-4) System Uptime: 0 days 0:27:01.796 Loading Kernel Symbols ............................................................... ................................................................ .................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {31d0, 2, 1, fffff800030a81b3} Probably caused by : ntkrnlmp.exe ( nt!KiTimerWaitTest+2b3 ) 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. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Debug session time: Fri Apr 15 10:37:08.132 2011 (GMT-4) System Uptime: 0 days 0:16:35.709 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 4E, {99, 10e3dc, 2, 12b3db} Probably caused by : memory_corruption ( nt!MiBadShareCount+4c ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PFN_LIST_CORRUPT (4e) Typically caused by drivers passing bad memory descriptor lists (ie: calling MmUnlockPages twice with the same list, etc). If a kernel debugger is available get the stack trace. Debug session time: Fri Apr 15 11:50:40.246 2011 (GMT-4) System Uptime: 0 days 1:12:32.822 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffff8a00cfcd160, 0, fffff8800432d586, 0} Could not read faulting driver name Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+636 ) Followup: MachineOwner --------- 3: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* PAGE_FAULT_IN_NONPAGED_AREA (50) 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. Debug session time: Fri Apr 15 17:55:52.633 2011 (GMT-4) System Uptime: 0 days 0:35:12.210 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3B, {c0000005, fffff88004e8754b, fffff8800adfc790, 0} Probably caused by : atikmdag.sys ( atikmdag+3c254b ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_SERVICE_EXCEPTION (3b) An exception happened while executing a system service routine. Arguments: Arg1: 00000000c0000005, Exception code that caused the bugcheck Arg2: fffff88004e8754b, Address of the exception record for the exception that caused the bugcheck Arg3: fffff8800adfc790, Address of the context record for the exception that caused the bugcheck Arg4: 0000000000000000, zero. Debug session time: Fri Apr 15 17:19:32.456 2011 (GMT-4) System Uptime: 0 days 4:07:57.642 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {ffffffffc0000005, fffff880053d3d90, fffff880027916a8, fffff88002790f00} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForPreparation+c4 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit.