Comp crashes now from BSOD after a Display Driver has stopped responding error that keeps happening!!!!

[Gares]

Ok this is pissing me off now cause I really don't know what is going on.

I haven't changed anything since I started boxing and every once in awhile my comp will just freeze and go black and then flash my screen 5-6 times with the Display Driver has stopped responding....then it drops me to BSOD.

System setup:

Windows Vista Home Ultimate 64 SP 1
4 Gig of RAM
ATI Radeon 4850

I have the latest ATI Catalyst drivers dated August 2008. I also disabled the Catalist AI in it because it was mentioned to do it somewhere.

I checked the temperature of everything on my comp that matters (Vid Card, RAM, HD's) and they are all well below the max.

I honestly don't know what the BSOD of death actually says cause I only see if for like 1-2 seconds before a reset (I really should disable that)

My game/connections on some slaves sometimes are laggy as hell. 4 screens have green conn and 1 not.

It still seems like my clones lag behind for no apparent reason and I don't know why (I get this is solo play as well)

I HAVE NO ADDON's installed!


Anyone have any suggestions that I should do? Maybe turn my graphics down in the game on my main screen and/or slaves?

I honestly really don't know what to do....

I seen a macro somewhere about turning down the graphics on my slave screens. Maybe I should go use that? Would it really make that big of a difference?

Maybe I should get 8 gigs of RAM instead of 4? But that really won't solve my Graphics card crashing problem.

Anyone help? Suggestions?

[keyclone]

well, sounds like you're beyond the basics and you've checked your drivers... so i'll go with hardware...

check your power supply... is it enough?
next, i'd guess the memory is hosed. got any way to check it? how about just swapping it out?
could your motherboard be hosed? i had a 750i SLI FTW that was whacked... changed it out and all was better (i was getting hard system lockups)

let me know if that helps.

Rob

[Gares]

well, sounds like you're beyond the basics and you've checked your drivers... so i'll go with hardware...

check your power supply... is it enough?
next, i'd guess the memory is hosed. got any way to check it? how about just swapping it out?
could your motherboard be hosed? i had a 750i SLI FTW that was whacked... changed it out and all was better (i was getting hard system lockups)

let me know if that helps.

Rob

Ok so my power supply is 700w which is more then enough.

As for the memory I could swap it out, but I don't have any extra laying around (or the money to buy some extra ATM) so swapping it out is probably out of the question. It doesn't really lead me to believe that its that because it only happens (BSOD) so far when I am boxing and in nothing else at all. I haven't been solo playing much (Different WOW folder and HD with addons) but the only problem I have with that is choppy/soft lag gameplay that I get even when I am boxing which is starting to annoy me.

Again I don't think my MB is hose cause I only get this problem with WOW and boxing so I swear its gotta be something mixed with Graphics Pressure against my card or something along those lines. I know I am not using all my RAM up (Around 75%) as my indicator shows my RAM and CPU usage when I start doing stuff...

Very puzzled and annoyed..

[Freddie]

I honestly don't know what the BSOD of death actually says cause I only see if for like 1-2 seconds before a reset (I really should disable that)

This is a good place to start -- with the info that Windows collects to help figure out the cause of crashes. Depending on how your options are set, Windows collects a lot of it. To find it:

Go to Start Search, enter "wercon", then "View Problem History."

Microsoft provides on-line assistance for analyzing crashes. For XP this is at:

http://oca.microsoft.com/en/Welcome.aspx

I'm not sure how it's been rearranged for Vista. It may be all automated and built into Wercon now, I don't know.

Edit: If you can find reports for several instances of the same type of crash, are the memory/register numbers the same each time? If so I think it's probably a software problem, not a hardware problem.

[Gares]

I don't know what I am looking for or should copy for you to look at?

I see alot of errors but I don't know specifically what I should look at/for?

This is the Video Error I get listed 6 times before my comp shuts down..

Product
Windows

Problem
Video hardware error

Date
14/09/2008 9:29 PM

Status
Not Reported

Description
A problem with your video hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 4105

Files that help describe the problem
WD-20080914-2128.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 117
BCP1: FFFFFA80042D00D0
BCP2: FFFFFA6002836390
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1

Then this is the actual shutdown problem:

Product
Windows

Problem
Shut down unexpectedly

Date
14/09/2008 9:31 PM

Status
Report Sent

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 4105

Files that help describe the problem (some files may no longer be available)
Mini091408-01.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 116
BCP1: FFFFFA8006FFF4E0
BCP2: FFFFFA6002836390
BCP3: 0000000000000000
BCP4: 000000000000000D
OS Version: 6_0_6001
Service Pack: 1_0
Product: 768_1
Server information: b405d52d-2a67-4893-b9de-0df582da84c2


I have this error listed for each time my comp has looped with a display driver stopped responding and then shutdown problem.

[bugilt]

Did you take a temp reading while the computer was peak stress?

Pull out the video card and check it out. Blow it off with some compressed air (Making sure to hold the fan still to not over spin the bearing.)

[Yamio]

"Description
A problem with your video hardware caused Windows to stop working correctly."


I wouldn't be trusting that card now. Blow it off, take care of the fan, but I'm thinking that thing is on it's last leg.

[Freddie]

The first thing I'd notice is the BC code ("bug check code") for the initial problem, 117. We can look that up on Microsoft's website:

http://msdn.microsoft.com/en-us/library/aa469203.aspx

That page explains, "The VIDEO_TDR_TIMEOUT_DETECTED bug check has a value of 0x00000117. This indicates that the display driver failed to respond in a timely fashion." In other words, the driver froze. In a case like this, the operating system tries to re-initialize the driver. Which brings us to the second BC code, 116:

http://msdn.microsoft.com/en-us/library/aa469184.aspx

That page explains, "The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed."

So the sequence of events seems to be, the driver froze and the OS tried to restart it. The OS couldn't restart it, so it shut down the machine.

Unfortunately we don't know why the video driver froze. (The dump files contain information that could help explain this, but it may be meaningful only to the people who wrote the driver.) One possibility is a bug in the driver, so you could try an earlier driver.

Another possibility, like other folks are saying, is that the video card malfunctioned due to heat or some other reason. In a case like that the driver should handle the problem gracefully and not lock up, but maybe the driver's error handling is incomplete for this particular case.

Another thing you can do is check to see whether Microsoft has any advice for this problem. You probably did that already -- I think you have to push a button on the WER panel. I'm on an XP machine atm so I can't look.

Anothing thing would be to send the WER info to ATI customer support.

If you want to send me the set of files for 117 I'll look at them but probably I won't be able to say anything useful. My email is freddie at hotkeynet.com.

[aNiMaL]

The atikmdag error probably.

Note: most of this info is from ~april but I suppose it's still unchanged.

It is a known error for several cards in any version of Vista64.

Either turn of the secondary screen or turn of the aero theme worked for me.


I got introduced to it when AoC was launched and I installed my new computer with Ultimate Vista 64.
It's not related to anything you're doing, some have reported their system crashed before they could even pass the windows login.
Vista tries to recover from the crashed driver, sometimes manages to do so even,
but most of the time gets into a loop of recovering and crashing again, which gives you your BSOD in the end.

The error has been around since vista 64 launched and till now there hasn't been a decent solution which works for everyone.
Some fixed it by setting the gpu fan to a fixed 50% or more,
some fixed it by adding more memory,
and a lot of other things i've tried before turning off the aero theme..
(After all, it's a "new" os, I wanted it's new look,
so I tried all the other options I could find before turning off the aero theme.)

Not only ati cards have this trouble btw,
many reports have been around of people with nivida cards with the same troubles,
they just have "nvlddmkm" in stead of "atikmdag" in the error.

[Freddie]

The atikmdag error probably.

I'm a little skeptical there's any single "atikmdag error," even though many people describe it that way. I think it's more likely that there are many different bugs and incompatibilities that make atikmdag lock up, causing this same series of error messages.

I just googled "aktikmdag bsod" and noticed that people report many different ways they fixed "the" problem. On some machines they fixed "it" by adjusting their BIOS. Other people fixed it by replacing RAM. Other people fixed it by cleaning out their drivers and installing from scratch. Etc.

Bad RAM ... incompatible BIOS settings ... improperly installed drivers ... it goes on and on. It's a pretty good rule of thumb that when the solutions are different, the bugs are probably also different.

For example:

http://www.repairyourpcnow.com/resou...responding.php