09.05.2024, 16:18
Sprache ändern
Registrieren
Anmelden
Sie sind nicht angemeldet.
Lieber Besucher, herzlich willkommen bei: Aqua Computer Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.
- 1
- 2
Dienstag, 8. März 2022, 00:29
So, after a bunch of screwing around (such as installing Win10 on a secondary drive and later updating my BIOS to 4703 with AGESA 1206) I found a rather bizarre fix to get the HFN working under Win7: disabling the Aquasuite Service fixes (????) the dropout issue. Re-enabling it causes the HFN to drop out again.
Dienstag, 8. März 2022, 10:12
So, after a bunch of screwing around (such as installing Win10 and updating my BIOS to 4703 with AGESA 1206) I found a rather bizarre fix: disabling the Aquasuite Service fixes (????) the dropout issue. Re-enabling it causes the HFN to drop out again.
Can you clarify something please:
Are the High Flow Next parameter Values dissapearing from
1) HWINFO Only
2) Aquasuite Only
3) Both at the same time?
Dienstag, 8. März 2022, 14:06
With the service on HWiNFO sensors won't detect the HFN at all, Aquasuite and Device Manager go crazy and does this:So, after a bunch of screwing around (such as installing Win10 and updating my BIOS to 4703 with AGESA 1206) I found a rather bizarre fix: disabling the Aquasuite Service fixes (????) the dropout issue. Re-enabling it causes the HFN to drop out again.
Can you clarify something please:
Are the High Flow Next parameter Values dissapearing from
1) HWINFO Only
2) Aquasuite Only
3) Both at the same time?
https://www.youtube.com/watch?v=ozwROcRU2ks
Aquasuite X.50, Windows 7 Enterprise. Funny you mention you're running a C8DH Speedy-VI, my main system also has one and that's where the D5 Next will be going into in the near future.
Dienstag, 8. März 2022, 18:16
Your video shows that things are definitely messed up.With the service on HWiNFO sensors won't detect the HFN at all, Aquasuite and Device Manager go crazy and does this:
https://www.youtube.com/watch?v=ozwROcRU2ks
Aquasuite X.50, Windows 7 Enterprise. Funny you mention you're running a C8DH Speedy-VI, my main system also has one and that's where the D5 Next will be going into in the near future.
The video shows that you are running AQS X.50 but your HFN is constantly connecting and disconnecting. When its connected, AQS is saying it needs a firmware update. AQS X.50 included a firmware update for the HFN (v1014). When you updated to X.50 were you able to get this firmware update installed into the HFN? If no, can you go back to X.49 and try updating AQS and the HFN firmware again? I am thinking that AQS updated to X.50 but the firmware update failed for whatever reason. Now you have a HFN running old firmware that is not compatible with AQS X.50. That or the HFN is defective.
Next, what about the D5 Next? I don't see it in AQS in your video. Have you tried connecting it? If yes, does it do the same thing as the HFN? When you installed AQS X.50, did your D5 Next firmware update to v1021? If yes, does it work OK? If no, does it constantly connect and disconnect like the HFN?
Finally, the other variable here is Windows. You said in an earlier post that you had updated to Windows 10, but in this post you say you are running Windows 7 Enterprise. Sebastian has already said that Windows 7 is not supported. If you want help from Aquacomputer, I think you need to be running Windows 10 as they are not going to spend their time troubleshooting the issue when you are running an OS that they have already said is not supported.
Dienstag, 8. März 2022, 20:14
tl;dr: main SSD has Win7, installed Win10 Enterprise on secondary SSD, upgraded FW on HFN, switched back to Win7, disabled AS service, got bored, shutdown PC for the night, fast forward a day or so, found out my HFN works while I was testing a GPU OC.Your video shows that things are definitely messed up.With the service on HWiNFO sensors won't detect the HFN at all, Aquasuite and Device Manager go crazy and does this:
https://www.youtube.com/watch?v=ozwROcRU2ks
Aquasuite X.50, Windows 7 Enterprise. Funny you mention you're running a C8DH Speedy-VI, my main system also has one and that's where the D5 Next will be going into in the near future.
The video shows that you are running AQS X.50 but your HFN is constantly connecting and disconnecting. When its connected, AQS is saying it needs a firmware update. AQS X.50 included a firmware update for the HFN (v1014). When you updated to X.50 were you able to get this firmware update installed into the HFN? If no, can you go back to X.49 and try updating AQS and the HFN firmware again? I am thinking that AQS updated to X.50 but the firmware update failed for whatever reason. Now you have a HFN running old firmware that is not compatible with AQS X.50. That or the HFN is defective.
Next, what about the D5 Next? I don't see it in AQS in your video. Have you tried connecting it? If yes, does it do the same thing as the HFN? When you installed AQS X.50, did your D5 Next firmware update to v1021? If yes, does it work OK? If no, does it constantly connect and disconnect like the HFN?
Finally, the other variable here is Windows. You said in an earlier post that you had updated to Windows 10, but in this post you say you are running Windows 7 Enterprise. Sebastian has already said that Windows 7 is not supported. If you want help from Aquacomputer, I think you need to be running Windows 10 as they are not going to spend their time troubleshooting the issue when you are running an OS that they have already said is not supported.
Mittwoch, 9. März 2022, 08:58
can you go back to X.49 and try updating AQS and the HFN firmware again? I am thinking that AQS updated to X.50 but the firmware update failed for whatever reason. Now you have a HFN running old firmware that is not compatible with AQS X.50. That or the HFN is defective.
Therein lies another problem. Due to the way the installer works you can only install the current version (it checks on line during the install) and it is not possible to roll back to an older version (unless AC decide there is a major issue and change the download the installer fetches from)
Freitag, 11. März 2022, 00:12
Oh I was not aware of that. I usually update from within AQS rather than download the new version. I have never tried to regress (never had any reason to), so I did not know that it won't let you, even if you have a setup EXE of an older version. Due to this restriction, I am not sure what to advise OP. His video shows that there is something very wrong and it looks to me like every time the the HFN connects, AQS says it needs a firmware update, but it won't stay connected long enough to do a firmware update. I am still wondering if his D5 Next is also doing this on the system running Windows 10. If it is, then it's most likely some system level problem. If the D5 Next connects and works fine, then maybe the HFN is defective and its time for an RMA. I don't know what else to suggest.
can you go back to X.49 and try updating AQS and the HFN firmware again? I am thinking that AQS updated to X.50 but the firmware update failed for whatever reason. Now you have a HFN running old firmware that is not compatible with AQS X.50. That or the HFN is defective.
Therein lies another problem. Due to the way the installer works you can only install the current version (it checks on line during the install) and it is not possible to roll back to an older version (unless AC decide there is a major issue and change the download the installer fetches from)
Freitag, 11. März 2022, 00:48
Oh I was not aware of that. I usually update from within AQS rather than download the new version. I have never tried to regress (never had any reason to), so I did not know that it won't let you, even if you have a setup EXE of an older version. Due to this restriction, I am not sure what to advise OP. His video shows that there is something very wrong and it looks to me like every time the the HFN connects, AQS says it needs a firmware update, but it won't stay connected long enough to do a firmware update. I am still wondering if his D5 Next is also doing this on the system running Windows 10. If it is, then it's most likely some system level problem. If the D5 Next connects and works fine, then maybe the HFN is defective and its time for an RMA. I don't know what else to suggest.
can you go back to X.49 and try updating AQS and the HFN firmware again? I am thinking that AQS updated to X.50 but the firmware update failed for whatever reason. Now you have a HFN running old firmware that is not compatible with AQS X.50. That or the HFN is defective.
Therein lies another problem. Due to the way the installer works you can only install the current version (it checks on line during the install) and it is not possible to roll back to an older version (unless AC decide there is a major issue and change the download the installer fetches from)
me personally I would probably ferret out my spare 256Gb SSD, disable the current NVME boot drive and do a clean W10/W11 install on the SSD followed by a clean install of AQS and see what happens.
Freitag, 11. März 2022, 18:51
I think OP may have got it working. In his last post he says he installed Windows 10 Enterprise on another drive, (assume) installed AQS, connected his HFN and updated the firmware. So it sounds like the HFN was connecting OK with Win 10 Enterprise. Then he put it back into a Win 7 build and disabled the AQS service. OP does not mention why he disabled AQS service in Win 7 but I assume he was still having problems with the HFN and Win 7. Then he said he shut down for the night, then found out the HFN was working while doing a GPU overclock. So I think this means that the HFN worked fine with the Win 10 Enterprise OS, then started working with the Win 7 OS. I re-read this thread and don't see any statement that the HFN did not work with Win 10 so I think all of OP's problems were due to trying to run AQS in Win 7, which Aquacomputer has stated is not supported.
me personally I would probably ferret out my spare 256Gb SSD, disable the current NVME boot drive and do a clean W10/W11 install on the SSD followed by a clean install of AQS and see what happens.
Samstag, 12. März 2022, 00:46
I'm tired as shit so I will keep this short for now:I think OP may have got it working. In his last post he says he installed Windows 10 Enterprise on another drive, (assume) installed AQS, connected his HFN and updated the firmware. So it sounds like the HFN was connecting OK with Win 10 Enterprise. Then he put it back into a Win 7 build and disabled the AQS service. OP does not mention why he disabled AQS service in Win 7 but I assume he was still having problems with the HFN and Win 7. Then he said he shut down for the night, then found out the HFN was working while doing a GPU overclock. So I think this means that the HFN worked fine with the Win 10 Enterprise OS, then started working with the Win 7 OS. I re-read this thread and don't see any statement that the HFN did not work with Win 10 so I think all of OP's problems were due to trying to run AQS in Win 7, which Aquacomputer has stated is not supported.
me personally I would probably ferret out my spare 256Gb SSD, disable the current NVME boot drive and do a clean W10/W11 install on the SSD followed by a clean install of AQS and see what happens.
Win7: needs AQS service disabled.
Win10: everything works somehow.
In other news, I built a open loop in my main also running Win7 and guess what: the D5 Next also has disconnection issues. 3950X/C8DH on latest BIOS. Disabled the AQS service and everything is fine somehow.
Samstag, 12. März 2022, 14:32
Because Win7 still gets updates? https://forums.mydigitallife.net/threads…ribution.45005/Well, why don't you try WinXP instead?!
Just kidding. I wonder why people are insisting on using outdated OS versions if it even causes them so many headaches.
That, it's got a sane UI, "net stop wuauserv" stops updates dead in it's tracks and I don't care about new games since it's all politicized bullshit or outright broken releases these days.
@topic: After disabling the AQS service everything works somehow, both on my old and main system with AC stuff. (old: HFN, new: D5 Next)
- 1
- 2
Ähnliche Themen
-
English forum »-
high flow NEXT - The next generation of flow sensors
(26. August 2020, 11:17)
-
- English forum »
-
Feature Request: Select high flow NEXT under flow sensor in OCTO
(27. Januar 2022, 06:17)
-
- English forum »
-
New to Aquacomputer Product Ecosystem - Need Advice
(27. März 2021, 02:32)
-
- English forum »
-
Want to see pump info on aquaero 6 touch
(27. August 2016, 17:00)