Display driver stopped responding

I have read that nVidia has the same problem as this, and I have an ATI
card.

The whole message reads,
Display driver stopped responding and has recovered
Display driver atikmdag stopped responding and has successfully
recovered.

This happens about ever 15 to 30 seconds when I am watching Live TV in MCE.
And the problem started about 2 driver builds ago. So, today I downloaded
and installed ATI's Catalyst 7.7 drivers for Vista, and the problem
persists. I even did a clean install and immeaditely installed the 7.7
drivers, and the problem remains.

Since this bug is present with both nVidia and ATI cards, then the problem
would appear to be Microsoft's fault. I hope that there is not a major bug
with the WDDM design? If so, then Vista is in trouble. ;o(


Wayne Wastier

In Control Panel > Problem Reports and Solutions, right click on a problem and
select view details. What does it show? You can copy to clipboard and past in a
reply.

--
I Bleed Blue and Gold
GO BEARS!


"Wayne Wastier" <hww1955@msn.com> wrote in message
news:e7fFeT9yHHA.3696@TK2MSFTNGP03.phx.gbl...
>I have read that nVidia has the same problem as this, and I have an ATI card.
>
> The whole message reads,
> Display driver stopped responding and has recovered
> Display driver atikmdag stopped responding and has successfully
> recovered.
>
> This happens about ever 15 to 30 seconds when I am watching Live TV in MCE.
> And the problem started about 2 driver builds ago. So, today I downloaded and
> installed ATI's Catalyst 7.7 drivers for Vista, and the problem persists. I
> even did a clean install and immeaditely installed the 7.7 drivers, and the
> problem remains.
>
> Since this bug is present with both nVidia and ATI cards, then the problem
> would appear to be Microsoft's fault. I hope that there is not a major bug
> with the WDDM design? If so, then Vista is in trouble. ;o(
>
>
> Wayne Wastier

"Cal Bear '66" <xxx@xxx.org> wrote in message
news:A3D82BAA-DFD2-4FB6-BB61-E22E49F779C7@microsoft.com...
> In Control Panel > Problem Reports and Solutions, right click on a problem
> and select view details. What does it show? You can copy to clipboard and
> past in a reply.
>
> --
> I Bleed Blue and Gold
> GO BEARS!
>
>

Product
Windows

Problem
Video hardware error

Date
7/21/2007 2:27 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.6000.2.0.0.768.3
Locale ID: 1033

Files that help describe the problem
WD-20070721-1427.dmp
sysdata.xml
Version.txt

Extra information about the problem
BCCode: 117
BCP1: 844A8E90
BCP2: 8A919A44
BCP3: 00000000
BCP4: 00000000
OS Version: 6_0_6000
Service Pack: 0_0
Product: 768_1

P.S. I reported it contrary to what the info says. :)

What is the bucket number?

--
I Bleed Blue and Gold
GO BEARS!


"Wayne Wastier" <hww1955@msn.com> wrote in message
news:eI$3K59yHHA.1100@TK2MSFTNGP06.phx.gbl...
>
> "Cal Bear '66" <xxx@xxx.org> wrote in message
> news:A3D82BAA-DFD2-4FB6-BB61-E22E49F779C7@microsoft.com...
>> In Control Panel > Problem Reports and Solutions, right click on a problem
>> and select view details. What does it show? You can copy to clipboard and
>> past in a reply.
>>
>> --
>> I Bleed Blue and Gold
>> GO BEARS!
>>
>>
>
> Product
> Windows
>
> Problem
> Video hardware error
>
> Date
> 7/21/2007 2:27 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.6000.2.0.0.768.3
> Locale ID: 1033
>
> Files that help describe the problem
> WD-20070721-1427.dmp
> sysdata.xml
> Version.txt
>
> Extra information about the problem
> BCCode: 117
> BCP1: 844A8E90
> BCP2: 8A919A44
> BCP3: 00000000
> BCP4: 00000000
> OS Version: 6_0_6000
> Service Pack: 0_0
> Product: 768_1
>

"Cal Bear '66" <xxx@xxx.org> wrote in message
news:47F8474D-858A-453C-A17F-340F676E3601@microsoft.com...
> What is the bucket number?
>
> --

There doesn't seem to be one.

"Wayne Wastier" <hww1955@msn.com> wrote in message
news:%23hd%23tE%23yHHA.3940@TK2MSFTNGP05.phx.gbl.. .
>
> "Cal Bear '66" <xxx@xxx.org> wrote in message
> news:47F8474D-858A-453C-A17F-340F676E3601@microsoft.com...
>> What is the bucket number?
>>
>> --
>
> There doesn't seem to be one.

Will look back here later as I have to watch TV in XP right now, and I hate
to kep switching back and forth as I keep missing my show.

Wayne and All,

You have what is called a VPU Recover error. This is an ATI technology
adopted by Microsoft for Vista. The technology keeps your computer from
crashing when you have a conflict, but gives you the VPU Recover error
message instead (of crashing). This has been around for a number of years,
and it can be difficult identifying the problem, unless you're lucky. Here
is a guide about troubleshooting the VPU Recover problem. The guide
addresses the issue as it was written before Vista came to live with us, but
nothing has changed. The comments apply to Vista as well. Take a look:

http://www.foxpop.com/imre/2005/vpur...purecover.html

There is a lot of information on the Internet about this problem. I even
had it not long ago when using WinXP. It took me a long time to figure it
out.
--
freddy


"Wayne Wastier" wrote:

> P.S. I reported it contrary to what the info says. :)
>

