Attaching TXT files takes a long time to become available for viewing, but likely will not help much. Shutting down spontaneously usually means a hardware problem, caused by taxing the system to a level that it can't keep up. Like an untrained person doing a marathon. He can't keep up. To figure out where the problem is, look specifically at the temperatures in your case.
Read the second part of this link:
Thanks a lot for your response, yes i do suspect the hardware issue.
I am able to render anything thats under 3 mins and after 3 mins my system shuts down.
I went through your link and downloaded those tools and saved the configuration report.
Any thoughts on how to go about on troublehshooting heatsink or fan issues?
Again i really appreciate your help so far.
The HWMonitor file is still queued (tip: use the camera icon to upload a file more quickly than attaching. It is intended for screenshots, but also works with TXT files) so I can't see it yet.
From DXDIAG I see no strange codec packs, your video driver is up to date, in short nothing out of the ordinary. What strikes me is that you are really out of disk space, even with all your disks. In general I advise to expand storage capacity when fill rates on disks go over 60-70%, because from that moment disk thruput slows down significantly. Some of your disks have less than 10% free and may have insufficient room for temp files.
It appears you have a nVidia chipset on your motherboard. Do you have the latest chipset INF file for that chipset installed? In the early days of nVidia chipset based motherboards, there were some problems, but these have been ironed out. However it may require updating the INF file.
Your system is pretty full with all these hard disk drives plus the DVD player and burner. What PSU do you have in what case? Can you make a screenshot from Process Explorer when you are using PR and post it by uploading it with the camera icon.
HWMonitor just came out of the queue and temperature is indeed the problem. Maybe not the only one (disk space may be another) but definitely serious.
I see only one fan, at least only one fan attached to the mobo. Your CPU temperature is around 72-75 degrees C and that is just too high, especially since those temperatures go up significantly when under full load during encoding. Your video card OTOH has decent cooling. 56 degrees is not out of the ordinary. Your fan is probably an 80 mm fan with those RPM's or it is the stock Intel CPU cooler.
I suggest to have a look at a replacement CPU cooler. In a recent guide about building a PC I mentioned several brands to have a look at.
Usually hard disks are mounted in a disk slot flush with the front of the case (If you use drive cages, things may be different) and a possible solution then may be to attach 2 120 mm fans to the right hand sidepanel behind the disks in pull mode to pull in air from the front along the disk and into the case. Combine that with a new CPU cooler, for instance a Noctua NH-U12 with two fans, one in front to push the air over the cooler and one on the back to pull the air from the cooler and the first steps to improve your cooling are done. The only thing you may need to do too is mounting a fan in the back of the PC to pull all the air out. These steps will greatly improve the airflow and lower the temperatures.
From the looks of it, the thermal protection circuitry of the CPU kicks in when the temperature is getting too high.
Your target CPU temperature idle should be less than 50 degrees C.
Hope this helps.
This is how my i7-920 overclocked to 3.6 GHz performs with the temperatures in near idle mode with a room temperature of 22 degrees C.
Since your CPU is 65 nm based it will run hotter than my Nehalem CPU, but idle below 50 degrees must be attainable.
What can help also is to replace the stock cooler on your video card with something like the Accelero Twin Turbo from Arctic. In my case the video is an ATI 4870, overclocked to GPU @ 785 MHz and memory to 1005 MHz and my GPU is nearly 10 degrees cooler, despite the overclocking.
Let us know if this has helped or solved your problem.
I'm guessing this happens when you export to Quicktime?
I'm guessing it happens with any codec, not just quicktime, that is CPU intensive and takes long enough for the thermal protection to kick in. Quicktime is not the issue here, only the temperature of the CPU.
You're guessing. I'd like to know for sure because there are major issues with Quicktime, some Adobe related and some not.
To the poster, it appears you have not updated your CS4 since you installed. Make sure you update your program(s) with the latest updates.
It's a very educated guess, though. Harm knows what he's talking about when it comes to hardware.
I myself have never seen anyone complain of their system shutting down when encoding to Quicktime. Other issues, yes. But not a complete shutdown.
Dude it doesn't matter if it's an educated guess or not.
And yes, Harm does know his stuff, that's not a question at all.
I need to know because I have more than enough to share about Quicktime on Windows systems, with and without Adobe.
Get the most obvious causes out of the way before jumping to complicated issues sometimes helps, ya know?
If it's not Quicktime then fine, narrows it down a bit. And it's also important to know if his PPro and AME is updated or not because several
severe crashes can be caused if it's not, PARTICULARLY if the guy is working with Quicktime.
I'm looking at the reports' stop codes and crash info, and there are several cues that do not point to overheated CPUs.
Get the most obvious causes out of the way
Agreed. And in most cases of a complete system shutdown, you're looking at hardware issues. That it happens only when the CPU is busy and temps are high is very telling.
With systemic shutdowns the three main causes, and in the usual order:
2.) Power supply
3.) MoBo issues
There CAN be other issues of course, but the majority can be traced directly to one of those three.
The fix is: run cooler, have an adequate power supply and check that MoBo. If all of these check out fine, then you have much more field-testing ahead of you.
I am having the same problem I think? I just upgraded to CS4 from Premiere 2.0. I have Windows XP Pro, Service Pack 3, and I'll add the specs you talked about. Edditing AVI DVCPro50 files.
Long story short I am rendering a Boris film FX on 5 or 6 clips at a time. They run about 3-5 minutes each. I used to do this in Premiere 2.0 on the this same system and no problems. I usally would start 8 or 9 clips go home and the next morning Export them out. So I've done the same thing here but both times when I come in the next morning and the computer looks like it shut down or just the program. I'm 90% that it completely restarts. What to do? No idea but I have a ton or rendering and A upset client. Any suggestions?
A number of problems pop out of your DXDIAG:
Both your video driver and your audio driver are more than 3 years old.
Your F drive is slow, because of the fill rate of 90%. You lack other hard disks.
You have Matrox, BlackMagic, Nero, Sony, DivX and other stuff installed. It has been a long time ago that I have seen such a long list of DirectShow filters installed.
Suggestions: Update your drivers, clean up your F drive and add another disk, remove all that Matrox stuff, possibly include BlackMagic and Sony.
What export/encoding settings do you use from what sequence settings?
Still not working? I did find I was using Magic Bullet Frames 1.0 and that doesn't work with CS4. So I have deleted that. Right now I can't get anything to render out or export out without crashing. I am attaching new files with this. Anyone have any suggestions I'm pretty desperate. Thanks.
When the program crashes, what does Event Viewer tell you is happening in both your System and your Applications tabs?
Could be some very important clues there. Follow any error, or warning messages with links. Those links might lead you right to the issue.
This ARTICLE will give you some tips.
Your audio and video drivers are now up-to-date. All the crap in your direct show filters is still present however. Try removing that.
Ok. I'll get those out. Thanks so much!! Do I delete all of them? And whats the quickest way?
If I take out the Sony and Nero direct show filters my programs like SOny Sound Forge and Nero won't work properly or would they? I understand what your saying with the direct show to a degree so do think I'm disagreeing with you just trying to understand why all the suden they are causing this? It was fine before I updated tp CS4?
Likely using uninstall. But maybe you need to manually remove the remnants.
I'm also reading now that CS4.2 won't work with Matrox LE 4.1!!! So great. Maybe that is the real issue? What do you think?
I got Direct Show Filter Manager 0.5 will that work. And do I really take all of them out or what?
Both of you guys should go into the BIOS and check your voltages. What brand and wattage power supply do you have? Some of the off-brand power supplies are bad news. I've even seen some name brand power supplies fail miserably in Maximum PC and Tom's Hardware torture tests. They can stress your components with inconsistent voltages. Low voltages can be a cause of component overheating and premature failure.
Thanks! I'll check that out as well.