F.Terh
If the BSOD is caused by memory problems, try removing one of the 1GB of memory. Then re-open PPro to try to induce the crash. If yes, put the 1GB memory removed back in after removing the other, again re-open PPro. It is unlikely that both sticks of memory are defective. I previously ran on 1GB of memory successfully, only working with SD material. It may be the m/board and/or chipset that is defective, new memory may not do it.
I do not have Vista, but with XP you can do a repair, if a hardware problem the repair sometimes fails.
The undernoted link states you can safely ignore the error ?????????????????
"SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected
http://support.microsoft.com/kb/950375
The error message may be part of the computer domino effect, when something falls over it shows up way down the line with great difficulty in unravelling.
There seems to be a double post on this problem:
http://forums.adobe.com/thread/446365
John
This is somewhat similar to problems I had with my previous system. Mysterious hangs, followed by BSOD's. In my case it showed that not memory was the problem, but the PSU. That brings me back to your 8.8V on the +12V rail, as was shown by Speedfan. The fact that the Bios indicates an adequate 12V rail with sufficient voltage does not prove that the PSU is in good health, at least not 'beyond reasonable doubt'. I had the same problem, but it really was indicative of imminent death and I had to replace the PSU. That solved my problems. I'm not saying your case is exactly the same, but it may be worthwhile to have your PSU tested under load and replaced if necessary.
Firstly it's not an accidental double post. I posted in two threads in order to reach a "wider audience", as both threads are related to the post.
And secondly I just tried to trigger a crash. I started up, exited a LOT of processes, cleared the logs in Event Viewer and ran Premiere Pro. I clicked on my "actual project" under Recent Projects and I got a BSOD. However I believe Premiere Pro had nothing to do with the BSOD because under Event Viewer > Applications the ONLY error was the WMI one.
Under system, however, I had a "The previous system shutdown at 6:27:02 PM on 26/8/2009 was unexpected." and a "Unable to initialize the security package Kerberos for server side authentication. The data field contains the error number." The second one seems to have NOTHING to do with the BSOD. Thus I believe that one of the processes I killed triggered the crash.
I'm going to further experiment, though, and post the results here.
Oh sorry. Okay anyway I did another experiment.
This time I did not kill any processes, instead I just ran Premiere Pro and opened my project. I managed to slide the slider bars without any problem, change the file format, and export it to AME. At AME I started the queue without any problem, and the whole encoding started.
I went for dinner. When I came back, the Elapsed Queue time is 57 seconds and Elapsed time is 33 seconds. However Premiere Pro is STILL responding. I could slide the bar and watch the images in the preview window flicker and change. But then it hanged.
Huh.
What happens in a situation like that is that both the poster, and those making replies can get very confused. Many of us reply to many posts in a day. It's hard to follow threads, if they "seem" to be the same. We'll start replying with, "hey, did you see post ______, 'cause someone has the same issue?" Well, it the poster's other article. For the poster, one can get all sorts of answers, as different respondents see different things. Keeping tabs on two posts can be a real nightmare.
That is why it is not allowed.
Good luck,
Hunt
Okay I tried running it on Windows 7, and as usual I restarted my system and killed off a couple of apps.
It hanged and these are the logs from Event Viewer.
Firstly I got an error from ImporterProcessServer.exe:
Faulting application name: ImporterProcessServer.exe, version: 0.0.0.0, time stamp: 0x4a0e03b3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x50c10bd8
Faulting process id: 0x53c
Faulting application start time: 0x01ca283b4ad4c9e1
Faulting application path: E:\Software\Adobe\Adobe Premiere Pro CS4\ImporterProcessServer.exe
Faulting module path: unknown
Report Id: cdf10acb-942f-11de-a445-002185156cb3
Then followed by 3 "Information".
And then the typical not responding log:
The program Adobe Premiere Pro.exe version 4.1.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: e98
Start Time: 01ca283c51471895
Termination Time: 39
Application Path: E:\Software\Adobe\Adobe Premiere Pro CS4\Adobe Premiere Pro.exe
Report Id: ddf7731e-942f-11de-a445-002185156cb3
Okay I just got my 4GB of memory, installed it and started my Windows 7.
I ran Premiere Pro and tried to render. It was very responsive, the system was smooth and fast, and rendering it was a breeze. For the first 1 minute 28 seconds. After that Premiere hung.
=.=
I really need help here! ![]()
*Can't seem to edit my post, never mind*
Sorry, my bad, it's 1 minute 28 seconds approx time remaining. Only 18% of the encoding process is completed, and that's just an estimation.
The thing is when the rendering progress stops loading, I can still alt tab back to my PP and slide the timeline bar around and work as per normal. But AME just won't encode anymore.
This should be interesting.
System start-up, new project, import ALL my footage, tried to render. Encoding stopped halfway through my first clip. Alt-tabbed to my Premiere Pro, it's responsive. Alt-tabbed back to AME, and back to Premiere Pro and the "Not Responding" sign comes up.
System restart, same project (I didn't save the previous time), imported ONLY the first footage, tried to render. Encoding was successful.
System:
Intel Core 2 Duo E8400 @ 3.6GHz
Team Xtreem Dark DDR2 4GB
Nvidia Geforce 9600GT
Western Digital 640GB
Western Digital 750GB
Tested both hard drives for errors on HD Tune 2.55's Error Scan (Quick Scan), results positive.
Update 1/9/08: I continued experimenting with the project above. Imported first 2 footages, encoded successfully. Restarted. Imported first 3 footages, stopped halfway through the 2nd footage (which was successful the first time). Restarted and retried. Again, stopped halfway through the 2nd footage.
One thing, on another forum somebody said: Also, you're putting 1280x720 30 fps MJPEG footage into an HDV (MPEG) 29.97 fps project setting. That certainly isn't helping anything. You would need to setup a custom project and I'd advise to set the sequence for 1280x720, 30 fps, uncompressed to have a shot at it working...
I tried to change the MPEG to Uncompressed but there isn't the option to do so, there is ONLY MPEG under Video.
And where do I get DV materials? I only have a camera that takes HDV footage.
All I know about the settings is that the footage is MJPEG and the video preview file format is I-Frame Only MPEG. How do you change it to Uncompressed?
And how come when rendering Clip 1 and Clip 2 it works, but with Clip 1, 2, and 3 it stops at Clip 2 and eventually Premiere stops responding. Note that it is still responding initially.
Harm Millaard wrote:
HDV is the wrong preset. You need to create a custom sequence, that reflects what you shot.
Can you help me come up with the settings? I'm sorry but I have no idea what to use for the sequence settings.
this is just one of my clips. they were all taken from the same camera, with slight differences (go to first page, i listed them).
Thanks!
This is weird.
I dragged the first clip into the timeline, ctrl+M, chose Uncompressed Microsoft AVI, and tried to export. I got an error. (I didn't check but I strongly suspect it's the I/O error thing). I tried again this time changing video codec to UYVY and it works. Then I realized that my res is wrong; I need it to be 1280x720. So I retried but it kept throwing I/O errors at me. I even tried the UYVY, and tried the default settings but I kept getting I/Os.
Update: I ran the clip through G-spot and it was weird. It reported the codec as "jpeg" and the name "Apple Photo JPEG" while MediaInfo reports codec as "M-JPEG". So what exactly is it? LOL.
Motion pictures: “QuickTime Motion JPEG” (motion pictures with audio)
I guessed MediaInfo is right then.
***
Also, does I/O Error indicates a hardware problem/failure? Because I get that when trying to render in Uncompressed Microsoft AVI, but I have NO problems rendering using QuickTime > Photo - JPEG or PNG. I think I'll go for Photo - JPEG then since it's fast and pretty good quality. PNG is great but the file size is a tad too big, although it is lossless (I compared the original with the rendered one). Photo-JPEG has a slight loss of color quality, but it's still pretty decent.
We are now at post # 68 and the only conclusion I can draw from this extended discussion is that your source material from a digital still camera is not suitable for editing with PR and you may be better served with a consumer application like the free WMM or the low cost alternatives such as PE, Magix, and the like.
I just want to say a BIG THANK YOU to everyone here, especially Harm Millaard. Your last post is the solution. I pondered over it and thought it makes sense, I tried to export the footage as uncompressed AVI and reimport them but faced errors again.
So I used Vegas Pro 9.0 to export them as .mp4 files (very good quality) and import them in. And it works!
So once again, thank you to everybody here who had helped me troubleshoot my way, and have helped me tremendously. I would love to shake the hands of everybody here, really. But I can't.
Keep up the good work guys, and continue helping amateurs like me! Thanks a million!
North America
Europe, Middle East and Africa
Asia Pacific