1 person found this helpful
System shutdowns when rendering are usually hardware related. Often
they are heat induced. But even if it's not a case of just overheating,
you need to realize that rendering taxes your entire system to the
limit. Any weak components or drivers will fail under these conditions
even though they may operate perfectly well for more ordinary tasks like
web surfing, email or office work.
To help troubleshoot, you need to stop the automatic restart of the
system so that you can see a screen that will enumerate the cause of the
failure. To do that, go to Computer | System Properties | Advanced
System Settings. Click on the Settings button under Startup and
Recovery. Under System Failure, uncheck Automatically Restart.
The next time you have a system failure, you'll be presented with a
screen that contains information about the failure.
Thanks for the input, I'm sure you're correct about this being hardware-related. Now if I can just decipher the system logs, I'll know which module is the suspect.
With a complete system shutdown and restart, you may not get any
information from the system logs because Windows wouldn't have a chance
to write to the log files.
Changing the system failure options as described is still your best bet.
1 person found this helpful
While I completely agree with Jeff on the hardware side of things, the second link in the link below is oriented to system crashes and BSOD situations. You could try some of the suggestions there.
You described your process... now describe your hardware... in DETAIL
Brand/Model computer and/or motherboard
Ditto for CPU... AND what is your cooling... stock, or replacement cooling tower
Ditto for case, including a list of all case fans
When was the last time you opened the case and blew out the dust bunnies?
When you go to the system monitor in control panel, what is your current CPU temp?
(note that you may need to search to find this information... may not be called "system monitor")
How is your case "set" and are any of the fan openings in any way blocked
Do you have a different power supply you may install as a test?
Hard drive space out the wazoo.
Any good definitions of what this equates too?
Hmm... I work at Washington State University, which is sometimes call "Wazoo" but I've never seen anything in any of the WSU publications about how that would equate to anything involving a computer
Bill & John,
> Any good definitions of what this ["out the wazoo"] equates too?
Sorry for the confusion. This is a highly technical term for "a large amount". <G>
[And, FWIW, in this case the project (and render-to) drive is 465 gigs, with 157 gigs free. The root drive has 225 gigs free.]
1) As it turns out, Windows did manage to log a Premiere crash event. It's unclear from it, though, what the offending module is.
> Changing the system failure options as described is still your best bet.
2) Yes. I tried this and now when it crashes, the screen goes black, with a blinking cursor. <Sigh>
After some testing, I've eliminated the hard drive and am narrowing my focus to:
1) Bad memory chip or
2) Ancient sound card
Thanks again for the input!
> Brand/Model computer and/or motherboard
ZT brand, the motherboard is unknown (though it's been replaced).
> Ditto for CPU...
AMD phenom 9500 quad core
> AND what is your cooling... stock, or replacement cooling tower
> Ditto for case, including a list of all case fans
Couldn't tell you.
> When was the last time you opened the case and blew out the dust bunnies?
About 2 months ago.
> When you go to the system monitor in control panel, what is your current CPU temp?
Hmm. Couldn't find this.
> How is your case "set" and are any of the fan openings in any way blocked
Could be wrong, obviously, but I don't think this is a heating issue: I got these same symptoms after it cooled all night.
> Do you have a different power supply you may install as a test?
Huh. I had to replace the one that it (the PC) came with when I upgraded to the NVidia card. So, no, I don't have a different power supply. But I'll put that on my "test for this" list...
[Meant to come back sooner and report these findings for posterity...]
Turns out that Jeff was correct when he said:
"System shutdowns when rendering are usually hardware related."
I had an old (7+ years) Audigy soundcard that Vista complained about when I installed it. Replaced it with a near-new X-Fi and have been rendering without difficulties since.
Again, thanks to all the helpful souls who chimed in!
And thank you for posting back with your solution.
[Just when you thought it was fixed...]
Last time I posted in this forum, I identified the aged Audigy sound card as the culprit. After a couple of months, BLAM, the same system-reboots-when-rendering-HD problem reappeared.
The other hypothesis offered in this forum was overheating. So, disgusted, I installed SpeedFan (http://www.almico.com/speedfan.php) and sure enough, my CPU was operating in the Red Flames of Death zone. 3 Zalman case fans and a new CPU heatsink later, and we're running in the green, and no, NO system-rebooting problems. Been verifying this over the last month, so Yep, overheating was the problem, case fans and heatsink were the solution.
Thanks again for all the help!
I had a CPU fan fail once... and my system would only run for 5-6 minutes before it would die
New fan and it's been working ever since... and video rendering STILL makes all the variable speed fans run at top speed