Computer crashing while in Sleep mode... how? Why??

Hello, I have a problematic computer, one of the old 2002 MDD "wind tunnel" G4s that's been giving me trouble, all the more so since I updated to Tiger (probably in haste, I'm thinking of downgrading back to Panther since I didn't get quite so many crashes then, until I upgrade to a better/newer computer w/ Leopard). Yes, this thing crashes all the time, likely due to the insufficient fan that it came with that's causing it to overheat (used to just freeze until I installed Temperature Monitor to keep it in Nap mode, now I get the usual Kernal Panics, the computer NOT going to sleep/waking back up when I try putting it to sleep, etc).

However, a NEW crash I just noticed--it's happened twice so far--that I'll put it to sleep, and for whatever reason, the computer will be OFF when I return... somehow, something happened while in sleep mode causing it to crash & shutdown. When I restart it, the internal clock has reset (which is unusual). I copied one of the crash-logs below, if anyone can read over it and interpret any ideas of HOW/why it's crashing it SLEEP mode(!!!), I'd certainly appreciate it.


+(And yes, while I appreciate any suggestions about downloading/trying Rember and all of that, I don't know if it'll make any difference at this point, I know this computer *****, I absolutely hate it, I'd kind of just like to figure out WHERE these Sleep crashes are now coming from. Really, the RAM I have seems/seemed to be efficient enough to run Tiger--it certainly did for Panther--I think I just had the misfortune of inheriting a poorly-designed model in the first place from a family member who missed their own opportunity to take advantage of the fan/power replacement plan offered by Apple. Right now, about the only solution I can foresee to making my day-to-day use of this computer more productive--or giving me satisfaction--is again either downgrading to Panther, or tossing the offending POS out the window.)+


"Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x0000000059A96804 PC=0x00000000002957C0
Latest crash info for cpu 1:
Exception state (sv=0x32D96A00)
PC=0x002957C0; MSR=0x00009030; DAR=0x59A96804; DSISR=0x40000000; LR=0x00162468; R1=0x1C963BD0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00162468 0x00292520 0x00283C48 0x0027FAB4 0x0027F984
0x002ABDB8 0x000ABD30 0x021CC260
Proceeding back via exception chain:
Exception state (sv=0x32D96A00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x32CD7C80)
PC=0x901198E4; MSR=0x0000F030; DAR=0x00B4B8B0; DSISR=0x40000000; LR=0x9BE7A424; R1=0xF070CEE0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
panic(cpu 1 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
Proceeding back via exception chain:
Exception state (sv=0x32D96A00)
PC=0x002957C0; MSR=0x00009030; DAR=0x59A96804; DSISR=0x40000000; LR=0x00162468; R1=0x1C963BD0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00162468 0x00292520 0x00283C48 0x0027FAB4 0x0027F984
0x002ABDB8 0x000ABD30 0x021CC260
Exception state (sv=0x32CD7C80)
PC=0x901198E4; MSR=0x0000F030; DAR=0x00B4B8B0; DSISR=0x40000000; LR=0x9BE7A424; R1=0xF070CEE0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
Model: PowerMac3,6, BootROM 4.6.0f1, 2 processors, PowerPC G4 (3.3), 1.25 GHz, 1.25 GB
Graphics: ATI Radeon 9000 Pro, ATY,RV250, AGP, 64 MB
Memory Module: DIMM0/J21, 256 MB, DDR SDRAM, PC2700U-25330
Memory Module: DIMM1/J22, 512 MB, DDR SDRAM, PC2700U-25330
Memory Module: DIMM2/J23, 512 MB, DDR SDRAM, PC2700U-25330
Modem: Dash2, UCJ, V.92, 1.0F, APPLE VERSION 2.6.6
Network Service: Built-in Ethernet, Ethernet, en0
Parallel ATA Device: PHILIPS CDD5301
Parallel ATA Device: ST3120026A, 111.79 GB
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Apple Optical USB Mouse, Fujitsu Takamisawa Component, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA "

Power Mac G4 (Mirrored Drive Doors), Mac OS X (10.4.11), 1.25 GB DDR SDRAM

Posted on May 31, 2008 6:47 PM

Reply
4 replies

May 31, 2008 7:07 PM in response to phasmatrope

Hi-

Sleep problems are often USB device related. Do you have any external USB hard drives, etc.?
Sleep problems can also be caused by certain settings. See this article for troubleshooting steps.

Your crash log indicates "data access" as the action which causes the crash. So, looking at RAM, CPU cache, and hard drives would be best.
-Yes, I recommend downloading and running Rember....... RAM is one of the +single most common+ culprits in data access errors.
-Also, if you have the original system discs, run the Apple Hardware Test to test the CPU and VRAM of the graphics card (data handling also occurs in the VRAM).
If you don't have the AHT, download here, burn to CD, and run.
-Boot to your OS install disc, open Disk utility, and run "Repair Disk" on your hard drive.

If you had crashes in Panther as well, I would think that the problem is hardware based- RAM, CPU, Hard drive, Graphics card.

A note on temoperature- If you approach, or exceed 58ºC, you can expect crashes and freezes. Along with Nap mode, make sure the interior is dust free, an check the front air lower intake slots to insure free from dust and lint. Dirty components/blocked air passages can exacerbate system performance problems.

May 31, 2008 7:47 PM in response to japamac

Thanks, this is far from over, until I can actually try all of those tests you propose (starting w/ AHT).

*Yeah after I installed Temperature Monitor, I noticed that the processor seemed to run loudest as the computer approached 58 degrees (which it has done MANY times before), but since installing the Nap feature, it doesn't tend to go above 45 degrees or so. Still, I can't help but wonder, is it ANY kind of solution to keep your computer in "Nap" mode ALL the time?? This IS my first dual-processor computer, so I don't know if overheating is generally THAT common a problem with them, but if it is, and you DO have to keep it in "Nap" mode, HOW are you getting your money's worth?? In that case, why even bother getting a dual-processor in the first place, if it's just going to keep crashing??

*I already got and ran Rember, I originally thought that bad/3rd party RAM that my brother (the previous owner) had would be one of the problems this thing was experiencing, but it all seemed to show up a-okay.

*Also, I could see USB devices being a potential problem, but really, what's the solution to using/not using them?? Most people, if they have a printer, scanner, or even external drive plugged in to their desktop are going to want to keep those things plugged in most/all of the time: I could see someone unplugging/moving an external drive around, but a scanner??

*Wouldn't "Repair Disk" now put your HD at risk though?? I already repaired everything BEFORE I upgraded to Tiger, and am naturally worried about erasing over anything now.

Another major concern is backups: granted, if I DID have any concern about Repair Disk damaging my existing drives/boot drive, I suppose I could always try copying them to an external drive... but, my external drive is currently holding the clone of my old, Panther-running boot drive. And I'm STILL not convinced that just reverting to Panther wouldn't be a solution to make this computer less crash-prone (after all, the main problem it had with Panther was freezing, which it hasn't really done since I enabled Nap mode, so maybe if I revert back to it WITH that? Might run smoothly...). If I have to recopy much more stuff onto that external drive, I could risk compromising the Clone I have on there, and not being able to reinstall it.

After all, the MAIN reason I upgraded to Tiger was to TRY to keep this computer somewhat up-to-date (it's physically incapable of upgrading to Leopard as is), and MAYBE install some design apps: Photoshop, Final Cut, etc. However, with all these crashes, that's certainly not an option.

As it is, I think I'd be lucky just to have a computer that can go for 24 hours without overheating and crashing, and that's just for performing simple functions, like Word Processing and web-browsing...

May 31, 2008 9:17 PM in response to phasmatrope

is it ANY kind of solution to keep your computer in "Nap" mode ALL the time??

Yes. Enabling NAP mode allows the CPUs to throttle down when not taxed, reducing temperature and power use. When needed, the CPU's automatically throttle up.
In that case, why even bother getting a dual-processor in the first place,

Tasks like video rendering, graphics production, audio compiling, etc., have software that can utilize the multi-tasking/multi-thread handling ability of multiple processors.
if it's just going to keep crashing??

The crashing problem is not inherent to just multiple processors. The crashes are caused by problems within your system, which have yet to be properly identified.
I already got and ran Rember, I originally thought that bad/3rd party RAM that my brother (the previous owner) had would be one of the problems this thing was experiencing, but it all seemed to show up a-okay.

This is good, providing the tests were run multiple, consecutive times (10 times or more). The stress of continuous use will push the RAM to "recreate" errors, should this be the cause.
Also, I could see USB devices being a potential problem, but really, what's the solution to using/not using them?? Most people, if they have a printer, scanner, or even external drive plugged in to their desktop are going to want to keep those things plugged in most/all of the time: I could see someone unplugging/moving an external drive around, but a scanner??.

The fact of the matter is, all devices are not created equal. Neither is the power use/handling of USB devices. Often, simply adding a powered USB hub in between the tower and the USB device is all that is needed. USB does have limitations. This is why firewire and eSATA were developed. The problems that USB can have are not limited to Mac. They are commonplace throughout the computer world.
Wouldn't "Repair Disk" now put your HD at risk though?? I already repaired everything BEFORE I upgraded to Tiger, and am naturally worried about erasing over anything now.

For "normal" directory errors, not really. Besides, "Repair Disk" does not erase anything. However, any error on a hard drive puts your data at risk. Running any system without backup is playing Russian roulette. With your crash log indicating crashes at data access, you have not ruled out hard drive problems. And, the problem could be with the hard drive itself, not just the directory.
If it is directory problems, then one would still want to thoroughly check the RAM, VRAM, and the L3 cache of the processors. All handle data, and all, if defective, can cause data corruption.
At least, "Verify Disk" with Disk Utility....
but, my external drive is currently holding the clone of my old, Panther-running boot drive. And I'm STILL not convinced that just reverting to Panther wouldn't be a solution to make this computer less crash-prone (after all, the main problem it had with Panther was freezing,

You had problems in Panther. You have problems in Tiger. Changing OS versions will not cure a hardware problem.
which it hasn't really done since I enabled Nap mode, so maybe if I revert back to it WITH that?

Improvement since applying Nap mode indicates that temperature is a cause of your problems.
Read the web. MDD owners suffer from heat problems. Solutions include Nap mode, cleaning, reducing internal devices, increasing airflow, replacing heat sinks and/or thermal compound. Adding a PCI cooler that exhausts externally can help reduce internal case temperatures, allowing more efficient cooling.
As it is, I think I'd be lucky just to have a computer that can go for 24 hours without overheating and crashing, and that's just for performing simple functions, like Word Processing and web-browsing...

Until the cause of the problem is identified, and resolved, the ability to do anything on a sick machine is good.
So many want to point to "design flaws", "poor machine construction", "bad software engineering", etc. Though these are occasionally the issue, with Mac's, the most common problem that isn't already identified and solvable, is the failure to properly troubleshoot a problem. If one begrudgingly "attempts" troubleshooting, chances of success are slim.
One must roll up one's sleeves, get to it with a clear, objective mind, and not make excuses for not attempting a certain, potentially helpful procedure.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Computer crashing while in Sleep mode... how? Why??

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.