@voyn1x: no, i don't have SMB turned on.
@farcaller: it seems i recall the same keyboard issues.
@snow: next time instead of force-restarting, do apple+shift+Q and it will allow you to log out. then you can log back in with GUI working again.
ok here's a little report for now: i've had my system up for 10 hours now without reboot. i have ianxxx's suggested memory settings: cas latency @ 3, cycle time @ 18, row refresh @ 18, HT @ 3x. things are still running fine, however, i haven't tried stressing the system out again because i don't want it to freak out and give me the 10810 error once more (thus forcing me to reboot and start my long-term testing all over again). admittedly, most of these 10 hours were spent with the system being idle because i was asleep, so only about 2-3 hours of that time was me actually using the system. so, nothing intensive was going on. just a little bit of itunes, some web browsing, and some entourage email checking.
@ianxxx: not to be a pest, but for me a 7-hour stint still isn't enough. i've had this problem happen after many more hours than that. in fact, to me it seems like it may not even be an issue of time at all, but rather just the right combination of apps and usage. for example, i've had this issue happen after using Linotype Font Explorer (it's a great app for font organization, btw, if anyone is interested. google it.). this app, i believe, it highly RAM and CPU intensive, and i did notice once or twice that my system started acting up after it had been up for an hour or so. also, as i mentioned in a previous post, i used to run Tomato Torrent (not anymore though, because it sucks in general) and that also seemed to cause the problem, especially when i'd leave it running with torrents over night. i'll run Font Explorer now for a while and see if i can get the system to act up again.
now, here's a noob-ish question: what is this talk about "spawns"? can someone explain that to me? if it is what i think it is, then it makes sense because essentially Tomato torrent has many simultaneous processes going on (connecting to many peers, gathering data, etc.)...and Font Explorer also has this same thing going on because it has to process many different fonts (gathering info on the font, displaying the name of the font with the actual typeface, etc.).
ok that's all for now. sorry for the TLDR guys, hope you actually read all of this
