Alan_B

I suggest that if you want help you start a fresh topic commencing with full details of the computer which concerns you. If you wish then please copy to your topic relevant portions of your existing posts. I find it easier to understand if I can see everything simultaneously without having to remember what appeared on a separate page.

There most definitely IS a multistep scan procedure, which is to ONLY scan one partition at a time. I observe from your screen shots that you are trying to simultaneously deal with a minimum of partitions B:\ and C:\ and E:\, and perhaps there were other partitions also which are not apparent from the screen. I will allow those with more experience to answer your latest questions.

I think that 4 GB of RAM on a 64 bit system will probably be unable to deal with more data recovery than 2 GB of RAM on a 32 bit system, and Recuva may run out of RAM in your situation in some recovery modes. This shows success on a 10 TB drive so your situation is not hopeless http://forum.pirifor...showtopic=37586 In that case he had 32 GB of RAM, and he used 64 GB of memory - his Pagefile.sys must have been busy, but version 1.43 appears to be better than 1.44. You can get 1.43 from http://www.filehippo...d_recuva/12815/ I will leave it to those with more experience to give further advice.

Thanks, Now I can see them. Nice Topic Alan

I am signed in but when I click on any of the three SMART screen shots I get "You do not have permission to view this attachment." but your links to Wikipedia and Acronis work Alan

Could be a bug if you were dealing with a few hundred files in an 8 GB Flash Drive, but not if you have millions of deleted files in a multi TeraByte drive.

I have just tried the Portable version Piriform's Defraggler version 11, and I guess version 12 will have this same ability - it will show you hidden and inaccessible files. It will even show me the file "Chkdsk20110414213419.log" on the totally inaccessible and hidden path D:\System Volume Information\Chkdsk\ If there is a CCleaner registry backup it will have an extension REG. There is NO need to Defrag - or even to Analyze. Instead click on the TAB marched Search Tick the box against "Filename Contains:" and enter the word *.REG Tick the box "Include non-fragmented files" Then click the button "Search" and then an Analyze will happen after which every *.REG file will be shown. You can click on the header above the paths to sort the files into path order. and then look through the paths to see if any path includes something that looks like "Cleaner Backup Registry"

My previous laptop did not have enough USB2 ports for all my needs. My Desktop has far too many ports, including two on the "roof" that I can see and easily access on demand. (My "always needed/available" USB devices like keyboard/mouse/printer and things I forget are somewhere on the back panel) Macrium created on my secondary internal HDD a partition image backup file of C:\. I plugged into the rooftop my external backup HDD and used Windows to copy that backup file from secondary to external - no apparent problem. Then I used Macrium to validate the copy, which would have implied validity of the original. The copy failed, but I was able to validate the original. On a rampage I created a new folder on the external and copied the entire set of recent archives from the secondary to the internal. I think that was probably about 20 GB total consisting of two off 6.5 GB Full images and about 12 off Incremental and Differentials between 300 MB and 1.5 GB in size. Both the 6.5 GB copies had MD5 errors, and half of the small files also had errors. I am convinced that although I had properly and fully inserted the USB2 plug into the socket, the connection was defective. I have subsequently retested and found no problem - I just had a bad connection. The beauty of TeraCopy is that it does NOT assume the copy is good until it has subsequently read the copy. It does not CORRECT any error but is guaranteed to detect any MD5 hash checksum discrepancy, and if need be report the problem and retry a couple of times, and then allow me to fix any access problems and redo the few that fail. N.B. I do not know which of the two ports might be suspect because they are so close together and I failed to note at the time which was in use, and of course it could be a wonky USB2 plug or lead. I now am using an eSATA external drive for speed, but again it uses connectors and I still don't trust Windows so I still use Teracopy.

Your problem deserves to be in a separate topic. Probably the major and most significant difference is not the partition, but the operating system and to a far greater extent the fact that a "work computer" may well be under the jurisdiction of an I.T. department, and they may well have imposed special access permission restrictions that affect what you and CCleaner can delete. I think it would be unwise for anyone here to assist you in fixing a "wok computer" without the explicit approval of the owner of that computer.

You are welcome

Free and portable from a host I trust http://www.freewarefiles.com/CrystalDiskInfo-Portable_program_55190.html Just unzip and use - no installation.

