Problem with shut down during screensaver on

[rms]

Hi Kids,
New user here. This is an awsome screensaver. I have one problem though. I have my iMac G4 set up to shutdown automatically at certain times. If the serenescreen screensaver is running, the iMac will not shut down. The screen will just go black and the computer will stay on and it hangs there. When I move the mouse or hit a key on the keyboard, nothing happens. The screen stays black. I then have to manually turn the iMac off. This only happens with the serenescreen screensaver. All the other screensavers I have, behave as they should. Please help. Any advice is greatly appreciated.

[JimO'Connor]

Hi RMS, you need to look for a kernel panic log (/Library/Logs/panic.log) or in the system log or console log for warnings that the video card was reset.

We've had a couple instances of this, but it was a case of the video card giving out and MA showing it since MA works the video card for a long period of time. Other possible causes are corrupt or buggy video card drivers (boot from a fresh install of the OS).

[ESHIREY]

Welcome to the forums rms. I hope you hang around and check out the rest of the forums. You will find we are a great bunch of friends.

[rms]

Thanks for the responses. I took your advice and did a fresh install of the OS, and I still get the same results. I tried it with other screensavers and it only happens with MA. Can anyone else confirm this?

[JimO'Connor]

rms,

It isn't a general problem. I have MA running on all of my machines and I never turn off my machines, but let them go to sleep.

Did you look for a panic log?

Also, be sure that you limit the frame rate to 30 - 40 fps as you could be having a heat problem and limiting the fps can help with that.

[rms]

Hi Jim,
Thanks for the response. Here is the panic log. What does it all mean?


Tue May 23 12:08:32 2006




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000901F0014 PC=0x0000000000071FF8
Latest crash info for cpu 0:
Exception state (sv=0x2A3D3280)
PC=0x00071FF8; MSR=0x00009030; DAR=0x901F0014; DSISR=0x40000000; LR=0x00071FEC; R1=0x17603D60; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000852CC 0x00058A24 0x00091074 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x2A3D3280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x38E7BA00)
PC=0xFFFF8AD8; MSR=0x0200F030; DAR=0x01A3D000; DSISR=0x42000000; LR=0x7F408D14; R1=0xBFFFE220; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00083498 0x0008397C 0x0001EDA4 0x00090C38 0x0009402C
Proceeding back via exception chain:
Exception state (sv=0x2A3D3280)
PC=0x00071FF8; MSR=0x00009030; DAR=0x901F0014; DSISR=0x40000000; LR=0x00071FEC; R1=0x17603D60; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000852CC 0x00058A24 0x00091074 0x0009402C
Exception state (sv=0x38E7BA00)
PC=0xFFFF8AD8; MSR=0x0200F030; DAR=0x01A3D000; DSISR=0x42000000; LR=0x7F408D14; R1=0xBFFFE220; XCP=0x0000000C (0x300 - Data access)

Kernel version:
Darwin Kernel Version 7.9.0:
Wed Mar 30 20:11:17 PST 2005; root:xnu/xnu-517.12.7.obj~1/RELEASE_PPC



*********

[JimO'Connor]

A kernel panic is caused by a driver bug, an OS bug, or a hardware fault. Apple's done pretty good keeping driver and OS bugs down and we run into those pretty rarely.

Please set your limited fps to the very low end to determine if it is a heat induced fault. I seriusly doubt that any of your other screens savers are as resource intensive as MA. New versions will all default to frame limit at 60 fps (which you'll be able to turn off or adjust).