Ppro CS3 trial package crashes computer at DVinfo.net

Nick Birkett · August 19th, 2008, 07:12 PM

I have fixed the problem in my other thread (fouled up file system) but, now I can't get PPro CS3 to run. I installed the trial version about 4 days ago on an HP AMD duo core machine with 1GB ram and a 250 GB disc, running Win XP with sp2. I got PPro to run once and then closed the programme normally. Now, every time I try to start it, it crashes the computer back to a hard re-boot. It goes through loading the drivers and then goes to a black screen before the 'new/open project' selection window. This has happened multiple times in a row - I can never get the programme to run. The point in the load cycle with the crash is exactly the same point where it crashed and fouled up my disc.

I also tested it out on a separate boot disc on this computer which was running XP MCE with exactly the same results.

I know that many people use PPro with excellent results. So, I'm not trying to complain about the product. But, I am looking at buying the full Adobe package through work (where it will be installed on a new Dell quad core workstation with 3GB RAM and Vista Pro). I need the web and related packages and got PPro as part of a package deal. I'd like to be able to use it but can't risk getting into a situation where my primary computer also crashes regularly.

Any advice on what I can try would be appreciated.

Bob Hart · August 20th, 2008, 01:11 AM

With 1 GB of RAM you might be a bit light-on for memory for Premier Pro 3. Take notice of better brains than mine on this subject.

Jiri Fiala · August 20th, 2008, 01:56 AM

I have succesfully finished several projects on my laptop with just 1 GB RAM, CS3 and Vista (!). That amount of RAM is not a cause for crashing.

Nick Birkett · August 20th, 2008, 06:16 AM

