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

jedihobbit · 26-February-08, 11:52 PM

02/26/08 early morning

The Prime session was still going when I got home from work and when I stopped it; the run had gone on for approximately 10.5 hours. Sadly I forgot to get a screenie for proof.

So it would seem that

Core: 1.40v
Memory Voltage: 2.1v
CPU Frequency: 290
Hammer Fid Control: Factory (Can?t Find)
HT Frequency: 3X (K8 <-> HT Speed in Abit)
PCIE Clock: 100
Multi: 10.5
Memclock: 667-5-5-5-15
1T/2T Memory Timing: 2T

is a confirmed bootable base from which to work. Actually it wouldn?t be a bad stopping point as it gives me 3.05ish GHz.

Below are what are probably some meaningless screen shorts from this morning oc?ing session.

This one shows the highest ClkGen setting obtained while using the v2.0 version of Stresscpu a HTT value of 298 for 3.13GHz

This comes under the ?for S & Gs? category??. the highest ?bootable? HTT value was 300 but by no means stable with both cores at 100%. However I did manage (this is the S & G part) to get a 4M run of Super Pi at this setting. When I tried for an 8M run when it got to the 18th loop it locked up with the wee-woo, wee-woo alarm.

To end the morning session I started a Prime run with HTT set at 295 for 3.097GHz. Core #2 crashed at 3 hours, 32minutes and I stopped the session at 3 hours 40.

After the Prime session for 295 I shut down the system. On a side note my ?R & D? area has been moved (banished?) to the garage. This meant the ambient temp was about 18C through the morning session with cpu temps never breaking 50C.

02/26/08 late afternoon

As I?m fighting a major cough and chest issue I felt it prudent to get some heat in the garage so the ambient moved up to around 24C. Because of this the afternoon session have core temps running in the 52 ? 58C range. This was with the hsf fan rpm raised to about 4500-4600 as opposed to 4000 in the morning. Also the twin 120s on the Tech Station went form min to max.

The main thing the afternoon session taught me is I needed another value when I refer to my ?settings?. Originally I would reference ClkGen and ?bootable??.now I think I need to add ?Cold Bootable?.

In my ignorance I decided to drop the mem from the 667 to the 554(?) divider and see if I could at least break the ClkGen barrier of 300. Well that was meaningless attempt as nothing changed. With ud?s suggestion to keep the 667 and boost the vcore I gave that a try. Now comes my reason to add ?Cold Bootable??.no matter what I did, I could not obtain any of the oc values above 290 that had been achieved in the morning session.

The morning HTT bumps were done as the system was ?running? = ?warm boots?. In the afternoon I went directly to 295 at startup. Prime runs at 295 wouldn?t even last 20 minutes this time and I think it was Core #1 that crashed. This was a first as #2 up to this time had been the weak link.

So I turned everything off before my pre-work nap, and will just walk away for a while.

26-February-08, 11:52 PM		#4 (permalink)
jedihobbit Apex Advanced Techie	Re: OC'ing nView / 4000+ Brisbane (DreamCatcher v2.0) 02/26/08 early morning The Prime session was still going when I got home from work and when I stopped it; the run had gone on for approximately 10.5 hours. Sadly I forgot to get a screenie for proof. So it would seem that Core: 1.40v Memory Voltage: 2.1v CPU Frequency: 290 Hammer Fid Control: Factory (Can?t Find) HT Frequency: 3X (K8 <-> HT Speed in Abit) PCIE Clock: 100 Multi: 10.5 Memclock: 667-5-5-5-15 1T/2T Memory Timing: 2T is a confirmed bootable base from which to work. Actually it wouldn?t be a bad stopping point as it gives me 3.05ish GHz. Below are what are probably some meaningless screen shorts from this morning oc?ing session. This one shows the highest ClkGen setting obtained while using the v2.0 version of Stresscpu a HTT value of 298 for 3.13GHz This comes under the ?for S & Gs? category??. the highest ?bootable? HTT value was 300 but by no means stable with both cores at 100%. However I did manage (this is the S & G part) to get a 4M run of Super Pi at this setting. When I tried for an 8M run when it got to the 18th loop it locked up with the wee-woo, wee-woo alarm. To end the morning session I started a Prime run with HTT set at 295 for 3.097GHz. Core #2 crashed at 3 hours, 32minutes and I stopped the session at 3 hours 40. After the Prime session for 295 I shut down the system. On a side note my ?R & D? area has been moved (banished?) to the garage. This meant the ambient temp was about 18C through the morning session with cpu temps never breaking 50C. 02/26/08 late afternoon As I?m fighting a major cough and chest issue I felt it prudent to get some heat in the garage so the ambient moved up to around 24C. Because of this the afternoon session have core temps running in the 52 ? 58C range. This was with the hsf fan rpm raised to about 4500-4600 as opposed to 4000 in the morning. Also the twin 120s on the Tech Station went form min to max. The main thing the afternoon session taught me is I needed another value when I refer to my ?settings?. Originally I would reference ClkGen and ?bootable??.now I think I need to add ?Cold Bootable?. In my ignorance I decided to drop the mem from the 667 to the 554(?) divider and see if I could at least break the ClkGen barrier of 300. Well that was meaningless attempt as nothing changed. With ud?s suggestion to keep the 667 and boost the vcore I gave that a try. Now comes my reason to add ?Cold Bootable??.no matter what I did, I could not obtain any of the oc values above 290 that had been achieved in the morning session. The morning HTT bumps were done as the system was ?running? = ?warm boots?. In the afternoon I went directly to 295 at startup. Prime runs at 295 wouldn?t even last 20 minutes this time and I think it was Core #1 that crashed. This was a first as #2 up to this time had been the weak link. So I turned everything off before my pre-work nap, and will just walk away for a while.