BSOD (Again)

[alderosa]

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,

http://www.sevenforums.com/crashes-debugging/129605-bsod-ram-timings.html

 

[zigzag3143]

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,

http://www.sevenforums.com/crashes-debugging/129605-bsod-ram-timings.html

Memory management caused by your video driver

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.

 

[alderosa]

Thanks for taking a look for me Zigzag3143. I was coming to the conclusion that it was drivers or RAM after reading other posts but didn't know which. I've reinstalled the graphics drivers and left out the Catalyst Control Centre and other bundled 'goodies' that generally are a waste of space. Hopefully this will resolve the issue. I'm also running Memtest86+ as I type (so far so good!).

I had a few concerns about my RAM and have also been fiddling with the timings/voltages. I have 4x A-DATA AX3U1333GB2G8-2G and have read in a few places that they are pretty fussy about the voltages, etc that are used with them. When left on auto my Mobo seems to change the stable settings on each boot so I manually set them to the recommended and upped the voltage. Hopefully this helps too.

Again, thanks for having a look at this for me. I hope this sorts the problem!

Alex

This is the RAM I have btw (A-Data website is rubbish);
Newegg.com - A-DATA Gaming Series 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333G (PC3 10666) Desktop Memory Model AX3U1333GB2G8-2G

 

[alderosa]

One error showed up in Memtest86+ when all sticks were in. I'm currently testing one stick at a time and I'm on the first stick. Could be a while...

 

[alderosa]

Just found out I have defective RAM. 2 of the sticks were ok. One of the others wasn't Windows Memory Test didn't pick it up when I first put the PC together but Memtest86+ did. I guess this was actually the problem and not the graphics drivers?

 

[alderosa]

Scratch that. I tested all the sticks with Memtest86+ for 6 passes and found 1 defective. I thne used one of the good sticks to test all the motherboard slots out. All of these checked out fine too. I tried to run with 2 good sticks in the Mobo and the system crashed into BSOD almost straight after I booted (I got into Windows first). I've attached the dump file here... This is really starting to annoy me. The other dump files were attached previously. I am using the manufacturer recommended settings for my RAM, not the Mobo auto ones.

 

[alderosa]

So system won't shut down without BSOD now. It's got worse with the 2 RAM sticks instead of 4. Could this issue be related to something else? I can send more .dmp files if people want.

 

[zigzag3143]

So system won't shut down without BSOD now. It's got worse with the 2 RAM sticks instead of 4. Could this issue be related to something else? I can send more .dmp files if people want.

Dont forget as I told you on the other site. SPTD.sys needs to be removed.

Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads

You can use MagicDisc as an alternative.

Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

 

[alderosa]

Are you sure that this is the problem? Could all this be a symptom of RAM problems or other hardware isuues? Should I update my BIOS?

 

[CarlTR6]

Is he sure sptd.sys is the problem? No. Is sptd.sys a known problem? Yes. In troubleshooting you have to eliminate all possible causes of crashes. This includes removing sptd.sys and updating out of date drivers. Troubleshooting is a process of elimination. I recommend you follow Ken's expert advice.

 

[alderosa]

Sorry, I didn't mean to offend, I just had read about something else that might be the cause and wanted some advice. I'll definitely by removing these drivers too.

 

[CarlTR6]

No offense taken at all. I just wanted to explain why we do things the way we do in the troubleshooting process.

 

[alderosa]

I'll let you know when I've made the changes. The problem is the BSODs are random so it might be a while before I know if it's solved the issue.

 

[alderosa]

Just had another BSOD. I think it's the graphics drivers. I found a program called BlueScreenView and looked at some stuff. Seems the drivers below were the cause. Am I correct in thinking that they are graphics related? They're the same as some of the earlier ones in the other dump files I posted previously.

Drivers that caused problem according to BlueScreenView;
atikmpag.sys+6f94
dxgkrnl.sys+5cef8
dxgmms1.sys+ff07

I've attached a new set of files, this has all my dump files so far. The latest crash (that I just had) is the one occurring on 12/10/2010. Note that I was just about to remove the driver you told me to remove before when it crashed.

 

[alderosa]

Ok guys, sptd.sys is gone. As is my old BIOS. I have updated to version F7 and changed some of the RAM settings too. I have heard that the ADATA gaming series RAM I have is particularly power hungry so upped the voltage and reduced the timings to mobo recommended 9-9-9-24. We'll see how it goes...

 

[CarlTR6]

Thank you very much for the update on what you have done so far. Good job.

Just had another BSOD. I think it's the graphics drivers. I found a program called BlueScreenView and looked at some stuff. Seems the drivers below were the cause. Am I correct in thinking that they are graphics related? They're the same as some of the earlier ones in the other dump files I posted previously.

Drivers that caused problem according to BlueScreenView;
atikmpag.sys+6f94
dxgkrnl.sys+5cef8
dxgmms1.sys+ff07

I've attached a new set of files, this has all my dump files so far. The latest crash (that I just had) is the one occurring on 12/10/2010. Note that I was just about to remove the driver you told me to remove before when it crashed.

atikmpag.sys - ATI Video driver (remove the Catalyst Control Center and only install the Display Driver)Global Provider of Innovative Graphics, Processors and Media Solutions | AMD. This is a video driver.

dxgkrnl.sys - A Windows system Direct X driver and very unlikely to cause a crash.

dxgmms1.sys - A Windows system Direct X driver and very unlikely to cause a crash.

CCC is known to cause problems on some systems. I also suggest you check the temps of your video card. Overheating can also cause BSOD's. Other drivers can cause conflicts the interfere with the video system.

You actually have three dumps dated 12/10/10. All are different error codes and all blame different drivers. One of them is a VIDEO_TDR_FAILURE error. However, since you updated your BIOS, uninstalled sptd.sys and changed RAM settings, these dumps files are moot.

Ok guys, sptd.sys is gone. As is my old BIOS. I have updated to version F7 and changed some of the RAM settings too. I have heard that the ADATA gaming series RAM I have is particularly power hungry so upped the voltage and reduced the timings to mobo recommended 9-9-9-24. We'll see how it goes...

I hope your news will be good. Keep us posted. If you get another BSOD, upload it, and we will tackle it again.

 

[alderosa]

Thanks for taking a look at the files for me Carl. I had already looked at the video card drivers and replaced them (without the extra fluff like the CCC) yesterday I think? Ken found these to be a problem in one of the earlier dump files he examined. Does this mean the issue might be a problem elsewhere if I've already tried to sort this out before?

I've been meaning to update my BIOS for a while, I didn't realise it would render the files I have previously uploaded obsolete though. Sorry about this . If the past few days are anything to go by, I should get a BSOD either later tonight or tomorrow if something's still wrong. I'll keep you posted!

 

[CarlTR6]

You are welcome and thank you for the update. As far as that dump goes, we will just have to see how your system does.

There is certainly nothing to be sorry about; you updated your system and that is a good thing. It does change the hardware aspect and makes the previous dumps obsolete or at least partially obsolete - just like if you installed a new video card or uninstalled an obsolete program. I hope you do not get a BSOD later tonight. I hope you have solved your problem. But if you do get one, upload the dump and we will be here to look at it.

 

[alderosa]

Thanks Carl. I'll let you know how I get on. Your help is much appreciated. Fingers crossed!

 

[alderosa]

So i had another BSOD on my first reboot this morning. I had to revert to an earlier system restore point in order to get through the start up. I made sure to remove the files you suggested though (like the sptd.sys again) when I finally got back into windows. It said some stuff about startup registry needing repair and tried to check the disk for errors before loading the OS. I've attached the dump file.