Speccy 1.14.288 crashes as soon as analyzing of items is complete, OS is Windows XP Pro SP3. Previous version was working fine.
Any chance you could run in debug mode to get the devs some logs?
http://www.piriform.com/docs/speccy/troubleshooting-speccy/running-speccy-in-debug-mode
I tried to run C:\ProgramFiles\Speccy\Speccy.exe /debug and found that "debug" will not run. I keep getting a message that the program can't be located, however I have double checked to ensure that the path is correct execpt that "debug" is not listed in the folder. So I'm not sure where to go from here??
Not enough spaces in "C:\ProgramFiles\Speccy\Speccy.exe /debug"
You need one more within ProgramFiles
"C:\Program Files\Speccy\Speccy.exe /debug"
also you want /debug to be outside of the quotes
the correctly formatted command line is
"C:\Program Files\Speccy\Speccy.exe" /debug
the " are important, you must type them or you will get the message you got (old windows bug is old). replace C:\Program files\speccy with the location of your speccy program if it is not in the default location
Speccy 1.14.288 crashes as soon as analyzing of items is complete, OS is Windows XP Pro SP3. Previous version was working fine.
Hi
I have the same problem
mine says it has had to close
details are
Problem signature:
Problem Event Name: APPCRASH
Application Name: speccy64.exe
Application Version: 1.14.0.288
Application Timestamp: 4eca55ae
Fault Module Name: aticfx64.dll
Fault Module Version: 8.17.10.1047
Fault Module Timestamp: 4cabd6c0
Exception Code: c0000005
Exception Offset: 000000000002f5bf
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: fdb3
Additional Information 2: fdb39814baa201982a8f1a9e3204b6e6
Additional Information 3: e8a5
Additional Information 4: e8a5a9b6769765ba902d369e482b44bf
i ran it debug as well just the same
cpu is i3-370 win 7 64 bit 6 gig of memory previous version ran with no problem
also latest ccleaner also fails if there is a neww or changed dll with startup items if that helps have reverted ccleaner back but left speccy with duff version for now
defraggler does not seem to have a problem
Hi
I have the same problem
mine says it has had to close
details are
Problem signature:
Problem Event Name: APPCRASH
Application Name: speccy64.exe
Application Version: 1.14.0.288
Application Timestamp: 4eca55ae
Fault Module Name: aticfx64.dll
Fault Module Version: 8.17.10.1047
Fault Module Timestamp: 4cabd6c0
Exception Code: c0000005
Exception Offset: 000000000002f5bf
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 2057
Additional Information 1: fdb3
Additional Information 2: fdb39814baa201982a8f1a9e3204b6e6
Additional Information 3: e8a5
Additional Information 4: e8a5a9b6769765ba902d369e482b44bf
i ran it debug as well just the same
cpu is i3-370 win 7 64 bit 6 gig of memory previous version ran with no problem
Have just checked and it created a 118 mb dump can ftp if you wish
also
debug trace
[2011-12-05 16:35:30] [iNFO ] CPU SDK at: C:\Users\Ken\AppData\Local\Temp speccycpuid.dll
[2011-12-05 16:35:34] [iNFO ] Monitor enumerator handle: 0x4A18980h
[2011-12-05 16:35:34] [iNFO ] Monitor HardwareId: MONITOR\TOS5091 DriverId: {4d36e96e-e325-11ce-bfc1-08002be10318}\0001
[2011-12-05 16:35:34] [iNFO ] Monitor driver name: Intel® HD Graphics
[2011-12-05 16:35:34] [iNFO ] Monitor mirroring driver: False
[2011-12-05 16:35:34] [iNFO ] Monitor display device active: True
[2011-12-05 16:35:34] [iNFO ] monitor device ID = < MONITOR\TOS5091\{4d36e96e-e325-11ce-bfc1-08002be10318}\0001 >
[2011-12-05 16:35:34] [iNFO ] continue with monitor device ID = < MONITOR\TOS5091\{4d36e96e-e325-11ce-bfc1-08002be10318}\0001 >
[2011-12-05 16:35:34] [iNFO ] monitorNameStr.IsEmpty()
[2011-12-05 16:35:34] [iNFO ] monitorNameStr = < Generic PnP Monitor >
[2011-12-05 16:35:34] [iNFO ] Monitor driver name: Intel® HD Graphics
[2011-12-05 16:35:34] [iNFO ] Monitor mirroring driver: False
[2011-12-05 16:35:34] [iNFO ] continue with monitor device ID = < >
[2011-12-05 16:35:34] [iNFO ] monitorNameStr.IsEmpty()
[2011-12-05 16:35:34] [iNFO ] monitorNameStr = < >
[2011-12-05 16:35:34] [iNFO ] Monitor driver name: RDPDD Chained DD
[2011-12-05 16:35:34] [iNFO ] Monitor mirroring driver: True
[2011-12-05 16:35:34] [iNFO ] Monitor driver name: RDP Encoder Mirror Driver
[2011-12-05 16:35:34] [iNFO ] Monitor mirroring driver: True
[2011-12-05 16:35:34] [iNFO ] Monitor driver name: RDP Reflector Display Driver
[2011-12-05 16:35:34] [iNFO ] Monitor mirroring driver: True
[2011-12-05 16:35:34] [iNFO ] Driver: Try to load driver.
[2011-12-05 16:35:35] [iNFO ] Driver: Load driver OK.
[2011-12-05 16:35:35] [iNFO ] Driver: Driver unload OK.
I will PM Kenny with info on how to get the dmp to me.
This program has toooo many problems. I'm just going to uninstall it and I am not about to pay for a support account, I'll just move on.
Lots of luck!!
I have a similar problem. Program crashes on the graphics analysis. My screen is 1600x900 resolution and I actually installed another driver which lowered the resolution to 1175xsomething, and speccy worked under that but my graphics were't right.
I really like th program and hope someone can help me out with a solution.
Thanks Mike
Log Name: Application
Source: Application Error
Date: 12/24/2011 11:35:53 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Mijke-PC
Description:
Faulting application name: speccy64.exe, version: 1.14.0.288, time stamp: 0x4eca55ae
Faulting module name: atio6axx.dll, version: 6.14.10.9236, time stamp: 0x4b2aaa84
Exception code: 0xc0000005
Fault offset: 0x000000000000d218
Faulting process id: 0x2fc
Faulting application start time: 0x01ccc25a063e7727
Faulting application path: C:\Program Files\Speccy\speccy64.exe
Faulting module path: C:\Windows\system32\atio6axx.dll
Report Id: 57fbedd8-2e4d-11e1-a539-e0cb4e35c05c
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-12-24T16:35:53.000000000Z" />
<EventRecordID>6255</EventRecordID>
<Channel>Application</Channel>
<Computer>Mijke-PC</Computer>
<Security />
</System>
<EventData>
<Data>speccy64.exe</Data>
<Data>1.14.0.288</Data>
<Data>4eca55ae</Data>
<Data>atio6axx.dll</Data>
<Data>6.14.10.9236</Data>
<Data>4b2aaa84</Data>
<Data>c0000005</Data>
<Data>000000000000d218</Data>
<Data>2fc</Data>
<Data>01ccc25a063e7727</Data>
<Data>C:\Program Files\Speccy\speccy64.exe</Data>
<Data>C:\Windows\system32\atio6axx.dll</Data>
<Data>57fbedd8-2e4d-11e1-a539-e0cb4e35c05c</Data>
</EventData>
</Event>
I have 32 Bit Windows 7 on my machine. But it doesn't crash on mine. Just shows 5 memory slots, which is wrong, because I only have 4. Should I do a debug log?
I have 32 Bit Windows 7 on my machine. But it doesn't crash on mine. Just shows 5 memory slots, which is wrong, because I only have 4. Should I do a debug log?
y' need to post a new topic not hijack other people's
Same problem here and only with 1.14.
Speccy 1.14.288 also frequenly crashes on my XP SP3 machine. The previous version did not, and I kind of wish that I had not deleted it. 288 seems to crash and either display nothing at all when analysing, or sometimes displays an error code and an error message under the RAM section.
Speccy 1.14.288 also frequenly crashes on my XP SP3 machine. The previous version did not, and I kind of wish that I had not deleted it.
Previous versions of Speccy can be downloaded from the right-hand side of this page.
Thanks for the logs. We are working on improving the logging for these issues and will have some improvements in the next release
Speccy versions over v1.07 still crashing.
XP Home SP3
See Pic
Speccy versions over v1.07 still crashing.
XP Home SP3
See Pic
Please keep your issue to your other thread, else it is hard to give each individual their due. mr ron is directly aiding in your issue, please stick with that