1 of 1 people found this helpful
Hello Taurothar, I see your motherboard has three SATA controllers, is the Intel® SSD 520 connected to the Marvell controller? Is this the operating system drive?
For compatibility we recommend connecting the Intel® SSD to the Intel® SATA controller. If it is the boot drive the operating system must be reinstalled after changing to a different controller.
We will investigate about this issue. Would you be able to try with the Intel® SSD connected to the Intel® SATA controller just as a test and provide the results?
Then, you can move it back to the Marvell* controller again and use an older version of Intel® SSD Toolbox in the meantime. I will send you a private message with a temporary download link.
Just bought a new 240GB Intel 335-series SSD today ("INTEL SSDSC2CT240A4").
I'm on a P6X58D-E motherboard with the latest firmware. I've tried both the SATA 2 (Intel) and SATA 3 (Marvell) connections.
The disk is empty and is just an extra disk. No OS on it.
Trying to launch the latest SSD Toolbox gives immediate BSOD 0x3D.
Any solution? I'd like to check if I have the latest firmware and such before I start using the drive (and whatever else the tool does)...
This thread indicates that an older version might work, is it possible to get a download link for that?
Windows 7 Home Premium 64-bit.
A OCZ Vertex 3 (w/OS) and some HDDs are also connected to the SATA 2 controller.
Ps: I even attempted to download a custom firmware for the motherboard that updates the Marvell bios from 126.96.36.1999 to 188.8.131.529 but it did not change anythin. The disk is now on the Intel controller as apparently the Marvell one is utter crap anyway according to my googling.
Message was edited by: Jonas Rogne Added some more info after testing some more.
Chain, it is rare that you have the issue with the SSD(s) connected to Intel® ICH10R because we identified that the error appeared when the SSD was connected to the Marvell® PCIe 9128 controller; therefore, that was the workaround.
Unfortunately we have seen (here) that using an older version of Intel® SSD Toolbox does not make a difference but we are still investigating. I believe your issue is different somehow. Does it still occur if the Intel® SSD is connected to the SATA port 0?
I have figured it out. Short version: Marvell creates utter crap and my next motherboard will not feature any of their stuff that's for sure (I often have to restart their network device as well).
If ANY drive whatsoever is connected to the Marvell controller (I had a regular HDD connected) then starting SSD Toolbox will give a BSOD 0x3D (no matter where the SSD itself is connected). I guess it happens because the toolbox is trying to ask Marvell for some disk info (god forbid)?
The workaround is to disconnect all/any drives from the Marvell 9128 controller (basically the two SATA 3-connections on the motherboard). It's also possible to completely disable it in BIOS.
I guess Asus/Marvell needs to work this out, but perhaps the Toolbox can be improved a bit in the future for other user so it takes more care around Marvell 9128.
I've completely disabled my Marvell controller now since it just causes occasional random bluescreens in Windows anyway (not 0x3D however, that's just when running the toolbox).