Computer is rebooting when trying to burn a dvd

[clvlndta3]

Hi,
I am running an AMD Duron 1ghz with 384mb ram. Windows xp pro, liteon 1633s burner. Everytime I try to burn a dvd, the computer reboots. It has also thrown the error IRQL_NOT_LESS_OR_EQUAL and then it says beginning dump of physical memory. The computer is stable as long as I don't try to burn a dvd. I figured I would save on burning coasters and try using a dvd+rw, and when I did it still rebooted on me. When I go into my computer, it shows the drive as being a dvd-rw drive. Then when I put in the dvd+rw disk, it goes to saying it's a cd-rom drive. How am I supposed to erase the dvd+rw? When I try to right-click the drive and select "erase" it gives an error saying the disk can't be erased. I am about to try a cpu burn-in to be sure heat isn't the problem and also run a memory test to see if I have bad memory. Any other ideas?

[MOVIEGEEK]

Is this problem new or did you just buy a DVD writer?
What program are you using to burn and is DMA enabled?
Try setting the read buffer lower(<50MB) and go to Device Manager and make sure DMA is enabled for all drives.
Also try burning at 4x.
Make sure no other programs are running when burning.Another possibility is your PSU,try removing/unplugging a couple of drives or PCI cards.If it works then your PSU is about to die or isn't powerful enough(<300w).

[clvlndta3]

I just bought the dvd writer, but it was working before. It was just really slow and know that my machine was cluttered with old programs, etc. so I did a format and reinstall. Everything is working fine, except the dvd burner. The cpu test just got done running and was fine. I am getting ready to try the memory tester. I have tried using a couple different ways to burn, such as dvdshrink with nero, roxio using an image, and also dvdxcopy. All of them have the same result, reboot after starting the burn. I'm not sure what the psu rating is, but it worked before the reformat using the same configuration. Do you think the drive is possibly bad? That's kind of what I am leaning towards.

[clvlndta3]

I had 2 sticks of memory 1 128mb and 1 256mb. The 256mb had errors when the memory test ran, so I removed it, booted up and tried burning a disk. My computer froze at 1% using roxio disc copier from an image saved to the hard drive. I don't know if that's because of the 128mb or something else. I just ordered a 3ghz p4 and a new mb with 512mb ddr400 ram. Hopefully this will take care of things. I'm still not sure about the burner and whether or not it is any good though. If anyone has any more ideas, I'd like to hear them.

[clvlndta3]

Now I just tried burning a data cd with the dvd burner, and it restarted my computer as well. Earlier in the day I used my regular cd-rw to burn a cd and it burned it just fine. No problems at all. It's really looking like the burner is bad, any thoughts?

[fritzi93]

Now I just tried burning a data cd with the dvd burner, and it restarted my computer as well. Earlier in the day I used my regular cd-rw to burn a cd and it burned it just fine. No problems at all. It's really looking like the burner is bad, any thoughts?

Yes update your computer details with the model number of your DVD burner.

Seriously, I presume your drives are master/slave on the same IDE channel? I'd swap the drives (watch your jumper settings!) and try again. Just to rule out a bad connection. Good luck and post again with how things are going.

[clvlndta3]

My dvd burner is a liteon sohw-1633s and my cd burner is a liteon ltr-32123s. Right now I believe that my dvd burner is jumpered as master but is setup on the end and my cd is slave on the middle. Both same channel, secondary ide. I'll try swapping and see if that makes a difference.

[junkmalle]

Try getting the latest INF files (driver patches)for your motherboard.

[clvlndta3]

Okay, I just switched them to the dvd-rw on the middle with jumper set to slave, and the cd-rw on the end set to master. Same result, it locked up when trying to burn a dvd image using roxio 7. These coasters are really getting aggravating.

[clvlndta3]

junkmalle, I did that as well. No help though. I've also uninstalled and reinstalled the ide channels as well as the drive itself.

[fritzi93]

