Page 1 of 1

16x DVD burner issues

PostPosted: Sun Sep 18, 2005 7:07 pm
by expansion
I'm hoping someone might be able to help me with this...

I've tried 3 different models of DVD burner in the last 2 days. An I/O Magic, a Lite-On SOHW-1673S and I now have a Sony DRU-800A in my computer. They all seem to be giving me the same issue. I get about 50% through burning a DVD -R and suddenly the computer will just completely reset. I get no opportunity to get error messages or anything because the program doesn't even have a chance to register them. I've update the firmware on each of the burners and it hasn't helped. The only thing I've really got to go on is a 'power calibration error' that I got in nero on one of the rare instances where the write-error didn't completely shut my system down. Is it possible that my power supply can't handle the burner's demands? The power supply in my system looks to be a 250W unit.

Otherwise my system specs are:
Windows XP professional
AMD K7 1.1 ghz with 768 megs ram
FIC - AZ11E motherboard
... and the rest probably isn't important.

any help would be greatly appreciated.

PostPosted: Sun Sep 18, 2005 8:56 pm
by Gen-An
You might want to start by disabling the default setting in XP to reboot upon a system failure. It can be found in System Properties (right click My Computer or hit Winkey+Pause/Break), Advanced Tab, Startup and Recovery Settings button.

Re: 16x DVD burner issues

PostPosted: Tue Sep 20, 2005 6:27 am
by Bhairav
expansion wrote:I'm hoping someone might be able to help me with this...

I've tried 3 different models of DVD burner in the last 2 days. An I/O Magic, a Lite-On SOHW-1673S and I now have a Sony DRU-800A in my computer. They all seem to be giving me the same issue. I get about 50% through burning a DVD -R and suddenly the computer will just completely reset. I get no opportunity to get error messages or anything because the program doesn't even have a chance to register them. I've update the firmware on each of the burners and it hasn't helped. The only thing I've really got to go on is a 'power calibration error' that I got in nero on one of the rare instances where the write-error didn't completely shut my system down. Is it possible that my power supply can't handle the burner's demands? The power supply in my system looks to be a 250W unit.

Otherwise my system specs are:
Windows XP professional
AMD K7 1.1 ghz with 768 megs ram
FIC - AZ11E motherboard
... and the rest probably isn't important.

any help would be greatly appreciated.


Try changing your media around as well.

PostPosted: Tue Sep 20, 2005 6:45 am
by Noua
It sounds to me and just looking by the behaviour that or it's a memory problem, or a driver problem.
It could also be an overheatig problem. You say it completly shuts down. The windows xp setting will force a reboot on your PC uppon an error message (aka blue screen).
Most of boards have a system nowadays that shuts down the pc in order to prevent permanent damage on the board and processor.

Also, there is a powerful tool on windows that nobody uses it. It's called Event Viewer and it's where you can find information about problems and system behaviours. You can acess it by typing eventvwr on the command prompt or just go to administrative tools. Search for an error message. I'm sure you'll find someting more concrete there.

Good Luck.

PostPosted: Sun Sep 25, 2005 1:36 pm
by expansion
New development...

I can finally get the computer to let me see the blue screen before it shuts down and this is the error I'm getting:

IRQL_NOT_LESS_OR_EQUAL

***STOP: 0X0000000A (0xFFBE0000, 0x00000001, 0x00000000, 0x804F408F)

It then dumps the physical memory and forces me to restart. Does this indicate an IRQ conflict?? If yes, anyone know how I can figure out what other piece of hardware is causing the problem and how I can resolve the issue?

PostPosted: Sun Sep 25, 2005 4:26 pm
by dodecahedron
expansion wrote:I can finally get the computer to let me see the blue screen before it shuts down

how'd you do that? i never could!

PostPosted: Sun Sep 25, 2005 5:07 pm
by Scour
dodecahedron wrote:how'd you do that? i never could!


Hm, I don´t know exactly how the names in english.

If I choose "Arbeitsplatz" (maybe "Workstation"?), properties, Erweitert (advanced?), Starten und wiederherstellen (start and...?), Einstellungen (settings?), and deactivate "Automatisch Neustart durchführen" (automatically restart?)

PostPosted: Sun Sep 25, 2005 5:14 pm
by Ian
Scour has it right. For the English speakers:

Right click on My Computer and choose Properties.

Click on the Advanced tab and then Settings under Startup and Recovery.

Unclick the automatically restart option.

PostPosted: Mon Sep 26, 2005 3:03 am
by expansion
It sounds to me and just looking by the behaviour that or it's a memory problem, or a driver problem.
It could also be an overheatig problem. You say it completly shuts down. The windows xp setting will force a reboot on your PC uppon an error message (aka blue screen).
Most of boards have a system nowadays that shuts down the pc in order to prevent permanent damage on the board and processor.

Also, there is a powerful tool on windows that nobody uses it. It's called Event Viewer and it's where you can find information about problems and system behaviours. You can acess it by typing eventvwr on the command prompt or just go to administrative tools. Search for an error message. I'm sure you'll find someting more concrete there.

