Issues with SATA port expansion board with PCIE connection

Hello. I have found an bug in this disk monitoring program that is not present in other similar programs.

A few days ago I bought a SATA port expansion board for PCIE connection. To be more specific, this model:

SSU "SU-SA3034A" (PCIE 3.0 x1 to SATA 3.0):

This board uses the "ASM1064" controller chip:

With this driver:

- "Asmedia ASM-106x Sata 6G controller Drivers Version 3.3.3.0 WHQL" (Windows 7 x64):

- It also has for "Windows 10 x64", but it is not my case:

I tried this on an old PC. Gigabyte GA-P35-DS3L motherboard with Q6600 CPU, 8GB RAM, with Windows 7 Professional x64.

The expansion board works perfectly with the driver and the drive behaves as if it were native. But I noticed that this disk monitoring program does not detect the drives connected to the expansion board. However, "AIDA64" disk monitoring and disk monitoring inside "Auslogics Defrag Ultimate" defragmenter can see the disk and monitor it normally.

I am notifying you of this because I have a hunch that this problem is fixable.
 
Please attach the HWiNFO Debug File so I can analyze the details.
Well, I updated HWiNFO to the latest version (7.24) and now this happens...

97XCEuf5_o.png

System configuration scan...
Detection of ATA/SCSI Drivers...


...and from there it does not advance. The process gets stuck in memory, and not even a kill process to "HWiNFO64.exe" can close it.
I don't see any log files in the program directory.
 

Martin

HWiNFO Author
Staff member
The problem seems to be with the Hitachi HDS721616PLA380 drive. When HWiNFO queries the ASMedia driver for its SMART data the drive hangs.
So the problem seems to be similar to:
Try to replace the ASMedia driver with the generic SATA driver in Windows.
 
The problem seems to be with the Hitachi HDS721616PLA380 drive. When HWiNFO queries the ASMedia driver for its SMART data the drive hangs.
So the problem seems to be similar to:
Try to replace the ASMedia driver with the generic SATA driver in Windows.
HWiNFO starts and recognizes the drive without the drivers with the PCIE/SATA adapter. But Windows boot is extremely slow, and Device Manager shows an unknown device item, which should be the missing storage controller. When I refresh Device Manager Windows freezes for a few seconds.
Windows doesn't seem to register the generic drivers for the adapter it uses and loads them on every startup. It is very annoying and makes the system unstable.
I leave attached the debug file started with the generic drivers.

I think using the generic drivers is not the way to go. HWiNFO should have an alternative algorithm to recognize drives via PCIE interface. I have used this same drive (Hitachi HDS721616PLA380) with a USB/SATA adapter and it worked with HWiNFO without any problems.
As I said at the beginning, AIDA64 and Auslogics Defrag Ultimate have no problems with accessing the drive's ATA and SMART via PCIE.
 

Attachments

  • HWiNFO64 (generic driver).DBG
    423.9 KB · Views: 1
Try to enable SMART in BIOS.
The motherboard has this function:
HDD S.M.A.R.T. Capability
Enables or disables the S.M.A.R.T. (Self Monitoring and Reporting Technology) capability of your
hard drive. This feature allows your system to report read/write errors of the hard drive and to
issue warnings when a third party hardware monitor utility is installed. (Default: Disabled)
There are no improvements. The problem is the same. HWiNFO freezes when scanning the disk interface. Programs were always able to access S.M.A.R.T. even if that option is disabled. I even tried the optimal stable BIOS settings.

CrystalDiskInfo doesn't crash, but it doesn't recognize the drive. The problem is in the software and not the hardware, and it's not the driver files. Otherwise, the other monitoring programs that I mention could not either.

Anyway, I'll leave you with the debug file, but it's probably similar to the first one.
 

Attachments

  • HWiNFO64 (SMART enabled).DBG
    270.8 KB · Views: 2

Martin

HWiNFO Author
Staff member
I assume that enabling SMART in BIOS had no effect on this controller as it's not embedded.
If you run some tool (e.g. AIDA64) that recognizes the drive and polls its SMART data and after that HWiNFO64, will it then go thru?
 
I assume that enabling SMART in BIOS had no effect on this controller as it's not embedded.
If you run some tool (e.g. AIDA64) that recognizes the drive and polls its SMART data and after that HWiNFO64, will it then go thru?
I tried both ways, with AIDA64 running and without it. I do not think it's that.
From what I can see in BIOS boot, that SMART function is for IDE mode. I tried in IDE mode too and it didn't make a difference either.
Original SATA ports are controlled by the motherboard chipset, that's no problem.

There seem to be problems with "SATA to PCIE" interface, not any scanning protocol seems to work.

For a moment I thought that the chipset of the motherboard could be conflicting with that of the PCIE card, but that would create a lot of instability or directly crashes.
Or that maybe with the "SATA to USB" adapter there was no problem because the chipset itself treated the drive as IDE, and the "SATA to PCIE" adapter chipset treats it as AHCI.
 

Martin

HWiNFO Author
Staff member
I know.. My point was that if HWiNFO hangs because the SMART feature is not enabled and AIDA64 works (which might enable it), then try HWiNFO64 after running AIDA64. If it will work then, it means this is the issue and I know where to look.
 
I know.. My point was that if HWiNFO hangs because the SMART feature is not enabled and AIDA64 works (which might enable it), then try HWiNFO64 after running AIDA64. If it will work then, it means this is the issue and I know where to look.
I did that and it didn't work.
 
Please try this build and let me know the result: www.hwinfo.com/beta/hwi64_725_4776.zip
If it still crashes please attach a new Debug File from this version.
Something good and something bad happened.

The good: HWiNFO opened and recognized the drive via PCIe. But it collected little data from the disk, and it doesn't seem to read your SMART.

The bad: and strange is that when I run HWiNFO with Opera browser opened, it got stuck in memory again with the message "Flushing buffers...".
 

Attachments

  • hwi64_725_4776 (TEST).zip
    49.7 KB · Views: 2

Martin

HWiNFO Author
Staff member
Wow, that's great :) Hopefully this will also fix issues with some other ASMedia controllers/drivers.
Thanks for the feedback.
 
Top