Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Weird BSOD in Video Memory Management
New Posts  All Forums:Forum Nav:

Weird BSOD in Video Memory Management

post #1 of 3
Thread Starter 
Hello forum,

this particular bluescreen has been plaguing me for years now and I have done everything imaginable to get to the root of it but no luck. I hope that someone here can hopefully spot the cause.

First, a couple of facts about the BSOD:
  • It happens *only* while I am running a 3D application or when I close it.
  • It's always in VIDEO_MEMORY_MANAGEMENT_INTERNAL.
  • It's always caused by either dxgmms1 or the ati driver itself.
  • The BSOD happens more frequently the higher the OC but it never goes away, just happens less frequently (even on stock.) The timefrime for the BSOD to occur is between a couple of seconds after starting a game (high OC ~3.8GHz) or several months (stock/3.6 GHz).

Facts about my system:
  • The system is (usually) OC and runs stable in most* of the burn-in programs in existence.
  • The RAM is OK.

Because of that I am fairly sure that the cause must be either a faulty graphics card or, more likely, some weird bug in the AMD driver that is only triggered by my specific configuration. However, the fact that the BSOD seems to be sensitive to OC points into a more general faulty hardware direction. It doesn't make any sense.

The system:

Intel Core 2 Duo E8400 @ 3.6/3.8 GHz
Asus P5Q-E
AMD Radeon HD 5770

A typical bluescreen:
Code:
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\062413-29671-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 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`03065000 PsLoadedModuleList = 0xfffff800`032a9670
Debug session time: Mon Jun 24 22:30:01.908 2013 (UTC + 2:00)
System Uptime: 0 days 0:11:02.344
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 10E, {1f, fffff8a010b278c0, 0, 9eb8}

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: fffff8a010b278c0
Arg3: 0000000000000000
Arg4: 0000000000009eb8

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


BUGCHECK_STR:  0x10e_1f

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff88003c6622f to fffff800030e3fc0

STACK_TEXT:  
fffff880`0365b838 fffff880`03c6622f : 00000000`0000010e 00000000`0000001f fffff8a0`10b278c0 00000000`00000000 : nt!KeBugCheckEx
fffff880`0365b840 fffff880`04821098 : fffff8a0`10b278c0 fffff8a0`10b278c0 00000000`00009eb8 00000000`00000000 : watchdog!WdLogEvent5+0x11b
fffff880`0365b890 fffff880`0481e803 : 00000000`00000000 fffffa80`07493000 00000000`00000c3a fffff8a0`10b278c0 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0x148
fffff880`0365b8d0 fffff880`0483865d : 00000000`00000000 fffff8a0`0eefe0e0 fffffa80`00000000 fffffa80`07488d00 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd6f
fffff880`0365baa0 fffff880`04838398 : fffff880`009edec0 fffff880`04837d00 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`0365bc90 fffff880`04837e96 : 00000000`00000000 fffffa80`06fc3550 00000000`00000080 fffffa80`06fe8010 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`0365bcc0 fffff800`0337ae5a : 00000000`12a24882 fffffa80`06fcd060 fffffa80`051ec890 fffffa80`06fcd060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`0365bd00 fffff800`030d4d26 : fffff880`009e9180 fffffa80`06fcd060 fffffa80`06fa09a0 fffffa80`06fe7820 : nt!PspSystemThreadStartup+0x5a
fffff880`0365bd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+148
fffff880`04821098 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
---------


Thanks for any help in advance!

*I am fairly sure by now that I have missed none!

EDIT: Attached health report

Info.zip 2354k .zip file
Edited by ravv - 6/24/13 at 2:47pm
post #2 of 3
I'm not exactly sure what you're asking here.

You've identified the problem fairly well.
I'd say create a ticket with whomever you purchased the GPU from and send it back under warranty. (RMA)

The normal procedure to fix problems like this would be:
- rolling back/updating drivers
- removing an overclock/voltage modification
- test the card in a different system

If you're getting the same error after trying all of the above then you've got no choice but to replace the card.
Lan Master 2.0
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 3570k ASUS P8Z77-M Asus GTX 670 Patriot 2133mhz 
Hard DriveHard DriveCoolingOS
OZC Agility 4 WD Blue 500gb Coolermaster Hyper TX3 Win 7 Ultimate 
MonitorKeyboardPowerCase
Samsung S23700D Das Keyboard Ultimate Silent Corsair CX600 NZXT Vulcan 
MouseMouse PadAudio
Logitech MX-518 Razer Goliathus Control Asus Essence ST 
  hide details  
Reply
Lan Master 2.0
(15 items)
 
  
CPUMotherboardGraphicsRAM
i5 3570k ASUS P8Z77-M Asus GTX 670 Patriot 2133mhz 
Hard DriveHard DriveCoolingOS
OZC Agility 4 WD Blue 500gb Coolermaster Hyper TX3 Win 7 Ultimate 
MonitorKeyboardPowerCase
Samsung S23700D Das Keyboard Ultimate Silent Corsair CX600 NZXT Vulcan 
MouseMouse PadAudio
Logitech MX-518 Razer Goliathus Control Asus Essence ST 
  hide details  
Reply
post #3 of 3
Thread Starter 
Quote:
Originally Posted by ThirtySixNights View Post

I'm not exactly sure what you're asking here.

You've identified the problem fairly well.

I am well aware that it might be a problem with the card. I wanted to make sure it is though, especially because this BSOD is sensitive to OC.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Crash Analysis and Debugging
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Crash Analysis and Debugging › Weird BSOD in Video Memory Management