Temp. alarm? Or did I find a prime number...

Rawjhaw

Junior Member
Mar 21, 2007
12
0
0
Hey all - latest newb on the scene here...

I've been trying to overcome my first real oc hurdle - can't seem to be able to get my new rig to 3.3+ yet. 3.2Ghz (356X9) @ 1.375v (1.32 under Prime95 load) is where I semi-confidently stand at the moment (if you wish to offer some suggestions, I'm happy to share the rest of my experiences/settings).

My most recent bench - a pathetic 1.4v hail-mary @ 375X9 - treated me to a sonic surprise only 40 seconds in to a Prime95 blend run. I can only describe the sound as a loopy car alarm, but it was the first and only time I've heard it (and i've tried a higher setting or two before this with no such sound - well, maybe not @ 1.4v though... although my vdroop brings it down to 1.35ish load).

Totally caught off-guard from the sound, I immediately halted the Prime95 test and restarted the system (even though CoreTemp was showing the normal 52-55 load temps i'm accustomed to under Prime95). I can't find anything about any warning sounds that my mobo might produce (although I believe the sound was coming from my speakers). Prime95 (v25.6) does have a setting under Preferences where you can enable "make noise when a Mersenne prime number is found" - and it's been enabled since I started this voyage. Did I find a !$!#@ prime number and throw it away by rebooting? or am I just a dumbarse newb who couldn't overclock his way out of a silicon bag...
 

Idontcare

Elite Member
Oct 10, 1999
21,110
59
91
If you were running a tortue test in Prime95 then the answer is no you did not find a prime as the torture test runs a set of pre-defined matrix transforms.

Likely the noise you heard from your speakers was your BIOS telling you some internally monitored threshold (be it temps, volts, or amps) was exceeded in a critical manner and your response was precisely as the alarm was designed to invoke.