Fresh install, runs fine until the first time i shut down

randyrandy77 · 29 Aug 2012

Hello all,

Ive been troubleshooting an issue with a pc i built 2 years ago. this is a bit of long story.

PC worked flawlessly up until i moved to my new home. It was transported gently and once i powered it up at the new house i got bsods. I didnt touch it for about a year as i had been burnt out on building and tinkering with computers.

So what has been done for the past month of troubleshooting.

I have extensively tested the memory one stick at a time, all clear with memtest latest executable.

the cpu, memory was placed in an identical board on my media pc that has had zero issues. I have used various hard drives to load the OS to, and currently i have the mobo from the media pc in the case and still having the same problem as follows below.

I can start with a fresh valid install of win7 home premium, validate no problem, and update all the drivers and windows etc etc. I mostly play Civ5 and have no issues.

until i turn the pc off overnight then all hell breaks lose when i turn it on the next morning.

Services randomly shut down, stuff randomly stops responding, programs and services crash randomly and at worst i get rolling bsods if im unlucky.

I am pretty good at troubleshooting, my experience is high and this is just passing me by like im a noob with finding the root cause of the bsods after first shutdown of fresh completed install on the pc. I have tried it on different hard drives, 2 different identical boards, hardware checks out fine. In fact the last time i loaded was last friday and the pc stayed on the whole time until last night when i tested my luck and shutdown, went to work, came back and turned it and and its gone to crap in a hand basket. thus i am reaching out to higher powers for assistance as this is really pushing my button.

I appreciate the help on this gents, i followed the posting of sf_diagnostics and here is the zip file. Please let me know if more is needed.

just to give an idea of when it occurred on this latest install, event id 971 is when i shut down last night, event 972 is when i powered up and went to crap at event 1012.

also, i am not overclocking and temps are nice and cool.

thanks
Randy

Arc · 30 Aug 2012

Hello Randy, welcome to SevenForums :)

Your first dump says:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88007d4deea, fffff8800968a558, fffff88009689db0}

Probably caused by : dxgmms1.sys ( dxgmms1!DXGFASTMUTEX::Acquire+1a )

Followup: MachineOwner

It also says that

Code:

1: kd> lmvm dxgmms1
start             end                 module name
fffff880`07d48000 fffff880`07d8e000   dxgmms1    (pdb symbols)          c:\symcache\dxgmms1.pdb\685AF9F266284BE19008B39B739A572B1\dxgmms1.pdb
    Loaded symbol image file: dxgmms1.sys
    Mapped memory image file: c:\symcache\dxgmms1.sys\4A5BC57846000\dxgmms1.sys
    Image path: \SystemRoot\System32\drivers\dxgmms1.sys
    Image name: dxgmms1.sys
    Timestamp:        Tue Jul 14 05:08:32 2009 (4A5BC578)
    CheckSum:         0004AD44
    ImageSize:        00046000
    File version:     6.1.7600.16385
    Product version:  6.1.7600.16385
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     dxgmms1.sys
    OriginalFilename: dxgmms1.sys
    ProductVersion:   6.1.7600.16385
    FileVersion:      6.1.7600.16385 (win7_rtm.090713-1255)
    FileDescription:  DirectX Graphics MMS
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

You should upgrade your DirectX, as I think.

Your second dump says

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88007407da4, fffff88002b11038, fffff88002b10890}

Probably caused by : atikmdag.sys ( atikmdag+151da4 )

Followup: MachineOwner

So it indicates the ATI Graphics driver. But it is apparently up to date.

Code:

2: kd> lmvm atikmdag
start             end                 module name
fffff880`072b6000 fffff880`07cd1000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        Mon Jun 11 22:29:31 2012 (4FD623F3)
    CheckSum:         009CE2BA
    ImageSize:        00A1B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You Remove all the ATI Driver component, install an earlier version that worked good, and during the instalation, install the Display Driver only, not the Catalyst Control Center.

For a check, you may use the onboard graphics for a while, just to check if it is causing by the GFX Card itself.