Jump to content

tistou77

Members
  • Posts

    454
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by tistou77

  1. It may be "read" from the device manager I noticed that it was reversed too In the SMART Dump, it's the EVO on disk 0 and the Pro on disk 1 While with Diskpart, it's the Pro on disk 0 Really weird Windows10 Thanks
  2. Hello I have 2 Samsung NVMe SSDs (960 Pro and EVO) I noticed that it is the disc 1 (EVO) which is the 1st displayed in the list, and the disc 0 (Pro) in 2nd I have to reverse the disks and I have that Disk 0 : 960 Pro / Disk 1 : 960 EVO Disk 0 : 960 EVO / Disk 1 : 960 Pro It's not important, but it will be possible to have the disc 0 first, in the list Thanks
  3. I looked, in the bios I have 70 L/M and ~ 2900, 2920 RPM under Aida64 70 L/M = 70 * 1000/24 = 2916 It corresponds, no ? Asus's method will be the right one ?
  4. Seems to be good with 1201 bios 1.05v in bios, 1.05v with Probe It, And between 1.034v (idle) and 1.044v (load) with Aida64
  5. Ok thanks, I'll test the bios 1201 1102 for now
  6. I tested with only CPU, FPU and Cache There is just a little "lapse of time" at the beginning of the test, but the Elapsed Time always jumps (jumps from 5 to 10 seconds each time)
  7. I have 32 GB and there is only 500 MB left available when I test with Aida64 It will be a good idea this new option I do not know how the stress test allocates the memory, but for example with Ram Test, this stress test takes 3 to 4 seconds to allocate 90% of ram and no freeze Same with HCI Memtest EDIT: After I know that with RamTest the allocation of memory is faster when the Cache is also tested For Memory + Cache: ~ 4 sec to allocate memory Memory: ~ 12sec to allocate memory And no freeze in both cases
  8. at ~ 200 RPM, that will correspond to the conversion indicated by Koolance 76 L/M (in my bios) = 76 x1000 /24 = 3166 RPM In Aida64 = ~2950 RPM Having PWM pumps, I will have to check by disabling the PWM (the pumps can turn faster while being in the bios)
  9. So I use CPU, FPU, Cache and Memory I will test without "Memory" to see I am using the latest version of Windows 10 16299 Besides, I think that the amount of memory tested is too important (98%) whereas all the other stress tests, uses ~ 90%
  10. It would seem, according to Koolance for their flow meters, that the indicated RPMs would correspond approximately to ml/min And therefore 1500 RPM = ~1500 ml/min = 90 L/H After I do not know if it's applicable just to the product Koolance But in the bios, I have 76 L/M indicated and in Aida64, 2900RPM ... I think 76 L/M is huge
  11. Hello I am interested in this conversion from RPM to L/H With my Rampage VI Extreme, in the bios I have the indication as on the screen of Elderdeekey and in Aida64, it is RPM
  12. The stress test (System Stability Test) not the benchmark There is a gap between reading Computer/Sensor and the infromations with System Stability Test The System Stability Test window "freezes" very often (noticed with the Elapsed Time that can "jump" by several seconds), and reading temperatures, voltages is not "synchronized" with the monitoring of the sensor part of Aida64 (Computer/Sensor) several tens of seconds difference The problem comes from System Stability Stress app, because if I use another stress test and only use the System Stability Test for reading probes for example, the window "freezes" very often (it's ok with the Computer/Sensor window) Thanks
  13. Yes, EC bank is enabled The files, 1.05V Vcache setting ecdump 1.05v.txt isasensordump 1.05v.txt 1.10v Vcache setting ecdump 1.10v.txt isasensordump 1.10v.txt if you need other things Thanks
  14. Hello Vcache reading is wrong By setting to 1.0, 1.05 or 1.1v, Aida64 always reads the same value in load (~ 1.07, 1.08v) With the Probe It, the voltages are those indicated in the bios Is it possible to correct this problem or is it related to the Asus bios and only Asus can correct this problem ? Thanks
  15. Hello It is also normal that during the stress test, the weather, monitoring, etc ... freeze very regularly (the time can jump 20 seconds) ? What is annoying is that we do not know if it is Aida64 that "freezes" or if it is because of the OC (no worries with other stress test and Aida64 in the background, for monitoring) For the "bump" at the start of the benchmark, maybe it would be better to be like this Launch of the benchmark (Start) => allocated memory => start of the benchmark (begin time elapsed) Instead the benchmark starts (time elapsed), freeze (while memory is allocated) and the benchmark continues Thanks
  16. Ok, with CPU-Z, it's indicated 5005 mhz, I wondered if it was normal Thanks
  17. Hello is it normal to have 2502 mhz in load for memory, instead of 5004 or 10008 ? Thanks
  18. Ok indeed it's odd that in the other sections of Aida64, the DIMMs are correctly recognized
  19. Tested and there are DIMMs that do not exist (DIMM A3, DIMM C3) Still ok in Motherboard / SPD and Computer / Overclocking
×
×
  • Create New...