Rendering Errors - Help Please

reamenterprises wrote on 4/16/2003, 8:54 PM
VV Users,

I have been struggling for a very long time now to get the right hardware / software configuration for Video Vegas. The program alway installs and operates effeciently, but when I go to render a project the system always does 1 of 2 things. The program freezes with an error or Windows XP automatically reboots itself.

The most common reason I get is that there has been a conflict with a device driver, but we do not know which one. This happens most often when rendering an *.MPEG file.

I have actually experienced this now on 3 different systems and I recently made the investment in newer equipment. Here is what I have any suggestions would be appreciated, I know VV is a great program, but my business will not survive if I can not get the projects completed.

400 Watt PS (New - Replaced previous 250 watt PS)
MSI 6380 Motherboard (Bios and VIA drivers have been updated)
Athalon XP 1900
512 266DDR - Kingston (New - Replaced previous APACER Memory)
ATI Radeon Video Card (New - Replaced previous Geforce 4 card)
Dazzle Video Creator II
(Ethernet Card, Phillips Sound Card)
(CD-ROM and DVD-R Burner)

Things that I have noticed... 1.) I have better luck rendering files created through a DV camera compared to an Analog Signal 2.) Usually happens when rendering an *.MPEG file. 3.) I have had absolutely no problem running any other applications.

Again your help is needed and appreciated!

Chad

Comments

SonyEPM wrote on 4/17/2003, 8:58 AM
XP rebooting itself during a render is about as bad as it gets...

What version of Vegas are you running? What are your exact render settings?
reamenterprises wrote on 4/17/2003, 1:05 PM
I am using Vegas Video 4b and am using the default rendering setting. I have experienced errors while rendering *.mpeg, *.avi and *.wmv files.

Thanks for your help,

Chad
SonyEPM wrote on 4/17/2003, 1:20 PM
Heat? Is your system cool enough?
Frenchy wrote on 4/17/2003, 5:45 PM
Chad:

With my (limited) experience, I would echo SonicEPM's last post - I just had this happen to me (like 2 days ago), and I'm almost positive it was overheating. I set V4 into an mpg render (30 min project) while I was at work, and when I got home, my PC (P3-600, Win98SE) was frozen up at about 63% complete with the render. Had to reboot - lost it all, etc. I noticed it was very warm inside the cabinet where the CPU is (behind a cabinet door - vented, but apparantly not enough). Never had a similar problem before (with VV3 or V4) That night, I started another, identical render, this time leaving the cabinet door open. The next morning, it had completed after about 5 hours, and was fine (well, I had other issues with the production, but it was user error - project properties set to progressive while using interlaced material (bad interlacing artifacts throughout the vid)... Arrghhh - start re-render...). It was a lot cooler around the CPU as well. Now I leave the cabinet door open, and have to keep the cat out...

Frenchy
reamenterprises wrote on 4/17/2003, 6:03 PM
Thanks for the feedback... I believe my temperatures are within appropriate marks. My processor runs between 130 - 140 and the case sits right around 100 degrees.

I have even ran my system with the cover off and still experience the same problems.

I agree though temperatures can be hectic to a system. While running some high end games I have not had a problem iether.

Lets keep getting the suggestions, they are appreciated as we solve this mystery.

Thanks,

Chad
VideoArizona wrote on 4/17/2003, 10:41 PM
Hi Chad,

Anytime a computer reboots itself I get suspicious of hardware issues....especially when capturing or rendering a video file which does tend to "push" the system to its utmost.

Since you recently made a number of hardware changes, but you didn't say whether or not you changed the OS drive (reformatted and reloaded the OS), I might suggest you have a major driver conflict or two from previous installs. This can happen when you keep the same system hard drive and change MB's, etc. You get all these drivers in your system...most aren't used but left over.

IF this is not the case then:

1: Heat

