How is everyone getting on with this? Still having problems?

Still no issues here bud. Same RAM settings (HTx4 / 3-4-4-8)

If it turns out to be true then you made my system 100% stable, ya silly tit ;)

Gee thanks ;-)

Woops spoke too soon bud, PS just crashed again. Hmm, this didnt happend in a while though. I'll just post the console log here:

20/03/08 20 maart 20:34:04 Adobe Photoshop CS3[339] *** _NSAutoreleaseNoPool(): Object 0x1df78820 of class NSThread autoreleased with no pool in place - just leaking
Stack: (0x925aa12f 0x924b6ec2 0x924bc954 0x1e32c6 0x52e71a 0x61e9e9 0x219bee 0x219d31 0x3272 0x3199)
20/03/08 20 maart 20:34:07 [0x0-0x4a04a].com.adobe.Photoshop[339] objc[339]: Class EpicController is implemented in both /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_personalization.framework/adobe_personalization and /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_registration.framework/adobe_registration. Using implementation from /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_registration.framework/adobe_registration.
20/03/08 20 maart 20:34:07 [0x0-0x4a04a].com.adobe.Photoshop[339] objc[339]: Class EpicJSWindowExternalHandler is implemented in both /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_personalization.framework/adobe_personalization and /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_registration.framework/adobe_registration. Using implementation from /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_registration.framework/adobe_registration.
20/03/08 20 maart 20:34:07 [0x0-0x4a04a].com.adobe.Photoshop[339] objc[339]: Class EpicWizardController is implemented in both /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_personalization.framework/adobe_personalization and /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_registration.framework/adobe_registration. Using implementation from /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_registration.framework/adobe_registration.
20/03/08 20 maart 20:34:07 [0x0-0x4a04a].com.adobe.Photoshop[339] objc[339]: Class EpicPanel is implemented in both /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_personalization.framework/adobe_personalization and /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_registration.framework/adobe_registration. Using implementation from /Applications/Adobe Photoshop CS3/Adobe Photoshop CS3.app/Contents/Frameworks/adobe_registration.framework/adobe_registration.
20/03/08 20 maart 20:35:33 kernel CODE SIGNING: cs_invalid_page: p=361[lssave] clearing CS_VALID
20/03/08 20 maart 20:40:43 kernel CODE SIGNING: cs_invalid_page: p=364[mdworker] clearing CS_VALID
20/03/08 20 maart 20:45:53 kernel CODE SIGNING: cs_invalid_page: p=369[mdworker] clearing CS_VALID
20/03/08 20 maart 20:46:07 mDNSResponder[23] mDNSPlatformRawTime: last_mach_absolute_time EC45A25300000EAB
20/03/08 20 maart 20:46:07 mDNSResponder[23] mDNSPlatformRawTime: this_mach_absolute_time EC3520C400000EAB
20/03/08 20 maart 20:48:04 Adobe Crash Reporter[373] Process Id:
20/03/08 20 maart 20:48:04 Adobe Crash Reporter[373] 339
20/03/08 20 maart 20:48:04 [0x0-0x4a04a].com.adobe.Photoshop[339] 2008-03-20 20:48:04.270 Adobe Crash Reporter[373:10b] Process Id:
20/03/08 20 maart 20:48:04 [0x0-0x4a04a].com.adobe.Photoshop[339] 2008-03-20 20:48:04.271 Adobe Crash Reporter[373:10b] 339
20/03/08 20 maart 20:48:13 ReportCrash[374] Formulating crash report for process Adobe Photoshop CS3[339]
20/03/08 20 maart 20:48:19 ReportCrash[374] Saved crashreport to /Users/Snow/Library/Logs/CrashReporter/Adobe Photoshop CS3_2008-03-20-204805_Moeder.crash using uid: 501 gid: 20, euid: 501 egid: 20
20/03/08 20 maart 20:48:19 com.apple.launchd[119] ([0x0-0x4a04a].com.adobe.Photoshop[339]) Exited abnormally: Bus error
20/03/08 20 maart 20:48:20 kernel CODE SIGNING: cs_invalid_page: p=376[ATSServer] clearing CS_VALID
20/03/08 20 maart 20:48:37 kernel CODE SIGNING: cs_invalid_page: p=380[lssave] clearing CS_VALID
20/03/08 20 maart 20:48:38 kernel CODE SIGNING: cs_invalid_page: p=381[Console] clearing CS_VALID

I booted PS back up and bam, after a few mins another crash.

Log:

