I did what you said and all it did was open a dialog window with several options to analyze. I put a check mark for CPU and the program started...and it worked. However, if I start up the program outside of the cmd...it crashes. It did not generate a log or a new dmp file.
I just downloaded Speccy from Piriform. I installed it and ran it, but it crashes a few seconds after analyzing and I get a crash report. Same thing happens every time. The weird part is that behind the crash report, the application looks like it's running and has analyzed the system. There is a spinning circle by the version number though and once the crash report times out - the whole thing closes. It is version 1.17.340 and I'm running Windows 7 Pro 64-bit SP1 Ideas? Thanks!