Here is the error message I got reported in the event viewer just after it finished scanning for deleted files.
Application popup: Visual Studio Just-In-Time Debugger : An unhandled win32 exception occurred in recuva.exe [5680]. Just-In-Time debugging this exception failed with the following error: No installed debugger has Just-In-Time debugging enabled. In Visual Studio, Just-In-Time debugging can be enabled from Tools/Options/Debugging/Just-In-Time.
Check the documentation index for 'Just-in-time debugging, errors' for more information.
For more information, see Help and Support Center at
1
Application Crash After Scanning
Started by molitar, Jan 17 2007 02:46 AM
8 replies to this topic
#2 OFFLINE
-
- Admin
-
- 1,105 posts
Administrator
- Gender:Male
- Location:London, UK
Posted 17 January 2007 - 03:41 PM
Can you let me have your system specs and I'll look into it.
MrG
MrG
#3 OFFLINE
-
- Members
-
- 62 posts
Advanced Member
Posted 17 January 2007 - 03:56 PM
------------------ System Information ------------------ Time of this report: 1/17/2007, 10:45:46 Machine name: ALLEGIANCE Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519) Language: English (Regional Setting: English) System Manufacturer: NVIDIA System Model: AWRDACPI BIOS: Phoenix - AwardBIOS v6.00PG Processor: AMD Athlon(tm) 64 Processor 3000+, MMX, 3DNow, ~1.8GHz Memory: 1024MB RAM Page File: 461MB used, 2466MB available Windows Dir: C:\WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904) DX Setup Parameters: Not found DxDiag Version: 5.03.2600.2180 32bit Unicode --------------- Display Devices --------------- Card name: NVIDIA GeForce 6600 GT by TweaksRUs Manufacturer: NVIDIA Chip type: GeForce 6600 GT DAC type: Integrated RAMDAC Device Key: Enum\PCI\VEN_10DE&DEV_00F1&SUBSYS_00000000&REV_A2 Display Memory: 128.0 MB Current Mode: 1024 x 768 (32 bit) (85Hz) Monitor: Default Monitor ------------- Sound Devices ------------- Description: HDA Digital X-Mystique 7.1 Wave Device ------------------------ Disk & DVD/CD-ROM Drives ------------------------ ALL DRIVES ARE SATA Drive: C: Free Space: 253.9 GB Total Space: 476.9 GB File System: NTFS Model: SAMSUNG HD501LJ Drive: D: Free Space: 27.3 GB Total Space: 194.5 GB File System: NTFS Model: Maxtor 6Y200M0 Drive: E: Free Space: 22.5 GB Total Space: 156.3 GB File System: NTFS Model: Maxtor 6Y160M0 Drive: G: Model: LITE-ON DVDRW SHM-165H6S Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/3/2004 16:59:54, 49536 bytes Drive: F: Model: PLEXTOR CD-R PREMIUM Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/3/2004 16:59:54, 49536 bytes Drive: H: Model: GZ3743S UTT111R SCSI CdRom Device Driver: c:\windows\system32\drivers\cdrom.sys, 5.01.2600.2180 (English), 8/3/2004 16:59:54, 49536 bytes
#4 OFFLINE
-
- Members
-
- 62 posts
Advanced Member
Posted 20 January 2007 - 08:58 AM
Ok I found a possible reason for application crash. I have determined I can run it on Drive E just fine but it only fins just a little over 19K in files found.. But on drive D it finds over 78K in files found.. and drive C it finds over over 76K in files found. Drive E processing finishes just fine but both Drive C and D during processing crashes. So it seems the amount of files has something to do with the application crashes.
#6 OFFLINE
-
- Banned
-
- 2,198 posts
Annoyance
- Location:Internet
- Interests:Free software, open-source, GNU GPL, Linux, security, encryption, privacy, anonymity.
Posted 20 January 2007 - 05:31 PM
A crap cleaner shouldn't crash because there is too much crap.
Its the job of the cleaner to clean, so it should be able to clean even when there is much to clean.
Its the job of the cleaner to clean, so it should be able to clean even when there is much to clean.
#7 OFFLINE
-
- Members
-
- 409 posts
Advanced Member
Posted 20 January 2007 - 05:35 PM
Eldmannen, on Jan 20 2007, 05:31 PM, said:
A crap cleaner shouldn't crash because there is too much crap.
Its the job of the cleaner to clean, so it should be able to clean even when there is much to clean.
Its the job of the cleaner to clean, so it should be able to clean even when there is much to clean.
Does that apply to a recovery program as well
IE8 - NIS 2012 - Mbam -XP Home SP3
#8 OFFLINE
-
- Moderators
-
- 1,537 posts
Forum Moderator
- Gender:Male
- Location:Glendale, AZ
- Interests:CCleaner, Computers, and Movies
Posted 20 January 2007 - 10:18 PM
#1. This isn't a CCleaner thread. 
#2. More than likely it's a buffer overflow and is causing the program to crash. This should be able to fix easily (I think). I will see if I can reproduce this error, but I don't I can delete 70,000 files or so.
#2. More than likely it's a buffer overflow and is causing the program to crash. This should be able to fix easily (I think). I will see if I can reproduce this error, but I don't I can delete 70,000 files or so.
#9 OFFLINE
-
- Members
-
- 62 posts
Advanced Member
Posted 23 January 2007 - 07:37 AM
TwistedMetal, on Jan 20 2007, 05:18 PM, said:
#1. This isn't a CCleaner thread.
#2. More than likely it's a buffer overflow and is causing the program to crash. This should be able to fix easily (I think). I will see if I can reproduce this error, but I don't I can delete 70,000 files or so.
#2. More than likely it's a buffer overflow and is causing the program to crash. This should be able to fix easily (I think). I will see if I can reproduce this error, but I don't I can delete 70,000 files or so.
well one method could be to copy your win XP cd which has thousands of files onto a HD a few times.. than delete them.. wallah.. you will have tens of thousands of files soon.. Tho mine are from downloads.. files extracted.. than moved to the storage drives.. and deleted off the download drive.. adds up after a while ;p
