DVD-RB Pro + CCE SP 2.7 Trial = Constant Crashing

[Curmudgeon76]

Hey all,

I've been using DVD-Rebuilder for awhile now and haven't really had any problems. I dontated and downloaded the last version (1.0.9.2 i think) and subsequently downloaded the lastest release offered (.3)

I had been using procoder before, mainly, but had also used SP 2.70 trial, and didn't seem to have any problems.

As of late, I've found that Procoder still works and converts through a movie and rebuilds with no problems. I reinstalled the SP trial and the first run through was a success. However, when trying the next movie, RB Pro completely hangs usually around 50 percent of the way through the encoding process (it does half the VOBs). I also find that I have to reboot my machine in order to re-open RB after this happens. This seems to happen EVERY time with CCE trial and didn't happen with Procoder, though I've done several movies with CCE before and it seemed to just start happening recently.

I'm baffled. Anyone have any suggestions as to what might be going on and how i can fix it? Thanks

Justin

[Fishman0919]

Do you OC your PC.... CCE SP can crash on most system if they are OC..... It's one of the best test for OC'ing your PC.

If not try re-installing CCE SP

[Curmudgeon76]

Hi,

Hmm. No overclocking. I reinstalled SP after the initial crashing and it worked at first, but now it seems to be crashing again.

[HKT3020_1]

You might want to check out the event viewer in your control panel under administrative tools. I just discovered it a few days ago and fixed up a few errors which I've overlooked. :rolleyes:

[jdobbs]

Check your memory. Sometimes just removing it and reseating it is enough. CCE uses a lot of memory and often it hits locations that are never accessed otherwise. If you're in the Northern Hemisphere it's also getting to that time of year when it is more common for processors and memory to overheat.

CCE is the ultimate system integrity checker. If it crashes its usually an indicator of something gone awry.

[Voodoochild]

Very hot here this time of yeat, Though I don't have this problem ... I use Timer for my Air conition to start when encoding and to stop 3 hours later when I'm at work...:) ...
this way cpy stay cool.....

[Curmudgeon76]

Hey guys,

thanks for the input. I noticed often times, when I shut down my computer, I get an error message (don't have the exact message copied down) something along the lines of "error in module something or other, memory could not be read" or something to that effect. I'll write it down next time I get the message. Anyone ever heard of/seen anything like that?

Thanks
Justin

[Rockas]

ummmm... I had one of that once... it was easy to fix... a full new and fresh windows installation :D

note: I did a full Windows installation 'cause I needed it anyway... you really should take a not of the full error and search for a solution on Microsoft site.

[l8nights]

is this the error you are reffering to??

http://img477.imageshack.us/img477/8607/untitled15hc1.jpg

I got this error a while back just rarely, I think it's a warning that ie was unable to clear some memory after it had used it, I ran memtest for several hours and no errors were reported.
so it's still kind of a mystery to me, and firefox gave me no errors @ all.
I don't know if a windows update had addressed it or if my tinkering with memory timings soothed the beast, so I would still like to see what was going on here?

*note this was not happening with dvd-rb just in closing ie browser windows.

[Curmudgeon76]

l8nights,
yes that's the exact error.

Justin

[jptheripper]

is it just me or is cce 2.7 trial just a major headache?

[Curmudgeon76]

jptheripper,

yes, I'm getting that impression myself. It's got to be something with CCE trial. I've done movies (and am still able to do movies) with Procoder 2 and have no problems with crashing whatsoever. Problem is, I don't feel that Procoder has the control over the final product that CCE does, and don't feel that the quality is necessarily as good.

[jptheripper]

can you step back a version to 2.67 and run the same project and see if it works? maybe we can isolate something about 2.7

[Curmudgeon76]

Good idea man, I'll see if I can find a 2.67 trial version and give it a shot. I'll let you know when and if I find it, and will post my results.

Cheers,
Justin

[jdobbs]

CCE is very demanding of you system -- a lot more demanding than ProCoder. Earlier versions of 2.70 were definitely a little flakey -- but I've been using CCE 2.70 for a long time now without issues.

[magic144]

FWIW

I have only ever used CCE SP Trial versions on my PC (only P4 2GHz) and have never had a single issue, even when running other things at the same time, toggling process priorities - including CCE itself, etc...

of course, I've never tried to overclock this PC either... I can only dream of what a souped-up modern PC would do with DVD-RB! Maybe in another couple of years in the Vista era, I will be tempted to upgrade.

I can also confirm CCE is a process hog - if left on Normal process priority, it will easily consume 99% CPU - don't even think about launching that text editor alongside it!

[jdobbs]

@Curmudgeon76

Please also follow Rule #8. You don't have to post your problem with "crashing " in every thread you come across in order to get attention. You've posted about this in three different threads... you've been warned. Post in another and I'll have to strike you.

[DD51]

There's a great piece of software to check the stability of your memory called "memtest.exe". It is only 24KB in size and unlike the cd/floppy disk version, it works under windows!
Don't need to boot up to it like memtest86 or whatever other version there may be. Of course this memtest86 version is better but at least you can check without the hassle of rebooting.

Look at it as a quick way to check for its stability.

I'm going to try to attach it and hope it works.

[MuttLover]

I'd recommend to just go to the memtest site and get full instructions as to its use and download too:
http://www.memtest86.com/

I would suggest the problem is:

a) a heat problem -- see if you can find "pc health" monitoring software and check your operating temps of the CPU; Motherboard Monitor used to be a highly regarded monitoring tool and may still work with your computer. A can of compressed air blowing the dust out of the heatsink fins can work wonders!

b) a memory problem -- the above mentioned memtest86 is a great and highly regarded memory testing tool;

c) a hosed install of Windows, in which case a full re-install of the operating system is in order. Sometimes a repair installation can work too.

[l8nights]

in my exp. pro2 seems to hog my resources, cce will only use like 70% peaked of my cpu.

if I remember right the error croped up after I had began to run pro2 dual instances, but as it did not happen in rebuilder I did not associate the two.

it's been months since I have seen the error, and I've had my memory timings set ultra low 4-4-4-12 (ddr2) I have memtest reporting no errors also I see no heat problems I usually use pc wizard 2006 minimized to monitor system params while encoding.

I haven't been able to recreate the error again so if anyone else has any suggestions to do so please chime in.
if not =anomoly/coincidence??