Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Computer crashes when transcoding .VOB files

Dec 5, 2003 11:33AM PST

I can't backup my DVDs that are on my hard drive. For some reason, every application I use for transcoding .VOB files, whether it be DVD X Copy, InterVideo DVD Copy, Nero Recode, etc... either the program or the computer crashes. I used to be able to do these things. I've done system restore back to when I was able to transcode .vob files, and the same things keep happening. So finally, I formatted my computer, and reinstalled everything. For about 3 days, everything worked fine. Now the same thing is happening again. I've closed all applications before doing trying to run these apps, and I've even copied the DVDs to my hard drive that is not connected to my Ultra ATA/133 PCI card (i have 3 HDs). I thought that maybe the ATA card was messing things up. But I don't think it is. My OS is on Drive C which is connected to the motherboard and not the ATA card. That is where I have now copied the DVDs to... but I still have no luck. I've been doing this for over a year, and the this month has been bizarre. Anyone have any suggestions?

As a side note, I have a gateway with plenty of HD space, 768 mb ram, and a 2ghz p4.processor.

Discussion is locked

- Collapse -
Re:Computer crashes when transcoding .VOB files
Dec 7, 2003 7:49PM PST

since you are able to do this procedure a number of times and then begin the crash, I would suggest looking into any of the temporary store folders to make sure they are emptied out after each one you do to make sure there is enough room inside that folder for the next one. As an example:

When you install a program, most of them use the C:\Windows\Temp folder for the actual setup.exe files to be put and once the install is completed, that folder is 'supposed' to empty out after a reboot so that you can do another install at a later date. If it doesn't empty out because windows or the program author didn't do a good job of this, then when you go to install the next program and its files try to go to that same folder, there are times when identically named files are still inside that folder and the install won't complete or you get an error dialog box telling you that you are out of 'memory' to do the installation.

Because of this vague error message, lots of people think they need more ram, when all they need to do is empty the temp folder, reboot, and try the install again.

If there is a possibility that your copying program is using one folder over and over as a temporary holder for the image file and/or the playlist file and if some of those file names are identical to what the next copy will have, this may be the cause of the crash.

Just an idea...

- Collapse -
Another person found it was heat related.
Dec 7, 2003 8:30PM PST

Pull the cover and point a fan at it. That 768 MB ram is an odd number. Try it with just 256 or 512.

Bob

- Collapse -
All the lovely HISTORY. Your new worm is installed or other.
Dec 7, 2003 8:56PM PST
http://reviews.cnet.com/5208-6138-0.html?forumID=31&threadID=5001&start=0 finds more food for this discussion. You may still be in denial about Nachi and MS-Blaster worms that invade systems that have the OS freshly installed and your antivirus can't stop these WORMS.

In short, you've started a new discussion, but left out the details that people could latch onto and help you out.

I ask: You do want help? Do you?

Bob