CRC [Edit, R4] ripping

[carnageSWE]

I have burned 30-40 dvds lately, but now i cant burn anymore. Just gets the crcm, and ripping stops, also the computer hangs, and just dont wont to play anymore. It dosent matter if i use the dvd-rom or the burner! It also dosent matter what version of dvd shrink i use, and have also tried dvd x copy xpress, andsame result there, computer hangs!

Any ideas what this can be?

[ammck55]

Please familiarize yourself with the Forum Rules (http://forum.doom9.org/forum-rules.htm).

[carnageSWE]

doesent anyone know what this can depend on?
Could it be a virus of some kind?

[jggimi]

Possibilities: Hardware problem of some kind, in any one of many different components. It could be in innumerable places ...IDE bus cable or connection, power supply, PCI bus ... the list could be considerable.

Software problem of some kind, such as bad driver, damaged driver, misinstalled driver, interoperability failure between drivers ... operating system problem (missing or damaged software component) ... a BIOS bug .... the list could be considerable.Your thought that it may be a virus tuned to dvd burning applications or drivers is possible, but I would think highly unlikely. If you do not have virus protection software that is kept up to date regularly, then this could be possible, but I truly doubt this is your issue. Here are my recommendations, based upon the information you have provided regarding your difficulty. If you are running a DOS-based operating system such as Windows 98 or Windows Millenium Edition, a "PC hung" condition with no visible Blue Screen of Death from Microsoft is difficult to diagnose directly. My recommendation would be to run simple diagnostic software first. If your PC came from a major PC vendor, their packaged CDs or their support website should have diagnostic tools that do a cursory check of the hardware. If the diagnostics shows trouble or crashes, then you have a hardware problem. There are downloadable "stress test" applications that can help with diagnosing hardware problems, but those are typically more helpful with CPU heat-inducing application problems. These would be transcoding problems, not burning problems.

If you are running a DOS-based operating system and get a Blue Screen of Death, write down what you see on screen. It may be hardware or software related, but if it is a known condition to Microsoft, you'll find information and sometimes circumventions or fixes at http://support.microsoft.com.

If you are running an NT-based operating system such as Windows 2000 or Windows XP, then there are debugging tools that are available to you to help diagnose the problem. A "hung PC" can be diagnosed with Microsoft tools, but it takes two PCs connected together and special software running on both. If this is your trouble, you'll need two PCs, special cables, and WinDBG software downloaded from Microsoft. It's expensive and time consuming, so hardware diagnostics should be run prior to going down this path. Plus there are "keyboard commands" that can be set up to force a reboot...to collect a diagnostic "dump" of memory if the keyboard can still communicate with the operating system. These both should probably be attempted first.

Depending on how an NT-based operating system is configured, a Blue Screen of Death may only show on screen for an instant, followed by a reboot. It may show for a longer period of time. The system can be set to reboot or to halt. But unlike DOS-based operating systems, no matter how the operating system is configured, these errors are logged in the System Log, which is viewable by the Event Viewer application(in Administrative Tools, which can be found in the Control Panel). The log will show what was in the Blue Screen of Death message. But even better, if configured properly, the operating system can capture a "dump" of memory at the time of the error. WinDBG and other tools can read these dumps to provide indications of where a problem may be located, such as in a particular hardware driver.But here's my wild guess at the most likely trouble: a cable or it's connection. If both your DVD drives are on the same IDE bus (a commonly recommended practice), then the bus cable may have worked loose from the motherboard, or not been seated properly to begin with, if the installation was in recent weeks or months.

[carnageSWE]

Thank you for the answer,
I think i have haved this problem before, but re-installing windows (XP) solved the problem then. And when i got the problem this time, crc came up, but after a few tries i worked out fine again, but only for one time, and then it hung again!
But i am going to do as you said and look at the cabels, and see if they are ok. I dont get any blue screens of death, as its only the ripping programs that hungs, and everything else works fine.

[jggimi]

Now that we know it's XP, I recommend examining the System Log as described above,to determine if there were any entries at the time of the last event. To see if there was a dump created, look for an entry with a "Save Dump" source.

[carnageSWE]

i have looked att the system logg, and i can see where its start to cause truble. Its something about the dvd-rom, and as i got it all in swedish i´ll try to translate, can i post the dump here, or dosent it tell anything?

Anyway, it says something about an erroneous block at unit /device/cdrom0

That is the most common in the system logg, later there is marks of
unit /device/ide/idePort1 hasent responded within thelimited time frame!

All this is written in swedish and it is me and my bad english trying to translate it, but i hope it make some sense to u!

And by the way, i looked at the cabels and the all where in place!

[jggimi]

Based upon what you've found in the system log, I would say you have a likely hardware problem.

You mention that the cables are all in place -- they might look like they are seated, but there may be a bad connection. You might try removing and reseating them to the motherboard and to each device. The problem may dissappear by mererly improving a connection.

(You might also check to make sure that the devices on the IDE bus are not accidentally configured as both Master or Slave -- you should have one of each. I doubt this is the problem, but it is someting to double-check.)

If reseating the cable connections and checking the IDE device configurations doesn't solve the problem, then you may have a bad IDE cable, bad drive electronics, or a bad IDE bus controller on the motherboard. Here's how to determine which is most likely: To see if it is a motherboard problem, swap the two IDE cable connections at the motherboard. If the problem moves to the hard drives, then you know the problem is on the motherboard. If the problem stays with the DVD drives, you know it's either a cable or the electronics.

To see if it's the cable, swap cables. If the problem moves to the hard drives, it's the cable. If the problem stays with the DVD drives, its electronics on one of the disks.

To try to determine which drive's electronics may be bad, strap each drive as Master and connect it by itself to the IDE bus. If one drive doesn't work, you know it has bad electronics. If both work, perhaps it only works as a Master. Recall that originally one DVD was Master and the other was Slave. Try reversing their roles, and see if the problem goes away.Of course, it may be something else (bad BIOS, bad driver, etc.) but this is how to isolate a likely hardware problem.

[carnageSWE]

but shouldent i have problem with doing other stuff with them? I can use them for playing games and such!

[jggimi]

Based upon what you've found in the system log, I would say you have a likely hardware problem....Of course, it may be something else...