I have not had this issue before until now,i have deleted it and redownloaded and older versions and still get the same thing.The screens i show is what it shows first and a few seconds later the second one shows up....
1) 
2) 
What operating system are you using?
What security software do you run? Changed it recently?
Are you conected to the internet when you try to run Speccy?
Can you run it in debug mode and attach the log here?
http://www.piriform.com/docs/speccy/troubleshooting-speccy/running-speccy-in-debug-mode
"Class not registered" is typical of a WMI problem / corruption.
Try WMI Diagnosis Utility maybe this would help.
Richard S.
What operating system are you using?
What security software do you run? Changed it recently?
Are you conected to the internet when you try to run Speccy?
Can you run it in debug mode and attach the log here?
http://www.piriform.com/docs/speccy/troubleshooting-speccy/running-speccy-in-debug-mode
Operating system:Windows 7 ultimate 64 bit
Internet security:AVG
Connected to net:Yes
Debug:PC literate,need to know how please.
I never had issues before,i also use the CCLeaner,Defag,Recuva with no problems
Debug:PC literate,need to know how please.
Did you click on the link in Hazelnut's post? It explains what you are asking.
Click here--> http://www.piriform.com/docs/speccy/troubleshooting-speccy/running-speccy-in-debug-mode
Did you click on the link in Hazelnut's post? It explains what you are asking.
Click here--> http://www.piriform.com/docs/speccy/troubleshooting-speccy/running-speccy-in-debug-mode
Yes and there is no debug tool in the folder..
I found these documents where its downloaded at after it crashes
DOCUMENT NO.1
....1 08:35:51 (0) ** LOG file "C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.35.35.LOG" created.
....2 08:35:51 (0) ** CSV file "C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.35.35-STATISTICS.CSV" created.
....3 08:35:51 (0) ** TXT file "C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.35.35-REPORT.TXT" created.
....4 08:35:51 (0) ** WMIDiag v2.0 started on Saturday, July 02, 2011 at 08:35.
....5 08:35:51 (0) **
....6 08:35:51 (0) ** Copyright © Microsoft Corporation. All rights reserved - January 2007.
....7 08:35:51 (0) **
....8 08:35:51 (0) ** This script is not supported under any Microsoft standard support program or service.
....9 08:35:51 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
...10 08:35:51 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
...11 08:35:51 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
...12 08:35:51 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
...13 08:35:51 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
...14 08:35:51 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
...15 08:35:51 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
...16 08:35:51 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
...17 08:35:51 (0) ** of the possibility of such damages.
...18 08:35:51 (0) **
...19 08:35:51 (3) NOECHO=True
...20 08:35:51 (3) SILENT=False
...21 08:35:51 (3) SMS=False
...22 08:35:51 (3) FORCE=False
...23 08:35:51 (3) NOWINZIP=False
...24 08:35:51 (3) DEBUG=False
...25 08:35:51 (3) STATISTICS=False
...26 08:35:51 (3) RUNONCE=False
...27 08:35:51 (3) DEPTH LEVEL=1
...28 08:35:51 (3) LOGGINGLEVEL=0
...29 08:35:51 (3) EVENTLOG=False
...30 08:35:51 (3) EVENTLOGERRORS=False
...31 08:35:51 (3) LOGWMISTATE=False
...32 08:35:51 (3) ERRORPOPUP=False
...33 08:35:51 (3) REQUESTALLINSTANCES=1
...34 08:35:51 (3) WRITEINREPOSITORY=False
...35 08:35:51 (3) CHECKCONSISTENCY=False
...36 08:35:51 (3) SHOWMOFERRORS=False
...37 08:35:51 (3) SHOWHIGHPRIVPROVIDERS=False
...38 08:35:51 (3) CORRELATECLASSANDPROVIDER=False
...39 08:35:51 (3) STRICT=False
...40 08:35:51 (3) OLDESTLOGHISTORY=0
...41 08:35:51 (3) OLDESTEVENTLOGHISTORY=20
...42 08:35:51 (3) BASENAMESPACE=Root
...43 08:35:51 (0) ** Verifying last run of WMIDiag.
...44 08:35:51 (4) Reading registry (REG_SZ) 'HKLM\Software\Microsoft\WMIDiag\LastRun'.
...45 08:35:51 (0) ** Logging Run-time environment information.
...46 08:35:51 (3) StartMenu=C:\USERS\BRIAN\APPDATA\ROAMING\MICROSOFT\WINDOWS\START MENU\
...47 08:35:51 (3) Desktop=C:\USERS\BRIAN\DESKTOP\
...48 08:35:51 (3) Programs=C:\USERS\BRIAN\APPDATA\ROAMING\MICROSOFT\WINDOWS\START MENU\PROGRAMS\
...49 08:35:51 (3) SystemDrive=C:\
...50 08:35:51 (3) SystemRoot=C:\WINDOWS\
...51 08:35:51 (3) Path=C:\WINDOWS\SYSTEM32;C:\WINDOWS;C:\WINDOWS\SYSTEM32\WBEM;C:\PROGRAM FILES (X86)\ATI TECHNOLOGIES\ATI.ACE\CORE-STATIC;C:\WINDOWS\SYSTEM32\WINDOWSPOWERSHELL\V1.0\;C:\PROGRAM FILES (X86)\QUICKTIME\QTSYSTEM\;C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\WINDOWS LIVE\
...52 08:35:51 (3) UserTemp=C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\
...53 08:35:51 (3) SystemTemp=C:\WINDOWS\TEMP\
...54 08:35:51 (3) System32=C:\WINDOWS\SYSTEM32\
...55 08:35:51 (3) System=C:\WINDOWS\SYSTEM\
...56 08:35:51 (3) Wbem=C:\WINDOWS\SYSTEM32\WBEM\
...57 08:35:51 (3) WbemLogs=C:\WINDOWS\SYSTEM32\WBEM\LOGS\
...58 08:35:51 (3) CurrentDirectory=C:\USERS\BRIAN\DESKTOP\NEW FOLDER (4)
...59 08:35:51 (3) AllUsersStartMenu=C:\PROGRAMDATA\MICROSOFT\WINDOWS\START MENU\
...60 08:35:51 (3) AllUsersDesktop=C:\USERS\PUBLIC\DESKTOP\
...61 08:35:51 (3) AllUsersPrograms=C:\PROGRAMDATA\MICROSOFT\WINDOWS\START MENU\PROGRAMS\
...62 08:35:51 (3) ScriptName=WMIDIAG.VBS
...63 08:35:51 (3) ScriptFullName=C:\USERS\BRIAN\DESKTOP\NEW FOLDER (4)\WMIDIAG.VBS
...64 08:35:51 (3) ScriptingName=WINDOWS SCRIPT HOST
...65 08:35:51 (3) EngineFullName=C:\WINDOWS\SYSTEM32\WSCRIPT.EXE
...66 08:35:51 (3) CommandLine=C:\USERS\BRIAN\DESKTOP\NEW FOLDER (4)\WMIDIAG.VBS
...67 08:35:51 (3) EnginePath=C:\WINDOWS\SYSTEM32
...68 08:35:51 (3) EngineVersion=5.8
...69 08:35:51 (3) DomainName=BRIAN-PC
...70 08:35:51 (3) UserName=BRIAN
...71 08:35:51 (3) UserDNSDomain=
...72 08:35:51 (3) LogonServerName=BRIAN-PC
...73 08:35:51 (3) LocalComputerName=BRIAN-PC
...74 08:35:51 (3) ProductName=Windows 7 Ultimate
...75 08:35:51 (3) Locale=00000409
...76 08:35:51 (3) IsServerOS=False
...77 08:35:51 (3) Is64=True
...78 08:35:51 (3) IsWow64=False
...79 08:35:51 (3) ProcessorArchitecture=64-bit
...80 08:35:51 (3) ProcessorIdentifier=AMD64 Family 16 Model 2 Stepping 2, AuthenticAMD
...81 08:35:51 (3) NTVersion=6.1
...82 08:35:51 (3) NTBuild=7601
...83 08:35:51 (3) NTServicePack=Service Pack 1
...84 08:35:51 (3) FullName=Unsupported Windows version - 64-bit
...85 08:35:51 (3) ShortName=_____.___.___.__
...86 08:35:51 (3) SMSAgent=
...87 08:35:51 (3) WinZIP=
...88 08:35:51 (0) ** Initializing WMI System Information.
...89 08:35:51 (0) ** Unsupported Windows version - 64-bit (_____.___.___.__).
...90 08:35:51 (1) !! ERROR: (Main) : Unsupported OS version or build #.
...91 08:35:55 (0) ** ABORT: WMIDiag execution aborted. Check 'C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.35.35.LOG' for details.
...92 08:35:55 (0) **
...93 08:35:55 (0) ** WMIDiag executed in 20 second(s).
...94 08:35:55 (3)
...95 08:35:55 (3) 2.0,7/2/2011,8:35:51 AM,7/2/2011 8:35:51 AM,False,True,False,64-bit,AMD64 Family 16 Model 2 Stepping 2 AuthenticAMD,6.1,7601,Service Pack 1,Unsupported Windows version - 64-bit,_____.___.___.__,00000409,BRIAN-PC,BRIAN-PC\BRIAN, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,7/2/2011,8:35:55 AM,0,0,0,20,0,1,4,WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.35.35.LOG,C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.35.35.LOG
...96 08:35:55 (3)
...97 08:35:55 (0) ** WMIDiag v2.0 ended on Saturday, July 02, 2011 at 08:35 (W:0 E:1 S:4).
..129 08:35:55 (0) ** TXT file "C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.35.35-REPORT.TXT" closed.
..130 08:35:55 (0) ** CSV file "C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.35.35-STATISTICS.CSV" closed.
..131 08:35:55 (0) ** LOG file "C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.35.35.LOG" closed.
DOCUMENT NO.2
..100 08:41:20 (0) ** WMIDiag v2.0 started on Saturday, July 02, 2011 at 08:41.
..101 08:41:20 (0) **
..102 08:41:20 (0) ** Copyright © Microsoft Corporation. All rights reserved - January 2007.
..103 08:41:20 (0) **
..104 08:41:20 (0) ** This script is not supported under any Microsoft standard support program or service.
..105 08:41:20 (0) ** The script is provided AS IS without warranty of any kind. Microsoft further disclaims all
..106 08:41:20 (0) ** implied warranties including, without limitation, any implied warranties of merchantability
..107 08:41:20 (0) ** or of fitness for a particular purpose. The entire risk arising out of the use or performance
..108 08:41:20 (0) ** of the scripts and documentation remains with you. In no event shall Microsoft, its authors,
..109 08:41:20 (0) ** or anyone else involved in the creation, production, or delivery of the script be liable for
..110 08:41:20 (0) ** any damages whatsoever (including, without limitation, damages for loss of business profits,
..111 08:41:20 (0) ** business interruption, loss of business information, or other pecuniary loss) arising out of
..112 08:41:20 (0) ** the use of or inability to use the script or documentation, even if Microsoft has been advised
..113 08:41:20 (0) ** of the possibility of such damages.
..114 08:41:20 (0) **
..115 08:41:20 (0) **
..116 08:41:20 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..117 08:41:20 (0) ** ----------------------------------------------------- WMI REPORT: BEGIN ----------------------------------------------------------
..118 08:41:20 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..119 08:41:20 (0) **
..120 08:41:20 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..121 08:41:20 (0) ** Unsupported Windows version - 64-bit (7601) - User 'BRIAN-PC\BRIAN' on computer 'BRIAN-PC'.
..122 08:41:20 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..123 08:41:20 (0) **
..124 08:41:20 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..125 08:41:20 (0) ** ------------------------------------------------------ WMI REPORT: END -----------------------------------------------------------
..126 08:41:20 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
..127 08:41:20 (0) **
..128 08:41:20 (0) ** ABORT: WMIDiag execution aborted. Check 'C:\USERS\BRIAN\APPDATA\LOCAL\TEMP\WMIDIAG-V2.0______.___.___.___BRIAN-PC_2011.07.02_08.40.56.LOG' for details.
..129 08:41:20 (0) **
..130 08:41:20 (0) ** WMIDiag v2.0 ended on Saturday, July 02, 2011 at 08:41 (W:1 E:1 S:4).
You are correct, there is no "debug tool." You are not reading the instructions correctly. It is telling you to manually run the Speccy64.exe program with the /debug switch added to the end of the command. From the Windows Start button, type the word run and hit Enter. Type in the full path to the main Speccy program and add the debug switch, like this: C:\Program Files\Speccy\Speccy64.exe /debug
It looks like you are running Win7 64-bit, so your Run line should be the same as mine. When you click OK, this window should pop up. Check all the boxes.
Click OK and Speccy will run in debug mode. The debug log will be created in the main Speccy program folder:
This is the contents of my log:
[2011-07-02 10:09:35] [iNFO ] CPU SDK at: C:\Users\GARY&L~1\AppData\Local\Temp speccycpuid.dll
[2011-07-02 10:09:41] [iNFO ] Monitor enumerator handle: 0x66B5D60h
[2011-07-02 10:09:41] [iNFO ] Monitor HardwareId: MONITOR\LEN4036 DriverId: {4d36e96e-e325-11ce-bfc1-08002be10318}\0001
[2011-07-02 10:09:41] [iNFO ] Monitor driver name: Intel(R) HD Graphics
[2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: False
[2011-07-02 10:09:41] [iNFO ] Monitor display device active: True
[2011-07-02 10:09:41] [iNFO ] monitor device ID = < MONITOR\LEN4036\{4d36e96e-e325-11ce-bfc1-08002be10318}\0001 >
[2011-07-02 10:09:41] [iNFO ] continue with monitor device ID = < MONITOR\LEN4036\{4d36e96e-e325-11ce-bfc1-08002be10318}\0001 >
[2011-07-02 10:09:41] [iNFO ] monitorNameStr.IsEmpty()
[2011-07-02 10:09:41] [iNFO ] monitorNameStr = < ThinkPad Display 1440x900 >
[2011-07-02 10:09:41] [iNFO ] Monitor driver name: Intel(R) HD Graphics
[2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: False
[2011-07-02 10:09:41] [iNFO ] continue with monitor device ID = < >
[2011-07-02 10:09:41] [iNFO ] monitorNameStr.IsEmpty()
[2011-07-02 10:09:41] [iNFO ] monitorNameStr = < >
[2011-07-02 10:09:41] [iNFO ] Monitor driver name: RDPDD Chained DD
[2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: True
[2011-07-02 10:09:41] [iNFO ] Monitor driver name: RDP Encoder Mirror Driver
[2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: True
[2011-07-02 10:09:41] [iNFO ] Monitor driver name: RDP Reflector Display Driver
[2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: True
[2011-07-02 10:09:41] [iNFO ] Driver: Try to load driver.
[2011-07-02 10:09:41] [iNFO ] Driver: Load driver OK.
[2011-07-02 10:09:41] [iNFO ] Driver: Driver unload OK.
Hope that helps.
You are correct, there is no "debug tool." You are not reading the instructions correctly. It is telling you to manually run the Speccy64.exe program with the /debug switch added to the end of the command. From the Windows Start button, type the word run and hit Enter. Type in the full path to the main Speccy program and add the debug switch, like this: C:\Program Files\Speccy\Speccy64.exe /debug
It looks like you are running Win7 64-bit, so your Run line should be the same as mine. When you click OK, this window should pop up. Check all the boxes.
Click OK and Speccy will run in debug mode. The debug log will be created in the main Speccy program folder:
This is the contents of my log:
[2011-07-02 10:09:35] [iNFO ] CPU SDK at: C:\Users\GARY&L~1\AppData\Local\Temp speccycpuid.dll [2011-07-02 10:09:41] [iNFO ] Monitor enumerator handle: 0x66B5D60h [2011-07-02 10:09:41] [iNFO ] Monitor HardwareId: MONITOR\LEN4036 DriverId: {4d36e96e-e325-11ce-bfc1-08002be10318}\0001 [2011-07-02 10:09:41] [iNFO ] Monitor driver name: Intel(R) HD Graphics [2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: False [2011-07-02 10:09:41] [iNFO ] Monitor display device active: True [2011-07-02 10:09:41] [iNFO ] monitor device ID = < MONITOR\LEN4036\{4d36e96e-e325-11ce-bfc1-08002be10318}\0001 > [2011-07-02 10:09:41] [iNFO ] continue with monitor device ID = < MONITOR\LEN4036\{4d36e96e-e325-11ce-bfc1-08002be10318}\0001 > [2011-07-02 10:09:41] [iNFO ] monitorNameStr.IsEmpty() [2011-07-02 10:09:41] [iNFO ] monitorNameStr = < ThinkPad Display 1440x900 > [2011-07-02 10:09:41] [iNFO ] Monitor driver name: Intel(R) HD Graphics [2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: False [2011-07-02 10:09:41] [iNFO ] continue with monitor device ID = < > [2011-07-02 10:09:41] [iNFO ] monitorNameStr.IsEmpty() [2011-07-02 10:09:41] [iNFO ] monitorNameStr = < > [2011-07-02 10:09:41] [iNFO ] Monitor driver name: RDPDD Chained DD [2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: True [2011-07-02 10:09:41] [iNFO ] Monitor driver name: RDP Encoder Mirror Driver [2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: True [2011-07-02 10:09:41] [iNFO ] Monitor driver name: RDP Reflector Display Driver [2011-07-02 10:09:41] [iNFO ] Monitor mirroring driver: True [2011-07-02 10:09:41] [iNFO ] Driver: Try to load driver. [2011-07-02 10:09:41] [iNFO ] Driver: Load driver OK. [2011-07-02 10:09:41] [iNFO ] Driver: Driver unload OK.
Hope that helps.
well i did it and still get the same thing in my original post with the screenies,but this is the only file i came out with with though......
[2011-07-02 10:48:29] [iNFO ] CPU SDK at: C:\Users\Brian\AppData\Local\Temp speccycpuid0.dll
The crashes you're getting may be stopping Speccy before the debug log file can be created.
i dont know.......its rather disappointing though.I just uninstalled it i guess not to use it again.Hopefully some one might post a salution that might work.
PlayToy the WMIdiagnosis Utility Tool V 2 does not work on win7 64bit yet. Microsoft hasn't added some missing bits
So that is why in the logs you found (post 7 of this thread) it says
#ERROR: (Main) : Unsupported OS version or build
#ABORT: WMIDiag execution aborted
In your security centre is avg shown correctly as your antivirus?
If you just for a few seconds disable avg while you run speccy does it work then?
PlayToy the WMIdiagnosis Utility Tool V 2 does not work on win7 64bit yet. Microsoft hasn't added some missing bits
So that is why in the logs you found (post 7 of this thread) it says
#ERROR: (Main) : Unsupported OS version or build
#ABORT: WMIDiag execution aborted
In your security centre is avg shown correctly as your antivirus?
If you just for a few seconds disable avg while you run speccy does it work then?
Yes i disabled it when it was downloaded and when i tried to run it also,still dont work.Stupid popup comes up as i described,who knows.
Do you get any speccy crash if you run it in safe mode with networking option?
Do you get any speccy crash if you run it in safe mode with networking option?
tried in safe mode and safe mode with networking........still does it.
Just out of curiosity do you have anything noteworthy in the Application and System event logs (eventvwr.exe)??
Richard S.
Just out of curiosity do you have anything noteworthy in the Application and System event logs (eventvwr.exe)??
Richard S.
I found what you mentioned,but dont know what im suppose to be looking for....a little help would be appreciated please?
This is all i found in the [eventvwr.exe],hopefully some one can figure it out in this mess....
Log Name: Application
Source: Application Error
Date: 7/4/2011 3:56:53 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Brian-PC
Description:
Faulting application name: Speccy64.exe, version: 1.11.0.256, time stamp: 0x4de650b1
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c78c
Exception code: 0xe06d7363
Fault offset: 0x000000000000a49d
Faulting process id: 0x1594
Faulting application start time: 0x01cc3a8483d43199
Faulting application path: C:\Program Files\Speccy\Speccy64.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: c2fa4cdc-a677-11e0-8d83-00038a000015
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">'>http://schemas.microsoft.com/win/2004/08/events/event">'>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-07-04T19:56:53.000000000Z" />
<EventRecordID>68489</EventRecordID>
<Channel>Application</Channel>
<Computer>Brian-PC</Computer>
<Security />
</System>
<EventData>
<Data>Speccy64.exe</Data>
<Data>1.11.0.256</Data>
<Data>4de650b1</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.17514</Data>
<Data>4ce7c78c</Data>
<Data>e06d7363</Data>
<Data>000000000000a49d</Data>
<Data>1594</Data>
<Data>01cc3a8483d43199</Data>
<Data>C:\Program Files\Speccy\Speccy64.exe</Data>
<Data>C:\Windows\system32\KERNELBASE.dll</Data>
<Data>c2fa4cdc-a677-11e0-8d83-00038a000015</Data>
</EventData>
</Event>Log Name: Application
Source: Windows Error Reporting
Date: 7/4/2011 3:56:56 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Brian-PC
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Speccy64.exe
P2: 1.11.0.256
P3: 4de650b1
P4: KERNELBASE.dll
P5: 6.1.7601.17514
P6: 4ce7c78c
P7: e06d7363
P8: 000000000000a49d
P9:
P10:
Attached files:
C:\Users\Brian\AppData\Local\Temp\WER88B6.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\Brian\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Speccy64.exe_464ba147e9f920a21b9698ce8eca7b5dd889b43d_1acc9303
Analysis symbol:
Rechecking for solution: 0
Report Id: c2fa4cdc-a677-11e0-8d83-00038a000015
Report Status: 1
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-07-04T19:56:56.000000000Z" />
<EventRecordID>68490</EventRecordID>
<Channel>Application</Channel>
<Computer>Brian-PC</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>0</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>Speccy64.exe</Data>
<Data>1.11.0.256</Data>
<Data>4de650b1</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.17514</Data>
<Data>4ce7c78c</Data>
<Data>e06d7363</Data>
<Data>000000000000a49d</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Users\Brian\AppData\Local\Temp\WER88B6.tmp.WERInternalMetadata.xml</Data>
<Data>C:\Users\Brian\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Speccy64.exe_464ba147e9f920a21b9698ce8eca7b5dd889b43d_1acc9303</Data>
<Data>
</Data>
<Data>0</Data>
<Data>c2fa4cdc-a677-11e0-8d83-00038a000015</Data>
<Data>1</Data>
</EventData>
</Event>
Log Name: Application
Source: Application Error
Date: 7/4/2011 3:56:53 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Brian-PC
Description:
Faulting application name: Speccy64.exe, version: 1.11.0.256, time stamp: 0x4de650b1
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c78c
Exception code: 0xe06d7363
Fault offset: 0x000000000000a49d
Faulting process id: 0x1594
Faulting application start time: 0x01cc3a8483d43199
Faulting application path: C:\Program Files\Speccy\Speccy64.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: c2fa4cdc-a677-11e0-8d83-00038a000015
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-07-04T19:56:53.000000000Z" />
<EventRecordID>68489</EventRecordID>
<Channel>Application</Channel>
<Computer>Brian-PC</Computer>
<Security />
</System>
<EventData>
<Data>Speccy64.exe</Data>
<Data>1.11.0.256</Data>
<Data>4de650b1</Data>
<Data>KERNELBASE.dll</Data>
<Data>6.1.7601.17514</Data>
<Data>4ce7c78c</Data>
<Data>e06d7363</Data>
<Data>000000000000a49d</Data>
<Data>1594</Data>
<Data>01cc3a8483d43199</Data>
<Data>C:\Program Files\Speccy\Speccy64.exe</Data>
<Data>C:\Windows\system32\KERNELBASE.dll</Data>
<Data>c2fa4cdc-a677-11e0-8d83-00038a000015</Data>
</EventData>
</Event>
SIIGGHHHHH.............
The devs do read all the threads PlayToy, so there may be some input from them, and the information you've posted will no doubt help.
It makes no sense to me, but it probably will to them.
Don't get too despondent as these things can be tricky to pin down.
Just out of interest, have you tried any other System Information programs such as "SIW" (free version)? If so, do they run OK?