I wasn't even looking for issues they just came about through stability testing with the programs I mentioned.Originally Posted by The Stilt
To be fair the CPU was pushed quite high in frequency and somewhat in voltage, but I can't say I've seen the same error almost every time the system BS'd? If you in any way are involved with AMD and you guys choose to burry your heads in the sand and burn the last set of people that have supported you; so be it.
I've seen this a few times in the past with some old P4's but not to the extent it has come up with this chip, and if this is strictly a BIOS issue why doesn't this happen with the Thubans on the AM3+ boards?
Always the same error: A clock interrupt was not received by a ...yada,yada. I've pushed my 1090T pretty hard and have never seen this issue, only with the BD.
Now as far as specific's Aida's CPU Queen test crashed 2/3 times with the same error, but like I said to be fair mostly at higher frequency. I also use other benches to test for whole system stability not just CPU and this is where I throw in 3D mark as I've seen plenty of CPU's that will pass every Prime,ITB or what have you and fail in 1-2 minutes under 3D mark. Not that the CPU is to blame for every crash but yet again, and just with BD I get the "Clock Interrupt Error", sometimes 30's into and sometimes a minute into.
The same issue cropped up with JRiver and while just surfing the net, again both at higher clocks but what is the point of an enthusiast class CPU you can't OC to the limit? Yah no, not temp's, 50 is the max I'll let it go with all cores stressed and middle 40's for a regular 24/7 oc at 100% all cores/threads and I also walk the voltage down as far as I can go when I find a stable 24/7 OC.
So far 24/7 for me is 4.6@1.36 with all cores with memory at a mild OC of 100 or a little over. Changed voltage to 1.33.
Like I said don't know what's related and what's not, but I haven't seen this error in a long time.
Reply With Quote
Bookmarks