Okay, so the drive has worked before, just not on your machine? If it were me, I'd ditch Roxio, and disable XP's inbuilt cd burning. If you have any packet-writing software, such as InCD, get rid of that. Also, to run K-Probe and other Liteon apps, you need ASPI, v.4.6 recommended. Run ASPIchk.exe to see. Then I'd see about a Nero update. And perhaps a firmware upgrade.

Have a look at the Liteon hardware subforum at cdfreaks.

Good luck.

[clvlndta3]

fritzi93,
I just got the drive about 2 weeks ago, brand new. It was working on my machine fine, but it was taking forever to do anything because my computer was loaded down with old programs, etc. I decided to reformat and have a clean install to get rid of the clutter. Everything went fine, I reinstalled winxp pro sp2 and did the updates. Everything was stable and running fine until I went and tried to burn a dvd. This is on the same exact machine, just a fresh install of the OS. I have updated the mb drivers, ran the burn-in on the cpu, checked the memory (256mb bad, 128mb good so I removed the 256 stick), switched the dvd-rw to slave from master on the secondary ide. This reboot happens no matter what burning program I have tried to use, from nero or roxio. It also happened when I tried to burn a cd in the dvd burner, but when I burned a cd in the cd burner it was fine. If the problem was memory, I would think it would burn with the good 128mb stick. If the processor was overheating, it should have done that before and also during the cpu burn-in. It's not the media because it worked fine before. Everything is fine with the exception of when I try to burn either a cd or dvd using the dvd burner.

[junkmalle]

Is it possible your drives were running in PIO mode Before? That would explain why the system was so slow.

[POOPS]

How old is HD?It looks like your HD is about to die.I used to have the same problem long time before and just changed mine for a new one.

[clvlndta3]

junkmalle,
That is probably what it was as far as the speed issue before. The computer was due for a cleanup so I went ahead and did it thinking now would be a good time. The hard drive is probably around 4 years old or so. It's a 40gb, Seagate barracuda I think. It hasn't given any signs of going out, but that's always a possibility.

[fritzi93]

Thanks for the clarifications. Got an extra hard drive laying around to test? Barring hardware failure, it may be an obscure software conflict.

For every person who reports that two programs cannot coexist on a given machine, others will say the combination works for them.

However, it is established that some versions of Nero have had trouble with SP2. Many (not all!) people curse packet-writing software, others say Roxio and Nero can't coexist peacefully. Etc., etc. YMMV, but never say never.

If you can't fix the problem any other way, it may come down to a reinstall of the OS. Then carefully install and test your burning programs one by one. I'd start with DVDDecrypter and DVDShrink.

Other than that, I'm all out of ideas. Good luck.

[thinger62]

I think you hit it on the head with the memory post. Your pc froze, instead of rebooting when you took out the 256 chip, right? It probably froze because 128 is not enough, and it was rebooting because it was accessing defective memory in the 256 chip. I had that problem in an old computer. It would only reboot when burning cd's. Never had a problem doing anything else. I swapped out one of the chips and had no more problems.

[clvlndta3]

I do have an extra hard drive that I could try, I might do that when I get some time. I just don't understand how it freezes every time it tries to burn, cd or dvd, yet my regular cd burner burns just fine with no problems. Just a wierd situation all around.

[Richard_G]

Are you still getting the IRQL_NOT_LESS_OR_EQUAL error or is it just rebooting? I had that error appear randomly (not just when burning) after updating the drivers for my Soundblaster card. The microsloth diagnostics was telling me it was a video card driver problem but reverting back to the previous Soundblaster drivers cured it.

As you have done a reinstall and updated everything, maybe you have a similar problem.

[clvlndta3]

I have updated the drivers on the mb, just using onboard video. No luck there, right now it either locks up or reboots. No more blue screens that I have seen.

[POOPS]

i just faund this on the Microsoft site:

Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
The Stop 0xA message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.

Interpreting the Message
This Stop message has four parameters:

