Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
HWinfo64 hangs without "low-level PCI access" option on Windows 10
#1
Could You please help me to solve the following driver issue (as far as I understand):
under my old system (Windows 7 with all updates) HWinfo64 5.02-2575 works perfect without any errors BUT
after migration to Windows 10 HWinfo64 5.02-2575 hangs every time when I started it... without response!
The only solution to this error is to turn on the "low-level PCI access" option.

Thank You in advance!


Attached Files
.zip   HWiNFO64.zip (Size: 66.08 KB / Downloads: 1)
Reply
#2
I'll need a DBG file from the hang to have a look at what's happening there.
Reply
#3
(08-21-2015, 07:35 AM)Martin Wrote: I'll need a DBG file from the hang to have a look at what's happening there.

In this case, Is it possible to upload very large DBG file to the forum, about 15 Mb unzipped and ~3Mb zipped?
As far as I remember, only 1Mb available for upload.
Reply
#4
I have raised the limit for such attachments to 5MB. You can also try better compressors like 7z or RAR.
Reply
#5
(08-21-2015, 09:22 AM)Martin Wrote: I have raised the limit for such attachments to 5MB. You can also try better compressors like 7z or RAR.

Thank You very much for Your assistance!
Here, I uploaded DBG-file obtained by HWinfo64 using default options.


Attached Files
.zip   HWiNFO64_.zip (Size: 3.22 MB / Downloads: 3)
Reply
#6
This looks like an issue in the Windows 10 kernel (HAL) - it reports a bunch on random (internal memory) data when queried for PCI devices.
Besides the fact that this is an error in the kernel, this could be a security issue as well (because it seems to read internal memory).
I'm afraid there's nothing I can do about this, you'll have to use the "Low-level PCI Access" option until Microsoft fixes this issue.
Reply
#7
(08-21-2015, 07:55 PM)Martin Wrote: This looks like an issue in the Windows 10 kernel (HAL) - it reports a bunch on random (internal memory) data when queried for PCI devices.
Besides the fact that this is an error in the kernel, this could be a security issue as well (because it seems to read internal memory).
I'm afraid there's nothing I can do about this, you'll have to use the "Low-level PCI Access" option until Microsoft fixes this issue.

Thank You very much, Martin!
Pretty bad news everyone! Sad MS tested Win 10 for more than 2 years and the result of such intensive testings is kernel error! There d be a reason to think about MS products... once again....
Reply
#8
I think they concentrated most resources to make sure their Telemetry works well Wink
Reply
#9
Dear Martin, recently I found one more interesting thing, maybe this is a key to strange behavior of HWinfo64 on Win 10...
HWinfo64 incorrectly identified Win 10 (10.0.10240) as Win 8, Build 9200 (see screenshots)!


Attached Files Thumbnail(s)
       
Reply
#10
Are you maybe running HWiNFO in Compatibility Mode for Windows 8 (HWiNFO64.EXE -> Properties -> Compatibility) ?
Reply
#11
(08-29-2015, 10:57 PM)Martin Wrote: Are you maybe running HWiNFO in Compatibility Mode for Windows 8 (HWiNFO64.EXE -> Properties -> Compatibility) ?

Ooops. Yes! 
But I did NOT do it manually!!!!
Win 10 selected starting mode automatically after several unfortunate starts (I just repeated such situation).
One more interesting feature: After this auto-selection it is only possible to generate DBG file.
Reply
#12
I'm thinking about setting the "Low-level PCI Access" option to enabled by default for all.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)