OK, I solved this one but the problem was silly. Adobe has a tech note on the problem (#332888). It was with the audio card device driver. With an integrated Realtek sound card, you need an up-dated driver which makes it ASIO compatible. After I up-dated the driver, PPro boots fine.

This looks like really bad code design by Adobe. Fair enough they need ASIO sound cards. but, there is no way that the absence of such a sound card driver should lead to a crash of the entire computer. At worst, the programme should crash and not start-up but leave the rest of the system OK. Since this is a known compatibility issue, PPro should have a short code fragment to check that the sound card driver is acceptable and, if not, close with a polite error message (or, even better, run a code fragment which offer to up-date the driver. Or, even better still, check for the driver compatibility when the programme is being installed and ensure that the driver is up-dated.).

Andrew J Morin · August 20th, 2008, 09:27 AM

If it worked perfectly now, how could they expect to charge you money for future versions?

Jiri Fiala · August 20th, 2008, 11:49 AM

The thing with Premiere is, though, that the amount of little bugs and annoyances piles up with each subsequent release, not improve.

Victor Guzman · September 24th, 2008, 05:16 AM

[QUOTE=Nick Birkett;922479]OK, I solved this one but the problem was silly. Adobe has a tech note on the problem (#332888). It was with the audio card device driver. With an integrated Realtek sound card, you need an up-dated driver which makes it ASIO compatible. After I up-dated the driver, PPro boots fine.

how did you get that problem code? did it just show it? because I have cs3 w premiere pro, and it keeps shuting down on me, giving me problems

Nick Birkett · September 24th, 2008, 05:25 AM

Not quite sure if you are asking how I got the driver update or if you are asking for something else. I got the driver update by using the manage option of 'my computer'. I went to the audio driver section and clicked the driver up-date option. That fixed my problem.

Victor Guzman · September 24th, 2008, 05:39 AM

Im asking how you got that error code, did it pop up every time the program had an error? or did you look for it on premiere ie "tools" "edit"

Nick Birkett · September 24th, 2008, 05:49 AM

I never got an error code with this problem. Rather, the computer just re-booted every time I tried to start PPro.

I had another thread about a fouled up file system. There was an error code for that problem but the code flashed on the screen for such a short time that it wasn't readable. I don't remember now how I eventually managed to read the code. It wasn't through PPro though since my computer wouldn't boot at all.

Tripp Woelfel · September 24th, 2008, 05:57 AM

PP CS3 seems to be very sensitive to audio issues. Never had the problem described here but I'm currently mucking through with a workaround to what is apparently an audio codec issue (according to Adobe tech support). PP would crash fairly randomly, and rendering or transcoding would crash/fail at 99% more often than not.

The fix is uninstalling CS3, uninstalling the two other audio programs then re-installing CS3. Haven't had time to do all that yet.

In Adobe's defense, what their software does is pretty amazing and mind bogglingly complex. The fact that it requires a fairly controlled operating environment is not unreasonable. I understand this because of 20 years experience in the software business.

Now, if they'd just fix the memory leak.

Nick Birkett · September 24th, 2008, 06:01 AM

Quote:

Originally Posted by Tripp Woelfel

In Adobe's defense, what their software does is pretty amazing and mind bogglingly complex. The fact that it requires a fairly controlled operating environment is not unreasonable. I understand this because of 20 years experience in the software business.

I agree 100% with this comment. But, if a programme needs specific components or operating system features to work probably, then good programme design would be to check that the environment is 'right' and provide constructive messages and remedial code to fix the deficiencies. Having your programme crash the operating system with no indication of why, is not very helpful :)

Tripp Woelfel · September 24th, 2008, 09:20 AM

Nick... Yes... this is the right way to do it. But the modern software development business model requires companies to balance features and bug fixes. New features make a company money. Bug fixes keep a company from losing money. It's a high wire act that each company handles differently.

It's interesting to note that model was shifted dramatically by Microsoft over ten years ago when they started shipping software that was buggier than the competition. This was done to get new functionality out sooner and made them more money. If consumers hadn't accepted the MSFT products the software world wouldn't be the way it is today.

What Adobe could do to help those of us who trip over bugs in their products is to publish their error codes. That would save us calls to to tech support. But remember that Adobe support is a billable product too.

August 19th, 2008, 07:12 PM	#1
Nick Birkett New Boot Join Date: Apr 2008 Location: Ottawa, Canada Posts: 14	Ppro CS3 trial package crashes computer I have fixed the problem in my other thread (fouled up file system) but, now I can't get PPro CS3 to run. I installed the trial version about 4 days ago on an HP AMD duo core machine with 1GB ram and a 250 GB disc, running Win XP with sp2. I got PPro to run once and then closed the programme normally. Now, every time I try to start it, it crashes the computer back to a hard re-boot. It goes through loading the drivers and then goes to a black screen before the 'new/open project' selection window. This has happened multiple times in a row - I can never get the programme to run. The point in the load cycle with the crash is exactly the same point where it crashed and fouled up my disc. I also tested it out on a separate boot disc on this computer which was running XP MCE with exactly the same results. I know that many people use PPro with excellent results. So, I'm not trying to complain about the product. But, I am looking at buying the full Adobe package through work (where it will be installed on a new Dell quad core workstation with 3GB RAM and Vista Pro). I need the web and related packages and got PPro as part of a package deal. I'd like to be able to use it but can't risk getting into a situation where my primary computer also crashes regularly. Any advice on what I can try would be appreciated.

August 20th, 2008, 01:11 AM	#2
Bob Hart Inner Circle Join Date: Dec 2003 Location: PERTH. W.A. AUSTRALIA. Posts: 4,476	With 1 GB of RAM you might be a bit light-on for memory for Premier Pro 3. Take notice of better brains than mine on this subject. Last edited by Bob Hart; August 20th, 2008 at 10:00 AM.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

August 20th, 2008, 01:56 AM	#3
Jiri Fiala Major Player Join Date: Feb 2007 Location: Brno Czech Republic Posts: 453	I have succesfully finished several projects on my laptop with just 1 GB RAM, CS3 and Vista (!). That amount of RAM is not a cause for crashing.

August 20th, 2008, 06:16 AM	#4
Nick Birkett New Boot Join Date: Apr 2008 Location: Ottawa, Canada Posts: 14	OK, I solved this one but the problem was silly. Adobe has a tech note on the problem (#332888). It was with the audio card device driver. With an integrated Realtek sound card, you need an up-dated driver which makes it ASIO compatible. After I up-dated the driver, PPro boots fine. This looks like really bad code design by Adobe. Fair enough they need ASIO sound cards. but, there is no way that the absence of such a sound card driver should lead to a crash of the entire computer. At worst, the programme should crash and not start-up but leave the rest of the system OK. Since this is a known compatibility issue, PPro should have a short code fragment to check that the sound card driver is acceptable and, if not, close with a polite error message (or, even better, run a code fragment which offer to up-date the driver. Or, even better still, check for the driver compatibility when the programme is being installed and ensure that the driver is up-dated.).

August 20th, 2008, 09:27 AM	#5
Andrew J Morin Regular Crew Join Date: Dec 2005 Location: Chicago, IL Posts: 140	If it worked perfectly now, how could they expect to charge you money for future versions?

August 20th, 2008, 11:49 AM	#6
Jiri Fiala Major Player Join Date: Feb 2007 Location: Brno Czech Republic Posts: 453	The thing with Premiere is, though, that the amount of little bugs and annoyances piles up with each subsequent release, not improve.

September 24th, 2008, 05:16 AM	#7
Victor Guzman Regular Crew Join Date: Aug 2008 Location: Kansas Posts: 113	[QUOTE=Nick Birkett;922479]OK, I solved this one but the problem was silly. Adobe has a tech note on the problem (#332888). It was with the audio card device driver. With an integrated Realtek sound card, you need an up-dated driver which makes it ASIO compatible. After I up-dated the driver, PPro boots fine. how did you get that problem code? did it just show it? because I have cs3 w premiere pro, and it keeps shuting down on me, giving me problems

September 24th, 2008, 05:25 AM	#8
Nick Birkett New Boot Join Date: Apr 2008 Location: Ottawa, Canada Posts: 14	Not quite sure if you are asking how I got the driver update or if you are asking for something else. I got the driver update by using the manage option of 'my computer'. I went to the audio driver section and clicked the driver up-date option. That fixed my problem.

September 24th, 2008, 05:39 AM	#9
Victor Guzman Regular Crew Join Date: Aug 2008 Location: Kansas Posts: 113	Im asking how you got that error code, did it pop up every time the program had an error? or did you look for it on premiere ie "tools" "edit"

September 24th, 2008, 05:49 AM	#10
Nick Birkett New Boot Join Date: Apr 2008 Location: Ottawa, Canada Posts: 14	I never got an error code with this problem. Rather, the computer just re-booted every time I tried to start PPro. I had another thread about a fouled up file system. There was an error code for that problem but the code flashed on the screen for such a short time that it wasn't readable. I don't remember now how I eventually managed to read the code. It wasn't through PPro though since my computer wouldn't boot at all.

September 24th, 2008, 05:57 AM	#11
Tripp Woelfel Trustee Join Date: Jan 2008 Location: North Conway, NH Posts: 1,745	PP CS3 seems to be very sensitive to audio issues. Never had the problem described here but I'm currently mucking through with a workaround to what is apparently an audio codec issue (according to Adobe tech support). PP would crash fairly randomly, and rendering or transcoding would crash/fail at 99% more often than not. The fix is uninstalling CS3, uninstalling the two other audio programs then re-installing CS3. Haven't had time to do all that yet. In Adobe's defense, what their software does is pretty amazing and mind bogglingly complex. The fact that it requires a fairly controlled operating environment is not unreasonable. I understand this because of 20 years experience in the software business. Now, if they'd just fix the memory leak.

September 24th, 2008, 09:20 AM	#13
Tripp Woelfel Trustee Join Date: Jan 2008 Location: North Conway, NH Posts: 1,745	Nick... Yes... this is the right way to do it. But the modern software development business model requires companies to balance features and bug fixes. New features make a company money. Bug fixes keep a company from losing money. It's a high wire act that each company handles differently. It's interesting to note that model was shifted dramatically by Microsoft over ten years ago when they started shipping software that was buggier than the competition. This was done to get new functionality out sooner and made them more money. If consumers hadn't accepted the MSFT products the software world wouldn't be the way it is today. What Adobe could do to help those of us who trip over bugs in their products is to publish their error codes. That would save us calls to to tech support. But remember that Adobe support is a billable product too.