I used Windows native COPY to duplicate my essential partition image backup files from my Secondary Internal HDD to an external USB2 HDD. The duplicates were NOT - they were the same size but the binary patterns differed and I was NOT aware of a problem until I ran Macrium Verify to validate them. (I have 40 years experience of computers and my distrust increases year by year). USB2 is good, but I do not bet my life or my archives on it. Since then I use Teracopy I appreciate and utilise all that Dennis quoted, and in addition appreciate that :- As each file is read from source a MD5 hash checksum is computed whilst it is being written to the destination ; After all files are written it then reads back from the destination and computes the MD5 hash checksum and compares with the value computed for the source ; After the above the screen shows all that has happened ; Then a single click will remove all successful results from the screen, leaving only the failures due to "no access etc." or MD5 hash errors, and after any user actions to obtain access etc. another click will reattempt everything that failed. When copying a large set of files and folders it will automatically retry 3 times and then SKIP any which are not readable, and then proceed to continue with all the other files.

I think you are wrong. The recommendation under discussion is that CCleaner should modify its behaviour when "Wiping", and that "Repair" provides a more suitable method for an SSD than using the Erase tool That recommendation has no impact upon the use by a non-SSD of any other capability in the Repair option.

Sorry. I glanced at your post and assumed the link was to a fix for a compressed NTDLR. My Malware concern was raised by what appears to be a computer reboot that was caused by downloading a file. Even if the file was INSTALLED as well as downloaded I would not expect defraggler to cause a computer reboot.

Simple Change the name with an extra space, i.e. [snagit 9 More*] and not [snagit 9 More*]

I have searched for the single word without referring to Microsoft or computers QCPRV and only find 11 results, mostly in foreign languages, plus this same problem at http://www.tomshardware.com/forum/64447-63-qcprv-compressed-control-restart-back-qcpr Defraggler was NOT run. Something that appeared to be defraggler was downloaded from an unknown site, and the computer rebooted and gave the error message. This definitely looks to me like malware, possibly from a File Hosting site that bundles in extra goodies like a downloader that went wrong, or something that is now capturing all financial transactions that are being attempted on the shop computer or network.

With all due respect, I feel that an observed speed improvement on a no trim/ncq SSD is not much more relevant to current technology than the physical layout of 80 column card punchers, sorters, and collators The probability is that your SSD is thoroughly constipated because when a file is deleted the SSD flash is not disturbed - the controller merely remembers the space that can now be reused. When a file is written it cannot be held in the space that can now be reused until the entire block containing that space has been erased, and that will FIRSTLY require that UN-deleted files held in the same block must be relocated into other empty Flash. Such an SSD system rapidly becomes very much slower when writing or updating files because when the user writes a 100 KB file, there might be 100 MB of data that need rewriting from one block to another so that a complete block can be erased and start life again. I know of this by the term "Write Multiplication". A simple illustration, Windows might write 10 GB to a new SSD and update those files 5 times before all 60 GB of Flash Cells have been written to. After this for every 10 GB that is updated, 20 GB has to be written and shuffled around to erase complete blocks to which the new 10 GB update is written I believe my SSD has a life of 10,000 Program Erase Cycles if I am lucky, but on a user forum I was warned not to expect better than 3000. I understand that more recent SSD with 3 bits per cell are much closer to single use and throw away Always remember that an SSD has a life expectancy that is a bit better than the 9 lives of a cat. A single pass defrag is likely to use up 3 Program Erase Cycle lives of every individual Flash cell, and much worse if the free space was not contiguous and a preliminary pass was needed to obtain a large enough space.

Are both computers 64 bit ?

