Welcome to the MacNN Forums.

IFLY2HIGH · Jun 10, 2005, 04:11 PM

Well in light of after a couple of months on the shelf, My MDD Dual 1.25 gets a second chance at life.

Here's the begining of the story

So I finially gathered enough internals after stripping her clean months ago. I now have a 60 gig HD, my old 1x Superdrive from my QS, and a Geforce 2 Display Card. Did a 100% clean install running 10.4.1 with 896 megs of ram (3x256 1x128).

Well low and behold the problem still exists. Still crashes within just a few mins of operating. The ONLY way this thing runs is if I have the side panel open and a fan blowing across the motherboard and cpu heatsink. Now obviously there is a problem somewhere and it's gota be linked to a heat issue, but where? I also wonder if the CPU card is faulty, as it seems that this machine has no fan control. My dad's dual 1.25 will ramp up the fans on boot, throttle them back and will constantly change depending on system needs, this machine, they never change from running slow when the case is closed. I've cheked the firmware and it's up to date. I've run temp monitor and the processor gets no where near as hot as my dad's "operating temp" before mine freezes up, but the fans don't ramp up at all. When I installed panther before upgradeing to tiger, I noticed in one of the logs that it said the fan kernal or system could not tell what model it was running on, so that makes me think there is more to this. In Tiger I can't find it in the log anymore as it's all different. I do have a panic report from when I closed the box up hoping maybee Tiger would fix something but no go. A Hardware Test shows everything passed and is fine.

So here is my panic log, this is since this afternoon, with the system al closed up like it should be. Sorry for the long nature of this post, but this system shouldn't be doing this. It's been running with the side panel open and the fan blowing across the system for well over an hour now with no problems, but this is not how I intend to run this thing, it needs to run like this all closed up, and it's the system I sit here and write all this to you from lol...

----
panic.log:

Description: Panic (system crashes) log
Size: 3.09 KB
Last Modified: 6/10/05 4:21 PM
Location: /Library/Logs/panic.log
Recent Contents: Fri Jun 10 16:17:27 2005

Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x000000001EED8044 PC=0x00000000000290D4
Latest crash info for cpu 0:
Exception state (sv=0x2ED97C80)
PC=0x000290D4; MSR=0x00089030; DAR=0x1EED8044; DSISR=0x40000000; LR=0x000233AC; R1=0x14D63E10; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x0001AC98 0x000233AC 0x000ABE2C 0x01D97CA0
Proceeding back via exception chain:
Exception state (sv=0x2ED97C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2B42D000)
PC=0x9000A778; MSR=0x0200D030; DAR=0x1EED8044; DSISR=0x40000000; LR=0x9000A6BC; R1=0xBFFED060; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0007): 0x700 - Program
Latest stack backtrace for cpu 0:
Backtrace:
0x00095564 0x00095A7C 0x0002683C 0x000A819C 0x000ABB00
Proceeding back via exception chain:
Exception state (sv=0x2ED97C80)
PC=0x000290D4; MSR=0x00089030; DAR=0x1EED8044; DSISR=0x40000000; LR=0x000233AC; R1=0x14D63E10; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x0001AC98 0x000233AC 0x000ABE2C 0x01D97CA0
Exception state (sv=0x2B42D000)
PC=0x9000A778; MSR=0x0200D030; DAR=0x1EED8044; DSISR=0x40000000; LR=0x9000A6BC; R1=0xBFFED060; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC

*********

Fri Jun 10 16:21:02 2005

Unresolved kernel trap(cpu 0): 0x700 - Program DAR=0x000000001EED8044 PC=0x000000000001A27C
Latest crash info for cpu 0:
Exception state (sv=0x36F55A00)
PC=0x0001A27C; MSR=0x00089030; DAR=0x1EED8044; DSISR=0x40000000; LR=0x0001AA54; R1=0x14D83510; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x0001AA54 0x000295AC 0x00042E20 0x00026C24 0x00026CF4
0x000A8954 0x000A8714 0x000ABB00
Proceeding back via exception chain:
Exception state (sv=0x36F55A00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2A532280)
PC=0x04F63758; MSR=0x0008F030; DAR=0x1EED8044; DSISR=0x40000000; LR=0x04F63640; R1=0xF0283AF8; XCP=0x00000007 (0x100 - System reset)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0007): 0x700 - Program
Latest stack backtrace for cpu 0:
Backtrace:
0x00095564 0x00095A7C 0x0002683C 0x000A819C 0x000ABB00
Proceeding back via exception chain:
Exception state (sv=0x36F55A00)
PC=0x0001A27C; MSR=0x00089030; DAR=0x1EED8044; DSISR=0x40000000; LR=0x0001AA54; R1=0x14D83510; XCP=0x0000001C (0x700 - Program)
Backtrace:
0x00000000 0x0001AA54 0x000295AC 0x00042E20 0x00026C24 0x00026CF4
0x000A8954 0x000A8714 0x000ABB00
Exception state (sv=0x2A532280)
PC=0x04F63758; MSR=0x0008F030; DAR=0x1EED8044; DSISR=0x40000000; LR=0x04F63640; R1=0xF0283AF8; XCP=0x00000007 (0x100 - System reset)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
*********

seanc · Jun 11, 2005, 04:19 PM

Wow, your certainly having problems.

Some suggestions:

1. Swap CPU's from your Dad's MDD and put that into yours and see what happens, it could be that your CPU is 'over sensitive' or something. Make sure you use your heatsink. If it fails then try your Dad's heatsink.

2. Get a cpu fan like they use on PC processors and put that on, it might fit. I've never seen the inside of an MDD but if it's like a G3 B&W then the PC cpu fan should fit ok.

It makes me wonder why it was gathering dust in a warehouse for all those years?

The CPU change will help to determine whether the problem is the CPU or motherboard.
Once you've worked that out you can decide what to do.

If your CPU starts crashing your Dad's MDD then you've got an excuse to buy a new one, and you could buy an upgrade card.

Hope this helps,

Sean