|
In the Fabcar race yesterday, I got "Application error" and rFactor crashed to desktop. That happened 3rd time for me and all 3 times it happened in "long" races. Once during F1 race ~1.5 hours after the race start, once somewheer else, and this time, again, with ~5 mins to go in a 2 hour race. I was very disappointed and it seems previous crashes were not "accidental" - there is something wrong on my side. - I checked system logs. Yes, around the time I got CTD, there was Antivirus activity - LiveUpdate or something like this.
Do someone else have any suggestions/advises? My PC spec.: AMD Athlon64 3200+ / 1Gb RAM / nVidia 7900GS 256 Mb |
I would start from checking that all the cooling fans are working and that there are not much dust etc. Remember to check the PSU (Power supply unit) fan too , those are known to fail at times and it can take a long time before it creates a visible problems. Live update refers to Symantec products and some of the Norton NIS/NAV updates are just huge , if you get such a update during the race , it could well drop you out of the race. I don't know how the Live Update can be de-activated , but maybe someone else here can help on that. -----
| ||
Thanks, Samuel :) Yes, I already deactivated LiveUpdate. It really caused disconnects before, while downloading updates. I checked the logs and the times when I got disconnects were the same when it was updating. But those were just disconnects, not "Application Errors" from rFactor. So about the "Application Errors" - I'm not sure that Symantec causes this. Though, yesterday in the Fabcar event, at the time I got "Application Error", there was LiveUpdate activity again, so, possibly, it could cause the "Applilcation Error". I disabled LiveUpdate, so I hope the won't be more CTDs. I created this entry just to ask for advises if there could be something else :) Like MoTeC logging, maybe. My next "trial" is PLMS race this Sunday :) Keep fingers crossed for me, please :) | ||
CTD again for me :) In today's PLMS race. This time there was no Antivirus activity. So the last thing which I suspect in doing this is Data Logging. The next attempt with MoTeC logging off will be my last attempt to race 60+ minutes races. If disabling MoTeC logging won't help, I give up. :) Someone has other ideas or experienced such problem? | ||
Have you tried some memtest and stuff like that? Seems it might be hardware issue, so try more of those diagnostic programs... memtest, prime... etc... | ||
Thanks for the tip, Janco, I'll try. :) | ||
Dmitriy, try CPU burn, memtest and voltage monitor to locolizi your problem | ||
|