Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Solved Can't open HWiNFO64 (Stops Responding)
#1
I've got a HP desktop and I installed HWiNFO64. When I first opened it, it caused a blue screen of death. I looked at a few threads here and, then, disabled the "SW SMI" option.

But now it stops responding halfway into the scan. I've attached the debug file with "SW SMI" disabled.

Appreciate the help!


Attached Files
.dbg   HWiNFO64.DBG (Size: 145.39 KB / Downloads: 1)
Reply
#2
Does HWiNFO just stop responding, or does it crash, or maybe does the entire system crash with "SW SMI" disabled.
Reply
#3
(08-24-2014, 07:35 PM)Martin Wrote: Does HWiNFO just stop responding, or does it crash, or maybe does the entire system crash with "SW SMI" disabled.

It stops responding. The message that Windows gives is 'HWiNFO64 has stopped working'. The only option is to 'Close Program'.

This seems to happen when HWiNFO is:

"Examining system configuration
Detecting Video Adapter(s)..."

The entire system crashes (bsod) when "SW SMI" is enabled.
Reply
#4
I'm not able to determine the exact cause of this issue with current HWiNFO, so I need to enhance the debug file reporting.
Please get this build: http://www.hwinfo.com/beta/hw64_443_2293.zip
and run it. It will hang again, so after killing the hung HWiNFO, please attach the new Debug File produced.
Reply
#5
(08-24-2014, 08:26 PM)Martin Wrote: I'm not able to determine the exact cause of this issue with current HWiNFO, so I need to enhance the debug file reporting.
Please get this build: http://www.hwinfo.com/beta/hw64_443_2293.zip
and run it. It will hang again, so after killing the hung HWiNFO, please attach the new Debug File produced.

I ran it without changing any of the settings: "SW SMI" was left on. I've attached the debug file. This time, there was no blue screen of death: the program just stopped responding.


Attached Files
.dbg   HWiNFO64.DBG (Size: 149.72 KB / Downloads: 0)
Reply
#6
Please try both - with disabled SW SMI and enabled. Then please attach both debug files - I can have a look at both issues then.
Reply
#7
(08-24-2014, 08:33 PM)Martin Wrote: Please try both - with disabled SW SMI and enabled. Then please attach both debug files - I can have a look at both issues then.

And here is the debug file for "SW SMI" disabled...


Attached Files
.dbg   HWiNFO64.DBG (Size: 149.56 KB / Downloads: 1)
Reply
#8
Thanks. Please try this build: http://www.hwinfo.com/beta/hw64_443_2294.zip
and let me know the result. If it still doesn't work, then please attach a new debug file.
Reply
#9
(08-24-2014, 08:56 PM)Martin Wrote: Thanks. Please try this build: http://www.hwinfo.com/beta/hw64_443_2294.zip
and let me know the result. If it still doesn't work, then please attach a new debug file.

It worked! Big Grin Thank you very much! Especially for your quick responses. Out of interest, what was the issue?

By the way, only one CPU core temp is being shown. I suppose this is a limitation of the hardware rather than the software. Is that right?

Finally, what is the CPU Package temperature? It's is idling at around 70°C but this seems to be too hot: it's near the CPU's max temp. So, is that reading an error?

Thank you very much once again!
Reply
#10
Thanks for the feedback.
The issue was reading the (UEFI) video BIOS from ACPI tables. I'm not sure without further investigation if it's a fault of the system's firmware or HWiNFO, but the workaround I implemented seems to work.

AMD CPUs cannot monitor per-core temperatures, there's only one sensor in the chip, so it's a hardware limitation. There are some tools displaying per-core temperatures on AMD CPUs, but those values are just fake copies of one single temperature.

Please check this about more details regarding monitoring of CPU temperatures: http://www.hwinfo.com/forum/Thread-CPU-C...s-Fictions
Reply
#11
(08-24-2014, 09:37 PM)Martin Wrote: Thanks for the feedback.
The issue was reading the (UEFI) video BIOS from ACPI tables. I'm not sure without further investigation if it's a fault of the system's firmware or HWiNFO, but the workaround I implemented seems to work.

AMD CPUs cannot monitor per-core temperatures, there's only one sensor in the chip, so it's a hardware limitation. There are some tools displaying per-core temperatures on AMD CPUs, but those values are just fake copies of one single temperature.

Please check this about more details regarding monitoring of CPU temperatures: http://www.hwinfo.com/forum/Thread-CPU-C...s-Fictions

Thanks for the help! I really appreciate it!
Reply
#12
(08-24-2014, 09:37 PM)Martin Wrote: -Snip-

For future reference, can I update HWiNFO like normal? Or would that break the fix? Thanks again!
Reply
#13
Sure, you can update - all fixes are carried forward.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)