Apex Community Forums - View Single Post - OC'ing nView / 4000+ Brisbane (DreamCatcher v2.0)

jedihobbit · 29-February-08, 12:03 AM

02/27/08

When I shut the system off, the idea was just to get away and leave it alone for a while?.. Yah right! There are two major things I lack, that would be a lack of resolve and patience.

Lack of Resolve??.
Got home from work this morning and promptly (even before feeding the critters) fired up the Tech Station and adjusted the nView?s Bios.

HTT back to 295 and bumped the Vcore up to 1.45v (I know ud you said one bump ? 1.42v!) and threw on Prime. Then hit the sack.

Lack of Patience??
After the nap and doing a few other things I stopped the Prime run at 4.5 hours ? which was an hour longer than yesterdays 3.5 hour crash. Had to go out on some errands so turned off the system for 5 minutes to get my ?cold boot? and fired her up at 296 started Prime and off I went. When I got home I could here an audible wee-woo, wee-woo or however you want to describe that two-tone alarm that reminds me of the European style PD sirens.

Got inside and found Prime running merrily along, the screen wasn?t lock, and everything seemed fine except for the alarm. Did a screenie and rebooted the system with the alarm stopping a boot-up. Man am I glad I did the screen shot! When I pulled it up and was looking at it, I found what should have caused the alarm?..in Spdfan

Temp1: 19C
Temp 2: 112C
Temp3: 47C
HD0: 22C
Temp 1: 0C
Core: 20C

Now I need someone to tell which temp is what, but it is obvious something was ?over temp?! But what I find interesting is in Bios:

Temp Alarm is set to 80C
Over Temp Shut Down is set to 90C

In two to three days of playing never did I see any of the temps in Spdfan reach 60C much less 112C. Okay I have raised the Vcore from 1.4v to 1.45v, but come on that shouldn?t cause that much of a temp change!!

Also to make it more ?curiouser? I started it all over again with everything set the same and Core #2 failed after 5 minutes. Now trying stresscpu v2 to watch the temps as the heater is on and ambient is around 21C (assuming Temp 1 is = to case temp).

While I was up in the wife's "office" typing up the thread reply, the system lockup running S'CPU v2 at 296 / 1.45v. Unfortunately the screen saver was running when it locked up so I don't know when it happened.

THIS IS WHAT IS DRIVING ME TO DISTRACTION!

First run with these settings was chugging alone fine (except for the flaky high temp alarm) in Prime for over 1.5 hours. Second run has a Core #2 failure after 5 minutes of Prime. Third run has a system lockup in Stresscpu v2 in less than 15 minutes.

So it is back to turning off the system and contemplate my navel for a while. What I think is really going to happen is I?ll see if I can get the 295 to run Prime without crashing (if I can repeat the interrupted 4+ hour run) and be satisfied with what appears to be a 80 ? 90% OC. Worst-case situation would be somewhere between 290 and 295?? and be happy!! Then all I have to do is figure out how to keep everything cool enough while running in a shoebox.

Working on that with my W/C thread!!!

02/28/07

Went back to piddled some more but it appears I may be at the limits of the CPU & board without getting ridiculous with the Vcore. So I dropped it back to 1.425v @ 294 and started a Prime run around 14:00. Somewhere around 18:30 I ended up with the BSOD. Friday will give it another try but drop back to 293 @ 1.425 as my next challenge will be heat issues in the case.

Later!

29-February-08, 12:03 AM		#5 (permalink)
jedihobbit Apex Advanced Techie	Re: OC'ing nView / 4000+ Brisbane (DreamCatcher v2.0) 02/27/08 When I shut the system off, the idea was just to get away and leave it alone for a while?.. Yah right! There are two major things I lack, that would be a lack of resolve and patience. *Lack of Resolve??.* Got home from work this morning and promptly (even before feeding the critters) fired up the Tech Station and adjusted the nView?s Bios. HTT back to 295 and bumped the Vcore up to 1.45v (I know ud you said one bump ? 1.42v!) and threw on Prime. Then hit the sack. *Lack of Patience??* After the nap and doing a few other things I stopped the Prime run at 4.5 hours ? which was an hour longer than yesterdays 3.5 hour crash. Had to go out on some errands so turned off the system for 5 minutes to get my ?cold boot? and fired her up at 296 started Prime and off I went. When I got home I could here an audible wee-woo, wee-woo or however you want to describe that two-tone alarm that reminds me of the European style PD sirens. Got inside and found Prime running merrily along, the screen wasn?t lock, and everything seemed fine except for the alarm. Did a screenie and rebooted the system with the alarm stopping a boot-up. Man am I glad I did the screen shot! When I pulled it up and was looking at it, I found what should have caused the alarm?..in Spdfan Temp1: 19C Temp 2: 112C Temp3: 47C HD0: 22C Temp 1: 0C Core: 20C Now I need someone to tell which temp is what, but it is obvious something was ?over temp?! But what I find interesting is in Bios: Temp Alarm is set to 80C Over Temp Shut Down is set to 90C In two to three days of playing never did I see any of the temps in Spdfan reach 60C much less 112C. Okay I have raised the Vcore from 1.4v to 1.45v, but come on that shouldn?t cause that much of a temp change!! Also to make it more ?curiouser? I started it all over again with everything set the same and Core #2 failed after 5 minutes. Now trying stresscpu v2 to watch the temps as the heater is on and ambient is around 21C (assuming Temp 1 is = to case temp). While I was up in the wife's "office" typing up the thread reply, the system lockup running S'CPU v2 at 296 / 1.45v. Unfortunately the screen saver was running when it locked up so I don't know when it happened. *THIS IS WHAT IS DRIVING ME TO DISTRACTION!* First run with these settings was chugging alone fine (except for the flaky high temp alarm) in Prime for over 1.5 hours. Second run has a Core #2 failure after 5 minutes of Prime. Third run has a system lockup in Stresscpu v2 in less than 15 minutes. So it is back to turning off the system and contemplate my navel for a while. What I think is really going to happen is I?ll see if I can get the 295 to run Prime without crashing (if I can repeat the interrupted 4+ hour run) and be satisfied with what appears to be a 80 ? 90% OC. Worst-case situation would be somewhere between 290 and 295?? and be happy!! Then all I have to do is figure out how to keep everything cool enough while running in a shoebox. Working on that with my W/C thread!!! 02/28/07 Went back to piddled some more but it appears I may be at the limits of the CPU & board without getting ridiculous with the Vcore. So I dropped it back to 1.425v @ 294 and started a Prime run around 14:00. Somewhere around 18:30 I ended up with the BSOD. Friday will give it another try but drop back to 293 @ 1.425 as my next challenge will be heat issues in the case. Later!