Solved BSOD when idle, error 0x000000ea

[Tubacca]

Hi,

I've been having problems with the random crash and reboots when the computer is idle. I'm not usually at the computer when it happens so don't see the BSOD but today I was.

The problems have been going on for around 6 months. In that period I have replaced both the RAM (Crucial Ballistix Tactical 8GB) and PSU (XFX XTR 650W).
In the last week or so I have also reformatted the hard drives and done a fresh install of Windows 7.

The problem began at roughly the same time as I installed a new graphics card (Gigabyte R9 285).
I've stress tested the GPU and there have been no errors. I monitor the temps and they are fine. I have never known a crash while in games. I've updated the drivers a number of times over the 6 months with no change.

A crash only seems to occur when the computer is either completely idle or doing very basic tasks such as deleting emails in outlook or most recently at the point of shutting down the pc.

I've attached the DM log.

Any help you can give would be great.

Thanks.

 

[Boozad]

All of three of the dumps on your logs are the same and they all blame your ATI driver.

BugCheck 100000EA, {fffffa800672f310, 0, 0, 0}

[COLOR=Red]*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys[/COLOR]

3: kd> lmvm atikmdag
start             end                 module name
fffff880`0f26e000 fffff880`10778000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR=Red]Wed Jul 29 03:46:46 2015[/COLOR] (55B83E96)
    CheckSum:         014AD73A
    ImageSize:        0150A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download the latest driver from here and save it to your desktop. Download DDU and follow http://www.sevenforums.com/tutorials/367109-display-driver-uninstaller-how-use.html to remove all traces of your current driver. Reboot and install the downloaded driver.

Can you also run all rounds of Windows Updates until no more are offered.

 

[Tubacca]

Thanks for the quick reply.

I've done what you suggested. Hopefully it will fix it but it seems strange if it does as it was already a fresh install of windows and a fresh install of the latest drivers.

I'll keep you updated!

 

[Tubacca]

After a few days with no problems I was hopeful but I woke up to find that it had happened again this morning and I left my computer on while I went out for an hour and came back to find it had happened a second time.

I've uploaded the new DM log.

Regarding the Windows Update - I seem to have a separate problem there. Since the fresh install it's done hundreds of updates but for some reason these 5 keep failing. I've tried running SURT but that hasn't helped. If I don't get it sorted soon I'll make a post in the Updates sub-forum.

Thanks

 

[Boozad]

I can't read the whole dump (Microsoft's issue with symbols) but the ATI driver is showing once again.

BugCheck 100000EA, {fffffa800b928060, 0, 0, 0}

[COLOR=Red]*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys

[/COLOR]3: kd> lmvm atikmdag
start             end                 module name
fffff880`0f25f000 fffff880`10769000   atikmdag T (no symbols)           
    Loaded symbol image file: atikmdag.sys
    Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
    Image name: atikmdag.sys
    Timestamp:        [COLOR=Red]Tue Aug 04 04:28:52 2015[/COLOR] (55C03174)
    CheckSum:         014A6ED0
    ImageSize:        0150A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

I'm wondering if this is a problem with the card itself, can you try stress testing it please.

:ar: Run Furmark to stress test your GPU. http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

   Note

Run Furmark for around 30 minutes.

   Warning

Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them, if the temperature continues to rise steadily once it has reached 80°C be prepared to stop the test so as to not damage your GPU.

 

[Tubacca]

I ran Furmark for 32 minutes this morning. I was using the computer for other things at the same time. I didn't see any artifacts and the temperature reached a maximum of 75 celsius.
I've never had a crash or problem while gaming or video editing.

Having said that - I didn't have any problems prior to this graphics card.

It hasn't happened again since the last post. I don't know if it's just coincidence but from what I could see on the event viewer the crashes have happened at some point after the computer has woken from sleep.

Thanks for all your continued help!

 

[Tubacca]

Just come back from a meeting to find my computer shut down.

It looks like the same error again.

I've attached the DM log.

Thanks in advance for any help.

 

[Boozad]

There aren't any new dumps in the last logs unfortunately so there's nothing new to analyse. What I'd recommend is downloading the latest driver then uninstall your card via Device Manager then shut down and physically remove it from the PC. Reseat it making sure it's fully seated and make sure the power connections are made securely. Then reboot and install the latest driver you downloaded.

 

[Tubacca]

Hi Boozad,

Thanks for all your help. Just to let you know that it seems to be all sorted. I ended up seating the GPU in the second PCI slot. At the same time I completed a windows start up repair and then once all booted up did a fresh install of the drivers again.
I'm not 100% sure which of those 3 things in the end sorted it but I haven't had any problems since!
Great to have everything working and that it wasn't a faulty GPU which I was beginning to fear.

Thanks again for all your help!

 

[Boozad]

Great to hear you got things sorted mate. If you really want to pinpoint the problem you could always revert to previous PCI slot and see if the problem presents itself again, although I understand you'd probably want to keep a working system as it is after all the hassle you had!

Thanks for letting us know you got there.