Memory address that was improperly referenced.
IRQL that was required to access the memory.
Type of access (0x00000000 = read operation, 0x00000001 = write operation).
Address of the instruction that attempted to reference memory specified in parameter 1.
If the last parameter is within the address range of a device driver used on your system, you can determine which device driver was running when the memory access occurred. You can typically determine the driver name by reading the line that begins with:

**Address 0xZZZZZZZZ has base at <address>- <driver name>

If the third parameter is the same as the first parameter, a special condition exists in which a system worker routine, carried out by a worker thread to handle background tasks known as work items, returned at a higher IRQL. In that case, some of the four parameters take on new meanings:

Address of the worker routine.
Kernel interrupt request level (IRQL).
Address of the worker routine.
Address of the work item.

Resolving the Problem

The following suggestions are specific to Stop 0xA errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.

A Stop 0xA message might occur after installing a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, and CD mastering tools.

A Stop 0xA message might also be due to failing or defective hardware. If a Stop message points to a category of devices (video or disk adapters, for example), try removing or replacing the hardware to determine if it is causing the problem.

If you encounter a Stop 0xA message while upgrading to Windows XP Professional, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows XP Professional, contact the hardware manufacturer to obtain compatible updates. For more information about simplifying your system for troubleshooting purposes, see " Troubleshooting Concepts and Strategies" and "Troubleshooting Startup" in this book.

For more information about Stop 0xA messages, see the Microsoft Knowledge Base link on the Web Resources page at http://www.microsoft.com/windows/reskits/webresources. Search using keywords winnt, 0x0000000A, and 0xA

Also this:

This error indicates that Windows or a kernel-mode device driver accessed paged memory at DISPATCH_LEVEL or above.
On the blue screen, the following parameters are displayed:

Memory referenced
IRQ at time of reference
0: Read
1: Write
Address which referenced memory
Cause
This error usually occurs after installation of a faulty device driver, system service or BIOS.

If you encounter this stop code whilst upgrading to a later version of Windows or when applying a service pack or hotfix, the error may be caused by a device driver, system service, anti-virus package, third-party network client or backup tool which is incompatible with the new version.

Resolution

To resolve an error caused by a faulty device driver, system service or BIOS:

Restart the computer.
Press F8 at the character-based menu that displays the operating system options.
Select the Last Known Good Configuration option.
To resolve an error caused by an incompatible device driver, system service, anti-virus package, network client or backup tool:
Check the System Log in the Event Viewer for identifying error messages.
Try disabling memory caching of the BIOS.
If available run any manufacturer-supplied hardware diagnostics, especially the memory scanner.
Make sure the latest Service Pack is installed and all applicable hotfixes have been applied.
If your system has SCSI adapters, obtain the latest manufacturer device drivers. Try disabling sync negotiation in the SCSI BIOS, check the cabling and SCSI IDs of each device and confirm proper termination.
For IDE devices, define the onboard IDE port as Primary only. Check each IDE device for proper master/slave/stand-alone setting. Try disabling all IDE devices other than the hard drives.
------------

Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
The Stop 0xD1 message indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.

Interpreting the Message
This Stop message has four parameters:

Memory referenced.
IRQL at time of reference.
Type of access (0x00000000 = read operation, 0x00000001 = write operation).
Address that referenced memory.


Stop 0xD1 messages can occur after installing faulty drivers or system services. If a driver is listed by name, disable, remove, or roll back that driver to confirm that this resolves the error

...and this:

If you feel like being overwhelmed by technical detail (or you've got your system set to reboot automatically and you didn't see the blue screen) you can load the dump file in one of the system debuggers.

First, get your debuggers from http://www.microsoft.com/whdc/devtools/debugging/default.mspx. Next, set up the _NT_SYMBOL_PATH environment variable, using the System Properties > Advanced tab > Environment Variables dialog. I'm a C++ developer, so mine reads

