Search results

Most M.2 SSD seems to have two sensors. The first is for ASIC controller and the second is for NAND flash. And the general rule of thumb is that the controller temperature is always higher because it consumes more power and does most of the work. However on my S70 blade (4TB model) for some...

GPU-Z is able to report that on my 2080 Ti (GDDR6). So i think there is a way too read it on older cards too. I could inquire the developer how he did that and report back.

Nope. No luck. Never shows up. I went trugh the hidden values up and down ten times (including when a game was running in the background) but no FPS value appeared. I even tried the latest HWiNFO Beta but no change. Is it supposed to work with an AMD card at all? EDIT: Got it to work. I had to...

Hmm doesent seem to work for me. What is the exact name of the value? The only one i could find is RTSS sensor value (wich i renamed to FPS). I tried with both "Show own statistics" on and off in RTSS. In either case the RTSS sensor value shows no info (even when fullscreen or windowed D3D...

RE: AMD GPU VRM reading randomly dissapearing from OSD since v5.20 (build 2800). Good news. Version 5.22 fixed the issue.

RE: AMD GPU VRM reading randomly dissapearing from OSD since v5.20 (build 2800). With ADL disabled (and i did reset I2C cache) OSD didnt show VRM reading at all. Like literally nothing. With ADL in 5.20 it flickers on and off but it's there. With previous HWInfo versions it worked normally and...

Like the title says since 5.20 my GPU VRM reading is flickering on and off in afterburner OSD. It worked ok earlier this week and i havent updated either afterburner or AMD drivers - however i did update HWInfo. Yes im using ADL because this is the only way to get VRM temperature. AMD Radeon...

Not sure why it didnt work for you. I created my own 64bit startup key and hwinfo64 defenetly started properly on 64bit windows 7. I used the following in commandline: REG ADD HKLM\Software\Microsoft\Windows\CurrentVersion\Run /v HWiNFO64 /d "C:\Program Files\HWiNFO64\HWiNFO64.EXE" /f

The 64bit version of the program should create its startup in 64bit registry not in 32bit. I just debugged a problem where i was unable to delete the hwinfo64 startup key from the registry via commandline. Turns out i was trying to delete a nonexistant 64bit key. Use System32\Reg.exe to create...