Basically, I'll be working in Premiere Pro and it will sometimes just... freeze. Not the program freeze where I force kill it and restart. The system itself, TOTAL lockdown but no BSOD. It's happened a few times while I try to move a large video file around on the timeline. It mostly happens, though when I try to render. Render settings don't seem to matter. I've tried it at both 10MB/s and 7 and it can still happen. 9 minute long video, 30 minute long video, every variable I can think of I've looked at and it doesn't seem to change anything.
Just to get this out of the way immediately, I DO NOT suspect ANY kind of HARDWARE failure. There was another thread I made several weeks ago where I was troubleshooting BSODs and tons of errors in Windows event viewer. Following every diagnosis suggested to me, I have turned up not a single sign of hardware failure. And since doing a lot of that repair work with things like the Windows page file, the BSOD have completely gone away. I'm 99% sure that garbage was all caused by Win10 just being shitty.
Soooo... here's some hardware specs. Other than what I've said, I don't know what other info to give. So ask away! CPU: AMD-FX 6300 OC to 4.5GHz (let me emphasise that I'm... 99% sure the OC is stable I've not had my CPU throw an error in over a year and prime95 has gone for an hour without an error. Games never lock up like this) GPU: GTX-760 RAM: G Skills 16GBs of 1600Mhz PSU: Thermaltake Toughpower 750W gold (newest piece of the system, other than a few HDDs and a new SSD) OS on a new SSD, everything else spread across HDDs
EDIT: just remembered a bunch of stuff I wanted to include. Tell me if any of this sounds abnormal... Render times: 10MB/s 1080p, 5.1, VBR 1 pass... 1:1 render rate, meaning for every minute of video it takes 1 minute to render -oh, and 98% average CPU usage 7MB/s 1080p, 5.1, CBR... 1:~.7 render rate, meaning for every minute of video it takes about 42 seconds to render -about 90% average CPU usage -yes, I've considered that Promiere Pro might be creating a unique situation that makes my overclock unstable whereas such as situation is not arising in Prime95. Not sure though, just a thought.
Also.... the above averages are while working on a hard drive. The video clips I"m using IN the video and the video ITSELF that is being saved, all on the same drive. For kicks, I just starting rendering this video (while typing here) that locked up twice now with the save destination as my SSD... render times seems a teeny tiny bit better but this is the first time I've tried this so I can't really say. And so far it's not locked up and I'm 66% rendering as of typing THIS word.
I will suggest a couple things since I have had similar issues in the past. When it happened to me it turned out to be a bad hard drive. At the time everything seemed great but would lock up when writing large data to the drive, there ended up being some corruption on the drive. I also had some weird issues when I had a bad ram module. The only time I have had a ram module go bad on me but the computer was acting fine until I would use memory intensive programs. Tested Memtest and was showing late in the testing.
Only way to know its not your OC is to set it back to stock settings and see if you get the error. If that doesnt fix it then I would test the memory
I have been needing to try this running stock speeds. I've been too lazy, but I know I need to and it's on the to-do list. I really should have tested that before making another thread... oh well.
I doubt it's memory. I ran memtest for 8 hours and got nothing. I also doubts it's a faulty hard drive, as this drive is literally just a month... month & 1/2 or so old (err.. actually let me think... did I use the old drive for the primary and the new for the backup or the other way around... crap...). But, it could be a dud, of course. I'll need to try to test it. I suppose I really can't move forward with this until I try it with stock clockspeeds, but if you have any troubleshooting tips, go ahead and throw em at me.
you have my sympathies and I am a bit too burned out on figuring out Premiere Pro issues from the bad old days to have experimented much with CC or even CS5.5 Premiere Pro but the GTX 760 card is not a Recommended card for windows and that may be part of the problem.
In the bad old days Premier's Recommended Graphics cards were really the Required graphics cards if you wanted a stable build. While I hope its better than back in CS4 and CS3 I can not help but feel like the graphics card may be part of the issue.
Huh... Yeah, it's possible. I'll try to find the time today to render a video at stock speeds. Let's assume for a moment that the overclock is what's causing it. How would I go about stabilizing it or would you suggest just running it at stock speeds any time I do video rendering? (I don't render often enough for it to be a huge nuisance to restart)
Oooook... so I'm 5 days late on my response but I've been stupid busy so you'll have to excuse me.
Anyway, tonight I got around to rendering a new video (with the overlock turned off) and... here's the results... they make no sense...
First of all, no lockups... The video is 48 minutes long but only took 24 minutes to render. This was a 1080p, 30FPS, 5.1 audio, 7MB/s bitrate video. Average CPU usage was only 55% during render times. Temperatures were in the high 30s (no surprise, with the overlock off and it being rainy/chilly today). And I was able to fiddle around with other stuff on my computer and still not get a lockup.
So lemme get this straight... having no overclock not only made the render not lock up my system... but it reduced the CPU usage while splitting the render times in half??? Wha... guh.. just... WHY????
The MMX instruction set I know next to nothing about. But if anybody has some reasoning for this... weird... turn of events... please let me know. In the meantime, case closed... I guess?
EDIT: I just found something out. The video was actually rendered in 720p, not 1080p. It was using "match sequence settings" and it was picking 720p for somer reason. Strange.... sure as hell doesn't look 720p.