_NT_SYMBOL_PATH=C:\WINDOWS;C:\WINDOWS\SYSTEM32;SRV *C:\WebSymbols*http://msdl.microsoft.com/download/symbols

Visual Studio dumps some PDB files for the MFC and CRT runtimes in C:\WINDOWS. The SRV part tells the debuggers to download any symbols you need from the Web. If you don't add this part, it's likely that the process won't work, because it won't be able to walk the stacks.

Next, open the debugger. I use WinDbg because I can't possibly remember all the debugger commands (I use it occasionally, not all the time, although it is more powerful than VS.NET). In WinDbg, choose File > Open Crash Dump.

If your PC is set to do minidumps, you'll find the dump file in C:\Windows\Minidump with a name of Mini{mmddyy}-{serial}.dmp, where {mmddyy} is the month/date/year and {serial} the number of the dump on that day. If set to do full or kernel-mode only dumps, you'll find it in C:\Windows. For more info on configuring crash dumps, see http://support.microsoft.com/default.aspx?kbid=254649.

The debugger now loads the dump file and the symbols for the modules that were loaded at the time of the dump. The first time you do this will take a while. When it's loaded, the debugger will tell you what caused the crash. You can use the command

!analyze -v
to get more details.

__________________________________________________ ___________

I Hope this will help u

[clvlndta3]

Okay, last night I took a different hard drive, formatted it and installed winxp pro sp2. The only additional programs I installed were dvddecrypter, dvdshrink, and nero. I then used dvddecrypter to decrypt, dvdshrink to analyze and encode, then nero to try and burn. Everything went fine until it got to the burn part. When I got up this morning the computer had rebooted and when I logged in, it says windows has recovered from a serious error. I have the files from the error dump, but the extension is a .dmp Does anyone know what program would open that file and if it would even have any information that would help diagnose this problem? Thanks.

[jim prince]

Youv'e done everything but the most obvious which is to try a different DVD Burner....

[fbellflo]

Just my two cents,Roxio caused all kinds of trouble with my computer,but I also had a problem with mine starting to reboot during a burn after everything had been working fine.It turned out to be my power supply.I guess it was getting old?Take care.........

[clvlndta3]

I am getting ready to build a new computer with a new power supply, MB, cpu, memory, and all new cables. This burner will be going into this new computer so that should rule out any other hardware conflicting. The power supply is the only thing I haven't tested, but it worked fine before the reformat. Never know though. It can't be roxio because when I tested a different hard drive, I never installed roxio.

[junkmalle]

Did you try putting your DVD burner in PIO mode?

[POOPS]

Get debuggers tools from http://www.microsoft.com/whdc/devtools/debugging/default.mspx.
load your .dmp file in the debugger and ....have a look in my previouse post
...Have u tried to upgrade your PS memory ...let's say to 256mb??This can be helpfull aswell

[clvlndta3]

junkmalle, I believe the burner was running in PIO mode before the reformat, but I can't be sure. I never went and checked but it was running very slowly. That's why I went and did the reformat, because it was so slow and the hd was cluttered and full of stuff I no longer used. If it will burn in PIO mode but not DMA mode, what would that indicate?

[junkmalle]

junkmalle, I believe the burner was running in PIO mode before the reformat, but I can't be sure.

Which is why I suggest you try changing it back. Burning DVDs slowing is better than having your system crash every time you try.

If PIO works you know there is something wrong with DMA on your system. That's usually IDE driver related but you've already updated your motherboard INF files.

Do you have any PCI cards installed? In theory IRQ sharing should work on modern hardware but the reality is that some devices don't like sharing with others. Try moving your PCI cards around if you can.

[thegig]

Had the same behavior see: https://www.videohelp.com/forum/viewtopic.php?t=247409&highlight=

It actually became intermittant, but after I loaded SP2, everything played nice. But the problem stemmed from a couple things A:bad IDE controller, B:bad memory module, C:Nero, D:Windows driver