Please report all spam threads, posts and suspicious members. We receive spam notifications and will take immediate action!
Page 1 of 4 123 ... LastLast
Results 1 to 10 of 36

Thread: Saga #2 - Q9450 @ 3.2Ghz woes




  1. #1
    Join Date
    Oct 2008
    Posts
    82

    Default Saga #2 - Q9450 @ 3.2Ghz woes

    This is primarily at lsdmeasap's request that I make my own topic. As you requested mate, here are my current settings...

    HDD Smart Capability = disabled
    Limit CPUID Max to 3 = disabled
    No-Execute Memory protect = enabled
    C1E = disabled
    TM2 = enabled
    EIST = disabled
    Virtualization Tech = disabled
    Init Display First = PEG
    CPU Warning Temp = 70oC
    CPU FAN Warning = enabled
    SYSTEM FAN 1 Warning = enabled
    Smart FAN Control Method = disabled
    R.G.B = auto
    CPU Clock Ratio = 8x
    CPU Host Clock Control = enabled
    CPU Host Frequency = 400 mhz
    PCI-E Frequency = 100 mhz
    CIA2 = disabled
    Performance Enhance = standard
    System Memory Multiplier = 2.00D
    CAS Latency Timer = 4
    DRAM RAS# to CAS# Delay = 4
    DRAM RAS# precharge = 4
    Precharge Delay = 12
    ACT to ACT delay = 3
    Rank write to read delay = 3
    Write to precharge delay = 6
    refresh to act delay = 55
    read to precharge delay = 3
    static tread value = 7
    static tread phase adjust = Auto/0
    command rate = 2T
    System Voltage Control = manual
    DDR2 OV Control = +0.30v
    PCI-E OV Control = +0.10vl
    FSB OV Control = +0.10v
    (G)MCH OV Control = +0.200v
    CPU Voltage Control = 1.33something volts


    Currently, the Vcore on CPU-Z hovers between 1.31v and 1.32v, depending on idle/loading conditions. There have been no hardware changes to anything for the past few months.

  2. #2
    Lsdmeasap's Avatar
    Lsdmeasap is offline GIGABYTE Guru
    Join Date
    Jan 2008
    Location
    PCB Island
    Posts
    25,940

  3. #3
    Join Date
    Oct 2008
    Posts
    82

    Default Re: Saga #2 - Q9450 @ 3.2Ghz woes

    Issues: BSODs and blur-tear effects (video pattern rapidly descending the screen accompanied by stuttering sound) caused by idling and some games (not always) respectively. Error code always begins with 0x00000124. Vcore changes in either direction seem to do nothing against the BSODs, or just delay them.

    Specs:
    Gigabyte GA-EX38-DS4 Motherboard
    Intel Q9450 @ 3.2Ghz Processor
    Patriot Viper 2x2GB DDR2-800 4-4-4-12 Memory
    Seagate 500GB HDD SATA2
    2x Powercolor HD3870X2 GDDR4 Video Cards
    TRU120E Heatsink w/2x Scythe S-Flex SFF21F fans
    Thermaltake Armor+ Case
    Windows Vista Home Premium 64-bit w/SP1

    At current time of posting, I've checked RealTemp and these are the CPU temps...

    C1 = 50
    C2 = 47
    C3 = 62
    C4 = 54

    I'm no temp expert, but even I know this is incorrect!!

  4. #4

    Default Re: Saga #2 - Q9450 @ 3.2Ghz woes

    static tread value = 7 .. this is too low ... should be 8 to 10 ... when ever i got to 400mhz .. i need 8 .. some time 9

  5. #5
    Join Date
    Oct 2008
    Posts
    82

    Default Re: Saga #2 - Q9450 @ 3.2Ghz woes

    Static tRead = 8 you say? Okay, I'll give it a shot!

    UPDATE: Value set according to what godto suggested. Actually, the BIOS seemed to want "8" too because it had as the standard/auto setting for this value.

    Also, as a trial thing (as things can't get any worse I guess), I backed my Vcore way down to 1.25000v (my chip's VID) and slightly upped the NB/MCH by +0.250v. Is this bad, or potentially good?

    It's just that I read these particular CPUs like slightly high NB/MCH volts somewhat more than Vcore.
    Last edited by Nova Phoenix; 12-10-2008 at 03:43 PM. Reason: Update!

  6. #6
    Lsdmeasap's Avatar
    Lsdmeasap is offline GIGABYTE Guru
    Join Date
    Jan 2008
    Location
    PCB Island
    Posts
    25,940

    Default Re: Saga #2 - Q9450 @ 3.2Ghz woes

    I would say MCH .2-.3 is ok, NB/FSB should be good at .1-.2 and vcore should be raised instead as you do not have direct control over Vtt and raising the generic FSB Voltage may raise more things then you want.

    Graphical errors are almost always caused by overheating cards. What does GPU-z show for your card temps at idle and while gaming or benching them?

    I would also suggest you use 399 FSB with 2.00B multi (Lower Static tRead can be used on the B strap), or 401 FSB with 2.00D multi as 400 exact may cause you issues.

    What is your CPU Load temps?

  7. #7
    Join Date
    Oct 2008
    Posts
    82

    Default Re: Saga #2 - Q9450 @ 3.2Ghz woes

    (all temps are in degrees celsius)

    As stated many times before (btw, that's a reminder, not an attack), I have no way to monitor the NB short of attaching an actual thermometer to it. I was under the impression that NB and MCH voltage were and are one in the same thing. In any case, MCH is still at +0.250v. If necessary I will lower it back to +0.200v.

    A recent error has caused my second HD3870X2 to be undetected. However this is fine as I'm sure it rarely got used in games anyway (ie. Crysis, which scales better with Nvidia - a future goal of mine). As for the primary HD3870X2, GPU-Z is currently reporting between 49 on the first GPU and 51 on the second.

    I never see the temps for long when gaming (I can glance very-quickly after I exit), but in CCC I've seen the temp sometimes reach 65.

    I'm not sure this is viable financially, seeing as I wanna upgrade at some point, but are there any aftermarket coolers designed for the HDxxxxX2 cards?

    Currently running a short Prime95 Large FFT test to heck for CPU load temps. Going from Core 1 to Core 4 as follows (keep in mind they fluctuate): 56/51/65/59.

    I can set the FSB to 399/401 to test, but why would exactly 400 pose a problem anyway?

    Update: At this time, I just finished playing about 20 minutes of Far Cry 2. Now I only saw this just as FC2 fully shutdown, but GPUZ reported about 60-65 on both GPUs on my HD3870X2.
    Last edited by Nova Phoenix; 12-10-2008 at 09:15 PM. Reason: GPUZ update!

  8. #8
    Join Date
    Oct 2008
    Posts
    82

    Default Re: Saga #2 - Q9450 @ 3.2Ghz woes

    Seems everything survived overnight w/3.2Ghz on stock voltage (technically 1.323v after vdroop). Will continue to monitor. I may still need help though.

    EDIT: Had a BSOD. Figured it was because of my F-ed up HD3870X2s (I HATE!!! ATI right now!). I upped the Vcore to 1.27500v, which CPU-Z reads as between 1.232v and 1.248v.

    #2-EDIT: I went into CCC and set it to only use 2 GPUs in Crossfire. Hopefully it figured out to only use one of my HD3870X2s - the primary one. I did this thinking that this would disabled the second HD3870X2 entirely.
    Last edited by Nova Phoenix; 12-11-2008 at 08:19 AM.

  9. #9
    Join Date
    Oct 2008
    Posts
    82

    Default Re: Saga #2 - Q9450 @ 3.2Ghz woes

    This is pissing me off something shocking!!!!!!!!!!!!!!!!!!!!!!

    I just got a RED SCREEN of death, not a BSOD, just now whilst playing Crysis Wars. I backed the NB down a tick and upped the Vcore a tick.

    WTF is going on here??? I'm f-ing sick of this ****! Do I need a new CPU? Water cooling instead of air? Better GPU? WHAT??

  10. #10
    Join Date
    Nov 2008
    Posts
    66

    Default Re: Saga #2 - Q9450 @ 3.2Ghz woes

    Instead of getting pissed off why don't you post you full specs and BIOS settings, so we can be of some help....
    Gigabyte EP45- UD3P
    E8500 Wolfdale @ 4.1ghz
    2x2gb G.Skill PC6400, DDR864, 5-4-4-12
    (3)- Samsung 320gb Spinpoint hdd's in Raid 5
    ASUS TOP 4850 w/Glaciator Fansink
    Lite-On 16x DVD x 2
    D-Tek Fuzion WB
    Thermochill PA120.2 radiator
    2x120 SFF21-F fans
    Liang D5 pump

Page 1 of 4 123 ... LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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