CCE SP 2.70 crashing...

[desta]

Hi all...

Not really sure where to begin with this. Basically the title pretty much sums it up.

I've been using CCE SP to encode some avi's to mpeg-2, and each time CCE crashes. I've used versions from 2.70.02.00 through to 2.70.02.06, and always the same thing. The first vaf pass always goes fine, but during one of the following passes it always crashes - it's not always on the same pass either.

I've tried the exact same encodes in CCE SP 2.67.00.27, and they work fine. In all cases I've loaded the avi's through Avisynth 2.56 - obviously the filters or settings change from one movie to another, but one thing they have all had in common is that I've used 'DirectShowSource' each time to call up the movies in avs.

I can't think why 2.70 is having problems, or what I might be doing to cause them. Any ideas welcome.

[Boulder]

Is there a specific need to use DirectShowSource?

[desta]

Is there a specific need to use DirectShowSource?
Well, yeah there was, but I've since tried it with avisource and it also crashed. Actually, as an update to that, CCE SP 2.67.00.27 is also crashing now. For the life of me I can't think what I've done wrong... it was all working fine a few days ago.

The only think I can think I've done is that I updated my version of x264. I wouldn't have thought that would make any difference, but I uninstalled it anyway to see... no difference.

[Boulder]

What kind of a crash it is, do you get a crashdump or anything like that.

[desta]

Sometimes it just crashes out with no message, while other times it comes up with the "cce sp has encountered a problem and needs to close. We are sorry for the inconvenience." message.

:(


edit: Just to add, I'm trying an encode at the moment with the avi loaded direct into CCE SP 2.70.02.00, with no avisynth. I've set it to do 5 passes (6 including the vaf), and I'm gonna see how far it gets.

edit2: Crashed again...

The only other thing I can think I've changed recently is that I installed DVD-RB Pro 1.09, but as it wasn't being used I can't see how that would've made a difference.

[Boulder]

Are you overclocking or anything like that? What is the AVI file encoded with? Have you tried updating the appropriate codec?

[desta]

No, not overclocking. The avi was an xvid encode. I've tried updating, uninstalling, going back versions, etc etc. I've currently got the xvid 1.1.0 final (http://www.xvid.org/downloads.html) release, AC3 Filter 1.01a, and FFDShow-20060226 installed... though I've tried various version of xvid and FFDShow.

The last thing I've tried doing is switching my pc off for a while. It had been on for a few days, although it's been on weeks before and still encoded fine. It's not the highest spec pc, but I've not had these problems before - AlthonXP 2400+, 1GB Crucial DDR400, MSI KT6V-LSR, WinXP Pro.

It's encoding at the moment (still on the first pass), so I'll see how far it gets. Failing that all I can think of now is a fresh format, and install everything again.

[Boulder]

Try using MemTest86+ first. I'd say run the test overnight to see if you get any errors - a single error is enough for instability.

http://www.memtest.org/

CCE is very picky when it comes to memory problems.

[desta]

Hi again... Yeah, I ran memtest - left it running for 11 hours, and no errors. I also formatted my pc, and started again - this time with only koepi's xvid 1.1 final, and ac3 filter as my installed codecs.... did the encode with cce sp 2.67.00.27... crashed again.

At the moment, all I can think is there's a hardware problem somewhere... don't know what though.

:(


edit: Well, one memtest, one format and fresh install, two defrags, and two hdd checks later, and it's still not working. I am now completely out of ideas. There appears to be nothing wrong with my pc.. that I can see anyway, but I still can't get through a full encode. Probably time to give up, mefinks.

edit2: Just as another update to this, I think I 'may' have found the problem.... or at least I hope I have. I rebooted my pc, went into the bios and was astounded to see that my cpu was hitting temperatures around 88 °C!! Dangerous to say the least. I don't know if CCE SP would shut off at high temperatures - maybe someone can clarify that? Anyway, I've just ordered myself a new Thermaltake Big Typhoon, so I'll have to wait and see if it makes any difference. I only hope I haven't damaged my cpu already.

[Trahald]

cce itself doesnt monitor temps.. but at that high your system can get pretty unpredictable. my wifes laptop reboots at 77c. 88 is crazy. and thats while you were in bios (cpus tend to cool off of extremely high temps fairly fast.. ) which means its likely it was higher during encode.

invest in a cpu/fan moniter (speedfan is free) and see if fan is flowing ok and what your temps are doing different things in windows. use cpu /fan monitors with caution (some can change the speed of the fan)

check your fan(s) for debris or replace them if needed. (w/fresh contact compound)

it seems that encoding is a way better system test than memory testers are. many systems that pass memory testers fail at encodes. (not just memory integrity but cpu integrity at high loads (read floating point math/math) and bus integrity)

[Boulder]

Yep, CCE can raise the temperature quite a bit. Based on your CPU, the temps are extremely high.

If you want to stress test your system, I suggest Prime95. Its stress test feature will quite soon produce errors if your system isn't rock solid. But as Trahald said, you should check the fans etc. first.

[desta]

In response to both... Well, my pc is currently idling at around 72c... which obviously is worrying. I've only got it on for limited times at the moment (this being one of them). As I said though, I've just ordered a new Thermaltake cpu heatsink/fan, which hopefully should arrive early next week. So I'll wait till that comes, clean out my pc, and start again.

Just to note - although the 88c that i mentioned is extremely high, it was immediately following a reboot after I had just tried the encoding. 88c isn't my idle temp.... even though it shouldn't be my load temp either.

Anyway, hopefully all fixed soon. Fingers crossed.

:)


Update: Forgot to let you know the outcome.... All is working well now. I bought a Thermaltake Big Typhoon ('Big' being the operative word). Processor now runs at 42C under full load, and no more CCE crashes, so all's well that ends well.

:)