Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HWInfo x64 5.04 - showed Kraken details at first but not after a reboot
#1
Hi,

I was pleasantly surprised to see pump temp/speed of my Kraken X61 show up when installing HWInfo 64 on a fresh install of windows 10 today but after rebooting, the monitoring of the Kraken has disappeared and the option to add it to layout isn't visible.
Reply
#2
Please attach the HWiNFO debug file, so I can check it in detail.
Reply
#3
Attached Smile


Attached Files
.dbg   HWiNFO64.DBG (Size: 654.71 KB / Downloads: 2)
Reply
#4
It seems that something is not allowing HWiNFO to access the device. Are you maybe running other Kraken monitoring tools ?
Reply
#5
I'm using the NZXT cam software which monitors fan speeds and also lets me adjust the fan speed curves etc.
Reply
#6
Please try to disable that software to see if then HWiNFO will be able to access the Kraken.
Reply
#7
Hi,
I have a similar problem with Kraken X62.
Scenario is a bit confusing:

1. HWInfo does not show the Kraken in sensors when CAM is disabled at system start.
2. Launching CAM after HWinfo in that case does not change anything - Kraken still isn't there. Even when I restart HWinfo with CAM enabled.
3. When CAM is set to launch at system start, HWinfo still does not recognize it, BUT now, when HWinfo gets restarted, Kraken is shown in the sensors.

I dont have the slightest idea why Kraken sensors in HWinfo seem to depend on CAM autostart.
Can you provide some help getting Kraken sensors to be shown without restarting HWinfo?


Attached Files
.dbg   HWiNFO64.DBG (Size: 1.62 MB / Downloads: 1)
.htm   HWinfo.HTM (Size: 216.64 KB / Downloads: 1)
Reply
#8
The Debug File you attached seems to be from a run when HWiNFO recognized the device.
Please also attach a Debug File when HWiNFO doesn't recognize it.
Reply
#9
Here is the debug file from scenario where Kraken wasn't recognized.
CAM was running at system start.


Attached Files
.dbg   HWiNFO64_Kraken_Not_Recognized.DBG (Size: 1.58 MB / Downloads: 1)
Reply
#10
This looks like something else in the system is not allowing HWiNFO to access the cooler.
I suppose it might be the CAM software, which allows only exclusive access for itself when it's running.
Reply
#11
As a temporary workaround, one can slow down the autostart of HWiNFO for 1 minute in Windows task scheduler, so it gets loaded after the CAM upon system start.
Tested and working.
Reply
#12
Thanks for the hint.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)