"freddy" <fkirschen@tidalwave.net> wrote in message
news:5C476FA3-00E4-4A80-9F5C-E3845291F28C@microsoft.com...
> Wayne and All,
>
> You have what is called a VPU Recover error. This is an ATI technology
> adopted by Microsoft for Vista. The technology keeps your computer from
> crashing when you have a conflict, but gives you the VPU Recover error
> message instead (of crashing). This has been around for a number of
> years,
> and it can be difficult identifying the problem, unless you're lucky.
> Here
> is a guide about troubleshooting the VPU Recover problem. The guide
> addresses the issue as it was written before Vista came to live with us,
> but
> nothing has changed. The comments apply to Vista as well. Take a look:
>
> http://www.foxpop.com/imre/2005/vpur...purecover.html
>
> There is a lot of information on the Internet about this problem. I even
> had it not long ago when using WinXP. It took me a long time to figure it
> out.
> --
> freddy
>
>

Sorry for the late response.

Thanks Freddy. I wish it were that simple. There is no VPU recover option
that I can see in the latest ATI Vista drivers.

Thanks for your response anyway.


Wayne

Wayne,

The VPU Recover is not an option as it's now built into Vista. What you
have IS the VPU Recover option. It's an error, and your visual processing
has been recovered, rather than your computer having crashed.
--
freddy


"Wayne Wastier" wrote:

>
> "freddy" <fkirschen@tidalwave.net> wrote in message
> news:5C476FA3-00E4-4A80-9F5C-E3845291F28C@microsoft.com...
> > Wayne and All,
> >
> > You have what is called a VPU Recover error. This is an ATI technology
> > adopted by Microsoft for Vista. The technology keeps your computer from
> > crashing when you have a conflict, but gives you the VPU Recover error
> > message instead (of crashing). This has been around for a number of
> > years,
> > and it can be difficult identifying the problem, unless you're lucky.
> > Here
> > is a guide about troubleshooting the VPU Recover problem. The guide
> > addresses the issue as it was written before Vista came to live with us,
> > but
> > nothing has changed. The comments apply to Vista as well. Take a look:
> >
> > http://www.foxpop.com/imre/2005/vpur...purecover.html
> >
> > There is a lot of information on the Internet about this problem. I even
> > had it not long ago when using WinXP. It took me a long time to figure it
> > out.
> > --
> > freddy
> >
> >
>
> Sorry for the late response.
>
> Thanks Freddy. I wish it were that simple. There is no VPU recover option
> that I can see in the latest ATI Vista drivers.
>
> Thanks for your response anyway.
>
>
> Wayne
>
>

"freddy" <fkirschen@tidalwave.net> wrote in message
news:1D3CEF9F-0156-4031-91DD-C0ACAA7F66A4@microsoft.com...
> Wayne,
>
> The VPU Recover is not an option as it's now built into Vista. What you
> have IS the VPU Recover option. It's an error, and your visual processing
> has been recovered, rather than your computer having crashed.
> --
> freddy
>
>

It shouldn't do this as I don't have my graphic card over-clocked or my cpu.
My CPU is running at 38c and my mobo at 40c. And, this only happens with
the last 3 drivers from ATI. Do a search for "Display driver stopped
responding and has recovered" and you will see the problem also exists with
the nVidia branded graphic cards.


