Is my system underclocked?

Joemoney

Banned
Oct 17, 2004
43
0
0
I was playing around with this "Pc Wizard" software and I noticed it said my "initial frequency" on my processor was 1.666 Ghz, but it says I'm only running at 1.261Ghz.

Does this mean my system is underclocked?

I've downloaded the "ClockGen" software from the same site, but I made no changes yet.

Is my system underclocked? Can I move it up to 1.666 or perhaps further? How far can it go?

My system is as followed:

CPU-Z Report

--------------------------------------------------------------------------------

CPU-Z version 1.30.


CPU(s)
Number of CPUs 1

Name AMD Athlon XP
Code Name Thorton
Specification AMD Athlon(tm) Processor
Family / Model / Stepping 6 A 0
Extended Family / Model 7 A
Package Socket A
Technology 0.13 µ
Supported Instructions Sets MMX, Extended MMX, 3DNow!, Extended 3DNow!, SSE
CPU Clock Speed 1261.2 MHz
Clock multiplier x 12.5
Front Side Bus Frequency 100.9 MHz
Bus Speed 201.8 MHz
L1 Data Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L1 Instruction Cache 64 KBytes, 2-way set associative, 64 Bytes line size
L2 Cache 256 KBytes, 16-way set associative, 64 Bytes line size
L2 Speed 1261.2 MHz (Full)
L2 Location On Chip
L2 Data Prefetch Logic yes
L2 Bus Width 64 bits



Mainboard and chipset
Motherboard manufacturer ECS
Motherboard model K7S5A,
BIOS vendor American Megatrends Inc.
BIOS revision 07.00T
BIOS release date 04/02/01
Chipset SiS 735 rev. 01
Southbridge SiS ID0008 rev. 00
Sensor chip IT 0

Graphic Interface AGP
AGP Status enabled, rev. 2.0
AGP Data Transfer Rate 4x
AGP Max Rate 4x
AGP Side Band Addressing supported, not enabled
AGP Aperture Size 64 MBytes



Memory
DRAM Type DDR-SDRAM
DRAM Size 128 MBytes
CAS# Latency 2.5 clocks
RAS# to CAS# 3 clocks
RAS# Precharge 4 clocks
Cycle Time (TRAS) 6 clocks
Bank Cycle Time (TRC) 10 clocks
# of memory modules 1
Module 0 Hitashi DDR-SDRAM PC2100 - 128 MBytes
 
Sep 3, 2005
75
0
61
For starters, that temperature is leaning on the high side for being an idle processor(approx 118 deg F). Check your BIOS and up your clock frequency multiplier to the default one. That should kick it back to 1.6 gHz.
 

Joemoney

Banned
Oct 17, 2004
43
0
0
Originally posted by: enzoslashslash
For starters, that temperature is leaning on the high side for being an idle processor(approx 118 deg F). Check your BIOS and up your clock frequency multiplier to the default one. That should kick it back to 1.6 gHz.

Humble Inquiry,

How do I check bios and how do I change my frequency multiplier?
 

imported_rod

Golden Member
Apr 13, 2005
1,788
0
0
------
You multiplier (from your CPU-Z report) is currently x12.5
It should probably be about x16.5 (100.9MHz x 16.5 ~ 1.66GHz)

To change it, you will have to enter your BIOS, as the computer boots-up.
If your not sure what to do, be VERY careful.
------
To check your current BIOS, goto the "Mainboard" tab in CPU-Z.
------
RoD
 

Joemoney

Banned
Oct 17, 2004
43
0
0
I have a modest idea of what I'm doing, but I rebooted and I was unable to figure out how to get into BIOS. I'm running Windows 2k pro. I'm unsure how to open bios.
 

ViRGE

Elite Member, Moderator Emeritus
Oct 9, 1999
31,516
167
106
Ahh, I see the problem. Your multiplier is fine, the problem is that your front side bus is underclocked. It should be at 266mhz(133mhz double pumped), when it's only at 200mhz(100mhz double pumped) right now.
 

Joemoney

Banned
Oct 17, 2004
43
0
0
Originally posted by: ViRGE
Ahh, I see the problem. Your multiplier is fine, the problem is that your front side bus is underclocked. It should be at 266mhz(133mhz double pumped), when it's only at 200mhz(100mhz double pumped) right now.

I found this program called "ClockGen" which allows you to change clockspeed on the fly. Should I pump it up to 1.66Ghz and 133mhz? The first person said I'm already running very hot (49C), would this be a danger?
 

ViRGE

Elite Member, Moderator Emeritus
Oct 9, 1999
31,516
167
106
49C is fine. You ultimately need to fix the setting in your computer's BIOS(ClockGen is just a temporary fix, and make sure you have the right copy of it!), but there should be no problem bumping up the FSB to 133mhz.
 

