Hard-lock on starting Aida64 Extreme

[Thomas_Theobald]

New user here.

Been working on putting a monitor up on a 7" HDMI screen on my Windows 10 desktop.  Got the monitor built, no problem there.  However, I have had 4 hard lockups in the last day and a half with Aida starting up.  Two of those lockups resulted in a kernel corruption requiring repair from USB stick, because the system required a physical power-down to return it to operation.

This is somewhat shameful condition for released software.  However, I figured I'd ask about to see if this was a known issue with a possible workaround before going for a refund.

Seems this happens when Aida64 is starting up, and oddly enough may be happening when I am accessing my non-boot drive which happens to be an iSCSI mount from a NAS (which also happens to be the drive on which Aida is installed).  

Anyone have any experience with something like this?

Thanks - 

  T

[Thomas_Theobald]

Okay, two more hard lockups.  I've uninstalled Aida.  This is f'ing irresponsible.

  T

[Fiery]

8 hours ago, Thomas_Theobald said:

Okay, two more hard lockups.  I've uninstalled Aida.  This is f'ing irresponsible.

  T

I'm wondering if the issue happens if you have no NAS mounted... But I understand if you already gave up on AIDA64

[Thomas_Theobald]

53 minutes ago, Fiery said:

I'm wondering if the issue happens if you have no NAS mounted... But I understand if you already gave up on AIDA64

Answering from my work PC - it can't happen without the NAS being mounted.  A64 is installed on drive "D:", which is the iSCSI hosted storage.  Any attempt to run it while dismounted will result in a "not found" or "host not connected" message.  

I didn't necessarily give up, I'm just insanely frustrated with it. I am very close to giving up, though.  I need my desktop to be running, which is why I uninstalled it.  The constant lockups and having to use rescue media introduces too much risk to keep it going there - sooner or later the rescue won't work and I'll end up having to pull files from backup.  I just don't have that kind of time to dedicate to dealing with that kind of risk.  

I recognize that I have an outlier hardware setup, so it may not have been something that was tested for in QA, but the Enterprise version seems like it would have been tested on VMs or other forms that use iSCSI.   

If it helps at all, this is a Win10 box, the "C:" drive is a Samsung SATA 2.5" SSD, "D:" is a Synology NAS offering a 3TB iSCSI (single-connection) storage.  They are connected over 10Gb ethernet.  There are a few other drives which are unused internal spinners and one add'l SSD used as generally as a write-seldom read-often repository. 

Among the various crashes, I have a sneaking suspicion that when Aida is loading and connecting to do the reads in order to keep the sensor panel up to date, if anything else accesses the iSCSI drive, the system locks up.  I only observed this when I went to connect my email (the outlook .pst is on "D:"), and also when loading a 3D design app.  The other instances, I don't know what else was running, I hadn't invoked anything myself.  

I don't know what to really do here.  I'm concerned if I re-install I'm putting my data at risk.

  T