Skip to main content

TI 2009 suddenly crashing entire machine

Thread needs solution

Been using TI 2009 successfully on a XP Pro machine successfully since, well... 2009!
Same machine, same TI, same back up task, but beginning this month, TI freezes, entire screen freezes, and all I can do it press/hold power button to shut down. (Ctrl-Alt-Del doesn't give the usual window).
Once or twice before this started happening, I got a message that is failed to read a certain sector, I'd click "ignore," but entire thing would crash anyway.
I did a checkdisk, a few clusters were fixed - now I get no error msg from TI, but still it crashes and I haven't been able to back up. I reinstalled TI, but problem persists. Recreating the back up task yields same results.

Attached is what I believe to be most recent log. No errors shown in event log window, but I have noticed that when I select any event of any back up (successful or not, recent or past) there will often (always?) be an error code in the details of that event as listed below.

Incidentally, I CAN backup a single folder (as I have done for the photos I am currently working on.)

Getting very nervous since I haven't been able to back up!
Ideas?

0 Users found this helpful

It looks like you may have problems with some Windows files on your system. You may want to use your Recovery Disk to do a full disk backup.
At least you will have a backup, before proceeding further.

My last successful back up was June 29 (or thereabouts). Since then I've been on the road, not on the computer. The only real changes were added photos, whose folder I was able to back up individually. So I *think* I've got what I need. (correct me if you see my logic as faulty)
Meantime, what to do about the possible problems with the Windows files? Restore from the June 29 backup? Or something else? Run another checkdisk and see what I get?
Thank you!

FWIW, I should add that the bad clusters found/replaced by windows during the original checkdisk weren't system files as far as I can tell. They seemed to be the following: one in a podcast, one in a movie taken by my camera, one in spotify storage file.

If you are having sector read or write errors, your hard disk is probably failing. Since you have a full backup from June 29th, you could download a utility from the hard disk (not computer system) manufacturer to test your hard disk. If you run a destructive test, your hard disk will be wiped, but if the software corrects the problems on your hard drive, you thern could restore your backup to the corrected drive. If you drive continues to have sector read or write errors, I would suggest replacing it.

Yeah, I was afraid that I'd be shopping for a new disk. I *think* it's made by Toshiba. The little Toshiba utility on my laptop takes about a half second to run and says all is fine (how does it know in a half second?), and I've yet to find a better one on the Toshiba site/confirm the make of mine (need to just look at it directly.) But a second checkdisk reveals the following, which is pretty suspicious, at least according to my limited knowledge:

Checking file system on C:
The type of the file system is NTFS.
Volume label is SQ004953P02.

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 17 unused index entries from index $SII of file 0x9.
Cleaning up 17 unused index entries from index $SDH of file 0x9.
Cleaning up 17 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc0000185 at offset 0x4602416000 for 0x10000 bytes.
Read failure with status 0xc0000185 at offset 0x4602423000 for 0x1000 bytes.
Windows replaced bad clusters in file 41727
of name \DOCUME~1\Paula\LOCALS~1\APPLIC~1\MICROS~2\WINDOW~4\TH5E45~1.DB.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 1 bad clusters to the Bad Clusters File.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

381439295 KB total disk space.
248048852 KB in 275207 files.
114348 KB in 39148 indexes.
48 KB in bad sectors.
505379 KB in use by the system.
65536 KB occupied by the log file.
132770668 KB available on disk.

4096 bytes in each allocation unit.
95359823 total allocation units on disk.
33192667 allocation units available on disk.

Internal Info:
90 53 06 00 ff cb 04 00 52 ad 06 00 00 00 00 00 .S......R.......
b3 ee 00 00 09 00 00 00 4a 05 00 00 00 00 00 00 ........J.......
c6 75 0a 0f 00 00 00 00 e0 7f 78 fd 01 00 00 00 .u........x.....
38 2e 1b 1f 00 00 00 00 36 9b 07 fe 19 00 00 00 8.......6.......
22 42 49 40 08 00 00 00 44 ea e1 75 24 00 00 00 "BI@....D..u$...
99 9e 36 00 00 00 00 00 98 38 07 00 07 33 04 00 ..6......8...3..
00 00 00 00 00 50 b3 23 3b 00 00 00 ec 98 00 00 .....P.#;.......

Windows has finished checking your disk.
Please wait while your computer restarts.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Hmm, more info:

So I thought I'd try to verify the backup I've been counting on (on an external HDD). When I did so, I got read errors. Yikes! When I did so using someone else's machine, it verified fine. Makes me wonder if there's something else going on rather than/in additional to my internal HDD failing. As it stands, my machine operates normally except for backing up which either crashes or is extraordinarily slow.
Hm. Thoughts?

operaflute,

I'd concur with James F that this is most likely due to disk issues. Make sure you run chkdsk X: /R on each partition of the disk, where you replace X with the right partition letter. Use an elevated command prompt.
Alternatively, use the check disk option in the disk properties, but check both boxes.
Sometimes chkdsk won't detect errors that ATI detects. You best next step is to use your disk manufacturer's or a third party disk diagnostics tools...

Okay, thoughts on which diagnostic tool?
I have the Toshiba MK4055GSK and I don't believe there IS a Toshiba drive specific diagnostic tool, or at least I haven't found one. I have the Ultimate Windows Boot CD with many utilities, but again, they seem mfr specific, and none for Toshiba. Checkdisk already run with results posted earlier.

(Toshiba Disk Specs)
http://storage.toshiba.eu/cms/en/hdd/multimedia/product_detail.jsp?prod…

Before this let's try to uninstall and reinstall 2009 in a clean boot environment. This will help verify that your problem is not a conflict with third party software:
- uninstall 2009 from the control panel
- run msconfig
- disable all non-Microsoft services, disable all startup items
- reboot,
- reinstall 2009

Verify the problem has disappeared. If it is still there, well, we are still left with a potential disk issue. If it is gone, then we know some other software conflicts with 2009.

Yeah, reinstalling TI2009 was my first tactic. No go.

Now I'm trying to clone my disk to newly purchased HDD (if for no other reason than to see what happens), and running into a different set of problems. (FWIW, I have new disk in a temporary enclosure and connected via USB)
Problems:

1) Set partition size manually: I want one partition to remain same size, other to increase. (I'm moving from 400GB to 500GB disk. When I edit the smaller partition to downsize it to original size, I end up with unallocated space that I can not seem to add to the larger partition. Will not let me increase size of larger partition proportionally. Whatever, it's only 2GB, but annoying.

2) Nowhere does it ask me what I want to do with data on source disk (maintain or destroy). Not wanting to click "proceed" until I know what will happen to old disk. Perhaps it asks after hitting process, but don't really want to take the chance on this one.

