AUGI member Hypnox1 has begun posting from experience as an application engineer or support analyst for a reseller.
I've clipped a portion of one post that might be interesting for some, though I recommend reading through the rest at AUGI. This is part of a crash explanation...
...snip...Lets start with the required though. If Revit crashes it leaves behind a temp file. This temp file can cause even more crashes in the future and continue a cycle of angering you as an end user ad infinitum. What can you do about it? Clean the Revit temp files out. Here how to do it:
In Windows XP
Go to C:\Documents and Settings\username\Local Settings\Temp\
In Windows Vista
Go to C:\Users\username\AppData\Local\Temp
Delete any files beginning with “revittemp_...”. This is a temp file that can get left behind if Revit crashes. If that happens this temp file may contain bad or corrupt information that could cause additional Revit crashes. Also, after a crash this file will get recreated at double the previous file size.
What causes the most crashes? Your system running low or out of memory. Most computers, that I've troubleshot, have only 2 gigabytes of RAM. I grew up playing with computers since 1990 so I know many people that have used computers that long and longer that 2 gigabytes seems like a lot these days, but it isn't. Seriously, it's bare minimum for a system running Vista, don't get me started on Vista hating. Even on high end systems that have 4 gigabytes you can still run into memory issues with large Revit models. 64 bit systems aren't limited by silly RAM issues, to a point at least. Usually you run into a hardware limitation on how much RAM you can have before you run into the OS limiting RAM.
Read more at AUGI...