Wayne

Wayne,

I'm well aware that this condition shouldn't happen and that it happens with
cards other than those by ATI. Overclocking and heat are only two of the
possible sources causing this condition. No one has said this condition is
exclusive to ATI cards. From where did you get that idea?

You should reread what has been posted here, and also take a look at the
reference for troubleshooting. That guide was written with ATI cards in
mind, because ATI developed the technology for VPU Recover before Vista was
developed. Microsoft incorporated that technology in Vista, so whatever card
you use with Vista can have the VPU Recover message. That guide tells you
some of the other (besides overclocking and heat) causes for the VPU Recover
condition.
--
freddy


"Wayne Wastier" wrote:

>
> "freddy" <fkirschen@tidalwave.net> wrote in message
> news:1D3CEF9F-0156-4031-91DD-C0ACAA7F66A4@microsoft.com...
> > Wayne,
> >
> > The VPU Recover is not an option as it's now built into Vista. What you
> > have IS the VPU Recover option. It's an error, and your visual processing
> > has been recovered, rather than your computer having crashed.
> > --
> > freddy
> >
> >
>
> It shouldn't do this as I don't have my graphic card over-clocked or my cpu.
> My CPU is running at 38c and my mobo at 40c. And, this only happens with
> the last 3 drivers from ATI. Do a search for "Display driver stopped
> responding and has recovered" and you will see the problem also exists with
> the nVidia branded graphic cards.
>
>
> Wayne
>
>
>

"freddy" <fkirschen@tidalwave.net> wrote in message
news:6D12C4DA-5142-41E5-A101-6DCBA63D1EB6@microsoft.com...
> Wayne,
>
> I'm well aware that this condition shouldn't happen and that it happens
> with
> cards other than those by ATI. Overclocking and heat are only two of the
> possible sources causing this condition. No one has said this condition is
> exclusive to ATI cards. From where did you get that idea?
>
> You should reread what has been posted here, and also take a look at the
> reference for troubleshooting. That guide was written with ATI cards in
> mind, because ATI developed the technology for VPU Recover before Vista
> was
> developed. Microsoft incorporated that technology in Vista, so whatever
> card
> you use with Vista can have the VPU Recover message. That guide tells you
> some of the other (besides overclocking and heat) causes for the VPU
> Recover
> condition.
> --
> freddy
>
>

Freddy, you are mistaken. This is not caused by VPU. Please get your facts
straight.

Now I see why you have been called a troll by many on this newsgroup.


Wayne

Wayne,

These are your words from your original post:

"The whole message reads,
Display driver stopped responding and has recovered
Display driver atikmdag stopped responding and has successfully
recovered."

So, what is it?

--
freddy


"Wayne Wastier" wrote:

>
> "freddy" <fkirschen@tidalwave.net> wrote in message
> news:6D12C4DA-5142-41E5-A101-6DCBA63D1EB6@microsoft.com...
> > Wayne,
> >
> > I'm well aware that this condition shouldn't happen and that it happens
> > with
> > cards other than those by ATI. Overclocking and heat are only two of the
> > possible sources causing this condition. No one has said this condition is
> > exclusive to ATI cards. From where did you get that idea?
> >
> > You should reread what has been posted here, and also take a look at the
> > reference for troubleshooting. That guide was written with ATI cards in
> > mind, because ATI developed the technology for VPU Recover before Vista
> > was
> > developed. Microsoft incorporated that technology in Vista, so whatever
> > card
> > you use with Vista can have the VPU Recover message. That guide tells you
> > some of the other (besides overclocking and heat) causes for the VPU
> > Recover
> > condition.
> > --
> > freddy
> >
> >
>
> Freddy, you are mistaken. This is not caused by VPU. Please get your facts
> straight.
>
> Now I see why you have been called a troll by many on this newsgroup.
>
>
> Wayne
>
>
>

"freddy" <fkirschen@tidalwave.net> wrote in message
news:318880B6-F198-4049-83FE-21D54487F87B@microsoft.com...
> Wayne,
>
> These are your words from your original post:
>
> "The whole message reads,
> Display driver stopped responding and has recovered
> Display driver atikmdag stopped responding and has successfully
> recovered."
>
> So, what is it?
>
> --
> freddy
>

It is a problem with the WDDM driver specification.