• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Big Issues with AMD system

  • Thread starter Thread starter wolf2009
  • Start date Start date
W

wolf2009

Guest
CPU - Athlon II X2 250
Motherboard - Gigabyte MA770T-UD3P
RAM - Crucial 4GB DDR3 1333
OS - Vista x64 SP2

This is my first AMD system, so need explanation of a few stuff in bios.

2d7sttt.jpg


1. That TMPIN2 temp is scaring me. What is that ? It stays there, it doesn't go up when the CPU is under OCCT stress test.

2. Cool & Quiet was working with F1 bios on this board with the CPU downclocking to 0.8 Ghz. Updated to F2 and it doesn't work anymore even though it is enabled in bios. C1E is also enabled.

3. I set the the voltage for memory as 1.5V in Bios, but AMD Overdrive 3.0.2 is showing me 1.8V and doesn't allow me to lower it than 1.8V

ekqr9h.jpg


while HWMonitor shows 1.62V

ekqr9h.jpg


4. The frequencies are strange. IT should be 3000 Mhz for CPU, but it is 3020, for Memory it is 1333MHz in bios. It should be near 667Mhz, but it is 671

5. There are two voltages for RAM. One is DRAM Voltage and the other is DDR VTT voltage. What is this VTT voltage ?

aud36f.jpg


6. the ACC is disabled in Bios. It offers options such as auto, and +%(number) and -%(number) . What do these values do ?

2qkr0uw.jpg


7. What is better for this option

15eztxs.jpg
 
TMPIN2 isn't actually used here, so that is a default max value. Don't worry, your temps look good.



So far as cool & quiet, downgrade the BIOS if it is needed.


The variance in speed is due to the multipliers and the fact that no crystal is going to be 100% accurate.



VTT is memory termination voltage, leave it alone unless during overclock of the HT you start having issues with random memory issues, and you have isolated everythign else.





ACC is/was used by older Phenom processors to help with overclocks and stability. You don't need to use this.



I have understood SuperIO is better, however I haven't done much research.
 
TMPIN2 is your North Bridge. I believe I told you about it's temps with this board a while ago.
 
TMPIN2 is your North Bridge. I believe I told you about it's temps with this board a while ago.

yes you did. But I thought the MOSFETs would be the problem since they don't have any Heatsink, while the northbridge has one.
 
This is precisely the same temps my friend is getting on his GD-MA770T-UD3P as well. The other quirk of his system (X3 710, said mobo, 2x1Gb of OCZ DDR3) being it doesn't want to run his DDR3 at 1333Mhz (Random lockups) and only runs it at 1066Mhz (That RAM is rated 1600Mhz CL7-7-7-24 at 1.9v), but exams are here and we don't have the time to spend on tweaking the thing and it works fine for now at the current settings

Interesting to know that TMPIN2 is the northbridge, I do remember the heatsink wasn't getting hot. Look like we might need to try and reseat it...
 
The board I had the NB got extremely hot as well and in turn it wasn't stable at stock speeds. It seems to me that the mounting pins they use aren't strong enough. The heatsink is unbalanced in weight and doesn't make proper contact with the chip which is an already hot chip to begin with. If you want to keep the board I would suggest using a Xigmatek Porter.
 
4. The frequencies are strange. IT should be 3000 Mhz for CPU, but it is 3020, for Memory it is 1333MHz in bios. It should be near 667Mhz, but it is 671

Nothing strange there... your FSB is 201.4 and not 200, therefore all other speeds which are a factor of FSB will be increased as well.


2. Cool & Quiet was working with F1 bios on this board with the CPU downclocking to 0.8 Ghz. Updated to F2 and it doesn't work anymore even though it is enabled in bios. C1E is also enabled.

I had a similar issue after a BIOS update on my board, the Cool & Quiet stopped working. This was resolved by a clean OS re-install.
 
Last edited:
Back
Top