Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Hwinfo64 keeps crashes...
#1
When i start the program it goes well for about 4 sec then it crashes... I think i have tryed every settings and still the same problem...

My computer setup if it helps,

i have amd A10-6790K CPU
Geforce GTX 750 Ti GPU
16GB HyperX Fury DDR3 1866 MHz RAM
Gigabyte F2A88XM-D3H Motherboard
SSD storage and a "normal" HDD

i attach the debug file.

Thanks in advance!

Edit: When i start sensor only.


Attached Files
.dbg   HWiNFO64.DBG (Size: 222.3 KB / Downloads: 1)
Reply
#2
Try to disable the "Use HPET" Safety option in HWiNFO and let me know if that helped.
Reply
#3
I have tryed that now but it dident help.
Reply
#4
OK, a few questions:
- What happens there exactly, does only HWiNFO crash or the entire system ?
- Are you maybe using other system monitoring tools together with HWiNFO ?
- Does it crash also when you don't use "Sensor-only" and you have the System Summary window open ?
Reply
#5
(01-03-2016, 03:54 PM)Martin Wrote: Try to disable the "Use HPET" Safety option in HWiNFO and let me know if that helped.

(01-05-2016, 08:42 PM)Martin Wrote: OK, a few questions:
- What happens there exactly, does only HWiNFO crash or the entire system ?
- Are you maybe using other system monitoring tools together with HWiNFO ?
- Does it crash also when you don't use "Sensor-only" and you have the System Summary window open ?

Only HWINFO Crashes
No.. i have a logitech g13 that can watch cpu and RAM usage, can that be the problem?
It only crash when i use "sensors-only" what i know of... Havent tryed the whole program longer periods.
Reply
#6
Can you please try the latest HWiNFO version (5.12) and if it still crashes, please attach the new DBG file.
Can you also try to run without "Sensor-only" mode, make sure the System Summary window open, wait a few minutes and let me know if it crashes too.
Reply
#7
Same here, start program, run, 'examining system configuration' crash.
Using HWiNFO64 v5.12 x64 Portable on my x64 system.
Previous versions-no problems.

I made a video -HWInfo crashes_2016-01-09_083247.wmv
but regretfully I cannot attach it to this post sorry (rejected)


Made some small screenshots instead then
=
   

=
Reply
#8
Please attach the HWiNFO Debug File of the crash for analysis. See here how to create it: http://www.hwinfo.com/forum/Thread-IMPOR...g-a-report
Reply
#9
But eh ..
I guess for for that at least HWiNFO should _start_?

=
Reply
#10
The scan doesn't need to finish, you need to enable Debug Mode in Settings before starting the scan where it crashes.
Reply
#11
Sorry, my mistake... I thought the settings were available only after launching the program, but didn't think of this [Settings]  button when launching.

Pls find it attached.

System: Windows 10 x64 Pro


pls find file attached.
=


Attached Files
.dbg   HWiNFO64.DBG (Size: 473.63 KB / Downloads: 6)
Reply
#12
Please try to disable Drive Scan option to see if that fixes the problem.
Reply
#13
Sorry for the delay. Seems I missed a notification.
This solved the issue. HWiNFO64 was launched successfully.
Obviously drives are not listed.
With open HWiNfo I change the settings back to what it was before, nothing changed.
Of course, closing/relaunching caused the crash again.

=
Reply
#14
Hello to you,
Out of curiosity: have you been able to reproduce the issue?
As said, whilst disabling Drive Scan, they are now not listed anymore.
Keep up the good work!
=
Reply
#15
I'm sorry, I can't reproduce that problem on my machines. It seems it happens only on some specific systems (specific drive configuration, OS, drivers, chipsets).
But the increasing amount of similar reports I'm recently getting is alarming, though I believe it's not HWiNFO's fault, just an issue of the storage drivers.
Reply
#16
FWIW and I don't know if at all it may have something to do with it...

You are talking about storage.
Please note that I am using Samsung 850 Pro SSD's  (2 in fact, 1x 512GB and 1x 1TB) and a number of HDD's (not in RAID).
Also note that the Windows C-drive (stored on the 512GB SSD) is listed as  "Disk1" under diskmgmt.msc.
Not Disk0.
Disk0 is a single Samsung 3.5 inch HDD.

So,
Disk0 = Samsung 3.5"hdd
Disk1 = Samsung SSD
Disk2 = Samsung SSD
Disk3 = WD HDD
etc.

=
   
=

As said, I don't know if it has something to do with it.

=
Reply
#17
Hello again, do you think you can fix it?
FWIW System info

OS   
Windows 10 Pro 64-bit (bld 10586.63)
CPU   
Intel Core i7 5820K @ 3.30GHz Haswell-E/EP 22nm Technology
RAM   
32,0GB Unknown @ 1065MHz (15-15-15-36)
Mobo   
ASUSTeK COMPUTER INC. X99-DELUXE (SOCKET 2011)    
Video   
HP Z27x ([email protected])
4095MB NVIDIA GeForce GTX 970 (ASUStek Computer Inc)    
HDDs   
0B SAMSUNG HD204UI (SATA)
476GB Samsung SSD 850 PRO 512GB (SSD)    
953GB Samsung SSD 850 PRO 1TB (SSD)    
1863GB Western Digital WDC WD2003FZEX-00Z4SA0 (SATA)    
1863GB Western Digital WDC WD2003FZEX-00Z4SA0 (SATA)    
3726GB Western Digital WDC WD4003FZEX-00Z4SA0 (SATA)    
3726GB Western Digital WDC WD4003FZEX-00Z4SA0 (SATA)    
59GB SanDisk Extreme USB Device (SSD)
999GB BestCrypt virtual drive (SATA)
Optical   
ASUS BC-12D2HT
Audio   
Realtek High Definition Audio

=

   
=

Specifically HWiNFO has an issue when scanning the drives.
Am not sure whether it is a hardware/storage drivers matter.

Thing is, I checked other tools and they have no issues.
HWiNFO is my 'favoratite' one, so I do hope it will be solved soon.

=
Reply
#18
Please attach a new HWiNFO Debug File using the latest Beta version that captures the crash.
Does only HWiNFO crash, or the entire system ?
Reply
#19
Hi there,
Downloaded the latest beta (HWiNFO_5.13_2750 x64)
Regretfully HWiNFO still crashed.
dbg file, pls find attached.
It is only HWiNFO that crashes only.

=

.dbg   HWiNFO64.DBG (Size: 473.29 KB / Downloads: 1)
Reply
#20
Thanks. I have replied via e-mail.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)