20/03/08 20 maart 21:05:31 Adobe Crash Reporter[400] Process Id:
20/03/08 20 maart 21:05:31 Adobe Crash Reporter[400] 388
20/03/08 20 maart 21:05:31 [0x0-0x53053].com.adobe.Photoshop[388] 2008-03-20 21:05:31.407 Adobe Crash Reporter[400:10b] Process Id:
20/03/08 20 maart 21:05:31 [0x0-0x53053].com.adobe.Photoshop[388] 2008-03-20 21:05:31.409 Adobe Crash Reporter[400:10b] 388
20/03/08 20 maart 21:05:35 Adobe Crash Reporter[400] (null)
20/03/08 20 maart 21:05:35 [0x0-0x53053].com.adobe.Photoshop[388] reproStepsString:
20/03/08 20 maart 21:05:35 [0x0-0x53053].com.adobe.Photoshop[388] 2008-03-20 21:05:35.530 Adobe Crash Reporter[400:10b] (null)
20/03/08 20 maart 21:05:41 com.apple.launchd[119] ([0x0-0x53053].com.adobe.Photoshop[388]) Exited: Terminated
20/03/08 20 maart 21:05:49 Adobe Crash Reporter[373] (null)
20/03/08 20 maart 21:05:49 [0x0-0x4a04a].com.adobe.Photoshop reproStepsString:
20/03/08 20 maart 21:05:49 [0x0-0x4a04a].com.adobe.Photoshop 2008-03-20 21:05:49.353 Adobe Crash Reporter[373:10b] (null)

Oh well, so we know memory times improves things but doesn't cure. I am 100% its network related and even more specifically internet.
Snow how are you connecting to the internet? router, modem etc?

Don't be too sure of that yet Ianxxx. I thought the same for a while, but...

Last night, I turned Little Snitch off (to rule it out) and I was running Transmission to download a couple of torrents. I added an XVid torrent and started downloading it to my desktop. I looked over at my Console and suddenly, I noticed that "quicklook" (the process that creates thumbnails for files) was trying to create a thumbnail for the XVid movie. The thumbnailing process failed (probably because the file wasn't done downloading yet), and it was rapidly spitting out this same error message over and over again:

It repeated this about a thousand times (not exaggerating), and the "p=" part of that second line grew higher and higher in number.

Now, I know why this happened: it is because Finder tries to create thumbnails for any file that is in an "active" window. Since the desktop is technically a constantly "active" window, it wouldn't stop trying to create the thumbnail as it failed each time. So, because this error was repeating and Finder was trying soooo hard to make it happen, my system bogged down A LOT, and lo and behold: The return of the jerky mouse! I eventually stopped downloading the file, moved it to a folder that wouldn't be in an "active" window, and the errors in Console stopped. However, the jerky mouse remained. It appears that when Leopard gets stressed, it doesn't recover after the stressful incident has stopped. It doesn't "refresh" itself in any way, apparently.

Now, this thumbnail scenario is very rare, and I know it is not THE ONLY reason that a jerky mouse will occur. BUT, I believe the answer lies in this following statement:

The mouse, GUI, and performance problems will occur when the system is under large amounts of stress of any kind. Period. There is no ONE solution, and it is not always related to the internet or networking. It could be anything: an intensive process, a power-hungry app, too much file-processing, repetitive errors (in my case), and on and on and on.

So what do we do about it? Well, if I am correct, there is nothing that can be done. We don't know if Zeph can do anything, because this may be a genuine Apple bug straight from the developers' desks. All we can do is keep Zeph notified and hope he chooses to help us out in any way he can.

Well guys, that's my 2 cents. I could be wrong, and I hope I am, but I have a feeling I'm not. Good luck to us all.

I went back to non-overclock setup, and so far I haven't gotten any 10810 errors, nor system reboots, but after coming back to my computer after a while of being idle (an hour or two), i've come back to a crashed photoshop, and just now, a crashed firefox. This is an improvement, but still not what I'd like. If I stay stable like this for a few more days I'll install logitech mouse drivers again and see if they run fine.

The mouse, GUI, and performance problems will occur when the system is under large amounts of stress of any kind.

I agree with this totally agrafuese. Thing is now for me these faults always happen after 3 hours use, I left my system on but no internet connected and it didn't happen.
To me it sounds like some kind of memory leak, whatever it is it obviously mounts up over time and then causes the instability.
I would love for someone else to try using there system for over 3 hours with no internet just to see if they get the same results!

Yes!! I was waiting for someone to say this because I wasn't sure if that was the correct term to use! (I know nothing about advanced crap like that, haha) Also, back in the days of Tiger, I recall Netkas (I think) dealing with some setting inside the kernel that had to do with processor timings. I wonder if I can go that far back on his site and find what he was talking about? This is exactly the kind of thing that needs to be investigated.

Question Ianxxx, what are you doing with your system while it is unhooked from internet? Any apps, anything intensive? And when it IS connected to the internet, what are you doing? And what if you simply connect it to the internet and walk away? Would it still slow you down? After the slowdowns, are you seeing anything excessive in Console? Anything repeating? Any "CODE SIGNING" messages? Sorry for so many questions, but they're all important :)