Jump to content
AIDA64 Discussion Forum

Elderdeekey

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Elderdeekey

  • Rank
    Member
  • Birthday 02/06/1954

Profile Information

  • Gender
    Male
  • Location
    Moscow, Russian Federation
  1. Thanks a lot for the explanation! Ref. second reading - both SSD are Samsung 970 PRO, one 512GB and the other 1TB, and it is seen from AIDA64 Gadget Items screen. On a screencapture below are both temperature readings (disk Boot C is 512GB, disk Games G is 1TB). I have no idea why those temperatures are so different (indeed #2 temperatures might be controller ones) - both SSD use radiators, 512GB one even has custom fan... Anyway, thank you very much for fast implementation and great feedback!
  2. Fiery - you did it again - it works great! 2 questions though: 1. Do you "artificially" start numbering fans from 21 or do those numbers come from GRID? 2. I've marked 2 SSD temperatures by green pen - where those come from? They are marked #2, and I do have temperature of those already... Thanks a bunch!
  3. Do you guys have plans to support NZXT Grid+ V3? Got long awaited digital fan controller but fans are not seen by AIDA64...
  4. Bottom line: The cause of games' screen freezing was/is Embedded Controller (EC) sensor support enabled at Stability screen. It might be due to my setup - I do have lots of sensors/ASUS extension card, mps etc. It might be due to my overclocking (the most recent setup is 5000 MHz CPU and 4000 MhZ RAM). Or anything else, but the fact of the matter is - as soon as I disable this support there is no freeze... Its a real pity as I'm missing a lot of information w/o this feature. And my question remains - what does this support do and how it is related with screen freeze?
  5. Test#3 Conditions: same as Test#2 but EC bank switching DISabled Results: Games freezing Test#4 Conditions: same as Test#3 but EC support DISabled Results: so far 24 hours w/o a single freeze... Could someone please elaborate what EC support does with video and why it is freezing video games??? P.S. Now I'm bringing back Aquaero in HWMon Module to see if Aida and Aquasuite could coexist peacefully...
  6. Test#1 Conditions: AXi and Corsair Link support disabled, HXi - enabled. HWMon Module Aquaero enabled. Results: Games keep freezing. Test#2 Conditions: same as above but HWMon Module Aquaero DISabled. Results: Games keep freezing. Will keep testing and reports...
  7. Thank you for suggestions. Yes, I do have HX850i and no, I do NOT have Corsair Commander. Test started, will report results soon.
  8. Nope... disabling Aquaero module didn't help - games keep freezing. I went a bit further and remove PCI bus operations support from Stability (somehow I think it is related with PCI bus) - same freeze occurs. Attaching a screencapture of current support enables in Stability section but this combo steel freezing games. Note - Aquasuite was running together with Aida64. As soon as I exit from Aida freezes are gone... I will disconnect one of MPS flow meters from USB and will report a bit later.
  9. Fiery, thanks for the attention to this issue! AquaSuite version is 2017-3.2 AquaComputer: 2 MPS, one 100, another 400 (https://shop.aquacomputer.de/product_info.php?products_id=2900). That is interesting flow meters w/o rotating parts... I'll start testing right away and will post my findings.
  10. A very strange (and intermittent) situation occurred when I played games (mostly World of Warcraft and Overwatch) - my games' screen freezes. If there was a sound it still was playing. I could switch to, say, Windows Start button menu and click on a program but program will not start. Ctrl-Alt-Del switches to its menu, I could select Task Manager but it will open with empty window. Generally speaking CPU hasn't stopped but it can't recover while game window freezed (that window looks like a screencapture and it seems GPU just stopped rendering). The only way out is soft reset with power or reset button. I can't recall when exactly it started and, as I wrote above, it is intermittent - it could happened in 10 sec after I've started the game or in like 30 mins. But it always happened several time during the gameplay. Interesting enough that all tests I've run (including AIDA System Stability one) never froze the screen and I didn't have even a single BSOD. The system itself is custom made, it is ASUS Maximus X Formula with i7 8700K @ 5000Mhz, 16Gb Corsair DDR4 @ 3400MHz, ASUS GTX 1070 (not overclocked), M.2 SSD Samsung 960 Evo and 2 water cooled loops (one for CPU and one for GPU). I've been fighting with this situation for about a month. I went away from overclocking and played my games with CPU/memory and motherboard default settings - it didn't help. I've used old NVIDIA drivers (like 389.xx ones) - same story. My best guess was/is that it started when I've added second flow meter from Aqua Computers but I'm not 100% sure, so I've uninstalled their aquasuite SW that visualizes sensors' data. For about an hour I thought I found the reason... but I was wrong - games were freezing again but not that often. In the end I decided to uninstall AIDA... and those freezes are gone... I know there is a long list of devices in AIDA Stability section where it is written "may cause system lockup in rare cases" - could one of those be the source of my trouble? Is there any logging ability to find out what is causing those freezes when AIDA runs? Perhaps there is something built in into AIDA so I could trace it to? I like AIDA very much as I'm that kind of person who is watching a lot of parameters of my complicated built (mostly temperatures, fan speeds and frequencies) and I really do not want not to use it any more. Any hints/suggestions/advice are more than welcome!
  11. I finally got the second Aqua-Computer Flow sensor MPS flow 400, which is seen as Flow sensor in AIDA64, and which shows flow as LPH. It takes data from Aqua software, aka Aquasuite. Sensor is connected to motherboard via USB2. AIDA64 takes Flow data from Aquasuite and shows it as LPH within its sensors. So conversion is done by Aqua SW from the data received from their own sensor. To compare flow data I could rely on my water pump RPM only - it always was/is around 2200 RPM from the very beginning. Now let's see what data I've got: - my previous Koolance flow meter, connected to WATER_FLOW header, was showing 36 L/M in BIOS (see 1st screencapture) - unrealistically high value, while AIDA64 was showing ~1300 RPM. If connected to any fan header it was showing 1200-1250 RPM; - my today's flow meter from Aqua (with the same water pump RPM) shows ~100 LPH. It is very realistic number as D5 PWM from EKWB is capable to produce up to 400 LPH under full load, which is ~4800 RPM (and my loop has low flow resistance). In my particular case Aqua sensor shows ~330 LPH when pump is around 4800 RPM. It could be calibrated more precisely but my point is - ASUS has made WATER_FLOW header but didn't specify what flow meters should/could be connected to this one. It doesn't take into consideration the internal diameter of your tubes etc. That makes me think this is rather marketing feature of this motherboard than a precise tool you could rely on for water flow measurement in flow units (L/M or L/H). If you need such tool - buy flow meter from Koolance (with appropriate LCD and HW converter, so you will see flow in LPH) or Aqua one. The measurement through WATER_FLOW header depends on what flow meter you connect there and since you can't specify which one you have connected (ASUS BIOS doesn't have such feature) as well as diameter of your tubes and/or other parameters, BIOS data might not be realistic and definitely are not precise whatever formula ASUS is using for conversion. Bottom line - after second thought I agree with Fiery - no need to convert this header info in AIDA from RPM to LPH - the data might not be correct... Let's leave it as such - RPM
  12. Just to add - according to asus support answer the conversion RPM into flow units is done by using this approach - https://www.wou.edu/las/physci/taylor/g322/flow_meter_velocity_conversion_chart.pdf
  13. Fiery, great job! Yes, "Water Flow" as cooling fan is visible now. Also, as a free beer, I've also got 2 sensors from Aquasuite visible as well: 1) - the real flow meter (they call it Aqua-Computer Flow sensor MPS flow 100, it is connected via USB to motherboard) and 2) - it's internal temperature sensor. Both wasn't visible before Well, as you told before, "water flow" header is visible as cooling fan... and so it shows RPM, not L/min or L/hour the way ASUS BIOS shows it at monitoring page (please see a screencap below): I do know there is a simple math in conversion from RPMs to LPH or LPM (or even simply rename RPM into flow measurement) as I still need it that way... It seems like it shows it as ml/min (it is close to my 70 LPH for main loop w/o workload). So could it be possible to show it as a real flow units? P.S. Interesting enough that Aquasuite sensor is seen as Flow#1 and shows flow in correct format 56.8 LPH
  14. Actually I was eager to see if that helps and made that simple loop right away - as you may see below this is EKWB DDC PWM pump with the simplest flow meter from Barrow. Coolant rotates propeller which sends interrupts via 3-pin cable to fan's header on mother board. This cable was attached to W_FLOW header there. This is Flow Rate reading in BIOS: To my unfortunate nothing has changed since my first try - still no Water Flow Fan or alike in the list of sensors... I'm using 5.95.4557 Beta version and have attached dump files below from this simple test. Hope you could find something that prevents AIDA to see that bloody Flow Rate Thanks! ecdump2.txt isasensordump2.txt smbusdump_full2.txt
×
×
  • Create New...