Remarc Posted June 26, 2018 Share Posted June 26, 2018 (edited) gpupi 3.0+ (3.2 actual) legacy not work with old x86 cpu (s423,478,754) that problem with hwinfo32.dll library (i think hwinfo32 not support old cpu) fix this issue or remove support hwinfo32.dll from gpupi 3.2 legacy (3.3 not yet tested but i think there will be the same problem)...version gpupi 2.3.4 legacy work fine because there is no hwinfo32.dll but hwbot no longer accepts this version Edited June 26, 2018 by Remarc 2 Quote Link to comment Share on other sites More sharing options...
_mat_ Posted July 16, 2018 Share Posted July 16, 2018 Try to disable HWiNFO support in the dialog before the run and let me know if it works. Quote Link to comment Share on other sites More sharing options...
Remarc Posted July 21, 2018 Author Share Posted July 21, 2018 I tried it right away and not work,when gpupi save to file get error and close Quote Link to comment Share on other sites More sharing options...
TAGG Posted July 21, 2018 Share Posted July 21, 2018 Try not ticking "save screenshot", had the same crash when save screenshot was ticked, the benchmark will save a screenshot regardless Quote Link to comment Share on other sites More sharing options...
Remarc Posted July 24, 2018 Author Share Posted July 24, 2018 (edited) right now I checked and not help 3.2.0 again get error when save,but 2.3.4 save datafile normal... Edited July 25, 2018 by Remarc Quote Link to comment Share on other sites More sharing options...
_mat_ Posted July 25, 2018 Share Posted July 25, 2018 Open the debug log (Menu => Tools => Debug Log) and post a screenshot or the output of the log when the crash appears. The way it sounds to me it has nothing to do with HWiNFO. Especially when it's disabled, everything is done with WMI instead (a normal windows feature). Quote Link to comment Share on other sites More sharing options...
Remarc Posted July 25, 2018 Author Share Posted July 25, 2018 ok made log but it not show anything related to saving the file Quote Link to comment Share on other sites More sharing options...
_mat_ Posted August 16, 2018 Share Posted August 16, 2018 Were you able to scroll down in the debug log after the error occurs? It only shows the first few lines. Btw, there is something very wrong with the timer on this system. Seems like QueryPerformanceFrequency() is returning a crazy high frequency, that can't be correct. But that shouldn't be part of this particular problem. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.