Can't Burn a CDRW

kosstheory wrote on 11/19/2003, 8:57 AM
Everytime I try to burn a CD My windows 2000 system crashes.

It usually just restarts the computer automatically, but the last time it went to the "blue screen of death" with a 'kmode_exception_not_handled' tag.

The only diffference was that in the last instance I didn't use buffer underrun protection while burning the disc.

In all cases the burn process will begin, and burn through several songs, but then it just gives up and crashes. It doesn't stop on the same song either.

To be fair, I 've had this computer for about 3 years now...

I'm running an AMD athlon 1.2 GHZ on an Abit kt7a-RAID MB with 512 MB of pc 133 ram. The Motherboard uses a via chipset. I use a Creative Sound Blaster platinum 5.1 with a live drive for my audio device, and a Matrox Meillenium G450 for my video card...

So, it's not the biggest and the best available...Still, I have been able to burn discs using Vegas before with no problems...

The Only thing that has changed is that I recently formated my OS drive and re-installed everything to clean my system up. I've tried burning about 7 disc since then, and I've only successfully burned one using Windows Media Player's Roxio burner plugin. However, that disc only had 2 songs on it...It seems like the longer the burn goes the better the chance it will fail, becaus eit never fails on the the first few songs it's always later in the burn when it crashes.

Additionally, I don't typically burn CDRWs it's just that I don't have any CD-Rs handy, but that couldn't be causing the problem could it?

Anyway, someone please help...

Thanks

Comments

BillyBoy wrote on 11/19/2003, 9:43 AM
It sounds like you answered your own question:

"I didn't use buffer underrun protection while burning the disc"

The dreaded buffer underrun problem used to loom large. The problem is as a disc is being burned it needs a constant data stream. If anything interupts it the drive's buffer can empty, thus the drive has no data to read and instant coaster. Newer drives prevent buffer under run either by having larger buffers which won't empty as fast or with hardware or software tricks that prevent underrun.
kosstheory wrote on 11/19/2003, 10:09 AM
Even when I burned the disc without using under run protection the computer crashed...

I've made coasters before, it happens sometimes...That's no big deal to me.

The real issue is my computer crashing...Why would my computer crash in the middle of a burn?
RichMacDonald wrote on 11/19/2003, 10:37 AM
>The real issue is my computer crashing...Why would my computer crash in the middle of a burn?

Does the app crash or do you get the dreaded blue-screen-of-death (BSOD)?

If BSOD, you probably have a hardware related problem and/or hardware drivers. Windows is getting pretty good at trapping software crashes and handling them without crashing. But hardware is still its achilles heel. Basically, Microsoft made a fatal decision some years ago to treat certain hardware errors as "the error has already happened so there is nothing we can do about it so we need to shut down totally". (Unlike the Mac, Unix, Linux et al., which is why Windows cannot compete at the high-end reliability shops, but that is OT.)

Curing BSOD is difficult, but at least you know its burner-related:

1) Check for IRQ conflicts.

2) Try uninstalling and reinstalling your burner-related software (having more than one burner-related software app is a well-known high-probability-of-problems, so try just one). Since Windows is absolutely terrible at cleaning up after itself, try something like Norton Utilities to examine your registry and fix any problems. If you've never done this and you've installed at least one Microsoft app, you almost certainly have them.

3) Go to your nearest superstore and buy another burner. Install it and see if that helps. Take it back when done. (Some might find this unethical, but it once solved a 100 hr burner sleuthing exercise for me several years back. That time I kept the new burner and threw the old one off a large building.)

4) Suck it up and reformat your drive and reinstall windows. Then install your burner software and see what happens.

P.S. Its almost certainly nothing to do with buffer underrun, so activate it and leave it on. It'll save coasters.

Oh yeah, test with rewritables. No need to waste money, even if its only 20cents/coaster.

---------
Update: I'm sorry, I didn't read your initial post well enough. I rechecked it and have additional comments:

So you do have a BSOD. And its related to a new install. Have you run a "Windows update" to be sure you have all the latest service packs? Try it with and without the service packs. I know the Windows media player just came out with a big update that included portions of Roxio. Perhaps the additional burner driver is causing conflicts.

Try a google search on "kmode_exception_not_handled". My first link led to a sex pirate page. My second link led to a Microsoft help page discussing virus infections. My 3rd link led to a Microsoft help page discussing an older ASPI driver. I expanded the search to "kmode_exception_not_handled CD burner" and found a blog reporting the same problem, and several other pages with reports and patches.

Theese links are all specific to whichever version of Windows you're running, so you'll need to take over the search from here.
Catwell wrote on 11/19/2003, 10:43 AM
Since you reinstalled Windows you may have replace a Vegas DLL or something with the original Windows file. Reinstall Vegas.
kosstheory wrote on 11/22/2003, 7:26 AM
Fixed it!

As it turns out my CPU was simply overheating...

I replaced my cpu fan and everything is working fine now...

Apparently the CPU was becoming unstable due to heat issues caused by a poor contact between the heat sink and the top of the processor.

This instability was causing the information being written to RAM during RAM intensive processes, like burning a disk, to be corrupted, and once the CPU got ot 68 degrees celsius the processor would shut itself down to keep from doing permanent damage...

Thanks for all of the suggestions...
kameronj wrote on 11/22/2003, 7:49 AM
It's probably overheating.

May want to check into that.