Good Luck.


I agree that it seems like a memory or a driver problem. The burner utilizes Microsoft's driver, so I'm confused as to why a driver written by microsoft would cause XP to crash... although maybe I shouldn't be all that surprised. Would there be some other issue that's somehow related?

I looked up the blue screen error I was getting http://support.microsoft.com/?scid=kb;en-us;314063&spid=1173&sid=253 and noticed that it may indicate an issue with memory paging. I tried increasing the size of the windows paging file and the next time got a blue screen "PFN_LIST_CORRUPT - STOP: 0x0000004E" error. I wasn't able to find anything at all on that error. Anyone have any ideas?

PostPosted: Mon Sep 26, 2005 2:36 pm
by thegdog
expansion wrote:I looked up the blue screen error I was getting http://support.microsoft.com/?scid=kb;en-us;314063&spid=1173&sid=253 and noticed that it may indicate an issue with memory paging. I tried increasing the size of the windows paging file and the next time got a blue screen "PFN_LIST_CORRUPT - STOP: 0x0000004E" error. I wasn't able to find anything at all on that error. Anyone have any ideas?

As I recall, those errors usually result from two programs trying to access the same memory chunk at the same time.

While it could be a memory hardware error, usually its not.

Close all other programs on your system. It could be that one of them is conflicting with the writing software. As an example, I had downloaded the newest version of Avant Browser (a tabbed browser based on IE) and it worked fine. Until I used it when Nero was open and burning a DVD. During the write process, my system would just reboot. It had no problems with any other program, or with Nero as long as it wasn't writing a DVD.

It might be something like that for you as well.

PostPosted: Fri Sep 30, 2005 2:28 am
by Wesociety
Run memtest86 to test your memory for errors.

You might also want to try upgrading your motherboard BIOS.
It doesn't sound related, but I've seen it fix strange reboot problems similar to this before...

PostPosted: Wed Nov 01, 2006 12:02 pm
by yournews777
Hello all :D How are you? I'm new on your forum and having exactly the same problem as the user named "expansion" (the author of the subject). It's really a nightmare :evil: ...I'm not able to backup my infos on a DVD (and when the PC doesn't reboot, the data verification fails -with nero).
Thanks for the help.

This is my configuration:

*"Hiper" 350W
*Motherboard: Biostar M7VKQ v.1.0
*WinXP Pro SP2
*AMD Athlon 1250 MHz
*768MB SDRAM PC133 (OK w/ memtest86+ )
*HDD: 160 GB "Hitachi" (IDE1)
*DVDwriter: "Sony DW-G120A" (firm. MYS6) [IDE2 master]
*DVDwriter (used only as a player): "Samsung TSSTcorp SH-S182D" (firm. SB04) [IDE2 slave)
*Floppy Disk
*PCI USB 2.0 "Connectland" (4 extern. + 1 intern. linked to a frontal memory card reader)
*DMA activated in Windows XP

PostPosted: Wed Nov 01, 2006 2:52 pm
by dodecahedron
hello yournews777, welcome to CDRLabs. :)

maybe a power supply issue?
can you swith in another PSU (even temporarily) to check if that's the case ?

also it's possible your 2 optical drives don't like being toghether on the same IDE channel toghether. try removing (unplugging) one of them, then the other, run the system with just one of them.

have you checked the jumper settings are OK?
checked the IDE cable? maybe replace it?

PostPosted: Wed Nov 01, 2006 7:25 pm
by Scour
Maybe a mainboard-chipset-driver problem?

PostPosted: Wed Nov 01, 2006 7:39 pm
by yournews777
Hi dodecahedron and Scour :) Thanks for your reply! I finally found the origin of the problem: it's not my DVDwriters,Nero, my PSU or even my motherboard....the problem is coming from a "Connectland" PCI USB 2.0 card using a Chipset ALI M5273 (ref. USB2-4P-ALI, this is it: http://www.connectland.net/fiche-514-ca ... p_ali.html ). I don't advice you to buy one...until "Connectland" fixes the problem (I've just sent them an email explaining them that they should create a special driver for it -I was using the Windows XP one-).
So that's it :D Thanks for your help guys :wink:

PostPosted: Wed Nov 01, 2006 8:04 pm
by Scour
Nice 2 hear that u found the problem :)

BTW, I prefer USB2.0-cards with NEC-chipsets

PostPosted: Wed Nov 01, 2006 8:44 pm
by dodecahedron
ah!
a drive in an external enclosure!
you should've said that from the start.
anyway glad you worked things out.

PostPosted: Fri Nov 03, 2006 9:09 pm
by yournews777
Hi dodecahedron :D No, no I'm not using an external enclosure. I don't know how, but the PCI card (giving to me 4 USB 2.0 ports) was bugging my nero and/or my dvd's writers. That's why I said I don't advice anyone to buy this kind of PCI card :wink:

PostPosted: Sat Nov 04, 2006 1:39 am
by dodecahedron
ah, OK!
sorry i misunderstood.