Short Story :- Last Saturday my OCZ VERTEX2 SSD very briefly had no partitions, and the BIOS chose to obliterate from its CMOS settings my SSD credentials before it responded to my DEL key over-ride, when I selected Boot into my WinPE Boot Rescue Flash Drive and restored SSD partitions from image backup files. That is my only guess as to why my SSD no longer booted. I am now puzzled by why I suffered this RANDOM misfortune, because on at least two previous occasions of erasing and then restoring partitions the BIOS always booted the SSD at every opportunity. Have I encountered a random misfortune which every SSD owner has to live with ? The only differences between this bad situation and previous good situations might be :- How long I was hammering on the DEL key before the BIOS finished scrolling and responded to the key ; or Whether the Linux session is closed by a Restart, or by a Shut-down followed eventually by a Power-Up ; or Whether I was using an earlier version of the OCZ toolkit running under a similar Linux ISO but burnt to Bootable CD instead of held in a Bootable Flash. Long Story ( so I do not disappoint your expectations ) :- I used a Linux Boot Flash drive to perform a 5 second duration Secure ATA Erase on my SSD Then I used a WinPE Macrium Reflect Rescue Boot Flash Drive to restore both "System Reserved" and C:\ partitions. After which the BIOS refused to Boot into the OCZ SSD BUT it took several hours for me to realise it failed to boot. Windows was running in 56 GB C:\ partition on my SSD when I used Partition Wizard and noticed a peculiarity - My SSD "System Reserved" was shown as merely "Active" but the Samsung HDD "System Reserved" had become "Active & Boot", and then chosen to switch to the 56 GB system (C:) partition on SSD instead of running on the 25 GB System partition of the HDD. ( My Samsung HDD was my system drive before I had the SSD, and the Samsung had been demoted to second priority. ) That is when I realised that my BIOS had scrambled its configurations. Why is Windows so nasty to me I then powered up into the 'F8' Boot Selection screen, and observed that my SSD was at the top of the list that allows manual selection of any drive (HDD / SSD / Flash) I powered up into the "Del" BIOS menu and Chose the "Boot Priority"" Sub menu, and found that my CD Drive had top priority followed by my two HDD, but there was no sign of the SSD and I was unable to resurrect it. I then used the "Hard Drive" Sub menu and again there was no sign of the SSD, but after several clicks I struck lucky and the SSD was detected as a non-removable device, and I was able to add it to the list of Hard Drives. Then I returned to the "Del" BIOS menu and Chose the "Boot Priority" Sub menu and again could not see the SSD, but now I was able to resurrect it as a viable boot drive and I gave it Boot priority. After that my system booted into the SSD properly. MY ASSUMPTIONS :- The 'F8' Boot Selection screen is NOT affected by any BIOS configurations held in CMOS RAM, but merely lists all devices, removable and otherwise, that it can detect on startup. The "Boot Priority" is a BIOS configuration held in CMOS RAM, and apparently the CMOS RAM also holds a list of appropriate and "approved/known" non-removable Drives, After the SSD had all partitions removed the LINUX system closed down, and the computer powered back up into the BIOS and saw the SSD was totally empty, and chose to update the CMOS settings to totally exclude the SSD before it proceeded to respond to the DEL key and launch the WinPE Flash Drive. .

Do not use 2 defraggers. 1. They may have different optimising strategies and undo what the other does 2. You will not know which forum to complain to when a critical system file gets bent out of shape. Off Topic Is Kroozer getting younger every day

I believe SteamApps may "lock down" games to restrict cheating when competing. Is it possible that Steam "protection" is impeding Defraggler ?

The latest version has questionable performance with Pagefile. I might be worth trying the previous version held at FileHippo. http://www.filehippo.com/download_defraggler/tech/ Is it possible that what you need to defrag a 50 GB file is NOT 50 GB of Free Space but 50 GB of CONTIGUOUS Free Space. Perhaps your 200 GB Free Space is broken up into smaller 20 GB fragments by a few scattered files. Perhaps a preliminary defrag of only Free space might help, unless of course Windows has the scattered files "in use" and unmoveable. Perhaps a screen shot showing a Defraggler Analyse display would be useful. I ask questions because my skill is not with defraggler but in thinking "outside the box".

You are welcome. NB the third link was conveniently in my paste buffer so I repeated the link instead of referring to "the above".

Incorrect title. The "K" is Kilo as in Kilo Bytes. That image looks like Process Explorer and not Task Manager. I got 5550 search results from the phrase hardware interrupts and DPC This explains what DPC is https://en.wikipedia..._Procedure_Call This is an example of too much interrupt / DPC http://forums.majorg...ad.php?t=229157 You appear to suffer less than 1% of the CPU usage that caused grief at http://forums.majorg...ad.php?t=229157

@ svenvandewege You have asked a stupid question All moderators on this forum are fully experienced at creating and removing partitions. The ONLY reason I see for removing a partition is to obtain "Unallocated Space" that can be reused to create new partitions, and since partition creation requires that you launch a computer management/disk manager utility, why not defer the removal until you have launched this utility.