System unresponsive after Orthos

[sidefxv1]

Hi folks, I hope someone might be able to help with this. When I run Orthos it seems to run fine, no problems found. But then when I go to stop it things go wrong. Basically it stops ok and goes to idle, but then the computer becomes extremely unresponsive. It doesn't hang completely, but clicking the start button (for example) doesn't do anything. Or sometimes the start menu comes up but it takes 5-10 minutes. Same with right-clicking, or clicking "exit" in orthos. They seem to semi-hang the computer. Not completely hang, because TAT keeps updating its display, I can still move the mouse around, activate windows that are already open (sort of)

Anybody have any idea what might cause this? I'm running at stock clocks on the following:

E6420
Asus P5B
Crucial Ballistix PC5300
BFG OC2 GTX
2x Seagate 7200.10 RAID 0
Corsair 520W PSU

The thing is, it seems to run ok the rest of the time, but it's after running orthos that I have the problems. I usually have to restart to fix it...

 

[Substance]

I think it may be something to do with orthos using so much of your ram that none of windows is loaded to ram, which means everything you do will be loaded directly from harddrive.

Thats my guess anyway, corect me if im wrong people

 

[sidefxv1]

Hmm... that would be ok, but can anyone confirm this? I would think after a while of stopping orthos all the windows stuff should get loaded back into physical memory and things should be ok. But this doesn't seem to happen.


Just as an add on, all temperatures seem fine too. Under load it's around 52C and idle around 36C.

 

[sidefxv1]

Perhaps I could rephrase the question. Or rather ask another one:

Would you all think this is something I should worry about and spend time trying to diagnose? Or is it likely just a software bug, and not really something to worry about before overclocking?