Jump to content
Piriform Community Forums
hacker15

Win 10 Creator Edition (1703)

Recommended Posts

Just installed this yesterday and now app will launch and not run (failed repeatedly. Running Speccy 1.30.730 which ran fine on Win 10 Anniversary edition (16??).  Just tried it again and it finally launched.  Have sent several error reports - did something change here?

Share this post


Link to post
Share on other sites

Installed which one yesterday, the Win10 update or Speccy. If you didn't just install Speccy try to reinstall it again.

Share this post


Link to post
Share on other sites

My Windows 10 (32bit) 1703 Creators Update PC crashes completely and reproducible when starting Speccy, latest version. Error Code is PAGE_FAULT_IN_NONPAGED_AREA, reason: cpuz140_x32.sys. See photo attached. 

 

And just learned, that this issue happened with previous versions of Speccy and Windows 10, too: https://forum.piriform.com/?showtopic=44170 

post-66043-0-12624200-1492863947_thumb.jpg

Share this post


Link to post
Share on other sites

Same issue here.  Speccy 1.30.730 worked fine on 32-bit and 64-bit versions of Windows running the latest Anniversary Update (1607).  Updated machines to latest Creators Update (1703) and now 32-bit versions of Windows crash when Speccy is launched.  Same error as above: PAGE_FAULT_IN_NONPAGED_AREA, reason: cpuz140_x32.sys.  Speccy launches and runs fine on 64-bit versions of Windows that use cpuz140_x64.sys in C:\Users\Admin\AppData\Local\Temp\cpuz140.

 

I have tried reinstalling Speccy on the 32-bit machines.  It made no difference.

 

FYI, the latest version of CPU-Z (1.79) from CPUID, works fine on 32-bit Windows running the Creators Update.  It uses cpuz143_x32.sys in C:\Users\Admin\AppData\Local\Temp\cpuz143.

Share this post


Link to post
Share on other sites

Installed which one yesterday, the Win10 update or Speccy. If you didn't just install Speccy try to reinstall it again.

 

Win 10 update was installed the day before I reported this.  Speccy was the latest version and was updated to version 1.30.730 before this incident.  I tried a Speccy uninstall, down load from the Piriform website, and reinstall with no changes.  This is Win 10 Home 64bit on a Dell i5555 laptop with a 256 GB SSD and 16 GB RAM.  Speccy will launch and try to run.  It then returns an error form noting that the app unexpectedly terminated and closed.  It gives me 5 minutes to complete and return the form which I have completed and returned to Piriform at least four (4) times.  Since this is the free edition, I did not expect a response.  

Share this post


Link to post
Share on other sites

I have the same BSOD 4 times in a row as you on Speccy 1.30.730 and Win 10 Creator Update (1703) 32 bit.

It is fine on Win 10 Creator Update (1703) 64 bit.

 

I hope that this will get fixed soon.

I track the "Hotfixes" of windows KB updates in text which has helped protect me from malware.

C:\Windows\Minidump

Windows created 4 minidump files.

052617-24906-01.dmp 5/26/2017 1:21 PM DMP File 375 KB
052617-29968-01.dmp 5/26/2017 1:36 PM DMP File 375 KB
052617-33906-01.dmp 5/26/2017 1:12 PM DMP File 375 KB
052617-37546-01.dmp 5/26/2017 1:41 PM DMP File 375 KB

Share this post


Link to post
Share on other sites

It still continiue the problem with v1.30.730, :wacko: Windows 10 Creators Update (1703) 32bit.

 

When I started the Speccy v.1.30.730 it makes BLUE SCREEN. :angry: :angry: :angry:

 

please solve this problem. It needs Improved Windows 10 Creators Edition (1703) compatibility. please be quick.

Share this post


Link to post
Share on other sites

@turk and exellion,

 

if you have Windows 64bit OS, can you run the 64bit version of Speccy?

Share this post


Link to post
Share on other sites

word today from the Admin team - it is being investigated.

Share this post


Link to post
Share on other sites

@turk and exellion,

 

if you have Windows 64bit OS, can you run the 64bit version of Speccy?

@mta I use windows 32bit OS, so I can not test it in 64bit. I wrote it in my first message :"...Windows 10 Creators Update (1703) 32bit."

Share this post


Link to post
Share on other sites

@turk and exellion,

 

if you have Windows 64bit OS, can you run the 64bit version of Speccy?

@mta I'm running Windows 10 32bit (build 1703). As a side note, when it still worked, I used to get craxy reading about motherboard temperature (and I stille have with other tools).

Share this post


Link to post
Share on other sites

word today from the Admin team - it is being investigated.

thanks they realese a new version

v1.31.732 (04 Jul 2017)

- Improved Windows 10 Creators Update compatibility

- Updated GPU information and sensor tracking

- Improved 32-bit build architecture

- Improved localisation and languages support

- Minor GUI improvements

- Minor bug fixes

Share this post


Link to post
Share on other sites

thanks they realese a new version

v1.31.732 (04 Jul 2017)

- Improved Windows 10 Creators Update compatibility

- Updated GPU information and sensor tracking

- Improved 32-bit build architecture

- Improved localisation and languages support

- Minor GUI improvements

- Minor bug fixes

It works. Still getting crazy motherboard temperatures, though.

Share this post


Link to post
Share on other sites

Just installed speccy  on my win10 32bit machine. Everytime speccy is started, it shows up for a couple of seconds then the blue screen with the error message and the PC restarts. I have noticed many users having had the same problem.  Has am solution been found? Would be great to be able to use speccy, which came  with ccleanerpro

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×