imported_rod

Golden Member
Apr 13, 2005
1,788
0
0
Originally posted by: ViRGE
Ahh, I see the problem. Your multiplier is fine, the problem is that your front side bus is underclocked. It should be at 266mhz(133mhz double pumped), when it's only at 200mhz(100mhz double pumped) right now.
Nice spot ViRGE. :) I shoudda thought of that.
 

Joemoney

Banned
Oct 17, 2004
43
0
0
I moved it up, one notch at a time, to be safe, but when I got to 1.4GHz, it froze. Tried it again, it crashed.

Highest I could get to was 1.375Ghz.

This thing has a mind of it's own.
 

ViRGE

Elite Member, Moderator Emeritus
Oct 9, 1999
31,516
167
106
Humm, perhaps your memory dividers are >1:1? AXP chips are all based on a 133mhz FSB, there's no reason why you shouldn't be able to hit 1.66ghz.

Edit: Ya, I bet it's definitely a system multiplier issue; the multipliers aren't being adjusted by ClockGen. You need to set your FSB in your BIOS to 133mhz, otherwise the AGP and PCI multipliers are probably sticking at 3:1 and pushing those slots too high.
 

Joemoney

Banned
Oct 17, 2004
43
0
0
Originally posted by: Shenkoa
Buy a new one.

Oh I'm going to.

I'm going to buy an el-cheapo Dell for 300 bucks real soon.

And I'm going to start seriously reading up computer building and BIOS and those sorts of things, and THEN in about January, I'm going to build the mother of all "rigs" (as you guys call them). AMD FX-57 (or 59, if it's out by then), 4Gb of RAM, 1TB Harddrive, liquid cooling, top of the line everything. I plan to spend about 4k. It's going to be smoookin.
 

Joemoney

Banned
Oct 17, 2004
43
0
0
Originally posted by: ViRGE
Humm, perhaps your memory dividers are >1:1? AXP chips are all based on a 133mhz FSB, there's no reason why you shouldn't be able to hit 1.66ghz.

Edit: Ya, I bet it's definitely a system multiplier issue; the multipliers aren't being adjusted by ClockGen. You need to set your FSB in your BIOS to 133mhz, otherwise the AGP and PCI multipliers are probably sticking at 3:1 and pushing those slots too high.

Not sure if this is what you mean, but in PC Wizard, I found this:

"Cache L2: Multiplier : 1/1x (1244.7 MHz)"

Looked around some, could find nothing similar.
 

ViRGE

Elite Member, Moderator Emeritus
Oct 9, 1999
31,516
167
106
Originally posted by: Joemoney
Originally posted by: ViRGE
Humm, perhaps your memory dividers are >1:1? AXP chips are all based on a 133mhz FSB, there's no reason why you shouldn't be able to hit 1.66ghz.

Edit: Ya, I bet it's definitely a system multiplier issue; the multipliers aren't being adjusted by ClockGen. You need to set your FSB in your BIOS to 133mhz, otherwise the AGP and PCI multipliers are probably sticking at 3:1 and pushing those slots too high.

Not sure if this is what you mean, but in PC Wizard, I found this:

"Cache L2: Multiplier : 1/1x (1244.7 MHz)"

Looked around some, could find nothing similar.
The PCI/AGP multiplier won't be listed. It's an automatic thing. You're just going to have to put your FSB at 133mhz in the BIOS and give it a whirl.
 

Joemoney

Banned
Oct 17, 2004
43
0
0
Originally posted by: ViRGE
Originally posted by: Joemoney
Originally posted by: ViRGE
Humm, perhaps your memory dividers are >1:1? AXP chips are all based on a 133mhz FSB, there's no reason why you shouldn't be able to hit 1.66ghz.

Edit: Ya, I bet it's definitely a system multiplier issue; the multipliers aren't being adjusted by ClockGen. You need to set your FSB in your BIOS to 133mhz, otherwise the AGP and PCI multipliers are probably sticking at 3:1 and pushing those slots too high.

Not sure if this is what you mean, but in PC Wizard, I found this:

"Cache L2: Multiplier : 1/1x (1244.7 MHz)"

Looked around some, could find nothing similar.
The PCI/AGP multiplier won't be listed. It's an automatic thing. You're just going to have to put your FSB at 133mhz in the BIOS and give it a whirl.

I have an important project to finish, I'll finish it first. Then I'll save it on my slave drive, and unplug the slave drive, then I'll try that. Don't want to lose any info or burn my slave drive.

Thanks for all your help though, everyone.