So i created a previous post about system crashes and BSOD a few days ago. I later found that some of my RAM timings were incorrect and thought that this might have solved the issue. I was wrong. I have had 2 more BSOD crashes since then and have attached the recommended files, including those from my last post.
I put the PC together last week and it's my first time building my own system. It's running Win 7 Pro 64bit on a Gigabyte GA-880GA-UD3H board with an AMD Phenom II X4 3.4GHz processor and 4x2Gb A-Data RAM. I have a Radeon 6870 graphics card.
Any help would be much appreciated.
Alex
Also, here is the link to my last post,
https://www.sevenforums.com/crashes-d...m-timings.html
Memory management caused by your video driver
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\Windows_NT6_BSOD_jcgriff2\120910-21684-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0300a000 PsLoadedModuleList = 0xfffff800`03247e50
Debug session time: Thu Dec 9 12:40:36.512 2010 (GMT-5)
System Uptime: 0 days 1:01:40.182
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 10E, {24, fffff8a004b3fe50, 200000000000000, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c )
Followup: MachineOwner
---------
3: kd> t
^ No runnable debuggees error in 't'
3: 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: 0000000000000024, The subtype of the bugcheck:
Arg2: fffff8a004b3fe50
Arg3: 0200000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
BUGCHECK_STR: 0x10e_24
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88003ebd22f to fffff8000307a740
STACK_TEXT:
fffff880`03b95188 fffff880`03ebd22f : 00000000`0000010e 00000000`00000024 fffff8a0`04b3fe50 02000000`00000000 : nt!KeBugCheckEx
fffff880`03b95190 fffff880`0421ac64 : fffffa80`0941b000 fffff8a0`04b3fe50 fffffa80`0941b000 fffff8a0`02352000 : watchdog!WdLogEvent5+0x11b
fffff880`03b951e0 fffff880`0420198f : fffffa80`000008a8 fffff8a0`04607120 fffffa80`0941b000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+0x28c
fffff880`03b952c0 fffff880`042ccfb3 : fffff8a0`04cc14e0 00000000`00000000 fffff8a0`02352000 00000000`00000174 : dxgmms1!VidMmDestroyAllocation+0x4f
fffff880`03b952f0 fffff880`042cd2f0 : fffff8a0`04cc14e0 00000000`00000000 00000000`00000001 fffff8a0`02352000 : dxgkrnl!DXGDEVICE::DestroyAllocations+0x5eb
fffff880`03b953e0 fffff880`042cc53d : fffff8a0`02352000 fffff8a0`02352000 fffff8a0`0346f8a0 fffffa80`092dcc20 : dxgkrnl!DXGDEVICE::DestroyResource+0x84
fffff880`03b95410 fffff880`042cc825 : fffffa80`0940caf0 fffff8a0`02352000 00000000`00000001 fffff8a0`04ffc4b0 : dxgkrnl!DXGDEVICE::ProcessTerminationList+0x95
fffff880`03b95460 fffff880`042d032b : fffff8a0`02352000 00000000`c0001f40 fffff8a0`021df840 fffff880`042973af : dxgkrnl!DXGDEVICE::TerminateAllocations+0xb9
fffff880`03b954b0 fffff880`042d9ef5 : fffff8a0`02352000 fffff880`03b955a8 00000000`00000000 fffff8a0`021df840 : dxgkrnl!DXGDEVICE::DestroyAllocation+0x93
fffff880`03b95540 fffff960`00698804 : 00000000`00000000 00000000`00000000 fffff8a0`02204970 fffff8a0`02204970 : dxgkrnl!DxgkCddDestroyAllocation+0x241
fffff880`03b955f0 fffff960`00699a19 : 00000000`00000004 fffff900`c00c04e8 fffff900`c00c0d20 fffff900`c2213940 : cdd!CDDPDEV::DestroyAllocation+0x68
fffff880`03b95660 fffff960`0069b450 : 00000000`00000000 00000000`00000000 fffff900`c00bf020 ffffffff`fffe7960 : cdd!CHwCommandBuffer::FlushDestroyAllocationList+0x3d
fffff880`03b95690 fffff960`006995d5 : fffffa80`092c3b40 fffffa80`092c3b40 00000000`00000000 fffff900`c00bf020 : cdd!CHwCommandBuffer::FlushGdiCommands+0x2a0
fffff880`03b95980 fffff960`00695c6e : ffffffff`fffd74f6 00000000`00000010 00000000`00000001 fffffa80`00000000 : cdd!CDDPDEV::FlushGdiOutput+0x81
fffff880`03b959b0 fffff800`0331ec06 : 00000000`0462bd4b fffffa80`092e5b60 00000000`00000080 fffffa80`0925eb30 : cdd!PresentWorkerThread+0x902
fffff880`03b95d40 fffff800`03058c26 : fffff880`02f64180 fffffa80`092e5b60 fffff880`02f6efc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03b95d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c
fffff880`0421ac64 c78424e000000057f7ffff mov dword ptr [rsp+0E0h],0FFFFF757h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc578
FAILURE_BUCKET_ID: X64_0x10e_24_dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c
BUCKET_ID: X64_0x10e_24_dxgmms1!VIDMM_GLOBAL::DestroyOneAllocation+28c
Followup: MachineOwner
---------
Please re-install the video driver and re-run memtest
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
When it is removed then download and install the fresh copy.
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.