Fiery
-
Posts
11182 -
Joined
-
Last visited
-
Days Won
475
Content Type
Profiles
Forums
Events
Posts posted by Fiery
-
-
Thanks Fiery. Why I asked is that both NB and SB are shown in the Chipset description, as shown below.
North Bridge: Intel Sandy Bridge-DT IMC
South Bridge: Intel Cougar Point Z68
That NB is the IMC (Integrated Memory Controller) component of your CPU. Hence its temperature is listed as CPU temperature on the Sensor page
-
AIDA64 needs to have administrator privileges to make its sensor layer work properly.
-
1) What motherboard you have?
2) Did you have an older version of AIDA64 installed on your system before installing the latest trial version?
3) Does your Windows user have administrator privileges?
Thanks,
Fiery
-
AFAIK Asus P8Z68 series motherboards are not capable of measuring their north bridge or south bridge temperature. In fact, Z68 chipset has no north bridge at all, but only a single south bridge chip (PCH).
Regards,
Fiery
-
We don't mean to produce such benchmarks that would be comparable to benchmark results obtained using other software. And our customers demand more real-life application benchmarks, instead of expanding the current set of synthetic benchmarks with even more synthetic ones
-
CPU ZLib and CPU Hash benchmarks produce a MegaByte/sec result, so it should be easy to interpret them
The rest of the CPU benchmarks currently produce scores, which have no actual measurement unit. The unit could be "marks", just like with other benchmark software. Next year we'll revamp a selection of our existing AIDA64 benchmarks to produce more meaningful scores, e.g. MegaPixel/sec for CPU PhotoWorxx, and MegaByte/sec for CPU AES. The CPU Queen benchmark is a special one, since it solves a logical issue, hence there's no unit can be involved in making the score.
We do not have a Dhrystone or Whetstone benchmark, and we do not plan to implement such benchmarks in AIDA64.
Regards,
Fiery
-
1
-
-
Clearly size of a cache is shown. Testing cache L3 gives out the following data
Read 31050 MB/s
Write 22914 MB/s
Copy 28532 MB/s
Latency 5.6 ns
That is all is normal. I am right?
Yes, those L3 cache benchmark values look just fine for a Core i7-2600 CPU. The L3 cache is definitely operational in your CPU.
-
AIDA64 follows Intel's public DTS specifications, hence it should measure the right values if you have the right TJMax value configured. Automatic value means AIDA64 will take the TJMax value published by Intel, hence it should be the right one to use. The now discontinued Everest used different TJMax values, which may or may not be the right ones. But the right ones are now used by AIDA64.
If you cannot get your notebook to operate at HFM at 100% load, then there's definitely something fishy about your system. You can check BIOS options, Power Management options (in Windows Control Panel), but if nothing helps, it may worth disabling or completely removing the manufacturer supplied power management software(s) you may have installed.
-
1) Low Level SMART operations has to be enabled to let AIDA64 read any temperatures from HDD and SSD drives. You can have that option enabled and RAID SMART support disabled if you want to prevent AIDA64 reading temperatures from RAID arrays.
2) Stability options and other Preferences options are described in the AIDA64 user's manual. Just press F1 while AIDA64 is open, or navigate to AIDA64 installation folder and open AIDA64.CHM file there.
3) Dell, Apple and Toshiba related sensor modules are not used on other manufacturer systems. You can disable the related Stability options if you want, but it won't make any difference
Same goes for Koolance and T-Balancer, if you don't have such devices in your system, then you can disable those options. -
You can try enabling the option called SMBus access through ACPI (Asus motherboards) in AIDA64 / main menu / File / Preferences / Stability. You need to restart AIDA64 after altering that option.
Changing that may or may not help to fix that issue. AIDA64 implements industry standard mutexes to make sure its low-level hardware access features are synchronized with other monitoring software. Asus on the other hand refuses to implement those mutexes, hence their software (AI Suite) collides with other software, causing various anomalies
Asus is the one who needs to improve their software, but as most big companies, they tend to avoid doing so, and simply state that "You shouldn't be running XXXX other software along with ours".Regards,
Fiery
-
Yes, gauges and graphs are definitely on our list of improvements for "SensorPanel v2.0"
-
I guess it could be due to AIDA64 detecting SSD SMART attributes (including SSD temperature readings, if available) for your RAID array. Please try to increase or decrease the Disk temperature polling frequency value in AIDA64 / main menu / File / Preferences / Hardware Monitoring, and verify if the frequency of the blips follow the polling frequency change.
Regards,
Fiery
-
Please try to disable as many options on the Stability page in Preferences as possible. As a start, please disable the following options there:
- RAID SMART support
- SMBus access through ACPI
- Apple SMC sensor support
- Dell SMI sensor support
- Koolance TMS-200 sensor support
- T-Balancer sensor support
- DIMM thermal sensor support
- Toshiba TVALZ sensor support
- Volterra VT11xx sensor support
- GPU fan speed measurement
After altering the Stability page options, make sure to restart AIDA64 to apply the changes. Please let me know if it helps. If not, then please try to disable one more option on the Stability page:
- Fan divisor reconfiguration
If none of those helps, let me know, and we'll create you a special AIDA64 build with enhanced debugging features to pinpoint the code segment where the AIDA64 sensor module halts on your system.
Please use AIDA64 latest beta (Build 1720) for those tests.
Thanks,
Fiery
-
According to our own Sandy Bridge test runs -- albeit at slightly lower core clocks -- the mentioned AIDA64 benchmarks get memory bandwidth limited at high core clocks. You may want to use higher clocked DDR3 modules to squeeze out more performance from your system.
-
Do you use Turbo Boost? If yes, then can you please tell us all ratios you use? Max. Non-Turbo ratio, 1-core Turbo ratio, etc?
Thanks,
Fiery
-
Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic.
That data will help us to investigate this issue.
Thanks,
Fiery
-
this is not the case on Sandy bridge E.
That's why I said "most chipsets". AIDA64 latest beta already includes reference results for Sandy Bridge-E with Quad Channel DDR3-1600, and Bulldozer with Dual Channel DDR3-1866.
Overclocking is not required to use 1600mhz ram on most boards either, given the dram multiplier is unlocked on most x58 and p67/z68 boards.
When a chipset or CPU doesn't support a memory grade officially, raising the memory ratio still makes it overclocking. If you raise the CPU core multiplier on an unlocked CPU (e.g. Core i7 Extreme Edition), it is still overclocking
-
It is due to a BIOS bug about building DMI information. Please check Q#10 at:
http://www.aida64.co.../knowledge-base
I'm pretty sure the L3 cache isn't actually disabled. You can check the L3 cache size on the Motherboard / CPU page in AIDA64. If it shows a non-zero value there, your L3 cache is enabled. You can also try to run the Cache & Memory Benchmark (AIDA64 / main menu / Tools / Cache & Memory Benchmark) -- you should see a L3 cache read score somewhere between the L2 cache score and the Memory score. Since the L3 cache is a slower buffer than the L2 cache, but faster than the system memory.
And BTW, such DMI issues do not affect system performance or stability at all.
Regards,
Fiery
-
Different core temperature on Intel processors before the Core i3/i5/i7 era could be due to different TJMax value used. If you believe AIDA64 measures 10 Celsius more than what it should, then try to set a lower TJMax value in AIDA64 / main menu / File / Preferences / Hardware Monitoring.
-
1) Do you simply disconnect the drive without ejecting it from the System Tray icon?
2) Is it a USB, FireWire or eSATA drive?
Thanks,
Fiery
-
Thank you for the dump. We've verified the registers content, and also the relevant part of AIDA64, and everything looks fine. The only thing that may cause such issue would be the proprietary fan muxing feature that ASRock uses on your motherboard (and a number of other motherboards as well). It effectively muxes the RPM measurement signals of the CPU fan1 and the CPU fan2 headers into the same fan register of the Nuvoton sensor chip. When another software (for example ASRock's own monitoring software called Extreme Tuner) alters the GPIO setting for the fan mux, then the sensor chip will reflect the fan RPM for the CPU fan2 header. I'm afraid we don't have a solution for such issues
ASRock should simply stop using that weird GPIO fan muxing on their boards. -
1) On mobile systems you may need to alter the default setting of power management features (like SpeedStep) to make sure your computer will be running at HFM (High Frequency Mode) under heavy load. With certain settings that some manufacturers call "Battery saving mode" the computer will always work at LFM (Low Frequency Mode), no matter if the computer is running from AC or DC power. You have to make sure to check the current power management settings, although in most cases to get a mobile computer to work at HFM is easy: just connect it to AC power
2) The FPU stress test usually heats up all system components in 15-20 minutes.
3) AIDA64 System Stability Test is a lot more sophisticated and is better optimized to the latest processors than what EVEREST used to offer -- that's why with AIDA64 it's normal to reach higher temperatures due to the heavier workload it puts on the system. EVEREST is an obsolete and discontinued product that e.g. doesn't support any processors released in 2011 (e.g. Sandy Bridge, Bulldozer, Llano).
4) The FPU stress test uses a heavy workload, based on floating-point calculations, to fill up all the floating-point processing units of the processor with calculation threads. It stresses all available CPU cores and CPU threads, and it utilizes every relevant modern x86 extensions such as SSE, FMA4 and AVX. Modern processors can be heated up to the highest level by running exactly the type of worload that AIDA64 uses in the FPU stress test.
5) Most mobile computers cannot measure their own fan speed, but only able to control the fan speed based on the measured CPU temperature. Unfortunately most mobile computers are not equipped with a sophisticated sensor chip (due to size constraints on the motherboard PCB).
6) I42IL1 is most likely produced by Elitegroup, which manufactures a lot of different motherboard and notebook brands, e.g. ECS, PCChips, Uniwill, etc., and their products are rebranded by an even bigger number of computer assembly companies. Elitegroup a huge company, but since we're not sure which brand the notebook product called "I42IL1" belongs to, we show what DMI reflects. And DMI holds the manufacturer name as "OEM" on your system.
Regards,
Fiery
-
Mobile computers implement serious constraints on case space and fan sizes to make sure they are portable. Hence you cannot expect the same cooling performance from a mobile computer than from a desktop computer. Generally speaking, hard disk drives should be the same in mobile and desktop computers, but the mobile motherboards and mobile processors can stand a bit more than their desktop counterparts. So as long as your CPU isn't overheating, you should be fine.
You can check CPU overheating in the AIDA64 System Stability Test by enabling only the FPU test, and pressing the Start button. Watch the bottom graph where Throttling should never show any non-zero percentage activity. When your CPU is throttling, it means it is overheating. A properly designed computer should be able to run such a heavy workload like AIDA64 FPU stress test without the processor overheating.
Regards,
Fiery
-
Temperatures in AIDA64 may be missing and then re-appear because the temperature readout is unstable due to sensor device issues. GMCH sensors of Intel chipsets are notorious of providing unstable temperature readings
When AIDA64 reads an invalid temperature (e.g. 200 Celsius), it removes it from the Sensor page, to avoid displaying bogus/invalid/meaningless values. While HWiNFO doesn't seem to have such tricks, and so it displays bogus values too.
Asus P8Z68-Deluxe Motherboard, North Bridge Temperature
in General Discussion
Posted
"CPU" is the temperature measured by the sensor chip, while "CPU Package" is measured by the CPU itself using its on-die temperature diode. "CPU Package" should be the more accurate reading. "CPU IA Cores" and "CPU GT Cores" are also measured by the CPU itself, and show the temperature of the processing cores and the integrated GPU respectively.