Hello. it seems whenever I play a game, I blue screen with either a page fault in nonpaged area, or dxgmms1.sys crashing. I've run memtest, and checked the temp on my graphics card. No dice. Also updated all the drivers I could. Here is the dmp file http://www.bloodybits.com/041011-26769-01.dmp and http://www.bloodybits.com/041211-23290-01.dmp Any help would be appreciated. Thanks

******************************************************************************* * * * 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. Arguments: Arg1: fffff8800d4c0fc8, memory referenced. Arg2: 0000000000000000, value 0 = read operation, 1 = write operation. Arg3: fffff8800521d0b9, If non-zero, the instruction address which referenced the bad memory address. Arg4: 0000000000000002, (reserved) Debugging Details: ------------------ Could not read faulting driver name READ_ADDRESS: fffff8800d4c0fc8 FAULTING_IP: dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 fffff880`0521d0b9 448b54c208 mov r10d,dword ptr [rdx+rax*8+8] MM_INTERNAL_CODE: 2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x50 PROCESS_NAME: javaw.exe CURRENT_IRQL: 0 TRAP_FRAME: fffff88009de60a0 -- (.trap 0xfffff88009de60a0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=00000000000009f8 rbx=0000000000000000 rcx=00000000000004fc rdx=fffff8800d4bc000 rsi=0000000000000000 rdi=0000000000000000 rip=fffff8800521d0b9 rsp=fffff88009de6230 rbp=fffff88009de6a40 r8=fffffa80076e2028 r9=0000000000000001 r10=fffff8a0051eeab0 r11=0000000040013f00 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz ac pe nc dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169: fffff880`0521d0b9 448b54c208 mov r10d,dword ptr [rdx+rax*8+8] ds:6010:fffff880`0d4c0fc8=???????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff8000313d8f2 to fffff800030be740 STACK_TEXT: fffff880`09de5f38 fffff800`0313d8f2 : 00000000`00000050 fffff880`0d4c0fc8 00000000`00000000 fffff880`09de60a0 : nt!KeBugCheckEx fffff880`09de5f40 fffff800`030bc82e : 00000000`00000000 00000000`00000000 fffffa80`06984000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ec0 fffff880`09de60a0 fffff880`0521d0b9 : 00000000`00000102 fffff880`09de69f0 fffff8a0`02793b20 fffff880`05356279 : nt!KiPageFault+0x16e fffff880`09de6230 fffff880`052033e7 : fffffa80`07392501 fffffa80`067d6f10 00000000`53380028 fffff880`00000017 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169 fffff880`09de6320 fffff880`05360d6a : fffffa80`00000001 00000000`00000200 fffff880`09de6a40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43 fffff880`09de6370 fffff880`0536052f : fffff8a0`00000001 fffff8a0`0eff4cc0 fffff880`09de69f0 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x326 fffff880`09de6980 fffff960`001cc9da : 00000000`5158e6b0 00000000`00000200 00000000`5158fd20 00000000`7ef5c000 : dxgkrnl!DxgkRender+0x3e7 fffff880`09de6bf0 fffff800`030bd993 : fffffa80`072adb60 00000000`000005fc 00000000`00000000 fffffa80`0769b900 : win32k!NtGdiDdDDIRender+0x12 fffff880`09de6c20 00000000`730c143a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 00000000`5158e688 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x730c143a STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 fffff880`0521d0b9 448b54c208 mov r10d,dword ptr [rdx+rax*8+8] SYMBOL_STACK_INDEX: 3 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578 FAILURE_BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 BUCKET_ID: X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 Followup: MachineOwner --------- 0: kd> lmvm dxgmms1 start end module name fffff880`05200000 fffff880`05246000 dxgmms1 (pdb symbols) downstreamstore\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb Loaded symbol image file: dxgmms1.sys Mapped memory image file: DownstreamStore\dxgmms1.sys\4A5BC57846000\dxgmms1.sys Image path: \SystemRoot\System32\drivers\dxgmms1.sys Image name: dxgmms1.sys Timestamp: Tue Jul 14 01:38:32 2009 (4A5BC578) CheckSum: 0004AD44 ImageSize: 00046000 File version: 6.1.7600.16385 Product version: 6.1.7600.16385 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: dxgmms1.sys OriginalFilename: dxgmms1.sys ProductVersion: 6.1.7600.16385 FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255) FileDescription: DirectX Graphics MMS LegalCopyright: © Microsoft Corporation. All rights reserved. |||||||||||||||||||||||||||||||||||||||||| Your BSOD was caused by dxgmms1.sys driver which belongs to DirectX Graphics MMS. I see that the latest hotfix for this driver is installed. Please start by updating your graphic card driver. If this does not help, contact your graphic card manufacturer Technical Support. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration