New
#1
Constant BSOD/Crashing
Hi,
My pc crashes pretty much every time I play a game.
Battlefield Bad Company 2 and Crysis crash after ~5-20 minutes of gameplay.
COD:MW2 crashes after random amounts of time 1 hour+ usually.
I was wondering if any of you can tell me what you make of this mini dump!
Thanks!Code:Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\090510-24960-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols 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`02c01000 PsLoadedModuleList = 0xfffff800`02e3ee50 Debug session time: Sun Sep 5 19:52:33.207 2010 (UTC + 1:00) System Uptime: 0 days 8:10:21.720 Loading Kernel Symbols ............................................................... ................................................................ ............................... Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 10E, {1f, fffff8a00bea1e50, 0, 2c445f} Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) The video memory manager encountered a condition that it can't recover from. By crashing, the video memory manager is attempting to get enough information into the minidump such that somebody can pinpoint what lead to this condition. Arguments: Arg1: 000000000000001f, The subtype of the bugcheck: Arg2: fffff8a00bea1e50 Arg3: 0000000000000000 Arg4: 00000000002c445f Debugging Details: ------------------ BUGCHECK_STR: 0x10e_1f CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff88000c8022f to fffff80002c71740 STACK_TEXT: fffff880`036d6878 fffff880`00c8022f : 00000000`0000010e 00000000`0000001f fffff8a0`0bea1e50 00000000`00000000 : nt!KeBugCheckEx fffff880`036d6880 fffff880`03e21098 : fffff8a0`096a58d0 fffff8a0`0bea1e50 00000000`002c445f 00000000`00000000 : watchdog!WdLogEvent5+0x11b fffff880`036d68d0 fffff880`03e1e8af : 00000000`00000000 fffffa80`04557308 00000000`00000c3a fffffa80`073e2920 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148 fffff880`036d6910 fffff880`03e3865d : 00000000`00000000 fffff8a0`0cd59930 fffffa80`00000000 fffffa80`040c9900 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b fffff880`036d6ae0 fffff880`03e38398 : fffff800`040fa080 fffff880`03e37d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241 fffff880`036d6cd0 fffff880`03e37e96 : 00000000`00000000 fffffa80`04046b00 00000000`00000080 fffffa80`056cf010 : dxgmms1!VidSchiSubmitQueueCommand+0x50 fffff880`036d6d00 fffff800`02f15c06 : 00000000`038d65af fffffa80`056d6a10 fffffa80`039d4040 fffffa80`056d6a10 : dxgmms1!VidSchiWorkerThread+0xd6 fffff880`036d6d40 fffff800`02c4fc26 : fffff800`02debe80 fffffa80`056d6a10 fffff800`02df9c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a fffff880`036d6d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 fffff880`03e21098 c7442450c5f3ffff mov dword ptr [rsp+50h],0FFFFF3C5h SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms1 IMAGE_NAME: dxgmms1.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578 FAILURE_BUCKET_ID: X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 BUCKET_ID: X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 Followup: MachineOwner