My first suggestion is to update your video card and your audio card
And remove any Intellipoint driver you may have.
Thank you very much for the quick response. I am trying each of these solutions one at a time and checking how premiere functions, in hopes that we can figure out the exact source of the problem. So far I updated the video card driver. Things seemed to be going well for about 2 hours then the same old crash happened. Next step, the sound card driver. I am relying on the sound card that is on the motherboard. Is this good enough, or do I need a separate card? I looked on the ASUS website for a driver update but it does not seem that easy to download. Has anyone else completed this successfully?
Where exactly can I find the Intellipoint driver? Is it C:Windows\System32\drivers? Do you happen to know what it will be called? Thanks.
1 person found this helpful
Check in Device Manager and change a possible Intellipoint driver to a standard driver. Lots of people had problems with the Microsoft Intellipoint driver, which just did not seem very Intelligent.
Thanks. It looks as the though my IntelliMouse driver is hidclass.sys, hidparse.sys and hidusb.sys. I don't seem to have one that is called intellipoint. Darn.
I experinced these couple things , which causes Premiere to freeze
1> try to remove your plug ins one at a time and see (Third party plug ins sometimes causes to freeze)
2> Don't mix any other type of file format like .MOV and etc.just to trouble shoot (mixture of different file kind sometimes causes to freeze)
Start a new project with a simple AVI and see what happens
I'm having similar problems but in my case (Win 7, PPCS4) it's just the app that freezes. The rest of the computer runs. Same happens with Media Encoder. I use the Task Manager to kill the processes but the processes simply refuse to die - usually. I have to do a hard reset.
No particular action or sequence seems to cause this.
So, I got a hold of one of my friends that is a little more computer savvy than I am. He suggested swapping the graphics card out and seeing what happens. Luckily I have a couple of extra computers and was able to swap it out without spending any money. So far no crashes/freezes. It looks like I may have a defective card. I will take this newer old card through the gauntlet and let you know what happens.
These kind of things are extremely difficult to troubleshoot. I recently had a problem with an external firewire disk that was not recognized after turning it on. A dasy chained DV deck was easily recognized and worked flawless. The same disk over USB worked without problem, so what was going on? The daisy chained deck was recognized, so it did not appear like a firewire port. The disk itself gave no problems over USB, so it was not the disk. So, WTF was going on here?
Time for 'The case of the unexplained' to come into operation. It boiled down to having overclocked the PCI bus just a tad too much. Reducing the overclock on the PCI bus with 1% solved the problem and the disk is now easily recognized. Just to show you that in these cases you may have to look in different directions than one would expect initially.
Ah, "The Case of the Unexplained."
The difficulty with troubleshooting program hangs can be tedious. That's why so many start with the "stock questions," in hopes of finding an easy fix. When none of those pan out, they move on to straws to grasp at.
At least with more catastrophic crashes of either the program, or the system, there are often clues scattered about. With hangs, not so often. With peripherals, it can be even more difficult. In your case, Harm, you used good deductive reasoning to eliminate some possible causes. Once the easy stuff was out of the way, you had to move into deeper examinations.
Glad that you got it sorted. You're still my hardware guru!
PS - "The Case of the Unexplained" is both entertaining and informative. At points, I laughed, and then at others, I wanted to cry. "What, one has to go through all of THAT?" Sometimes, the answer is a simple, "yes." Thanks for sharing that link.
You're still my hardware guru!
Is there a time limit?
For you? No.
You're not the only who has spent loads on a new rig, and it's turning out more unstable than it should be.
I've done the same - in my case with an Asus P7P55D mobo, i7 860 cpu, 3x 1TB hard drives, 750watt power, GTX260 graphics and 8GB of Corsair ram. Nothing overclocked in the coolermaster case and superb chip air-cooler. Windows 7 64bit OS. (it's my first experience of a 64bit OS).
Memtest ran for abour 14 hours no errors before I stopped it.
Prime 95 blend mode ran for 24 hours at about 49-55c.
Only Premiere CS4 Freeze locks - once or twice when I scrub the timeline.
There's a thread I saw which I've looked at and tuned my rig to http://premierepro.wikia.com/wiki/Troubleshooting
I'm no guru on specific hardware tests that really highlights what can cause an app like Premiere to freeze, but have found very useful suggestions of what to fine-tune on these boards.
I wonder if these new i7 chips in Prem Pro prefer a certain make of ram or video card. I wonder if my Audigy 4 soundblaster would be better than the mobo sound chip. I wonder if Prem Pro prefers 1366 mobos or 1156 jobs. We'll get more idea over the next year ...
My lockup issue seems to be resolved by using the Compatibility function. Start / search for Compatibility. Run it against PPro and Media Encoder. Seems to make a significant difference.
Which compatibility setting works for you?
The only specifics I remember were selecting the app and the Next. I don't recall any specific settings, though I do recall seeing some choices when I've tried running the compatibility on other apps.