Kingston HyperX SSD not seen as an SSD

[equazcion]

My new Kingston HyperX SSD isn't showing up in Kingston's firmware updater, nor in Kingston's "toolbox", or in SSDLife (3rd-party SSD health checker).

I just installed this new Kingston HyperX 120GB. I successfully cloned my boot drive to it and am now running Windows 7 x64 from it. It seems to work fine aside from one blue screen, which I'm told the new firmware would fix.

I spent 2 hours on the phone with Kingston support because I couldn't get the firmware updater to see that I had a Kingston SSD. He said Marvell controllers sometimes have this problem, but the drive is connected to a non-Marvell SATA port.

I finally got the firmware updated by putting the drive in an external enclosure and connecting it to a laptop using eSata (it didn't show up in the updater using USB).

I'm not using RAID for this drive, but there are two other regular hard drives in RAID-0 in the computer.

-Intel i7-3930K / Asus P9X79 Pro
-16GB G.Skill 1866MHz
-120GB Kingston HyperX SSD / 2x320GB RAID-0 Samsung Spinpoint F4 / 1TB Samsung Spinpoint F3
-EVGA GTX 570
-AHCI and SMART enabled in BIOS

It's gonna be a real pain if I have to take the SSD out every time I want to update the firmware. Any ideas as to why this is happening?

 

[Burner27]

I assume you had it connected to your Intel SATA ports as per your post. Did you happen to set the controller to AHCI or IDE mode prior to trying to flash the drive with the updater? I do not think it is recommended that you try to update FW on SSDs while the controller is in RAID MODE. It doesn't matter if the the SSD isn't in a RAID array. The fact that the controller was in RAID MODE could be the source of your issue.

 

[equazcion]

Thanks for the response --

The drive is connected to an Intel port, and according to BIOS, the controller is in AHCI mode (although there seems to only be a single setting for that, at least on the BIOS page I'm looking at -- no mention of Marvell vs. Intel controllers). I did verify using the manual diagram that the port I'm using is Intel.

- The firmware updater is still not detecting an SSD drive.
- Kingston's "toolbox" utility isn't detecting it either. I discovered it has a log file that shows "Failed to get Identify Data" for 6 drives.
- SSDLife still can't see the drive.
- CrystalDiskInfo only shows the RAID drive, but no SSD, and no 1TB drive.
- Defraggler sees everything, and it even says it detects the boot drive as being an SSD. This is the first time any software has shown that there's an SSD in my computer. (I know not to actually run defrag on an SSD -- I just wanted to see what it would detect).

 

[groberts101]

I can only speak of what OCZ requires for their SF drives but the requirements for that drive should be very similar if not identical due to the SF specific toolbox coding which comes from Sandforce.

If you have an HDD raid array on the Intel port?.. then that chip is set to raid mode which will cause the non-detection issue you're seeing here.

There are a couple of workarounds that can be used. First would be to install W7 to another HDD which resides on another sata chip on the mobo. This enables separate bios sata modes to be set without affecting booting of the OS volume while still allowing you to change the Intel chips sata mode to ahci for enabling the drive to be detected.

Another method would be to just keep the drive on the Intel chip(where it should be installed for best results anyways).. and see if the drive will still boot to the OS after changing from raid to ahci mode in the bios. Many systems will still boot successfully since ahci/raid capable drivers are used by default for all Intel based/W7 systems. Otherwise you may need to un-install the Intel drivers to help enable a successful boot when the sata mode is changed to flash the firmware. The HDD raids data will still remain intact as long as you do not write to the individual drives while the sata mode is temporarily changed.

You really need to read the manual and be sure what ports go to what chip to get all this stuff right. If that toolbox is like many others.. then the Marvell chip will work so long as you keep the default msahci drivers running that OS volume due to the Marvell drivers causing scsi related issues.

PS. you might want to ask Kingston if they have similarly used Linux based utilities that can be run off a bootable USB stick as well. That's how many others are also doing it and makes doing it on a laptop/single OS drive based system much easier since you simply change the boot order for the utility to be run off the USB stick. That tool also makes the need to change the bios sata mode unnecessary as well.

 

[Burner27]

Thanks for the response --

The drive is connected to an Intel port, and according to BIOS, the controller is in AHCI mode (although there seems to only be a single setting for that, at least on the BIOS page I'm looking at -- no mention of Marvell vs. Intel controllers). I did verify using the manual diagram that the port I'm using is Intel.

- The firmware updater is still not detecting an SSD drive.
- Kingston's "toolbox" utility isn't detecting it either. I discovered it has a log file that shows "Failed to get Identify Data" for 6 drives.
- SSDLife still can't see the drive.
- CrystalDiskInfo only shows the RAID drive, but no SSD, and no 1TB drive.
- Defraggler sees everything, and it even says it detects the boot drive as being an SSD. This is the first time any software has shown that there's an SSD in my computer. (I know not to actually run defrag on an SSD -- I just wanted to see what it would detect).

You said you have 2 x 320GB drives in RAID and ALL your other drives on the INTEL ports. If that is the case, your CONTROLLER is in RAID mode and (like Groberts101 and I stated) may be causing this issue. Try setting the controller to AHCI or IDE mode and run the updater (assuming it runs from a CD/DVD/USB stick) and see if it runs. Don't switch to IDE or AHCI mode and try to boot back into windows without doing the reg hacks to enable those drivers or you won't be able to boot into windows.

 

[DooKey]

I have the same problem with my ASUS X79 motherboard. I think it has to do with the Intel RSTe software making the drives appear as SCSI.

 

[Burner27]

I have the same problem with my ASUS X79 motherboard. I think it has to do with the Intel RSTe software making the drives appear as SCSI.

When I had the 120GB HyperX I was able to run the updater without issues. I have a P67 Motherboard though. I did have the IRST software installed but my controller was set to AHCI mode not RAID like the OP

The controller is set to RAID mode according to the OP - that's why it shows up as SCSI in Device Manager.

 

[equazcion]

I have the same problem with my ASUS X79 motherboard. I think it has to do with the Intel RSTe software making the drives appear as SCSI.

It turns out that this was my problem^

I've reinstalled Windows 17 times in the past 24 hours trying to figure this out. I disabled the Marvell controller in BIOS altogether, and dismantled my RAID drive, but the issue was still occurring.

I found I was able to run the firmware updater successfully on a fresh Windows install with no drivers though -- so I installed one at a time with a reboot in-between, and viola, the Intel Rapid Storage Technology driver was indeed the culprit.

HOWEVER, uninstalling Rapid Storage does NOT fix the problem! I tried uninstalling everything, including from Device Manager, and the firmware updater would still not pick up the drive. I had to reinstall Windows (again) and skip the RST install. Everything seems to be working now.

I was going to experiment with the latest RST driver from Intel's site (I was using the Asus driver disc until now), but the downloaded one says I don't meet the minimum requirements. Not sure what that's about (Win7 x64 English). I hope I don't need that driver at some point in the future.

You said you have 2 x 320GB drives in RAID and ALL your other drives on the INTEL ports. If that is the case, your CONTROLLER is in RAID mode and (like Groberts101 and I stated) may be causing this issue.

The RAID drives were on the Marvell controller (everything ELSE were on Intel ports), so I don't think that would've helped, if I understand your suggestion correctly. BIOS shows the SATA ports are in AHCI mode, but again there's no mention of which controller it's referring to. Since I disabled the Marvell controller, and this still says the ports are in AHCI mode, I'm assuming that means the Intel controller is set to AHCI.

Thanks so much to everyone who replied. I'm still confused as to why this happened, but hopefully others can avoid it in the future now.

 

[razel]

I found I was able to run the firmware updater successfully on a fresh Windows install with no drivers though

I wonder if booting into Safe Mode would have worked the same.

 

[equazcion]

I wonder if booting into Safe Mode would have worked the same.

I probably should've tried that 🙂 but I wouldn't be comfortable with that as a permanent fix. If Windows isn't recognizing that the drive is SSD during my regular use, it might not be implementing TRIM and other SSD-saving tweaks...

 

[groberts101]

you simply had a driver issue as you found out the hard way. I have no detection issues with the 11.5 series drivers on my systems. And I often see users who have no issues with 1 particular driver revision and then have issues with the next newer or older revision. Welcome to life with Sandforce.

This is also very typical since Sandforce writes the base code to all the various implementations of the toolbox. Mfgrs just tweak the GUI code to make it look like their own personal utility, is all.

 

[razel]

Oh I agree... NO way can you use a PC in safe mode. 🙂 I meant boot into Safe Mode for the firmware upgrade. Of course that assumes the firmware software will run in Safe Mode. Maybe next time. Glad you got it working.

 

[DooKey]

When I had the 120GB HyperX I was able to run the updater without issues. I have a P67 Motherboard though. I did have the IRST software installed but my controller was set to AHCI mode not RAID like the OP

The controller is set to RAID mode according to the OP - that's why it shows up as SCSI in Device Manager.

I have the problem and my controller is set as AHCI. I may try the safe mode route to see if that helps.

 

[Burner27]

Groberts101-

Do you also have an x79 chipset motherboard? I am wondering if it is an issue relating to that?

 

[groberts101]

Groberts101-

Do you also have an x79 chipset motherboard? I am wondering if it is an issue relating to that?

not yet. But I can tell you that there are various limitations to the toolbox's. Like I said above.. some drivers will give no issue.. and some will. RSTe is known to cause some issues and should be avoided due to slower performance anyways.

PS. according to others.. this platform is the same as the previous ones in that you simply let Windows use its default MSAHCI driver to run the show until such time after the install that you would want to install RST's. If that's truly the case?(and I do believe I've seen a few doing just that).. then those having these issues just need to uninstall the RST/e drivers(which will then revert to the MSAHCI after reboot) to make the toolbox detect the drives. Do your thing.. and reinstall the preferred drivers after the fact. Although it's said to be the same with raids on this platform.. I do know that many I've seen have had to F6 the RST/e drivers at install to even make the array visable for the OS to even see it for the install. So, apparently there is yet another mish-mash of mfgr injected variables. Windows will "usually" tell you what you can.. and cannot do.

 

[Burner27]

I am currently using the 11.0 IRST drivers and have had peformance gains over the MS drivers and not one issue updating FW on my SSDs - FW update process for mine are done outside any OS so that is probably why I have no issues....LOL.

What's the difference between IRST and RSTe?

 

[tekkitan]

Mine is also not detected in Windows 7 x64. I have an X79 chipset, all Intel SATA3 ports, AHCI mode enabled on all ports. I would really hate to reinstall, so I am going to try and see if I can update it from a Linux live CD. If not, then I will try resizing my 2TB drive and installing Linux on it and dual booting it. Hopefully then it will see it 🙂

 

[tekkitan]

I was actually able to uninstall the Intel storage drivers in device manager and have it detect the drive using the generic SATA AHCI Windows driver. I just had to reboot about 3-4 times.

 

[2Many]

I'm having the same issue. The Kingston software won't see the SSD; so I can't update the firmware on the drive. My BIOS see's it, Win 7 see's it. Running from it. I have the 501A firmware. Have the new 503, but I can't get it on. Drive is in IDE mode, no RAID setup at all. My MB is a bit older and doesn't have ACHI as an option. I will try from safe mode like some above suggested. Here are my specs. I have the latest BIOS for my board.

I also have issues where Win 7 will lock up solid from 20-40 seconds avg, then free up. The HD light is basically lit up solid. Anyone have any ideas on how to fix that?
Below is my HW list from:


SiSoftware Sandra

ID
Host Name : XXXXXXXX
Workgroup : XXXXXX

Computer
Model : XFX Nforce 680i LT
Serial Number : 1
Chassis : XFX Desktop
Mainboard : XFX Nforce 680i LT
Serial Number : 1
BIOS : Phoenix Technologies, LTD 6.00 PG 09/04/2008
Total Memory : 8GB DIMM SDRAM

Processors
Processor : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz (4C 2.4GHz, 2x 4MB L2)
Socket/Slot : FC LGA (Socket T)

Chipset
Memory Controller : nVidia C55 Host Bridge 4x 267MHz (1GHz)
Memory Controller : nVidia MCP55 Memory Controller 2x 1.34GHz (2.67GHz), 8GB DIMM SDRAM 800MHz

Memory Module(s)
Memory Module : G.Skill F2-6400CL5-2GBNT 2GB DIMM DDR2 PC2-6400U DDR2-800 (5-5-5-15 3-24-6-3)
Memory Module : G.Skill F2-6400CL5-2GBNT 2GB DIMM DDR2 PC2-6400U DDR2-800 (5-5-5-15 3-24-6-3)
Memory Module : G.Skill F2-6400CL5-2GBNT 2GB DIMM DDR2 PC2-6400U DDR2-800 (5-5-5-15 3-24-6-3)
Memory Module : G.Skill F2-6400CL5-2GBNT 2GB DIMM DDR2 PC2-6400U DDR2-800 (5-5-5-15 3-24-6-3)

Video System
Monitor/Panel : Philips 200WB (20inch LCD MONITOR 200WB7) (1680x1050, 20.0")
Monitor/Panel : Philips Generic PnP Monitor (1600x1200, 21.7")
Video Adapter : NVIDIA GeForce GTX 560 SE (288 SM5.0 1.55GHz, 1GB 3.83GHz 192-bit, PCIe 2.00 x16)
Video Adapter : NVIDIA GeForce GTX 560 SE (288 SM5.0 1.55GHz, 1GB 3.83GHz 192-bit, PCIe 2.00 x16)

Graphics Processor
OpenCL GP Processor : NVIDIA GeForce GTX 560 SE (288SP 6C 1.55GHz, 1GB 3.83GHz 192-bit)
Compute Shader Processor : NVIDIA GeForce GTX 560 SE (288SP 1.55GHz, 1GB 3.83GHz 192-bit)
CUDA GP Processor : NVIDIA GeForce GTX 560 SE (288SP 6C 1.55GHz, 1GB 3.83GHz 192-bit)

Storage Devices
Seagate ST3300620A (300GB, ATA100, 3.5", 16MB Cache) : 279GB (D🙂 (G🙂
KINGSTON SH103S3120G (120GB, SATA600, SSD) : 112GB (C🙂
Seagate ST3500630NS (500.1GB, SATA150, 3.5", 16MB Cache) : 466GB (F🙂
Seagate ST31500341AS (1.5TB, SATA300, 3.5", 7200rpm) : 1TB (E🙂
PLEXTOR DVDR PX-740A (1.7MB, ATAPI, DVD+-RW, CD-RW, 2MB Cache) : 2MB (H🙂

Logical Storage Devices
Hard Disk (D🙂 140GB (NTFS) Seagate ST3300620A (300GB, ATA100, 3.5", 16MB Cache)
System Reserved : 100MB (NTFS)
BACKUP (F🙂 466GB (NTFS) Seagate ST3500630NS (500.1GB, SATA150, 3.5", 16MB Cache)
DATA (E🙂 1TB (NTFS) Seagate ST31500341AS (1.5TB, SATA300, 3.5", 7200rpm)
VISTA (G🙂 140GB (NTFS) Seagate ST3300620A (300GB, ATA100, 3.5", 16MB Cache
Hard Disk (C🙂 112GB (NTFS) KINGSTON SH103S3120G (120GB, SATA600, SSD)
SYSTEM_UTILS (H🙂 2MB (CDFS) PLEXTOR DVDR PX-740A (1.7MB, ATAPI, DVD+-RW, CD-RW, 2MB Cache)

Peripherals
LPC Hub Controller 1 : nVidia MCP55 LPC Bridge
LPC Legacy Controller 1 : Winbond W83627DHG
Audio Device : nVidia MCP55 High Definition Audio
Audio Codec : Realtek Semi Realtek 885 High Definition Audio
Audio Device : EVGA GF110 High Definition Audio Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
Disk Controller : nVidia C55 Memory Controller
USB Controller 1 : nVidia MCP55 USB Controller
USB Controller 2 : nVidia MCP55 USB Controller
FireWire/1394 Controller 1 : nVidia TSB43AB22 1394a-2000 OHCI PHY/Link-Layer Controller
SMBus/i2c Controller 1 : nVidia MCP5 SMBus 1
SMBus/i2c Controller 2 : nVidia MCP5 SMBus 2

Printers and Faxes
Printer : Microsoft XPS Document Writer (600x600, Colour)
Fax : Microsoft Shared Fax Driver (200x200)
Printer : Canon Inkjet iP5200 (600x600, USB, Colour)

Network Services
Network Adapter : NVIDIA nForce 10/100/1000 Mbps Ethernet (Ethernet, 1Gbps)

Operating System
Windows System : Microsoft Windows 7 Ultimate 6.01.7601 (Service Pack 1)
Platform Compliance : x64

Windows Experience Index
Current System : 7.1

 

[jarablue]

Are you guys looking under disk drives in device manager or IDE ATA/ATAPI controllers? With the latest Intel RST drivers under disk drives mine is using the MS driver but under IDE ATA/ATAPI controllers it is using the Intel AHCI driver. Just wanted to make sure what I'm supposed to be looking at. My motherboard is a Asus Z87-A and 840 Pro ssd.