Okay I got 2 monitors and 1 Duo Core (1.86 ghz). I put freelancer on one and Battlefield 2 on the other. It works fine and all but after a while my computer reboots. Is there anyway to devote one core to Freelancer and the other core to Battlefield 2? To prevent it from overloading like that.
I've searched for this too. I want a 3rd party program that will let me control my cores. I don't think there's a way, man.
I am a long-absent Supreme Commander, Executive Commander, Grand Admiral, Fleet Admiral, and Captain in the mighty Hellfire Legion. I have returned, and am on an urgent mission from Drake Thastus to return the Legion to its former glory, and to claim the galaxy for its own. Only then will I be able to rest.
RP Story (Still deciding whether or not to finish)
Does it just reboot? just like that? Or does it flash a bit of blue and white writing (IE Bsod). For me, my computer Bsods after its been on for more than a day or the memory is cold. I think i damaged it during OCing though, but thats another story.
If it just decides it needs a reboot, then there is not a way to stop this too my knowledge. Also, forcing the threads to stay in one core each will probably result in some performance degradation because core 0 (ie core number one, dont know why its core 0) handles all the ancillary background programmes. I see the difference in core 0 and core 1 whenever I run 3Dmark06 in the processor stress test.
In a nutshell, I do not think its possible, but if it is, do not expect its implememtation to be perfect. It may cause system instability or loss in performance. This stuff gets really precarious when you mess with the default commands for handling threads.
Well plan B for me was overclock it to 3.2 ghz and see if that helps. Duo core generate little amount of heat so it shouldn't be that hard. Except for moving the other motherboard into the case.:dry:. I heard that someone overclocked their Duo Core to 7.2 ghz once.
@ McNeo It just reboots and goes thru the normal startup it normally does.
Yes and then it displays a message of "Your system has recovered from a critical system error":dry:.
Core 2 Duos can go even higher, but you need insane cooling. Literally, liquid oxygen sitting on the processor, and thats not a joke. Imagine fixing a tube to your processor and filling it with liquid oxygen or nitrogen. Completely insane, but people still do it.
You will probably need very good air cooling to overclock your E6300 to that frequency. Apparently, it becomes unstable when it reaches ~2.7 GHz with the reference cooler.
My comp specs:
AMD Athlon 64 X2 5400+ 2.8ghz (non OC'ed)
2gig ddr2 memory
Nvidia GeForce 8800GTX 764mb Powered by EVGA My case
700W Thermaltake Toughtpower PSU
Windows Vista Home Premium 32bit
My comp specs:
AMD Athlon 64 X2 5400+ 2.8ghz (non OC'ed)
2gig ddr2 memory
Nvidia GeForce 8800GTX 764mb Powered by EVGA My case
700W Thermaltake Toughtpower PSU
Windows Vista Home Premium 32bit
I am a long-absent Supreme Commander, Executive Commander, Grand Admiral, Fleet Admiral, and Captain in the mighty Hellfire Legion. I have returned, and am on an urgent mission from Drake Thastus to return the Legion to its former glory, and to claim the galaxy for its own. Only then will I be able to rest.
RP Story (Still deciding whether or not to finish)
It is not that hard to set the affinty of a core, all you do is bring up both programs and bring up task manager then tab over to "processes" and find the .exe for the games. Then right click and select "set affinity" set one game on cpu zero and the other on cpu 1 (it does not matter which you choose) then reenter the game/s and all those nasty timing issues will be resolved. I should note that this has to be done every time you start up both games as affinty does not save to your settings. You will need to mess with your regestry if you want the changes to save. But I do not recommend doing this unless you have experience with regestry alterations. One more thing, I would not overclock unless you need to or are already planning on it, as overclocking can cause hardwere failure if not configured correctly.