Windows 10: BSOD when opening speccy.

  1.    25 Aug 2015 #1

    BSOD when opening speccy.

    Formatted yesterday using an iso and so far I've tried opening speccy.exe which is a freeware utility and sometimes it crashes giving a bsod. Any help would be appreciated.
      My ComputerSystem Spec

  2.    25 Aug 2015 #2

    Welcome to the forum,

    Yeah, it's actually the CPU-z part of it that crashes,

    Could not read faulting driver nameProbably caused by : cpuz138_x64.sys ( cpuz138_x64+24a2 )
    Loaded symbol image file: cpuz138_x64.sys
        Image path: \??\C:\Users\Giorgos\AppData\Local\Temp\cpuz138\cpuz138_x64.sys
        Image name: cpuz138_x64.sys
        Timestamp:        Thu Oct 23 08:03:05 2014 (544918A9)
        CheckSum:         0000B4BC
        ImageSize:        0000A000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Uninstall speccy and make sure that driver is removed from the location I highlighted above.

    That's a hidden folder so you need to unhide it,

    Hidden Files and Folders - Show or Hide - Windows 7 Help Forums

    You can try the portable version of Speccy and see if that doesn't crash.

    Speccy - Builds
      My ComputerSystem Spec

  3.    25 Aug 2015 #3

    So I uninstalled and deleted the .sys file but when trying the portable version the .sys file comes back in the same location.
      My ComputerSystem Spec


Related Threads
New Speccy out - 10TP fixes in Software and Apps
New Speccy out... Speccy - Standard
Justw ondering if anyone else lost Speccy when upgdating to 10525? I had a pop up telling me it was incompatible and sure enough it's nowhere to be found, looks like the update nuked it.
Hi, guys I got a problem with constantly repeating BSOD mostly because these two reasons in topic. I have checked online and did everything for preventing this from happening. And it doesnt worked :/ The other things I have done are checking...
Hi, Over the past couple of days I have been having reasonably frequent BSODs. Some have not created a dump file. I cant pinpoint anything in particular but it seems to be pointing to a driver issue but never identifies the driver from what I can...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:06.
Find Us