The 6-series Intel chipset bug has left early adopters in a hairy situation. Some of their Serial ATA ports may malfunction, but last we've heard, bug-free motherboards aren't due to ship until April. Although it has refunds and replacements just like other board makers, Gigabyte has now released a Windows utility to make life a little easier for early adopters in limbo.
In a nutshell, the Gigabyte 6 Series SATA Check utility lets you check whether your drives are plugged into potentially buggy 3Gbps ports or safe 6Gbps ports. (Remember that only the 3Gbps SATA ports hooked up to a 6-series chipset are susceptible to bad behavior.) Gigabyte says the software works on any Sandy Bridge mobo, and it generates the following output:
The 1st scenario is where there are no devices connected to the affected Intel PCH SATA 2.0 ports, and the utility will let you know that your “SATA configuration (is) OK”.
The 2nd scenario is where your devices are all connected to the affected Intel PCH SATA 2.0 ports, and the utility will advise you to “(Please) move 1 or 2 devices from (the) Intel PCH SATA 2.0 ports to the free SATA 3.0 ports.
The 3rd scenario is where you have devices connected to the affected Intel PCH SATA 2.0 ports and the SATA 3.0 ports are also populated. Here the utility will advice you that “Use of (the) Intel PCH SATA 2.0 ports is not recommended”.
Savvy power users might wanna skip this entirely and just pop off their PC's side panel to have a look, but for anyone who isn't sure, Gigabyte's new tool may well come in handy. You can download it here on Gigabyte's website.
|Tubular scaffolding surrounds In Win's D-Frame Mini chassis||31|
|Leak reveals next-gen Kindle with 300-PPI screen||1|
|Microsoft intros equal-opportunity Bluetooth keyboard||21|
|Nvidia gears up for Game24; AMD asks fans to crash the party||74|
|Rumored Nexus 9 tablet may have its own keyboard||12|
|Microsoft plans Windows event on September 30||15|
|32GB Shield tablet with LTE goes up for pre-order||6|
|Micron's M600 SSD accelerates writes with dynamic SLC cache||11|