Page 3 of 6 FirstFirst 123456 LastLast
Results 31 to 45 of 84
  1. #31
    Joined
    Feb 2003
    Posts
    8,739

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

    close cpuz, then open coretemp.

    it may not do it on your board. it's when both are open. it may also only happen when one isn't fully open and you start the other.


    ud

  2. #32
    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
    close cpuz, then open coretemp.

    it may not do it on your board. it's when both are open. it may also only happen when one isn't fully open and you start the other.

    ud


    BTW when i left for work Prime @ 295 had been running for 4 hours 20 minutes. If it is still running when I get home I will declare it finished! It is supposed to get down to the mid 20s tonight, no heat in the garage, and I left all the fans on high so it there is another over temp alarm.... on it!

    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

  3. #33
    Joined
    Feb 2003
    Posts
    8,739

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

    if it doesn't error out, it isn't too hot but yes cooler is better and the easy bake oven is the next step.


    ud

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

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

    When I got home this morning I was greeted by my "cleared" desktop which, to me, indicates the system re-booted some tme during the prime run, so it is npw 294 & Prime with me going to bed and saying to h with it!

    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. #35
    Joined
    Feb 2003
    Posts
    8,739

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

    it could have been heat.

    drop the vcore to 1.425v.

    ud

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

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

    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!

    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. #37
    Joined
    Jun 2003
    Location
    SO CAL USA
    Age
    68
    Posts
    1,602

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

    you still running 440+ on your memory? I'd go to a lower divider and see what happens.This Gskill maxes around there and was what caused all my lockups.Remember cpu mhz is king now.
    asrock x370 taichi,16g gskill flarex3200 wd250mu 3wdblack 1 tera
    Asrock 990FX FX8120 8G Gskill 2133 2x WD2T 6.0 pc p+c 950w
    Asrock 890FX 1090t 2x4 Gskill 1866 RipJaw WD 1T 6.0 mushkin 850w
    DFI 790FXB M3H5 PII 965 8 Gskill RipJaw 1866 WD1T 6.0 ocz 750 w
    DFI 790FXB M3H5 PII 965 2x4 Gskill Rip Jaw 1600 Ocz evo720
    DFI 790FXB M2RSH PII 955 2x1Gskill 1600 Saph 4670 Ocz Evo 720W
    DFI 790FXM2RS PII 720 2x1gig Gskill 1600 Sapphire HD3400
    DFI Lp ultra D SLI Opti 148@300x10 @33c 1 gig Crucial ballistix 4000

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

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

    Have to get back with this later as I've had to do a total re-install (http://forums.pcper.com/showthread.p...35#post4225435) and plan to figure out what is what!

    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. #39
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

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

    My re-install seems complete and have managed to donload most of my testing stuff to start again.

    So to do my usual rush I've started testing with the basics:

    HTT @ 293 for 3.07 GHz / HTT Link = 879.1Mhz / Dram Freq = 439.6MHz

    In the first 15 minutes of Prime SpeedFan (as I read it and yes ud I will download Core Temp)
    Ambient = 21C (Temp 1)
    Core 1 = 52C (Temp 2)
    Core 2 = 47C (Temp3)
    or 51C (the "other" Temp 3)

    Need to finish some honey dos and get ready for work (start new shift today), will leave running and will chk when I leave for work (14:00ish). If it is still runnig will leave it and chk when I get home (24:00ish). Fingers crossed it should still be running.

    T-L may for S&Gs later go back and see what the DRAM freq was @ 294 & 295. Also if I remember right I had some issues at 544, maybe I didn't have the timings right.

    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

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

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

    Before I left for work had 2.5 + on the run when I started getting the wee-woo alarm again (Prime was chugging along like nothing is wrong). Didn't look to confirm but it was like last time I had a high temp on one core. In such a rush to shut it up failed to look.

    Shut it down until I can chek more fully as I had to leave for work.

    Looking to do Core Temp and see what it gets for temps......not sure who is sending the audible - SpedFan or bios.

    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. #41
    Joined
    Aug 2004
    Posts
    10,610

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

    Check the bios, but that setting usually is to turn the rig off.

    You can go into config in speedfan to raise and or eliminate the alarm (didn't even know it had one through all the years I used it, didn't find it either). Next time don't panic, if the cpu hasn't errorred it has not overheated. It will error before it overheats enough to cause damage.


    "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)

  12. #42
    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
    Check the bios, but that setting usually is to turn the rig off.
    At work, but as I remember it the bios for nView has one for alarm (default is 80C) and one for shut down (default is 90C).

    However there is another set and I can't remember how it is worded, but it has something to do with "desired" or "ideal" settings and the default for that is 50C. The next test I will have those set at 60C just to see what happens!

    Quote Originally Posted by TheGlasMan View Post
    You can go into config in speedfan to raise and or eliminate the alarm (didn't even know it had one through all the years I used it, didn't find it either). Next time don't panic, if the cpu hasn't errorred it has not overheated. It will error before it overheats enough to cause damage.
    Didn’t have the time to check SpdFan for settings, might be able to sneak it in tonight. The panic was not from getting the alarm, it was the fact it came in while talking to the wife on the phone and she's assuming I doing honey dos and NOT work on the 'puter!!

    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. #43
    Joined
    Mar 2003
    Location
    Central Virginia, USA
    Age
    70
    Posts
    5,302

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

    Quote Originally Posted by jedihobbit View Post
    However there is another set and I can't remember how it is worded, but it has something to do with "desired" or "ideal" settings and the default for that is 50C. The next test I will have those set at 60C just to see what happens!
    The first one is "CPU FanEQ Target Temp (50C default reset to 60C)
    and "SYS FanEQ Target Temp" (30C default reset to 40C)

    If any abit guys are looking know what these really do?

    Okay here I go again with Prime but I will use Core Temp this time instead of SpdFan.

    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. #44
    Joined
    Feb 2003
    Posts
    8,739

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

    wee ooh, wee oooh, ,,,,





    ud

  15. #45
    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
    wee ooh, wee oooh, ,,,, ud
    And I thank you for the useful response!

    Trying the Core Temp software, but am a bit confused (what's new, right!) as the temps shown are quit low....Core 0 = 22C and Core 1 = 27C.

    From reading the How It Works area (http://www.alcpu.com/CoreTemp/howitworks.html) I find:

    AMD chips report the temperature by a special register in the CPU's NB. Core Temp reads that register and uses a formula provided by AMD to calculate the current temperature.
    The formula for the K8 is: 'Core Temp = Value - 49'.


    Does this mean I add 49C to what is showing to get "real time"? If so that means under load I'm at Core 0 = 71C and 1 = 76C which is indeed an issue! As I thought the Brisbanes are supposed to run cooler than the rest.

    BTW as you read this we're approx. 1 hour into the Prime run with those temps, and I'm going to bed - later.

    If we have an audible alarm I'm sure the wife will wake me as the system in currently in the office, right below the master bdrm!

    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
  •