Jump to content

speccy keeps crashing


rvboutin

Recommended Posts

Hi,

No matter what, Speccy always crashes! The funny thing is that I can see and navigate the various panels if I leave the DrWatson windows open!? As soon as I click "send report" or anything else in the error windows, Speccy shuts down.

I don't know exactly what causes this except I have the following error in Windows even viewer:

 

Event Type:	Error
Event Source:	Application Error
Event Category:	None
Event ID:	1000
Date:		21/03/2011
Time:		16:42:12
User:		N/A
Computer:	L-AV2021D02
Description:
Faulting application speccy.exe, version 1.9.0.231, faulting module kernel32.dll, version 5.1.2600.5781, fault address 0x00012afb.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 73 70 65   ure  spe
0018: 63 63 79 2e 65 78 65 20   ccy.exe 
0020: 31 2e 39 2e 30 2e 32 33   1.9.0.23
0028: 31 20 69 6e 20 6b 65 72   1 in ker
0030: 6e 65 6c 33 32 2e 64 6c   nel32.dl
0038: 6c 20 35 2e 31 2e 32 36   l 5.1.26
0040: 30 30 2e 35 37 38 31 20   00.5781 
0048: 61 74 20 6f 66 66 73 65   at offse
0050: 74 20 30 30 30 31 32 61   t 00012a
0058: 66 62 0d 0a               fb..    

 

AND

 

 

Event Type:	Error
Event Source:	Application Error
Event Category:	None
Event ID:	1001
Date:		21/03/2011
Time:		16:44:46
User:		N/A
Computer:	L-AV2021D02
Description:
Fault bucket -1959716890.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 75 63 6b 65 74 3a 20   Bucket: 
0008: 2d 31 39 35 39 37 31 36   -1959716
0010: 38 39 30 0d 0a            890..   

 

I don't know if that can help...

Cheers,

Rv

Edited by Nergal
added code tags for easier readin
Link to comment
Share on other sites

  • Moderators

Please run speccy in debugger mode http://www.piriform.com/docs/speccy/troubleshooting-speccy/running-speccy-in-debug-mode

 

If it crashes please locate the log file created in your speccy directory (usually c:\program files\speccy) and use the attach file (found after pressing the reply button)

 

If you want to experiment to find the cause of the crashes run the debug-mode a number of times with these steps

 


  1.  
  2. uncheck everything
  3. check the first item
  4. run speccy
  5. if no crash then
  6. re-run debug
  7. uncheck everything
  8. check the next item
  9. repeat until you discover the crash 5-8

 

the developers read every thread so it is very important for you to attach the log file

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

CCLEANER, RECUVA, DEFRAGGLER AND SPECCY DOCUMENTATION CAN BE FOUND AT  https://support.piriform.com/hc/en-us and  https://www.ccleaner.com/docs

Pro users file a PRIORITY SUPPORT request at https://support.piriform.com/hc/en-us/requests/new

link to WINAPP2.INI explanation

Link to comment
Share on other sites

  • 3 weeks later...

 

I can not run debug mode, I get the error message "Windows can not find 'C:\Program Files\Speccy\Speccy.exe /debug'. Make sure you typed the name correctly, and then try again"

 

This *is* the right location of the file, as if I run it without the debug switch it runs the program before crashing. It does generate a temporary error report (attached) which it deletes when I close the program, and adds a DMP file to the speccy folder (52MB)

 

Any ideas?

4bfd_appcompat.txt

Link to comment
Share on other sites

  • Moderators

Also it should be (with quotes) "C:\Program Files\Speccy\Speccy.exe" /debug

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

CCLEANER, RECUVA, DEFRAGGLER AND SPECCY DOCUMENTATION CAN BE FOUND AT  https://support.piriform.com/hc/en-us and  https://www.ccleaner.com/docs

Pro users file a PRIORITY SUPPORT request at https://support.piriform.com/hc/en-us/requests/new

link to WINAPP2.INI explanation

Link to comment
Share on other sites

  • 4 weeks later...
  • Moderators

I recommend uninstalling Speccy, then downloading it again and installing it again to see if that resolves the issue.

 

Why? That wouldn't help us find the issue and fix it. Also this poster has not replied in a month so they probably either fixed it or gave up.

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

CCLEANER, RECUVA, DEFRAGGLER AND SPECCY DOCUMENTATION CAN BE FOUND AT  https://support.piriform.com/hc/en-us and  https://www.ccleaner.com/docs

Pro users file a PRIORITY SUPPORT request at https://support.piriform.com/hc/en-us/requests/new

link to WINAPP2.INI explanation

Link to comment
Share on other sites

I am also having the same problem with Speccy crashing every time I try to run it, even in debug mode with every option unchecked. Attached is the txt file, as the dmp file is too big and the forum won't let me attach it. I can provide it by email, FTP, or http link upon request.

 

Speccy_log1_10_2483-5-2011_22-22.txt

 

Any help would be appreciated. Thanks!

 

Jason

 

 

 

 

Please run speccy in debugger mode http://www.piriform.com/docs/speccy/troubleshooting-speccy/running-speccy-in-debug-mode

 

If it crashes please locate the log file created in your speccy directory (usually c:\program files\speccy) and use the attach file (found after pressing the reply button)

 

If you want to experiment to find the cause of the crashes run the debug-mode a number of times with these steps

 


  1.  
  2. uncheck everything
  3. check the first item
  4. run speccy
  5. if no crash then
  6. re-run debug
  7. uncheck everything
  8. check the next item
  9. repeat until you discover the crash 5-8

 

the developers read every thread so it is very important for you to attach the log file

Link to comment
Share on other sites

@Hazelnut,

 

When the user clicks on ""Start"", ""Run"" and uses the command box in an attempt to run Speccy in debug mode, then an error occurs. And I know why. Windows XP doesn't like the space between ""Program"" and ""Files"" !!!! Because then it responds with: ""Can't find the program c:\program"".

 

Before typing the path to Speccy, the user should open the MS-Dos prompt window first. Type in the ""Run"" box: ""CMD.exe"" and then the path to Speccy.

 

If this ""space error"" occurs in Win 7 and Vista as well (I use XP) then the info in the online documentation should be rewritten.

System setup: http://speccy.piriform.com/results/gcNzIPEjEb0B2khOOBVCHPc

 

A discussion always stimulates the braincells !!!

Link to comment
Share on other sites

  • Moderators

@willy2 This should not be needed. the space error dose not occur if you type it exactly as I stated in reply #5 (on all Operating systems)

 

ADVICE FOR USING CCleaner'S REGISTRY INTEGRITY SECTION

DON'T JUST CLEAN EVERYTHING THAT'S CHECKED OFF.

Do your Registry Cleaning in small bits (at the very least Check-mark by Check-mark)

ALWAYS BACKUP THE ENTRY, YOU NEVER KNOW WHAT YOU'LL BREAK IF YOU DON'T.

CCLEANER, RECUVA, DEFRAGGLER AND SPECCY DOCUMENTATION CAN BE FOUND AT  https://support.piriform.com/hc/en-us and  https://www.ccleaner.com/docs

Pro users file a PRIORITY SUPPORT request at https://support.piriform.com/hc/en-us/requests/new

link to WINAPP2.INI explanation

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.