vrijdag 25 november 2011

Gigabyte motherboard RAM settings

I was looking for some info regarding my AMD motherboard (Gigabyte GA-890FXA-UD5 rev2.1(Bios F6)) and found this useful info

http://forum.giga-byte.co.uk/index.php/topic,2515.0.html
You are better off not trying to run your RAM above 1333 Mhz. when using an AM3 Phenom or Athlon CPU.
If you do so, you run the risk of system instability and even damaging the Memory Controller on the CPU. If, like me, you have invested in 1600 Mhz RAM, you will actually benefit from running your RAM at 1333 Mhz and tightening the timings. You also gain better performance by slightly overclocking your CPU. If, however, you do overclock your CPU, it is stongly recommended that you purchase a good quality 3rd party CPU heatsink to aid CPU cooling and also remember that officially, neither Gigabyte or AMD support overclocking of their products.
If you wish to run RAM above 1333 Mhz. and your RAM is rated at a higher speed, you are not overclocking your system. However, AMD recommend that you only use memory that appears on the QVL as this has been tested for compatability at higher speeds. If you are unsure about the compatability of the RAM you have bought the safest option is to run it at 1333 Mhz to avoid damaging the Memory Controller. If you are looking to buy RAM that is faster than 1333 Mhz. and it doesn't appear on the QVL be prepared to downclock the modules to gain system stability. There are no guarantees that the RAM will run as stated and you could possibly damage the CPU's Memory Controller.

THIS IS VERY IMPORTANT:If you do manage to get your RAM running over 1333 Mhz., your system can appear to be fine and might even pass Memtest and other benchmarking utilities successfully. However, AMD have discovered that, in certain scenarios, the system may fall over after a period of use, depending on system usage and if you are stressing the CPU. This normally indicates a problem with the Memory Controller and you may need to replace your CPU if this happens.
++++++++++++++++++++++++++++++++++++++++++++

http://forum.giga-byte.co.uk/index.php/topic,7439.0.html
What is the DRAM EOCP?

It stands for Easy Over Clock Profile and the BIOS can read the information on the RAM (if it is present) and automatically set the system to run at this.

As I said previously, with the Athlon processor AMD recommend running RAM at 1333MHz or slower. You will probably have to set this in BIOS and you do this under the MIT section.

Change Set Memory Clock to Manual
Next set the Memory Clock to x6.66 (1333 MHz)
Change System Voltage Control to Manual
Check the Voltage for your RAM Modules (printed on the label or on the packaging) then set the correct voltage under the DRAM Voltage Control. If the Voltage for your RAM is over 1.50V you will notice a warning message that flashes in red you can ignore this. So if, for example your RAM is rated at 1.7V you will need to set this here and it is safe to do so even with the warning message

donderdag 24 november 2011

align Samsung harddisk

(Source: http://www.samsung.com/global/business/hdd/support/downloads/support_in_aft.html)
Samsung Electronics offers Samsung Alignment Tool (Software) with the Samsung 4K sector HDDs.
This program is only required for OS prior to Windows Vista, or an operating system backed up and
recovered with an image copy software (cloning software) that does not enable 4K sector drives.
(Note: Hitachi got a similar tool) 

With the provided tool "AcronisAlignTool-Samsung" you can check and realign your partitions.
To see if your partitions are aligned  correctly go into system Information and check if the "Partition Starting Offset" for each partition can be divided by 4096; this should return an integer value.
(example:  1048576/4096= 256)







Enable AHCI mode afterwards

(source: http://www.patriotmemory.com/forums/showthread.php?5465-How-Do-I-Enable-AHCI-With-AMD-890-And-Win-7)

Typically, (IF you did not install AHCI initially but went with the default IDE setup) with mechanical SATA drives, the process is to do the AHCI registry hack: http://support.microsoft.com/kb/922976

Excerpt:
To resolve this issue yourself, enable the AHCI driver in the registry before you change the SATA mode of the boot drive. To do this, follow these steps:
  1. Exit all Windows-based programs.
  2. Click Start, type regedit in the Start Search box, and then press ENTER.
  3. If you receive the User Account Control dialog box, click Continue.
  4. Locate and then click one of the following registry subkeys:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Msahci
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IastorV
  5. In the right pane, right-click Start in the Name column, and then click Modify.
  6. In the Value data box, type 0, and then click OK.
  7. On the File menu, click Exit to close Registry Editor.
, then reboot, go into the BIOS, change to AHCI, save and reboot and all is well.

woensdag 23 november 2011

remove SYSTEM-owned files Win7

(source:http://www.blogsdna.com/2166/how-to-delete-undeletable-files-in-windows-7.htm)
In order to access the files and folder for manipulation, modification or deletion, we will need to take control of the files under Windows 7. Here are two command line syntaxes to instantly take ownership of such files,
For Files:
takeown /f file_name /d y
icacls file_name /grant administrators:F
For Directories (will perform action recursively):
takeown /f directory_name /r /d y
icacls directory_name /grant administrators:F /t
Please keep in mind above syntaxes will grant full permission to administrator group hence you must be a part of administrator group to take advantage of above command.

zaterdag 12 november 2011

Report of chkdsk Win 7

Source: http://janetalkstech.com/2009/windows-tip-of-the-day-viewing-your-chkdsk-report

If you want to look back the reports of the chkdsk runs you have done there are 2 ways to see the old reports:
1. Powershell
To start powershell go to START=>Run .. type "powershell" hit OK
With the use of PowerShell command it is easy to get the information gathered by chkdsk:
Copy and paste that into the Windows PowerShell command window:
get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message

2. Eventviewer:
Go into eventvwr.msc, right-click Custom Views and choose "Create Custome view". Give it a name for example Chkdsk.
Use the settings from the pull-down menu from this picture and save your view.
Event logs: tick the boxes as seen below
Event sources: check from the pulldown: Chkdsk and Wininit