[IFLY2HIGH]

This is a quickie capture of a panic log for an iMac 700 mhz, the half basket ball model, with 768 mb ram, that a friend has and can't figure out what the heck is wrong. It constantly crashes. We at first though it could of been a system coruption, but after reinstalling a fresh OS, witch wasn't easy to do, kept crashing, we feel it's something much deeper. When it crashes the screen gets all garbled up, we think it's hardware but not sure. Below is what we could get out of the panic log file. Maybee you guys can make some headway in this, and maybee can figure out what to do to fix it. I know the main logic board has been replaced but to no avail it's still having the same issue it did before the replacement.

---
Description: Panic (system crashes) log
Size: 45.68 KB
Last Modified: 7/28/06 6:51 PM
Location: /Library/Logs/panic.log
Recent Contents: ...
Proceeding back via exception chain:
Exception state (sv=0x2B063780)
PC=0x9000B208; MSR=0x0200F030; DAR=0x0108C3C0; DSISR=0x42000000;
LR=0x9000B15C; R1=0xBFFFE900; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.4.0: Tue Jan 3 18:22:10 PST 2006;
root:xnu-792.6.56.obj~1/RELEASE_PPC
*********

Sun Mar 19 11:02:38 2006


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000034EBA34E
PC=0x0000000000851D3C
Latest crash info for cpu 0:
Exception state (sv=0x2BE15280)
PC=0x00851D3C; MSR=0x00009030; DAR=0x34EBA34E; DSISR=0x40000000;
LR=0x00851D24; R1=0x121D3AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008536C4 0x0085282C 0x00861AD8 0x0083AEE0 0x002E7EE0 0x002E9DAC
0x0008C4B0 0x000291C0 0x000233AC 0x000AC02C 0x00000000
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x82f000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x47d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x62c000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x650000
dependency: com.apple.NVDAResman(4.1.8)@0x666000
Proceeding back via exception chain:
Exception state (sv=0x2BE15280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2BE88A00)
PC=0x9000B1E8; MSR=0x0200F030; DAR=0xE00800A8; DSISR=0x40000000;
LR=0x9000B13C; R1=0xF0080000; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.5.0: Sun Jan 22 10:38:46 PST 2006;
root:xnu-792.6.61.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8384 0x000ABD00
Proceeding back via exception chain:
Exception state (sv=0x2BE15280)
PC=0x00851D3C; MSR=0x00009030; DAR=0x34EBA34E; DSISR=0x40000000;
LR=0x00851D24; R1=0x121D3AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008536C4 0x0085282C 0x00861AD8 0x0083AEE0 0x002E7EE0 0x002E9DAC
0x0008C4B0 0x000291C0 0x000233AC 0x000AC02C 0x00000000
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x82f000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x47d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x62c000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x650000
dependency: com.apple.NVDAResman(4.1.8)@0x666000
Exception state (sv=0x2BE88A00)
PC=0x9000B1E8; MSR=0x0200F030; DAR=0xE00800A8; DSISR=0x40000000;
LR=0x9000B13C; R1=0xF0080000; XCP=0x00000030 (0xC00 - System call)

Kernel version:
*********

Fri Jul 28 18:51:16 2006


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000033E6434E
PC=0x0000000000851E14
Latest crash info for cpu 0:
Exception state (sv=0x26FC1500)
PC=0x00851E14; MSR=0x00009030; DAR=0x33E6434E; DSISR=0x40000000;
LR=0x0085282C; R1=0x122D3AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008536C4 0x0085282C 0x0084B07C 0x0083AC74 0x002E7EE0 0x002E9DAC
0x0008C4B0 0x000291C0 0x000233AC 0x000AC02C 0x6C743B69
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x82f000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x47d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x62c000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x650000
dependency: com.apple.NVDAResman(4.1.8)@0x666000
Proceeding back via exception chain:
Exception state (sv=0x26FC1500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2AC99C80)
PC=0x9000B1E8; MSR=0x0200F030; DAR=0x1C3923DC; DSISR=0x42000000;
LR=0x9000B13C; R1=0xBFFFE900; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.5.0: Sun Jan 22 10:38:46 PST 2006;
root:xnu-792.6.61.obj~1/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095718 0x00095C30 0x0002683C 0x000A8384 0x000ABD00
Proceeding back via exception chain:
Exception state (sv=0x26FC1500)
PC=0x00851E14; MSR=0x00009030; DAR=0x33E6434E; DSISR=0x40000000;
LR=0x0085282C; R1=0x122D3AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x008536C4 0x0085282C 0x0084B07C 0x0083AC74 0x002E7EE0 0x002E9DAC
0x0008C4B0 0x000291C0 0x000233AC 0x000AC02C 0x6C743B69
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x82f000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x47d000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x62c000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x650000
dependency: com.apple.NVDAResman(4.1.8)@0x666000
Exception state (sv=0x2AC99C80)
PC=0x9000B1E8; MSR=0x0200F030; DAR=0x1C3923DC; DSISR=0x42000000;
LR=0x9000B13C; R1=0xBFFFE900; XCP=0x00000030 (0xC00 - System call)

[Chinasaur]

If your friend has the HW test diagnostics disk, boot up with that and run it.

[cms]

This looks like a text-book mid-plane assembly problem that afflicted so many of these early G4 iMacs but which was never acknowledged by Apple -- and therefore there is no extended repair program. The only solution (if that is indeed what it is, and I'm sorry to say that your symptoms are classic) is to replace the logic board, which is just too expensive an option, IMHO, given the vintage of the kit.

If you can find the original Apple Hardware Test CD, you'll get an error on the video card. Your panic log is already pointing to a graphics error, and I've seen a ton of these, so know how to read them. Get the data off and park it somewhere safe, then run(don't walk) to your nearest Apple Store and invest in a tasty new Intel iMac!

[IFLY2HIGH]

We had a few Hardware Test Cd's around and non of them worked on the iMac. Some more history on the imac: The origional iMac mobo's ethernet port got zapped and then the mobo was replaced to fix that problem and then this crashing problem is present. We looked up the prices and yes we concur the price to fix it is better spent on a mac mini at this time.