Inside: SereneScreen Fan Forum - View Single Post - Driver Issue Crash when "F" is pressed a second time

Dale · 04-05-2009, 10:48 AM

Originally posted by Dale:

System is WXP SP3, Video card is Radeon X300.
MA3 is installed, placed in /windows/system32. set as default screensaver.

Right-click on desktop, choose properties, screen saver, preview. [Same thing happens when running directly by clicking on the file, by the way]
MA3 starts normally, shows about 64 fps, 1360x768x32, window size 1360x768.

Press F to go to widescreen mode. Shows about 8 fps (which seems strange, but not the problem). Window size 648x507

Without doing anything else, press F again. "...problem and needs to close..." (the usual unhelpful "do I want to send to Microsoft". I could capture the little bit of data in the report, if that would be helpful.

This is repeatable on my system. Didn't (yet) try it on a different computer.

After several updates of drivers, and updates of MA3, this problem still exists on only this one computer out of 8 that I have tested.

As far as I can tell, nobody else can duplicate it. And I can't think of anything else to try.

I do not expect Jim (or anybody else) to devote any time to this problem, and don't expect it to be fixed (other than by accident).

04-05-2009, 10:48 AM	#13
Dale Banned Join Date: Jun 2005 Location: Western Missouri Posts: 960	Originally posted by Dale: System is WXP SP3, Video card is Radeon X300. MA3 is installed, placed in /windows/system32. set as default screensaver. Right-click on desktop, choose properties, screen saver, preview. [Same thing happens when running directly by clicking on the file, by the way] MA3 starts normally, shows about 64 fps, 1360x768x32, window size 1360x768. Press F to go to widescreen mode. Shows about 8 fps (which seems strange, but not the problem). Window size 648x507 Without doing anything else, press F again. "...problem and needs to close..." (the usual unhelpful "do I want to send to Microsoft". I could capture the little bit of data in the report, if that would be helpful. This is repeatable on my system. Didn't (yet) try it on a different computer. After several updates of drivers, and updates of MA3, this problem still exists on only this one computer out of 8 that I have tested. As far as I can tell, nobody else can duplicate it. And I can't think of anything else to try. I do not expect Jim (or anybody else) to devote any time to this problem, and don't expect it to be fixed (other than by accident).