when i want to run hwinfo it is stuck on detecting ATA/SCSI drives

[deeperkk]

when i want to run hwinfo it is stuck on detecting ATA/SCSI drives
I have tried reinstall it and i also tried to end it task in task manager

 

[Martin]

IMPORTANT Thread 'Read this before submitting a report'

Feb 6, 2010

In order to submit a bug report, please include the following information:

1. HWiNFO32/64 Report File (HTM or TXT preferred)
2. HWiNFO32/64 Debug File (HWiNFO32.DBG or HWiNFO64.DBG)

In case the application crashes or you are not able to create a Report File, please submit only the Debug File. This will help to find the reason of crash.
In order to create the Debug File, HWiNFO32/64 needs to be run in Debug Mode. This can be enabled: right after starting HWiNFO32/64 click the Settings button and navigate to the "Safety" tab.

Then...

• Martin
• Replies: 0
• Forum: HWiNFO® 32 or HWiNFO® 64 Bug Reports

• 

 

[deeperkk]

where can i get this file from?

 

[deeperkk]

this is what happen when it went into debug mode

 

[Martin]

HWiNFO64.DBG should be in the folder when HWiNFO is installed. You might need to compress (ZIP, 7z, RAR) it before attaching here.

 

[deeperkk]

this is the debug file

 

[Martin]

Hmm, those Debug File seem to be from a different system/configuration.
First one has ATA drive WDC WD10EZEX and NVMe WDS100T3X0C. It hangs when HWiNFO queries the ATA drive for SMART status.
Second DBG has WDC PC SN730 and KINGSTON SA2000M NVMe drives. It hangs at detecting the KINGSTON drive.
Seems odd. So which one is from actual configuration? Are the drives working properly and also properly appear in Device Manager?

 

[deeperkk]

this is my setting for the second time
but the first time i run i close the ATA statistics support and the intel svid support

 

[Martin]

OK, looks like the first DBG file was from a very different (or old) system. You actual has WDC PC SN730 and KINGSTON SA2000M, right?

 

[deeperkk]

I just run it again. this is the lastest debug file. yes i use kingston SA2000M

 

[Martin]

The KINGSTON SA2000M isn't responding when HWiNFO queries it. Is it working well and also appears in Device Manager?
Can you try some other tool, e.g. CrystalDiskInfo?

 

[deeperkk]

the kingston SA2000M work when i play games and run anything. i use hwinfo for msi afterburner cuz afterburner cpu voltage and cpu temp is not showing. i just tried crystaldiskinfo nothing When i open it no program run

 

[Martin]

What means "nothing", "no program run" ? Does it hang too?

 

[deeperkk]

it doesnt even open i just ask me to give permission to change my device
and nothing show up

 

[Martin]

Looks like it's affected by the same issue. For some reason the KINGSTON drive doesn't respond to certain calls.
Try to upgrade the storage driver or Windows.

 

[deeperkk]

okok

 

[VortexEntity]

Might be late into the thread but it's this is a PCIe Power Management issue, the storage devices (specially SSDs) constantly enter on L0/L1.1/L1.2 states which lower their power comsuption but it increases the latency due to "waking up" from deep state, it seems HWInfo request a query on the SSD but when the SSDs is on a "deep" state or "low energy" it may cause hwinfo to hang out forever waiting for the storage to respond, it can be fixed going to power plan > advanced power plan > PCIe Power Management > Set it to Disabled. This should fix the issue, certain hardware configurations are more sensible to constant state change than others.