MMM

View Poll Results: did you experience corruptions at very low overclocks or even stock?

Voters
182. You may not vote on this poll
  • Striker 2 XE - no corruption

    41 22.53%
  • EVGA or XFX - no corruption

    59 32.42%
  • Striker 2 XE - corruption problems

    54 29.67%
  • EVGA or XFX - corruption problems

    48 26.37%
Multiple Choice Poll.
Results 1 to 25 of 833

Thread: 790 corruption issues?

Threaded View

  1. #10
    Registered User
    Join Date
    Mar 2008
    Posts
    74
    Sounds like the same freeze encountered by oh so many others including myself until I balanced my FSB & GTLREF properly.

    Adjusting the GTL is not like increasing the voltage to some other part of your PC.. You are simply setting a "REFERENCE" by which signals on your FSB are measured.

    My settings which I've stuck with and have not encountered any hangs with for over 1 week are:

    1.20 FSBV

    &

    +25mv GTLs

    -

    Simply put; The FSB voltage is the maximum setting for a "1" passing between the NB/SPP and the CPU I/O across the FSB and a "0" is always = to 0.4V. GTL REFERENCE Voltage can be thought of as the dividing line between these two, a signal registering as greater than the GTLREF is = to "1" and a signal registering as less than the GTLREF is = to "0". All current intel CPU's use this method of communication with the NB/SPP but with high frequencies and or "ring back" these signals can become confused thus causing the system to identify false "1"s and "0"s which causes "data corruption"(Hence wrong signal/corrupt signal) and system hangs/crashes.

    One of the reasons why this is most frequently encountered when using SLI is because of the additional bandwidth being used across the FSB which of course is adding strain to the GTL circuit and increasing the likelyhood of a fault to occur.

    Same thing applies to video decoding since a very great deal of data is streaming into and out of the CPU across the FSB.

    Also in the CRYSIS game menu's where many users can even hear their computers make something of a ringing/whistling noise due to the increased traffic on the FSB for whatever reason(high FPS) and also older games like "starcraft" since the high-FPS/amount of data passing across the FSB is incredible made up of alot of relitively small "packets"
    For the Record: I've found that I can remain 100% stable upto 450FSB(Basically my limit due to BIOS/BOARD) using the same 1.2FSBV & +25mv GTLs
    Last edited by 5010; 04-22-2008 at 07:43 PM.
    [SIGPIC][/SIGPIC]
    Crysis Very-High/XP 1280x1024: 54.40 FPS / 1680x1050: 43.88 FPS / 1920x1080: 37.90 FPS
    World in Conflict MaXXed + 16AA/AF 1680x1050: 58FPS
    3DMARK06: 20862 | SuperPi 1M: 14.25s
    Loaded Core Temps: <55C

Bookmarks

Bookmarks

Posting Permissions

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