The error type, given what we have apparently eliminated, still seems to suggest a hardware problem. The error address in the fault 0x81A5FC85 is somewhere in the vicinity of where the ntsokrnl loads. If you had "pstat" on your computer you could possibly verify by running from a command prompt:
pstat
and come up with a long module list, part of which would look like this:
ModuleName Load Addr Code Data Paged LinkDate
------------------------------------------------------------------------------
ntoskrnl.exe 804D7000 478976 93440 1243264 Tue Aug 03 23:19:48 2004
hal.dll 806EC000 35456 42624 29952 Tue Aug 03 22:59:05 2004
KDCOM.DLL F7BAF000 2560 256 1280 Fri Aug 17 13:49:10 2001
------------------------------------------
I don't think it would be especially fruitful to try to get you a copy of pstat if you don't have it.
The bottom line here is, if this is not a hardware problem such as faulty ram a misbehaving motherboard, or perhaps even a bad video card, then there is some corruption of a core system file which only a reinstall will fix in my opinion.
Do you have the means to do a reinstall? It may have to be a clean one.
>> Also, it's a longshot, but since these errors do not occur in Safe Mode, is there any chance you are short on available disk space? That seems to be one of the issues raised with this error ...
http://support.microsoft.com/?kbid=314451&sd=RMVP