I'm having this to. And I have not installed cpuz. Is it a component used by speccy?
yep, it seems CPU-Z is called from within Speccy.
have you tried what worked for me... http://forum.piriform.com/index.php?showtopic=44170&p=266736
update.
needed to run Speccy today to get some info for someone, and yep, BSoD on Win10.
workaround.
downloaded the Portable version, deleted speccy64.exe, double clicked speccy.exe and it worked fine.
but the same theory should work on the non-portable version, just get rid of the 64bit version of Speccy so it doesn't try to use it on a 64bit PC and it'll just use the 32bit one which the CPUZ sys file still works with.
What's difference between both exe?
32 bit version still can gather true info at a 64 bits system?
64bit software can utilise 64bit architecture, but 32bit software can still run on 64bit hardware.
I'll join in - Dell XPS13 running Windows 10. Speccy is unusable, causes the same issues as already described. Any news on an update for Win 10 64 bit?
64bit software can utilise 64bit architecture, but 32bit software can still run on 64bit hardware.
Then 32 bits version cant gather all information on Windows 10 64 bits?
yep, sure can.
on the storage side, the bit'ness is just the amount of info each register can store, 232 or 264.
and there's the speed side of it, the amount of bits that can be pushed through the processor and bus lines.
Win10 10586 64bit
WMIprvSE.exe in TaskManagers processes jumps to 21% cpu with both speccy portable 32 & 64bit here.
CPU fan kicks on and temperature rises.
Certainly wouldn't want to run it full time but it seems ok for a quick look at things.
can't confirm those findings on my PC.
Win 10 Pro (10240) 64bit.
Speccy portable 32bit.
before Speccy, there was just one wmiprvse.exe then during Speccy there was a wmiapsrv and 6 wmiprvse.
CPU for all those services stayed on 0, temps for mobo and CPU were unchanged.
Just got this exact BSOD after running Speccy... It did some damage as well though. After this BSOD I am not able to get to the login screen. System restore and system reset both failed... Somehow speccy managed to destroy my Windows 10 installation.
Hope this is fixed soon.
This is a Speccy discussion so I really don't want to cause an issue by talking about CCleaner, however, I have just had a hellish couple of days trying to upgrade a Win7Pro laptop to Win10. The laptop hung on reboot and has turned out to be unrecoverable (I'm having to reinstall from a Win10 ISO). The very last thing I did was install CCleaner. I've been using it for years, I did not (and never have) use the registry tool. I just used it for basic cleaning and had Active Monitoring on as this is the suggested workaround for CCleaner starting slowly in Win10. So, yes, I'm jumping to conclusions and yes, I could be wrong but when catastrophe happens I always backtrack to the last thing I did - as above, and the laptop was running fine up to that point. Feel free to move this post to the right thread - I only posted here in response to 'DeliciousSalad's post above. Unless someone restores my confidence I will not be reinstalling either CCleaner or Speccy and I'll be removing the former from the laptop I'm using now.
Jem's issue is likely unrelated, instead of reinstalling win10 (which is sometimes a necessity over upgrading in place) perhaps try safe mode disable active monitoring and see if it boots, however tons of people are not having your issue and has nothing to do with bluescreen errors or the cause of this issue (which is/was likely a fault in cpuz64 bundled into speccy and communication with 64bit WMI)
Hi guys, I bumped in this discussion while looking for a possible solution for Speccy crashing and causing blue screen error. My Windows 10 (32 bit) build is 1703. Before some major update, Speccy use to work fine but know it doesen't. Any of you guys was able to work this out? Thanks in advance.