• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

AMD Catalyst 12.8 (8.982.0 July 27) AMD Official WHQL

Rusty0611 said:
But you're missing the point that the OC was stable before the driver update.

This is nothing to do with choosing an OC and testing for stability.

It's seems like you're doing anything but blaming the driver which to me looks to be the cause of his particular issue.
Click to expand...

No im not doing anything but blaming the driver.
There where versions of Prime that would not pick up instabilities as much as other versions, wait it was ok with the over versions so its the other Primes fault for not being stable with my OC.

At the end of the day you dont know what changes have been made and it seems that more of the GPU is being utilised which usually means more stress and more susceptible to unstable overclocks, people are reporting gains and some are still keeping there overclocks, so in other words it was not stable before it just that the driver did not trip up on it.
 
Rusty0611 said:
Can only go on what information is available and I assume that the average high end pC user isn't completely stupid.
Click to expand...

Its just your logic that is.
People are stubborn when it comes the there OCs.
Well my OC is stable as long as i don't runs theses games, programs or versions of them.

Ill keep to the simple v1 calculator because the 2V scientific calculator, trips up on my 6GHz OC AMD.
 
Last edited:
Says the person who blamed a bad OC when the only thing that changed is the drivers... Who's logic is stupid again?

OK mate.

Borley is happy on the old drivers where the OC isn't tripped over by some dodgy driver code. Everyone's happy.
 
Last edited:
Rusty0611 said:
Says the person who blamed a bad OC when the only thing that changed is the drivers... Who's logic is stupid again?

OK mate.

Borley is happy on the old drivers where the OC isn't tripped over by some dodgy driver code. Everyone's happy.
Click to expand...

No im not blaming the OC because it may be the drivers fault, but he will not know that unless he does a process of elimination.
As i said your logic is flawed as i gave you many feasible examples that you did not address at all.

But then again im not surprised in the least that your quick to just blame the drivers.

And dodgy code will trip up at stock so as i said your logic is flawed.
 
Last edited:
Hi back again I should give a bit more info that I did try it on stock clocks 1000mhz/1375mhz and I still got a freeze, but it might not be the driver as I haven't had a good time to try so will try over the next few days. But I would also understand if I had installed a new OS,program etc but a driver not so much.
Regards
 
borley said:
Hi back again I should give a bit more info that I did try it on stock clocks 1000mhz/1375mhz and I still got a freeze, but it might not be the driver as I haven't had a good time to try so will try over the next few days. But I would also understand if I had installed a new OS,program etc but a driver not so much.
Regards
Click to expand...

How about the CPU ?
 
borley said:
Yeah I will give that a go, what I'm going to do is try the betas again over the next few days and if it still does it I will go stock CPU to see.
Regards
Click to expand...

Well my system has been very unstable the last few weeks so im running everything at stock and you know that AMD stock 3.2 is not saying much but it has to be done.
It could be that my CPU is degrading.

http://img189.imageshack.us/img189/1797/unstable.png
 
Last edited:
Final8y said:
No im not blaming the OC because it may be the drivers fault, but he will not know that unless he does a process of elimination.
As i said your logic is flawed as i gave you many feasible examples that you did not address at all.

But then again im not surprised in the least that your quick to just blame the drivers.

And dodgy code will trip up at stock so as i said your logic is flawed.
Click to expand...

You didn't give any examples which I didn't address. I really struggle to follow your sentences most of the time. They're disjointed....
 
Rusty0611 said:
You didn't give any examples which I didn't address. I really struggle to follow your sentences most of the time. They're disjointed....
Click to expand...

Yeah nice cop out.
The XP 32bit and the vista 64bit was a common issue when it came to stable OCs on AMD CPUs.
So as i said its the hardware fault and not Vista 64Bit for putting more strain on the CPU thus showing up the instabilities that XP 32bit would not.

There was people on XS that would dual boot vista 64bit and Vista 32bit for that very reason when benching.
 
Last edited:
Final8y said:
Yeah nice cop out.
Click to expand...

Cop out of what? When you rant you become unintelligible. You didn't make any points worth addressing. You're trying to over implicate it because your precious AMD drivers might have possibly caused a problem. Emphasis on 'might'.

You're over complicating because the issue is resolved on old drivers. Stop getting your back up over nothing.

He has not changed OS so while an example it is not a valid one or this reason?

Can you stop editing your posts with a load more waffle after you've posted them. It's a sneaky way of making me not address your nonsense.
 
Last edited:
Read my Edit:
Its funny how the OP can follow me but you cant.
If the new drivers put more strain on the GPU and or CPU then it could push the Oced system to be unstable, its not complicated at all.
 
Last edited:
Final8y said:
Read my Edit:
Its funny how the OP can follow me but you cant.
Click to expand...

I can follow you when you're not ranting. Otherwise I'm afraid my eyes skim over your post as I struggle to follow the thread of any point you're making.

It's OK though English is probably not your first language. You should refrain from ranting probably.
 
Rusty0611 said:
I can follow you when you're not ranting. Otherwise I'm afraid my eyes skim over your post as I struggle to follow the thread of any point you're making.

It's OK though English is probably not your first language. You should refrain from ranting probably.
Click to expand...

Well don't bother reading my post if you think im ranting as its clearly to difficult for you.

As again you have not contributed anything.
 
Last edited:
I didn't read them. That's why I said my eyes skimmed over them. I only replied to you because you were making out it wasn't the driver when to me it looked like it definitely was.

You then proceeded to rant in fragmented sentences.

It's OK though he's found one which works fine. As I said, everyone's happy :).
 
Rusty0611 said:
I didn't read them. That's why I said my eyes skimmed over them. I only replied to you because you were making out it wasn't the driver when to me it looked like it definitely was.

You then proceeded to rant in fragmented sentences.

It's OK though he's found one which works fine. As I said, everyone's happy :).
Click to expand...

Yes it does look like the driver but that does not mean it is.

But what happens when he really needs to upgrade the drivers and they don't accept the OC he has.

The logic is if its stable at stock then its not the fault of the SW period it does not matter if the previous version was.

The only part where the SW can be at fault is the Ocing SW itself where its not applying things correctly thus making things unstable or not fully compatible with the new drivers.
But you have been on the AMD driver bandwagon lately so it does not matter how its put because your doing the same to everyone who disagrees with your view of AMD drivers.

Now i have to go out.
 
Last edited:
12.8 seems to cause TF2 to crash on load for me, i had to roll back to 12.6 to find out the new mode was just another con job (which wouldn't connnect after all anyways)
 
Final8y said:
But you have been on the AMD driver bandwagon lately so it does not matter how its put because your doing the same to everyone who disagrees with your view of AMD drivers.

Now i have to go out.
Click to expand...

You can call it whatever you like to suit: fanboy, bandwagon etc. the driver caused an issue he has resolved it by rolling back. Discussion over. Stop trying to generate friction from some lingering grievance you hold. It's a little odd.
 
You must log in or register to reply here.
Back
Top Bottom