![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
DarkBahamut
Gawd
- Joined
- Mar 18, 2005
- Messages
- 551
Ok i have an interesting problem when overclocking this new cpu. I picked up a 4400+ last week and started to overclock it, but i have a problem.
So far ive been going slow in the overclocking. On monday i tried 11*209 (2.3GHz) and this seem fine. Primed it for an hour (not long i know, but still) and no problems, ran great. Then yesterday i set 11*218 (2.4GHz) and a problem came up. I started dual prime up and it ran fine for about 50min, then all of a sudden, teh system locks up. No error messages, no BSOD, it just locked up. The interesting point is that prime didnt fail, it was still priming when the system locked. I kinda put it down to a one off and memtested (which came back fine) and just left it as it was and went back into windows (but didnt restart prime).
It ran fine in everything else all night, so today i come home and i decide to OC abit more, so i try 11*223 (2.455GHz). This time starting dual prime causes the system to lock in a few seconds, but once again, no error messages, no BSOD, no prime failure, it just locks up. I tried 3 times with exactly the same result.
My core voltage was stock in the BIOS, and being a DFI this board undervolts, so my vcore was 1.328v, but i was still expecting prime failures if i had problems, not just a lock up for no real reason. So i went into the BIOS and set 1.375v (which runs at 1.344v) and it ran abit long, about for 30-45 seconds, but locked up again, once again, prime didnt fail.
Anyone got any ideas why prime will cause my system to lock, but why prime itself will not fail? Temps are fine, 42-43C (load) at 2.4GHz, even on a fairly warm day. Im using XP X64 and using the 64bit version of prime, running two copies using the -An command, running small fft tests.
So far ive been going slow in the overclocking. On monday i tried 11*209 (2.3GHz) and this seem fine. Primed it for an hour (not long i know, but still) and no problems, ran great. Then yesterday i set 11*218 (2.4GHz) and a problem came up. I started dual prime up and it ran fine for about 50min, then all of a sudden, teh system locks up. No error messages, no BSOD, it just locked up. The interesting point is that prime didnt fail, it was still priming when the system locked. I kinda put it down to a one off and memtested (which came back fine) and just left it as it was and went back into windows (but didnt restart prime).
It ran fine in everything else all night, so today i come home and i decide to OC abit more, so i try 11*223 (2.455GHz). This time starting dual prime causes the system to lock in a few seconds, but once again, no error messages, no BSOD, no prime failure, it just locks up. I tried 3 times with exactly the same result.
My core voltage was stock in the BIOS, and being a DFI this board undervolts, so my vcore was 1.328v, but i was still expecting prime failures if i had problems, not just a lock up for no real reason. So i went into the BIOS and set 1.375v (which runs at 1.344v) and it ran abit long, about for 30-45 seconds, but locked up again, once again, prime didnt fail.
Anyone got any ideas why prime will cause my system to lock, but why prime itself will not fail? Temps are fine, 42-43C (load) at 2.4GHz, even on a fairly warm day. Im using XP X64 and using the 64bit version of prime, running two copies using the -An command, running small fft tests.