[BSOD ?]

Thank you for your reply.

 

I did try the 32bit version, with the same results.

 

I ran the BlueScreenView app and here are the results:

040816-15163-01.dmp    2016-04-08 6:46:31 PM    DRIVER_VERIFIER_DETECTED_VIOLATION    0x000000c4    00000000`00000091    00000000`00000000    fffffa80`07c56060    00000000`00000000    ntoskrnl.exe    ntoskrnl.exe+74080    NT Kernel & System    Microsoft® Windows® Operating System    Microsoft Corporation    6.1.7601.19160 (win7sp1_gdr.160211-0600)    x64    ntoskrnl.exe+74080                    C:\Windows\Minidump\040816-15163-01.dmp    2    15    7601    276,424    2016-04-08 6:47:21 PM    
 

I'm guessing the ntoskrnl.exe file is suspect.  Not sure how to correct, so a little research is in order.

[BSOD ?]

I used to run Speccy Portable 64-bit (1.29.0.714), on Windows 7 Ultimate, but now I can't get it to run and it causes a BSOD with a line in it about new hardware.

 

A few days ago I attempted to add an 8GB stick of memory but I had ordered an incompatible version, so I'm using only the original 8GB stick.  All other programs, including SIW, work fine.  Only Speccy causes this problem.

 

Does anyone have any idea why this is happening, and how to correct?  I would prefer to keep using the portable version.

[Defraggler suggestions]

It would be nice if the drive map legend could be shown all the time, maybe a show/noshow option. I agree that showing the file-in-process name would be nice.