Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
problem detection temp crossfire sapphire 7950 dual x
#1
good day. as the title I wanted to report a bug that I've noticed on all versions of hwinfo64. in active practice with crossfire if I open hwinfo64, I'm busting the sensors of one of the vga that goes from 0 degrees to its real temp, so the fans start and stop continually resulting in increased temp. if I disable crossfire or a vga connection at a time no problem ... you can solve the problem with a future update? thank you very much

p.s. I guess the problem is the new vga bios that has a different and still not properly detected by hwinfo64 .. the version of the new card is: 11196-19-20g and the old is: 11196-16-20g
Reply
#2
The problem is the AMD ULPS feature, which completely disables the secondary GPU if not used. In such disabled state it's not possible to query that GPU for any parameters, otherwise a total system crash can occur. So HWiNFO is behaving correctly. This has been discussed several times here. To mitigate this problem you can disable ULPS (using registry or the TRiXX tool).
Reply
#3
(08-31-2013, 07:23 PM)Martin Wrote: The problem is the AMD ULPS feature, which completely disables the secondary GPU if not used. In such disabled state it's not possible to query that GPU for any parameters, otherwise a total system crash can occur. So HWiNFO is behaving correctly. This has been discussed several times here. To mitigate this problem you can disable ULPS (using registry or the TRiXX tool).

i have disabled it by trixx. the problem is not crossfire but is the new vga bios on the new card. i confused... if i connect only the new card have the same problem... can fix this please?
Reply
#4
If it's a VBIOS problem, then I'm not sure if that can be fixed in an application.
Nevertheless, please attach the HWiNFO Debug File and I'll check it.
Reply
#5
(09-06-2013, 09:03 AM)Martin Wrote: If it's a VBIOS problem, then I'm not sure if that can be fixed in an application.
Nevertheless, please attach the HWiNFO Debug File and I'll check it.

Thank you for your help. here the required files. I enclose also a picture where you see the problem clearly. thanks in advance

.csv   hwinfolog.CSV (Size: 17.84 KB / Downloads: 4)

.dbg   HWiNFO64.DBG (Size: 842.22 KB / Downloads: 4)
   
Reply
#6
Does it mean, that only when you have HWiNFO running, then all the other tools (TRiXX, MSI AB) sometimes report 0 C GPU temperature and if you close HWiNFO, they report the correct temperature always again ?
Reply
#7
(09-07-2013, 08:34 PM)Martin Wrote: Does it mean, that only when you have HWiNFO running, then all the other tools (TRiXX, MSI AB) sometimes report 0 C GPU temperature and if you close HWiNFO, they report the correct temperature always again ?
yes if i start msi ab and/or trixx all work fine. when i start hwinfo msi and trix showing 0° on the primary card. if i close hwinfo msi and trixx show the correct temp...
Reply
#8
Please try to disable those two GPU VRM CHL8228 sensors in HWiNFO (right-click on sensor and Disable Monitoring) and let me know if that helped.
Reply
#9
(09-08-2013, 01:29 PM)Martin Wrote: Please try to disable those two GPU VRM CHL8228 sensors in HWiNFO (right-click on sensor and Disable Monitoring) and let me know if that helped.

i don't have chl8228 on my hw info but i try to disable the sensor on the screen and now all work fine. tnx for the help. if is possible fix in the new hwinfo update, if not, no problem Wink really tnx    
Reply
#10
I think this is a conflict between the applications when they run concurrently.
My only advice is not to run them all at the same time.
Reply
#11
if I disable that sensor as screen does not give me any problem.. in this case i can also keep them active both at the same time right?
Reply
#12
Sorry, I don't understand the question.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)