Page 2 of 6 FirstFirst 123456 LastLast
Results 16 to 30 of 84
  1. #16
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    Thanks TGM, lost your link to stesscpu and the only copy I have is sitting on the HDD in DC's case! However ud as e-mailed one though, at work so will work on this more Tuesday. Only do the long runs with Prime (picked up the new version that runs both cores) when I have to do something else like honey dos or sleep.

    When I left for work at 21:45 it had been running for 3.5 hrs so just left it running 'til I get home.

    Will try to boot @ 295 Tuesday and play with ClkGen and download stresscpu to do the quick checks. Yep this one, so far, has not been as flustating as my Opty adventures. However I think part of that problem was too high of expectations and not wanting to believe in the limits of 2GB memory.

    Why F@H?? Click me!
    As of 07/28/11
    Oz1a v2.0 >> XFX MDA72P7509 750a, PI X2 8870BE, 2 x XFX GTS250, WD 250GB, F2-8500CL5D-2GBPK, Tt TR2 600W, XP Pro SP3

  2. #17
    Joined
    Aug 2004
    Posts
    10,610

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)



    UD, I think you have created a Monster!!!!


    "The significant problems we face cannot be solved at the same level of thinking we were at when we created them."
    - Albert Einstein (1879-1955)

  3. #18
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    Quote Originally Posted by TheGlasMan View Post


    UD, I think you have created a Monster!!!!
    Just call him Dr. Frankenstein!!

    Prime was still running when I got home so 18:03 - 08:38 = roughly 9.5 hrs. Re-booted to 295 and just did a 15 min Prime run before stopping. Going after stresscpu ( understand the is a V2.0 out there somewhere that is a true dual core test) and then on to ClkGen!
    Last edited by jedihobbit; 02-26-2008 at 09:14 AM.

    Why F@H?? Click me!
    As of 07/28/11
    Oz1a v2.0 >> XFX MDA72P7509 750a, PI X2 8870BE, 2 x XFX GTS250, WD 250GB, F2-8500CL5D-2GBPK, Tt TR2 600W, XP Pro SP3

  4. #19
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    Core Spd = 3.097 GHz
    Bus Spd = 295.0 MHz
    HT Link = 885.0 MHz

    And running stresscpu v2.0 that has SpdFan is showing both cores at 100%

    http://www.gromacs.org/component/opt...,80/Itemid,26/

    In ClkGen running s'cpu v2 @

    Core Spd = 3.114 GHz
    Bus Spd = 296.5 MHz
    HT Link = 889.6 MHz

    And doing this entry at the same time!!
    Last edited by jedihobbit; 02-26-2008 at 03:38 PM.

    Why F@H?? Click me!
    As of 07/28/11
    Oz1a v2.0 >> XFX MDA72P7509 750a, PI X2 8870BE, 2 x XFX GTS250, WD 250GB, F2-8500CL5D-2GBPK, Tt TR2 600W, XP Pro SP3

  5. #20
    Joined
    Feb 2003
    Posts
    8,739

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)




    just a few days ago, he was ready to tie concrete blocks to his ankles and jump off a pier. as bad as his luck had been, he wouldn't have thrown the blocks in first and ended up breaking his nose on a piling, just above water level.

    nothing more than good hardware and wrong combinations. looks like we got a winner here this time.


    hobbie,

    1. what fsb is your memory running at 295 htt?

    2. don't know if you board has a bios safe mode or not, but if you have boot failures moving higher, try bumping htt by only 1 or 2 at a time.


    ud

  6. #21
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    Quote Originally Posted by uddarts View Post
    1. what fsb is your memory running at 295 htt?

    2. don't know if you board has a bios safe mode or not, but if you have boot failures moving higher, try bumping htt by only 1 or 2 at a time. ud
    1. 667....thinking about dropping it to the 544ish divider as someone over at the abit forums had suggested as a starting point when I first was first fishing for info/answer on the board.

    2. belive so, if you mean at boot up it returns you to a screen suggesting you check your values in bios. It did that early one until I seemed to get a handle on this.

    BTW Core #2 gave out after "3 hours 32 minutes" with the booted HTT of 295. Trying to shake off some meds I took for this cough - will have a few screen shots, etc later on what went down this morning.

    Why F@H?? Click me!
    As of 07/28/11
    Oz1a v2.0 >> XFX MDA72P7509 750a, PI X2 8870BE, 2 x XFX GTS250, WD 250GB, F2-8500CL5D-2GBPK, Tt TR2 600W, XP Pro SP3

  7. #22
    Joined
    Feb 2003
    Posts
    8,739

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    667....thinking about dropping it to the 544ish divider
    1. no what does cpuz give for the frequency is in the memory tab.

    BTW Core #2 gave out after "3 hours 32 minutes" with the booted HTT of 295.
    bump the vcore once. check pc health to make sure it gives you the increase, after saving and exit.


    ud

  8. #23
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    Quote Originally Posted by uddarts View Post
    1. no what does cpuz give for the frequency is in the memory tab.
    442.5

    Quote Originally Posted by uddarts View Post
    bump the vcore once. check pc health to make sure it gives you the increase, after saving and exit. ud
    Will look into it tomorrow, will post some stuff possiblly later, but it seems the old ways are back.

    Need to crash before work, meds & cough are doing me in!!!

    Why F@H?? Click me!
    As of 07/28/11
    Oz1a v2.0 >> XFX MDA72P7509 750a, PI X2 8870BE, 2 x XFX GTS250, WD 250GB, F2-8500CL5D-2GBPK, Tt TR2 600W, XP Pro SP3

  9. #24
    Joined
    Feb 2003
    Posts
    8,739

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    442.5
    still running cas 5? my set of corsair run up over 500@cas 5, so i doubt you need to lower your divider. butttttttttt as we both have found out way too many times, things don't always do as expected.

    but it seems the old ways are back
    not quite because i never figured you be up as high as you are. 1.40v kicks my runs at 1.47v with lower mhz. your the king now.

    bump it one notch and see if it stabilizes. at some point you don't get a whole heck of a lot out of a lot more voltage. you can always drop the htt a couple of notches, the vcore back to 1.40v and your there.


    ud

  10. #25
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    Okay the gory details

    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.
    Last edited by jedihobbit; 02-27-2008 at 02:07 AM. Reason: [IMG] to [BIMG]

    Why F@H?? Click me!
    As of 07/28/11
    Oz1a v2.0 >> XFX MDA72P7509 750a, PI X2 8870BE, 2 x XFX GTS250, WD 250GB, F2-8500CL5D-2GBPK, Tt TR2 600W, XP Pro SP3

  11. #26
    Joined
    Feb 2003
    Posts
    8,739

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    cold boots go to safe mode? try entering bios, save and exit.

    also try 291, then 292, etc.


    ud

  12. #27
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    Quote Originally Posted by uddarts View Post
    cold boots go to safe mode? ud
    No, sorry missunderstanding here...... MY defined "Cold Boot" is powering up the system to achieve a "re-boot" with it loading all the way into windows.

    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, just ask ud, 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).

    Why F@H?? Click me!
    As of 07/28/11
    Oz1a v2.0 >> XFX MDA72P7509 750a, PI X2 8870BE, 2 x XFX GTS250, WD 250GB, F2-8500CL5D-2GBPK, Tt TR2 600W, XP Pro SP3

  13. #28
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    While I was up in the wife's "office" typing the thread reply, the system locked up 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 (repeat of 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’ing thread!!!
    Last edited by jedihobbit; 02-27-2008 at 06:50 PM. Reason: W/C'ing link

    Why F@H?? Click me!
    As of 07/28/11
    Oz1a v2.0 >> XFX MDA72P7509 750a, PI X2 8870BE, 2 x XFX GTS250, WD 250GB, F2-8500CL5D-2GBPK, Tt TR2 600W, XP Pro SP3

  14. #29
    Joined
    Feb 2003
    Posts
    8,739

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    http://www.alcpu.com/CoreTemp/

    compare

    as far as the oc, any chance you have maxed the cpu?


    ud
    Last edited by uddarts; 02-27-2008 at 06:48 PM.

  15. #30
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

    Re: Overclocking nView/4000+ Brisbane (DreamCatcher v2.0)

    Quote Originally Posted by uddarts View Post
    Weren't you the one who brought to my attention that it has issues with CPU-Z? That was the reason for some of the crashes during my Opty adventues?

    Quote Originally Posted by uddarts View Post
    as far as the oc, any chance you have maxed the cpu? ud
    Ya think!?!

    Why F@H?? Click me!
    As of 07/28/11
    Oz1a v2.0 >> XFX MDA72P7509 750a, PI X2 8870BE, 2 x XFX GTS250, WD 250GB, F2-8500CL5D-2GBPK, Tt TR2 600W, XP Pro SP3

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •