Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[solved]  NXZT Kraken X42/X52/X62 monitoring broken on 6.06
#1
Hello!

The sensor monitoring of the NXZT Kraken X42/X52/X62 does appear to be not functional anymore with the 6.06 update.


The entry still shows up in the sensors, but it is empty.  I have already done a fresh install, did a "Restore Original Order" and checked "Fixed order" in the sensor settings but it does not help.
Reply
#2
Please attach the HWiNFO Debug File with sensor data and I will check this.
Reply
#3
(05-17-2019, 08:46 AM)Martin Wrote: Please attach the HWiNFO Debug File with sensor data and I will check this.

I have been trying to find out how to create the debug file. Is it created automatically in the HWINFO64 folder by starting the application? Because there is only the executable and the .ini file in there.
Reply
#4
See here: https://www.hwinfo.com/forum/Thread-IMPO...g-a-report
Reply
#5
Alright!

I hope these are the correct files


Attached Files
.dbg   HWiNFO64.DBG (Size: 701.52 KB / Downloads: 1)
.htm   NETSU.HTM (Size: 1.4 KB / Downloads: 2)
Reply
#6
Thanks. Unfortunately you didn't open sensors, so the dump doesn't contain some required data.
Now please get this version: www.hwinfo.com/beta/hwi64_607_3775.zip and run in Debug Mode again, also don't forget to open sensors before closing the program.
Then please attach the new DBG file created using that version. I need to analyze it further...
Reply
#7
(05-17-2019, 09:33 AM)Martin Wrote: Thanks. Unfortunately you didn't open sensors, so the dump doesn't contain some required data.
Now please get this version: www.hwinfo.com/beta/hwi64_607_3775.zip and run in Debug Mode again, also don't forget to open sensors before closing the program.
Then please attach the new DBG file created using that version. I need to analyze it further...

Installed the version mentioned. Not sure if it's important, but the NZXT Kraken entry no longer shows up in the sensors at all anymore in this version.


Attached Files
.dbg   HWiNFO64.DBG (Size: 941.22 KB / Downloads: 1)
Reply
#8
Thanks. I can see that HWiNFO is unable to access that cooler because some other program is using it exclusively.
Are you running any other monitoring tools including CAM? If yes, can you try to close such tools and then see if it will work?
Reply
#9
(05-17-2019, 09:49 AM)Martin Wrote: Thanks. I can see that HWiNFO is unable to access that cooler because some other program is using it exclusively.
Are you running any other monitoring tools including CAM? If yes, can you try to close such tools and then see if it will work?

There should be no other program accessing it (exclusively) as all I did was updating HWiNFO to the new version. I will look over my system again and make sure there are no other programs running, reboot and then report back.


Okay, it seems that for some reason, CAM is now exclusively accessing the sensor, that has never been the case before. The program was not updated. This is rather strange. Closing CAM brings the sensors back, opening CAM removes the values again. I was able to run CAM and HWiNFO at the same time with no problems. But at least there is a workaround for this so far Smile
Reply
#10
Well, really not sure what happened, but it must be somehow related to CAM, perhaps start/boot order.
It's a shame that this application requests exclusive access to the device and won't allow any others while it's active.
Reply
#11
Oddly enough I didn't before. And by that I mean, like, two hours ago.
I tried both start orders (CAM first, HWiNFO first). It is also the  same version of CAM I have used before updating HWiNFO.

However it may be, thank you for the quick response, this is very much appreciated!
Reply
#12
You're welcome Smile
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)