Vista Tutorial - aero fatal error - "3" rating troubleshooting help?

I've seen some posts that are making me think there's some amount of voodoo
to this but... whenever I reboot, or manually run dwm.exe, aero kicks on for
several seconds, locks for about 5 seconds, and then disables.

First my specs:

ati radeo x1900xtx (5.9)
300 gig Samsung SATA (150GB partition) (3.8)
AMD 62x2 4200 (5.5)
2GB dual channel DDR ram (4.5)
Asus A8r32-MVP Deluxe motherboard
(Gaming Graphics 512MB)(5.9)
----

I have tried both the default drivers and the ati betas. I have also
attempted and had the same problem with the public beta 2 / 5456 / and the
latest build (the latest build just locks completely where the other builds
crash aero, so I'm sticking with 5456 to troubleshoot)

----

I've checked out the event viewer and gotten the following two error
messages stamped with the crash:

Application Error Event ID: 1000

Log Name: Application
Source: Application Error
Date: 7/29/2006 3:22:31 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: KHIDR-PC
Description:
Faulting application dwm.exe, version 6.0.5456.5, time stamp 0x4498b6da,
faulting module ntdll.dll, version 6.0.5456.5, time stamp 0x4498c894,
exception code 0x80000003, fault offset 0x00028ee0, process id 0x29c,
application start time 0x01c6b3445210ecda.

AND

Log Name: Application
Source: Desktop Window Manager
Date: 7/29/2006 3:22:31 PM
Event ID: 9020
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: KHIDR-PC
Description:
The Desktop Window Manager has encountered a fatal error (0x80000003)

--------

I've run sandra on my system, and everything is in top shape from that, with
no oddness on my xp partition. vista is also running reliably without any
other crashes once aero dies.

Figured this would be the place to troubleshoot what's going on, so any
ideas?

Thanks in advance, sorry if this was too much, or the wrong info to share.

Figured I'd bump this if anyone else was having this problem, it was the bios
on the A8r32. I updated to the latest version, and now, my windows
performance rating is 4.5 and aero works like a charm.

hope this helps someone.

"Khidr" wrote:

> I've seen some posts that are making me think there's some amount of voodoo
> to this but... whenever I reboot, or manually run dwm.exe, aero kicks on for
> several seconds, locks for about 5 seconds, and then disables.
>
> First my specs:
>
> ati radeo x1900xtx (5.9)
> 300 gig Samsung SATA (150GB partition) (3.8)
> AMD 62x2 4200 (5.5)
> 2GB dual channel DDR ram (4.5)
> Asus A8r32-MVP Deluxe motherboard
> (Gaming Graphics 512MB)(5.9)
> ----
>
> I have tried both the default drivers and the ati betas. I have also
> attempted and had the same problem with the public beta 2 / 5456 / and the
> latest build (the latest build just locks completely where the other builds
> crash aero, so I'm sticking with 5456 to troubleshoot)
>
> ----
>
> I've checked out the event viewer and gotten the following two error
> messages stamped with the crash:
>
> Application Error Event ID: 1000
>
> Log Name: Application
> Source: Application Error
> Date: 7/29/2006 3:22:31 PM
> Event ID: 1000
> Task Category: (100)
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: KHIDR-PC
> Description:
> Faulting application dwm.exe, version 6.0.5456.5, time stamp 0x4498b6da,
> faulting module ntdll.dll, version 6.0.5456.5, time stamp 0x4498c894,
> exception code 0x80000003, fault offset 0x00028ee0, process id 0x29c,
> application start time 0x01c6b3445210ecda.
>
> AND
>
> Log Name: Application
> Source: Desktop Window Manager
> Date: 7/29/2006 3:22:31 PM
> Event ID: 9020
> Task Category: None
> Level: Error
> Keywords: Classic
> User: N/A
> Computer: KHIDR-PC
> Description:
> The Desktop Window Manager has encountered a fatal error (0x80000003)
>
> --------
>
> I've run sandra on my system, and everything is in top shape from that, with
> no oddness on my xp partition. vista is also running reliably without any
> other crashes once aero dies.
>
> Figured this would be the place to troubleshoot what's going on, so any
> ideas?
>
> Thanks in advance, sorry if this was too much, or the wrong info to share.
>
>
>
>