An oddity with my Windows 3D screensavers

[Neroon]

I am not sure when this started, but currently the 3D screensavers that come with Windows XP are inoperative on my machine. These are the 3D Pipes, 3D Flowerbox, 3D Text, etc. They are listed in the screensavers from which yu can select. However, when I do select one, the little representation says "Preview unavailable". If I click on "settings" for that saver, the associated settings panel comes up fine. However, if I try to preview it or actually execute it.... the screen goes black and in some cases requires a reset to get back.

I'm running with DirectX 9, and I keep applying the appropriate Windows updates. As far as I can tell, everything else is working fine on the system, with no trouble anywhere. So far I have not found anything in any forum that describes this particular problem. Mind you, it's not really a problem but more a mere annoyance. Still, it bugs me and makes me wonder if there isn't anything else that could become a problem.

Suggestions?

 

[Noname Given]

What video card/on-board chipset are you using and what resolution are you running your drsktop at?

 

[farmkid]

Are you having any other 3D video-related issues? Do 3D games play okay?

 

[Neroon]

I use ATI All-in-Wonder 9600, at 1024 x 768. So far no other problems that I can see with 3D imaging. Do you have a suggestion on something to try, so I can verify that there aren't any other 3D problems?

 

[Noname Given]

I use ATI All-in-Wonder 9600, at 1024 x 768. So far no other problems that I can see with 3D imaging. Do you have a suggestion on something to try, so I can verify that there aren't any other 3D problems?

You might want to run 'DxDiag' and do the video subsystem tests and see what results you get.

 

[farmkid]

For a simple test of the hardware and DirectX, type "dxdiag" into the run command box. Go to the display tab and run the Direct3D test.

The reason I asked if there were any other 3D problems is to see if it is just an issue with the screensaver or if it is more global--i.e. DirectX or hardware, etc. My laptop developed a fault in the GPU where it would run fine with the generic Windows VGA drivers, but it would not load the ATI drivers to enable more than basic functionality. Apparently, it developed a problem in a part of the chip responsible for those features enabled by the drivers, but the rest was okay and would work fine. Your GPU may have developed a fault in a part of the chip used only for 3D rendering, so normal 2D stuff would be unaffected while anything 3D, such as games, screensaver, etc. would not work.

 

[Neroon]

Cool... I will try those as soon as I get home this evening. Thanks for the help.

 

[Neroon]

I used the DxDiag testing tool, and indeed experienced errors:

D3D7 Test Result: Failure at step 8 (Creating 3D Device): HRESULT = 0x80004005 (Generic failure)
D3D8 Test Result: Failure at step 8 (Creating 3D Device): HRESULT = 0x8876086c (error code)
D3D9 Test Result: Failure at step 8 (Creating 3D Device): HRESULT = 0x8876086c (error code)

Now, that is all Greek to me so far.......

 

[Warp Core Breach]

This could be a hardware problem, but have you updated the drivers or made any changes lately? I googled your error codes and came up with this thread, which recommends using the Catalyst 7.7 drivers.

It's worth a shot. I do like ATI cards, but they have some really shitty driver support issues.

 

[Alaedhros]

^ Only things is, that recommendation was made in October 2007, and referred to the drivers released in July 2007; it is entirely possible that one of the releases since then would be better for Neroon. Does anyone know if one of the more recent releases included improvements to the AGP code and/or the AIW code?

 

[Neroon]

This could be a hardware problem, but have you updated the drivers or made any changes lately? I googled your error codes and came up with this thread, which recommends using the Catalyst 7.7 drivers.

It's worth a shot. I do like ATI cards, but they have some really shitty driver support issues.

I was pretty sure I had updated them recently, but I will verify that.

And man do I ever feel silly not checking via Google.

 

[Neroon]

Well... do I feel sheepish. I did update the driver to version 8.46, dated 03/28. And darned if it didn't fix the problem.

I greatly appreciate the help. Foolish as I feel for not looking into such a logical solution, it's a good reminder that I need to be more thorough in exhausting possible solutions before I pester others.

Thanks again!

 

[Warp Core Breach]

Cool. Just glad it wasn't a hardware problem.