SiSoft Sandra 2002 - Underlige advarsler mm.
Hej!Jeg har lige kørt SiSoft Sandras TuneUp wizard, og rettet så mange fejl som jeg selv er i stand til. Men der er stadig nolge som jeg ikke kan tyde, de kommer længere nede.
Kort om mit hardware:
MB: ASUS P4P800
CPU: P4 (Northwood)
HD: Maxtor 80 gb SATA 7200 rpm (model nr. 6Y080M0)
Ram: Corsair XMS 512mb pc4000
SiSoft Sandra 2002 Advarsler:
Mainboard Information:
Tip T2530 - The MP BIOS in this machine is not MPS 1.04 or later compatible. This specification contains many improvements and is recommended for MP systems.
Fix: Check BIOS settings and set to MPS 1.04 or higher; otherwise consider a BIOS upgrade if there is no later BIOS upgrade available.
Notice N224 - SMBIOS/DMI information may be inaccurate. This information is reported verbatim and cannot be checked by Sandra. While brand-name companies set this information most generic manufacturers use generic data that is meaningless. This issue generates more technical support queries than all other issues combined.
Fix: If the information is not correct, check for a BIOS update (clear DMI pool) or fix any errors using the DMICFG tool provided with the board. Alternatively, disable Sandra’s DMI/SMBIOS reporting from module Options.
Tip T2545 - Large memory modules (256MB or greater) should be Registered/Buffered, especially if more than 2 are installed on the same channel. This improves signal quality by reducing the load on the chipset channel. While these modules add an extra clock delay due to the on-board buffers (thus CL2 effectively becomes CL3), the stability will be worth it. Server chipsets with many memory slots generally require Registered memory.
Fix: If you plan on adding more memory, consider replacing the modules with Registered/Buffered modules. Do note that you cannot mix Unbuffered and Registered/Buffered modules on the same channel, but you may be able to if the chipset has multiple memory channels.
Tip T2546 - Large memory modules (512 or greater) should be ECC/Parity. Since the probability that a bit will be corrupt is the same or increases with module density, the bigger the module, the bigger the overall probability that you will get one or more corrupted bits. While these modules add an extra delay on partial writes (e.g. less than data width) as parity for the whole line must be re-calculated, the stability will be worth it.
Fix: If you plan on adding more memory, consider replacing the modules with ECC/Parity modules. Do note that running plain and ECC/Parity modules will turn off ECC/Parity for the whole memory array.
CPU & BIOS Information:
Notice N224 - SMBIOS/DMI information may be inaccurate. This information is reported verbatim and cannot be checked by Sandra. While brand-name companies set this information most generic manufacturers use generic data that is meaningless. This issue generates more technical support queries than all other issues combined.
Fix: If the information is not correct, check for a BIOS update (clear DMI pool) or fix any errors using the DMICFG tool provided with the board. Alternatively, disable Sandra’s DMI/SMBIOS reporting from module Options.
WinSock Information:
Warning W503 - Some simple IP services are enabled. The simple services include Echo, Discard, Day Time, Quote of the Day and so on. While most UNIX workstations enable them by default, most of the time they are not required.
Fix: Uninstall or disable them unless you really need them.
ATA/ATAPI Information:
Warning W3103 - Acoustic Management enabled. While this reduces the noise the drive generates, the performance is almost always impaired. Most of the time fans generate more noise than the drive itself. If the drive does generate a lot of noise, it may be faulty. You could also consider swapping the drive for another model that generates less noise.
Fix: You may need to use a specific utility for the drive downloadable from the manufacturer’s website to enable or disable these settings.
Warning W3104 - Current transfer mode not optimal, i.e. not highest supported. This affects drive performance. If the controller is also capable of the highest supported transfer mode, there is no reason not to use it.
Fix: First check controller supported transfer modes. Then check the mode the driver for the controller/BIOS is set to use and modify; some default to a lower mode for compatibility. You may need to install newer drivers if the current drivers do not natively support the controller (especially for RAID). You may need to update the controller BIOS or drive firmware, if the mode does not stick. If data corruption occurs verify the cable and consider switching (if any) drives on the same channel onto other channels.
If the built-in controller does not support the mode, consider using the on-board/RAID controller or even disable the built-in controller and install a new controller.
