Computer shut down during burn process

[Guest]

Please help. I made a home movie in widows movie maker and saved it to my
harddrive as a dv-avi file.

I imported it into WINDVD, and made some more edits and when I try to burn
either I get a "cannot complete burn process" error, or my computer shuts
down completely.

I have a toshiba 512/80gig harddrive.

I also tried to burn through power director as well with the same shutdown
results, but it does at least start to burn. I have even tried to burn right
to disc and it shuts down.

any suggestionsf????

Thank you

 

[Guest]

Wendy.

THis sounds like my problem. Did you get a resolution. I would be
interested.

Ian

 

[Guest]

I also have This problem. It happens with 3 programs, Pinnicle , SOnic MyDVD
and WMM. I need help too

 

[NoNoBadDog!]

First, what are your system specs?

What other processes do you have running in the background when you attempt
to burn?

Have you tried burning at a slower speed, and if so, did the burn complete?

Do you have any screensavers active during the burn?

Bobby

 

[Guest]

I can't say for the others, but I've shut down ,screensavers, antivirus , and
anything else I can find. I have tried burning at a slow rate, I have 1 GB
memory , 60+GB hard drive free, 2.5 Ghtz Pentinium 4. I have had this work in
the past which is why it's diifucult to solve.

 

[NoNoBadDog!]

Are there any entries in Event Viewer that may shed some light on this?

Bobby

 

[Guest]

Not that I can see, but your getting a bit beyond my knowledge. I first
looked at the applicaion events, nothing different. By the system event log
is corupt. That's different ? Not sure what it means...

 

[NoNoBadDog!]

Yes, the System Event log would be critical. The fact that it is corrupt
indicates that the failure of windows was so sudden that an entry could not
be written. That indication alone is significant. It appears (from what we
have discussed) that it is Windows itself that is having problems. There
are so many variable that can cause this...bad memory, latency errors across
the PCI bus...but who really knows? Without a diagnostic tool that would
log system and application errors, there is no valid method to track it
down. If the frustration level were high enough, I personally would bite
the bullet and do a wipe and complete re-install. It is a drastic measure,
but for lack of better diagnostic input, it may be the only viable option.

Bobby

 

[Guest]

That is what I thought you were going to say. I can see I have my work cut
out for me. Thank you for your help, I really appriciate it. I'll let you
know it I get it working.
Brenda

 

[Joshua Smith [MSFT]]

Hi Borg,

To determine what driver is causing the problem I need you to enable driver
verifier.
Steps:
1) Windows Key + R
2) Type in 'verifier' and hit enter
3) Make sure 'Create Standard Setting' is selected and hit next
4) Click on 'Select all drivers installed on this computer' and hit Finish
5) Reboot

There is a possibility that your computer will crash on reboot. If this
occurs hit F8 when rebooting just before the windows logo screen and select
the safe mode boot option. Follow the same steps above but on step 4 choose
'Select driver names from a list'; hit next; check the box next to any
driver where the provider is not Microsoft; hit Finish; reboot.

This will slow the performance of you computer a little while enabled but
will hopefully catch the driver causing corruption. Next time you crash
the blue screen will hopefully say something like
"DRIVER_VERIFIER_DETECTED_VIOLATION". If this occurs please send the
corresponding minidump (by default it is at c:\windows\Minidump ) my way.
If you have any questions or I didn't explain something well enough don't
hesitate to e-mail me (remove "online") back. Good Luck,


Joshua Smith
OpenGL Test Lab
Microsoft