Proper cloning should be done using the Recovery Disk, not while booted into Windows. If you are attaching two drives to your system via internal connections, make your new drive the primary, and the old drive the secondary. Boot the system to the Recovery Disk, and clone from the old to the new drive. Be sure to remove the old drive before booting the system. During a clone operation from the Recovery Disk be VERY CAREFUL that you select the correct disks for source and destination, as the drive letters assigned will not be the same as in Windows. If you are careful and do the clone correctly, the source drive is not touched other than to read data. It will be in the same condition as when you started. If you accidently clone from the new to the old hard drive, both will be blank.

Okay, thoughts on which diagnostic tool?

I suggest using the Western Digital Data Lifeguard for Windows http://support.wdc.com/product/download.asp?groupid=502&sid=3&lang=en if you find you need to test the disk.

From what I understand, after selecting the cloning options, TI shuts down windows and does the cloning before reboot? Trying to follow the TI instructions, but...

Follow James F recommendations and do the cloning from the recovery CD, not from Windows. Choose the manual method to control what happens to the partitions.

Tried cloning from the CD and the same two problems described above occur:
Can't repartition destination disk the way I desire
Does not ask me how what to do with the data on source disk.
(Didn't "proceed" lest I inadvertently destroy data on source disk.)

Operaflute,

Switch your approach to a disk and partition backup. Do it from the recovery CD. Remember that the recovery CD will show you drive letters different from Windows., Pay extra attention to disk labels/brands when you select what to backup, where to backup.
Once the backup is complete, remove the disk, put the new disk inside, boot the computer on the recovery CD and restore your disk.
http://forum.acronis.com/forum/29618

Yes, I guess that will have to be the next thing I try. Fingers crossed it will work from recovery CD, as it does not from Windows.

Vent:
Frustrated that things don't work as stated:
"If you selected manual mode, the program will ask you what to do with the old disk." (it does not)
"The manual transfer method allows you to resize partitions on the new disk.... you can drag it to reduce or enlarge the partition size." (Well, no, not really.)

Took 24 hours to backup, but that's done. Then the TI restore disk died. Now have new one.
Windows XP Disk Manager windows do not look like the ones in the linked article. No indication of which partitions are active, which aren't. Was going to just give up and restore entire disk at once, but TI doesn't give me option to resize to fit new disk. The instructions in the article are for TI2012, so I wonder if they even apply to 2009 anyway?
I have two partitions - the main one C: - NTFS, and HDD Recovery - FAT32 hidden partition. I presume the NTFS is active, other is not? NTFS one marked "system", other marked as "unknown"
In disk list, the FAT32 partition listed first (top of lsit), then the C:(NTFS) partition next, therefore unclear which partition is considered "partition one"
In graphical view, it's the opposite, with C: on left, HDD Recovery on right. Graphical view uses dark blue for both partitions, indicating both are primary.

Oy.

Attempting restore from recovery CD and still, it will not allow me to resize partitions. The slider will move the partition to left or right (changing amount of space before and after partition), but will not let me enlarge it.
Ideas?
If I decide to go back to the clone method, I assume the default will be to preserve the data on the original disk. Can anyone confirm this?

operaflute,

As Pat suggested in post #16 ,the link
http://forum.acronis.com/forum/29618
"1. Grover's How to-- TIH2012 Restore to larger or smaller disk"
at that link can help and it will enable you to resize the user partition as each partition is restored individually.
While the illustration is using 2012, the 2009 is almost identical in appearance. Follow the guide.

It is important that you complete the illustrations 7-8-9 (in the #1 guide) because doing so can provide you with information you need to have a successful restore. Figure 9 can show you

A. Which partitions should be first.
B. Which partition is the active partition.
C. What space is needed to be created BEFORE partition 1. (most likely the default will suffice as you are restoring xp.)

I took photos of my original partitions configuration (no printer at my disposal, as I'm traveling), and went through the process point by point, according to the guide, which I had (on a different computer screen, of course) by my side, and had a second, very computer savvy person follow along with me. It simply will NOT let me resize the partitions, even when restoring them one at a time. I can type numbers in the boxes or drag the slider, but it will only move the partition, not enlarge it. I suspect a quirk in the 2009 version, but I can't know.

If the photos are from your Windows Disk Management graphical view, which is the the first partition being restored?

If it its the smallest partition being restored first, the restored size will probably be the same as the original size so no resize necessary on that partition.

Give it another try hovering your mouse pointer over the partition boundary marker several times and you should be able to see the marker indicator change. In order to resize the partition, there has to be free space or unallocated space in the area where you are resizing into.

Give the guides another try and work your way through each step. I have used 2009 several times to do what you are wanting to do so but you may have to try and get the feel as to the mouse pointer.

Here is another guide which might offer more details but not specific to your computer. This might offer more illustrations about partition resizing.
http://forum.acronis.com/sites/default/files/forum/2009/08/3426/mar15_g…

I am assuming that your backup is a full and complete backup and includes all partitions on the disk within the backup.

I do indeed see the partition boundary marker change and AM able to slide it with the mouse. But when I do so, the entire partition shifts to the right, without actually changing size.
According to graphical view, partition number one is the larger one - my main one.
The other (partition two) is simply the manufacturer's recovery partition.

Yup, back up is a full one - both partitions.

Usually when the whole partition moves, it is because the pointer has selected the partition rather than the boundary. Try moving the pointer very very slowly and bring the mouse pointer onto the boundary from right edge moving right to left. Do it several times and you should see the mouser pointer change appearances.

Get the left boundary correct with the correct amount of "free space before" before attempting to move the right boundary. In order to move the right boundary, there has to be be unallocated space on the right which can be consumed by the partition boundary as it is resized. Be sure and leave enough "free space after" on the right of partition 1 so you have space for partition 2 to be put into the "free space after" space.

After you get the feel for how all the pieces fit, you will probably want to start over from the beginning with all unallocated space.

Gave up on that, cloned the disk via recovery CD. New disk in and working fine as far as I can tell, except that TI still continues to crash when I back up. This time it crashed when I opened it, took about 6 hours backing up, and crashed when trying to validate the backup "error reading the file."

So I uninstalled/reinstalled ATI 2009 thinking perhaps it got corrupted with the old HDD failing. Then I bought the 2012 upgrade for good measure. Some errors in installing it - had to try a few times.
Did one backup - success! Yay!
Then defragged my disk - it was due.
Attempted a second backup yesterday - problem recurs. "Error reading file" when validating the backup, then crashed. FWIW, the external HDD I'm writing to for the backups is also new.
Insanity is soon to follow...

Error reading file seems like an I/O problem. Did you try to validate the file using the recovery CD on another computer? If that works, you know that the motherboard, memory or connectors of the other computer are a problem. Run memtest to see if the memory is failing somehow. If that didn't work, there is still a chance there is a problem with your backup disk. Move the image to another disk and validate on another computer.

I hope I read it right: you didn't defrag the backup disk. There is no point doing that.

Latest info:

I can validate backup archive using the recovery CD without problems.
I can also eventually successfully validate if I hit "retry" over and over in response error msg. (Which requires I sit in front the computer for hours, however.)
I've had the problem on two different external HDDs, so unlikely they are the problem.
The computer passes Memtest 86+ V4.20.
You read correctly: I did not defrag the backupdisk, I defragged the internal drive.

Now what? (Thanks for everyone's help and suggestions, by the way) This is extra complicated because I've been traveling all summer - less time to mess with/diagnose laptop.

Operaflute,

I am suspecting some issue with the disk connectors, or the motherboard. Try to reseat the disk connectors, use preferably back USB connectors, change internal disk port...

Okay, that's out of my range of knowledge. More detailed explanation on how to do so?

By disk connectors do you mean the internal HDD? Or something to do with the USB connection to external? (I presume the latter, since the file that can't be validated is on the external?
What is a "back USB connector"?
Is there a diagnostic test for the mother board?

Thanks!

operaflute,

I assume that the external disk is connected through USB. Did you try to just change the USB connector?

Since your backup validates from the recovery CD, since you observed the error is independent of the backup disk, and since the computer passes the memtest86, everything seems to point at some hardware issue.

BTW, does the validation work if it is done separately from the backup?

If you can use your computer normally, and if the only problem is the inability to validate in Windows, I wouldn't worry too much. The validation process tends to push hardware quite a bit...
Do your validations from the recovery CD from time to time and continue backing up your computer from Windows.

It worries me that once it would validate, and now it won't. Seems to take a loong time to boot up, too. (Longer than usual.) Still suspect something is wrong. Might try re-installing windows when I get home, before I spend any more money. Perhaps some corruption has made it to the new drive?