Grimrock

Javokis wrote:It's kind of funny... and sad because my OC settings completely stabilize my other games like Fallout: New Vegas and Witcher 2 that actually suffer random crashes and slowdowns if I DON'T OC.

Is there a way for the OC settings to have a kinda... Profile or something? Have settings during one game, and different settings during another? Or do you going to have to manually change it every time now?

Javokis wrote:It's kind of funny... and sad because my OC settings completely stabilize my other games like Fallout: New Vegas and Witcher 2 that actually suffer random crashes and slowdowns if I DON'T OC.

Indeed strange. But maybe the effects are independent: the increased voltage on the RAM (I assume) stabilized NV and TW2 and the OC'ed FSB destabilized LoG? Try to increase the RAM voltage (a little bit 0.1V or so) without OC, could stabilize the RAM if it runs on the "edge" even with factory settings.

All the OC settings are done in BIOS. I pretty much use the highest high performance voltage settings without going into the red. Might be the FSB. The FSB overclocks both the ram and the cpu at the same time. Right now my ram is running at 220 (totally 440 in dual channel). This adds 200mhz to each cpu core. This is the maximum I've been able to OC this 7 year old rig without crashing the whole mobo. I could test the FSB to see if there's a friendly setting for Grimrock.

Further investigation into this matter has isolated crashes of Legend of Grimrock primarily to my FSB settings. Setting my FSB to 220 will cause LoG to crash the whole computer when loading and require a hard reboot. All my high-voltage settings weren't the issue. LoG's major crash issue was caused by the FSB clock speeds. High-performance settings for RAM and all high voltage settings weren't the cause.

This is very annoying. Why out of all my games does LoG crap out from an FSB overclock?

Javokis wrote:Further investigation into this matter has isolated crashes of Legend of Grimrock primarily to my FSB settings. Setting my FSB to 220 will cause LoG to crash the whole computer when loading and require a hard reboot. All my high-voltage settings weren't the issue. LoG's major crash issue was caused by the FSB clock speeds. High-performance settings for RAM and all high voltage settings weren't the cause.

This is very annoying. Why out of all my games does LoG crap out from an FSB overclock?

Frankly: why the hell should anybody care when a beyond spec operated system is not running stable?

Stories like this reminds me of an old pal of mine. He was also into overclocking his rig, the more the better, and as long as he was using it home alone it worked fine (at least he said so). BUT when we gathered for LAN parties his rig did permanently crash because it could not cope with the added LAN network traffic. So the next thing we did was tell him to get rid of all that OC crap and woohoo! his system was stable again.

Javokis wrote:Further investigation into this matter has isolated crashes of Legend of Grimrock primarily to my FSB settings. Setting my FSB to 220 will cause LoG to crash the whole computer when loading and require a hard reboot. All my high-voltage settings weren't the issue. LoG's major crash issue was caused by the FSB clock speeds. High-performance settings for RAM and all high voltage settings weren't the cause.

This is very annoying. Why out of all my games does LoG crap out from an FSB overclock?

LoG is a suprisngly demanding game, by default it tries to use all your resources to get the game running as fast as it can, best answer I've seen for those having troubles was ensure Vsync was enabled as this fixes the FPS, and can be modified if you still have troubles, take a look at this thread, and specifically Petri's answers I've linked.

viewtopic.php?f=12&t=2324&p=25528&hilit=+vsync#p25528

If you read through that thread it'll probably answer some of your questions.

Daniel.

Unfortunately, I tried that before and still had to drop my FSB to default to get LoG to run properly. I don't have a graphics card overheat nonsense. I don't have any graphics card issues. I already isolated the problem to my FSB and solved everything. I'm just curious as to why only LoG craps out on OC settings when everything else has been perfectly stable. I guess this is more of personal issue and possibly a warning about people who OC their FSB and are somehow having issues with LoG.

I already solved my issue, I'm just trying to figure out why the problem started in the first place.

Javokis wrote:I already solved my issue, I'm just trying to figure out why the problem started in the first place.

Unless you're into hardware design and/or driver development, it's unlikely you'll be able to figure out the exact reason.

Basically you've been lucky with other software, and LoG just happens to cause the "correct" bus traffic that causes some kind of time out to occur - one piece of hardware not acting quickly enough, still busy with the earlier tasks due to OC, to catch message from another bit - which leads to confusion and eventually a crash.