[Resolved] Everytime i try to burn a cd/DVD my computer crashes

One setting to check ...

In Windows Explorer right click on the drive > Properties > Recording tab and uncheck 'Enable Recording on this drive' - or words to that effect and try again.

Originally Posted by PeteC

One setting to check ... In Windows Explorer right click on the drive > Properties > Recording tab and uncheck 'Enable Recording on this drive' - or words to that effect and try again.

I dont seem to have the Recording tab option available for my CD/DVD drives, they will play cds and dvds okay it's just when i try to burn to a cdr or dvr-r using either of them i have the problem.
I am not sure but it seems that the computer tends to crash when the drive tries to read the blank disc prior to starting the burn. I have tried different discs and different makes but it seems to crash with all of them.

If there is no Recording tab then Windows is not recognising the drives as recordable devices - see if this helps .....

CD-R drive or CD-RW drive is not recognized as a recordable device

Quote:

When you view the properties of the CD-R drive or the CD-RW drive, you notice that the Recording tab is not displayed in the CD Drive (drive_letter:) Properties dialog box, where drive_letter is the letter of the CD-R drive or CD-RW drive.

Originally Posted by PeteC

If there is no Recording tab then Windows is not recognising the drives as recordable devices - see if this helps ..... CD-R drive or CD-RW drive is not recognized as a recordable device

I have tried changing the registry settings as described on the Microsoft website but it has not made the recording tab appear. the value was 2 in the registry setting which should indicate a recordable drive.
In desperation I restored a ghosted image of the C drive that i knew to be stable and without any issues but even with the restored image it still crashes when trying to read the blank media i am stumped !!!

If you had a single DVD drive one conclusion would be that the drive has failed, but 2 - not very likely, but the fact that a restored (working) image now shows the same fault rather suggests a hardware problem. .

Are these PATA or SATA drives? If PATA try disconnecting the slave drive from the ribbon cable and try again. Remove and remake the cable connection to the motherboard. If you have a spare cable try that.

BTW - We encourage all members to complete their System Specifications which help us to help you

Does the computer crash to a BSOD? Stop Error details?

Have you looked in Event Viewer to see if there is a flagged entry at the time of the crash

Originally Posted by PeteC

If you had a single DVD drive one conclusion would be that the drive has failed, but 2 - not very likely, but the fact that a restored (working) image now shows the same fault rather suggests a hardware problem. . Are these PATA or SATA drives? If PATA try disconnecting the slave drive from the ribbon cable and try again. Remove and remake the cable connection to the motherboard. If you have a spare cable try that. BTW - We encourage all members to complete their System Specifications which help us to help you Does the computer crash to a BSOD? Stop Error details? Have you looked in Event Viewer to see if there is a flagged entry at the time of the crash

I am not sure what type of drives they are but when it crashes it goes back to a full re-boot from scratch.
They both seem to work okay when just used for playing but not for recording.
Can you tell me please how to find the Event Viewer and how to use it.

Quote:

I am not sure what type of drives they are

PATA drives use the 'old' standard flat ribbon cable, SATA drives a very narrow, flat cable - pic of SATA cable attached.

Quote:

Can you tell me please how to find the Event Viewer and how to use it

Start > Run > type in eventvwr.msc > Enter.

or....

Right click My Computer icon > Manage > Event Viewer.

You are looking for System or Application Events flagged red at the time the computer crashed. Doeble click on an Event to open and on the icon below the up/down arrows to copy to clipboard and paste in a post here.

Quote:

when it crashes it goes back to a full re-boot from scratch

Set up the computer so that it does not automatically restart on system failure (restart is the default) .....

Quote:

Control Panel > System > Advanced > Startup and Recovery > Settings .... Under System failure uncheck 'Automatically restart' and under Write debugging information select 'Kernel memory dump' from the dropdown list and OK out. The computer will now show the BSOD in the event of a System failure giving details of the Stop message and the contents of the memory will be dumped to disk. Run the dump data through our Dump Data Collection Tool and post the log here (copy/paste). Unfortunately these logs require expert knowledge to analyze and there are currently no members that have the depth of knowledge necessary. Members can only make observations and suggestions as to how you might proceed toward finding the cause .....

For the moment post the Error Code on the BSOD screen and any file that is referenced.

Footnote - I am away over Easter for a week starting tomorrow evening.

PeteC
They are both PATA drives,
I will do as you have suggested, many thanks for all your help hope you have a great time away.
regards
Alboy

Originally Posted by alboy

PeteC They are both PATA drives, I will do as you have suggested, many thanks for all your help hope you have a great time away. regards Alboy

This time it crashed just when putting a blank DVD in the drive no burning program was running

The dump was as follows


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: *** Invalid ***
*************************************************************************** *
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
*************************************************************************** *
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlpa.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_gdr.090206-1233
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553420
Debug session time: Mon Mar 29 15:42:09.593 2010 (GMT+1)
System Uptime: 0 days 0:08:24.166
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlpa.exe -
Loading Kernel Symbols
........................................................................... ........................................................................... ..
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd400c). Type ".hh dbgerr001" for details
Loading unloaded module list
...........
ERROR: FindPlugIns 8007007b
*************************************************************************** ****
* *
* Bugcheck Analysis *
* *
*************************************************************************** ****

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, 806d0753, a9082b0c, 0}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** ERROR: Symbol file could not be found. Defaulted to export symbols for halaacpi.dll -
*** ERROR: Module load completed but symbols could not be loaded for vobiw.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for fltmgr.sys -
*** ERROR: Module load completed but symbols could not be loaded for swenum.sys
Probably caused by : vobiw.SYS ( vobiw+2a95f )

Followup: MachineOwner

tn_Error2.jpg

There is a symbol problem with your dump file - you must remain connected to the internet while debugging.

However there is a clue .....

Quote:

Probably caused by : vobiw.SYS

Have you any Pinnacle Software installed, specifically Instant Write?

Originally Posted by PeteC

There is a symbol problem with your dump file - you must remain connected to the internet while debugging. However there is a clue ..... Have you any Pinnacle Software installed, specifically Instant Write?

I appear to have Pinnacle Instant CD/DVD suite installed although i don't recall ever having used it should i uninstall it and try again as the crash seems to happen no matter what CD is in the drives even one that is already used and finished.
I have disconnected each drive in turn but the crash happens with both drives.

Yes, uninstall it and test.

Originally Posted by PeteC

Yes, uninstall it and test.

I have uninstalled it and the Recording tabs have appeared on the drives and i have completed a burn without a crash.
Hopefully the problem has been solved.

Many thanks for all your help Pete have a good holiday.

regards
Alboy

That's great news There were clearly conflicts between Nero & Pinnacle.

Please mark this thread as 'Resolved', see .....

Quote:

New Functionality: Marking a thread as 'Resolved' We have added new functionality to the forum that allows you to mark your threads as 'Resolved'. It is considered courteous to post a reply if you have been able to resolve your problem, or received an answer to your question. If you were given multiple suggestions/solutions, it is also helpful if you would list the solution that worked for you. Once you have posted those details, when still looking at your thread, near the top of your thread you'll see Thread Tools. Click the down arrow to expand the drop down menu, at the bottom of it you'll see Mark this thread as solved. Click on it to mark your thread as solved. If later you find that the problem has returned, and you had previously marked your thread as solved, follow the steps above. Instead 'Mark this thread as solved' you will see that in this case Mark this thread as unsolved is listed. Please read the User Guide for more information.