"Titan Xenomorph" Intel Core i3 530 2.93GHz @ 4.20GHz - Lost Bios O.C. Settings

Status
Not open for further replies.
Paft said:
but but...





Do you have something against me? :) Because I do not understand the problem.
Click to expand...

the warranty on an overclocked system only remains if you do not update the bios, since updating the bios would wipe the overclock settings and maybe make those same settings unstable, ocuk dont have to help you if you can't be bothered reading :)
 
So if I said "bios crashed and repaired itself back to the standard clockspeed" I'd have got help?

I see now. My apologies. I Must remember to read absolutely everything, so next time I can lie. Also, it wasn't like I intended to update the bois. It was a 1 click job within Windows. (Prehaps that wasn't clear?)

You should have said "no we will not help you" form the start. Would have saved everyone's time.
 
Last edited:
Paft, if you did updated new bios firmware, then you will lose out your saved oc setting in the bios and ocuk is right that it your own responsible not to updating any bios firmware or otherwise it will void your warranty such as oc setting.

May I ask, why do you updated your bios firmware ?
 
Paft, if you did updated new bios firmware, then you will lose out your saved oc setting in the bios and ocuk is right that it your own responsible not to updating any bios firmware or otherwise it will void your warranty such as oc setting.
Click to expand...

No ****. ;)

May I ask, why do you updated your bios firmware ?
Click to expand...
Is that still not clear?

I was interested in the "Dynamic Energy Saver" utility but as I was downloading that I grabbed the others which included "@BIOS".

Like I said in my post above it was unintentional, really. I wasn't thinking. It was literally a single click auto update within Windows.
 
Paft said:
So if I said "bios crashed and repaired itself back to the standard clockspeed" I'd have got help?

I see now. My apologies. I Must remember to read absolutely everything, so next time I can lie.
Click to expand...

I appreciate that wasnt targetted at me but just to be totally clear here....I didnt falsify anything, read any warranty notes, or lie. I simply contacted oc when my problems started.....I was experiencing bluescreen issues (as documented in the webnotes against my order number). During one of the bluecreens it didnt freeze but it restarted itself and told be the bois was corrupt and it rebuilt itself (restarted about 15 times!!) back to the 3.07ghz settings.

Only at this point did i use the gigabyte utility that came bundled with the motherboard to update to 3.68ghz.

It should also be noted that i was recommended to remove the oc settings but a) i didnt know how, and b) it did the above before i found out how.

Having got it back to 4.2ghz (192x22) thanks to rjkoneill I found it immediately blue-screened the second I started prime95. Bugcheck code: 0x7F (0x8, 0x80050031, 0x6F8, 0xFFFFF88003B8DE89) Error: UNEXPECTED_KERNEL_MODE_TRAP same as before. So the oc was the prob all along i presume? :confused:

Also when I put the second suggestion of 4.2ghz (183x23) it hit 105c and 101c after like 20 seconds of prime running and idles at around 65c! Is this not too high for both max and idle?

I've queried the temps but out of paranoia until i get an answer or some reassurance ive reloaded the gigabyte 3.68 as it idles around 45 that way....and above all doesnt bluescreen!
 
Argggggghhhh :( cheers for the comparison paft, though it's not what I wanted to hear really!

ocuk staff - I'm far from an expert but it would seem logical to me that the bluescreens I was getting @ 4.2ghz was because of the 105c limit being reached when under load. What is my way forward here please? (I will obviously wind the clockspeed back to the defaults to reduce temps in the mean time).
 
Status
Not open for further replies.
Back
Top Bottom