2: Motherboard/Ram incompatibility (don't laugh this does happen)

3: Corrupted video driver (update?)

4: Corrupted or old MB drivers (update?)

5: Corrupted program dll's. Have you tried re-installing Vegas?

Hope this at least gives you some ideas.

David
Paul_Holmes wrote on 4/17/2003, 10:58 PM
130 to 140 sounds kind of high to me. My Athlon 1800 rarely goes beyond 123 and when it did it was failing on me (had forgotten to put heatsink compound on the processor -- as soon as I did the heat went back down).

I may be off-base here, don't know what acceptable heat specs are, but I believe I was having problems when it was up over 130.
rebel44 wrote on 4/17/2003, 11:27 PM
Any time computer reboot is when have memory problem.Run some other program like high graphic game and see if reboot.I would diagnose memory chip.Try to see if the memry module seated good.DOS will allways count memory even if is bad.I had similar problem and found out that one of my module was bad.I am running win2000pro and found out that it is the most stable OS in windows product.I have XP, but took it off.I have formated in NTFS and foun it very good.Captured AVI over 5GIG with no problem.XP if fancy OS, but not that stable as 2000pro.
reamenterprises wrote on 4/18/2003, 6:41 AM
I appreciate the recent posts!

I am going to investigate my heat options. I have been using a stand by system (borrowing and it does not exceed 115 degrees.) I am going to attempt one of these copper base fans. (I am using heat compound now though)

I have never had any other problem, running games etc. A memory test makes sense, unfortunately I have used 3 different sticks from 3 different manufactures and I am having the same problem in each dimm sockdet.

* I just read to that Athalon XP chips will reboot the computer if they are running to hot.

Thanks for you help, keep the suggestions coming if you have them.

Thank you,

Chad
mikkie wrote on 4/18/2003, 8:09 AM
Right on Paul

Check out the Athlon XP's heat specs at AMD, and 140 F range is about the max. The accuracy of the m/board temp sensors I don't think is perfect, and the CPUs will start failing as the temp rises before they quit. Also, if the machine's re-booting, you'd have to be watching the temp as it died to get an accurate reading, so in this case it could be surging to well past 140 over time as the ambient temp in the case can rise from the CPU heat causing the cpu to heat up more. In any case, useing something like MotherBoard Monitor you can watch your cpu temps rise on rendering/encoding.

"1.) I have better luck rendering files created through a DV camera compared to an Analog Signal"

Unsure how this would have an effect, but think possibly it might cause the CPU to do more work, increaseing the heat.

"2.) Usually happens when rendering an *.MPEG file."

This will cause the CPU to do more work (create more heat) then say rendering to most types of avi.

"3.) I have had absolutely no problem running any other applications."

If heat is the problem, another app would have to load the cpu to a similar level as rendering your mpegs in VV4. A decent way to check this out might be to use the free WinMedia 9 encoder on a large avi as the encoder will usually put a 100% load on the cpu, but there are also other apps out there designed specifically to stress out systems for testing.

Finally, an even easier way to find out if heat's the problem, pull the cover off your rendering PC, and aim a 10 - 12 inch fan with *good* airflow at the innards as it's running... Kind of like a poor man's substitute for water cooling and used more often then one might think.
reamenterprises wrote on 4/18/2003, 4:49 PM
Mikkie,

Thanks for the info, I appreciate the time and everyone has taken in providing some detailed comments. It appears no matter what a new heat sink and fan are needed. I should be running at cooler temps anytime.

I am already running cooler per a new fan etc. I suppose the best things to come from mistakes and mysteries are that we get to learn something. (I should have know to think of heat issues first and save some money.) I hope this works and will post my results.

Thanks,

Chad

reamenterprises wrote on 4/25/2003, 1:43 PM
VV Users,

After having the opportunity to render a couple of projects, I have to conclude that my challenge was "heat". The Athalon XP chips was hitting a peak I am guessing 145 - 150 if not hotter and resetting the computer system.

I switched out my heat sink and fan and it has worked great since.

Thanks for everyone's help!

Chad
Jsnkc wrote on 4/25/2003, 3:29 PM
Get rid of the Dazzle, all of their products are nothing but trouble and filled with tons of bugs that can screw up other aspects of your system.
vitalforce2 wrote on 4/25/2003, 3:40 PM
I have a Dazzle Hollywood DV converter box, which has given me no problems. Anecdotes aside, though, I do note as per Jsnkc's post that various forums do have complaints about difficulties with Dazzle and also ATI products. With Dazzle the pattern seems to be inconsistent manufacture quality from unit to unit, while with ATI it's never-ending bugs with the drivers.

This is not meant as a trash of either Dazzle or ATI products, both of which I have used with glee on many occasions. Reading the above posts, though, it sounds pretty likely you've hit on the problem anyway, as to improving your system cooling.