
Quote: Originally Posted by
darkxstorm
Thanks for the reply. I have uploaded the dump file of the latest BSOD that I had.
As I thought. Your DX video driver or card.
Please re-install using this.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using
Guru3D - Driver Sweeper
Or if the above doesnt work for you.
Phyxion.net - Driver Sweeper
When it is removed then download and install the fresh copy.
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\052211-22089-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e04000 PsLoadedModuleList = 0xfffff800`03049650
Debug session time: Mon May 23 02:56:11.857 2011 (GMT-4)
System Uptime: 0 days 14:05:47.732
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {1f, fffff8a00f4991e0, 0, 20193e}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148 )
Followup: MachineOwner
---------
0: 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: fffff8a00f4991e0
Arg3: 0000000000000000
Arg4: 000000000020193e
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 fffff8800145f22f to fffff80002e83d00
STACK_TEXT:
fffff880`059d9738 fffff880`0145f22f : 00000000`0000010e 00000000`0000001f fffff8a0`0f4991e0 00000000`00000000 : nt!KeBugCheckEx
fffff880`059d9740 fffff880`04391098 : fffff8a0`0f4991e0 fffff8a0`0f4991e0 00000000`0020193e 00000000`00000000 : watchdog!WdLogEvent5+0x11b
fffff880`059d9790 fffff880`0438e8af : 00000000`00000000 fffffa80`0a70b980 00000000`00000c3a fffffa80`0aac1c88 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148
fffff880`059d97d0 fffff880`043a865d : 00000000`00000000 fffff8a0`0ef1b860 fffffa80`00000000 fffffa80`0a60b430 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xe1b
fffff880`059d99a0 fffff880`043a8398 : fffff880`02f69f40 fffff880`043a7d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`059d9b90 fffff880`043a7e96 : 00000000`00000000 fffffa80`0a7fa730 00000000`00000080 fffffa80`086e0410 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`059d9bc0 fffff800`0312032e : 00000000`032136fa fffffa80`08cbda10 fffffa80`066edb30 fffffa80`08cbda10 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`059d9c00 fffff800`02e75666 : fffff880`02f65180 fffffa80`08cbda10 fffff880`02f6ffc0 fffff880`01269384 : nt!PspSystemThreadStartup+0x5a
fffff880`059d9c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
fffff880`04391098 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: 4ce799c1
FAILURE_BUCKET_ID: X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
BUCKET_ID: X64_0x10e_1f_dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
Followup: MachineOwner
---------