Premiere Pro Crashing On Windows

Question

PC's are also being struck by the mysteries of CUDA in Premiere CS6.  I have literally tried everything to get Premiere CS6 working, including a full erase and reformat the C drive, installing Windows 7 again with as little drivers as possible, and right after that installing THE PREMIERE FAMILY only, but it still crashes immediately when I switch the MPE to "GPU accelerated", with any kind of footage in the timeline, that is.
So even on a clean system this CUDA stuff isn't working, I wonder if I will ever get it to work. By the way, CS5 goes great with the CUDA enabled, so there MUST have been a GREAT change that Adobe made in the CS6 MPE, they simply won't admit this and keep saying it's a setting. But as said, CS 5 DOES work so what setting could that for heaven's sake be?
Sigh... I am starting to hate Premiere.

Answer 1

I tried this today after my system got to the point where I couldn't even get CS6 open without a crash...so far so good.....
I know this doesn't mean much to Mac users but there may be a similar issue out there....
In VISTA and WIN7 there is a known issue with Timeout detection of recovery in the registry.......I avoided this until I found a fix I could download from microsoft to make the adjustment...here are the notes I sent to the nvidia tech today.....
I have uninstalled and let windows install the basic driver, I have not updated that driver yet.
I had read about this TDR below last week and decided to give it a try, rather than adjusting the registry myself there was a download on this page for windows to fix it. I am going to try this now for a day and see if I still crash......You should both read this all over...it is related to two errors, both of the ones I sent you earlier.... Open GL and the other one about the driver.... Display driver stopped responding and has recovered.” lets see what happens....Ill let you know.
Charlie
Method 1: Increase the GPU (Graphics Processing Unit) processing time by adjusting the Timeout Detection and Recovery registry value
Timeout Detection and Recovery is a Windows feature that can detect when video adapter hardware or a driver on your PC has taken longer than expected to complete an operation. When this happens, Windows attempts to recover and reset the graphics hardware. If the GPU is unable to recover and reset the graphics hardware in the time permitted (2 seconds), your system may become unresponsive, and display the error “Display driver stopped responding and has recovered.”
Giving the Timeout Detection and Recovery feature more time to complete this operation by adjusting the registry value, may resolve this issue.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up the registry in Windows 7, see Back up the registry <http://windows.microsoft.com/en-US/windows7/Back-up-the-registry>
To have us modify the registry value for you, go to the "Fix it for me <http://support.microsoft.com/kb/2665946#FixItForMeAlways> " section. If you prefer to modify the registry value yourself, go to the "Let me fix it myself <http://support.microsoft.com/kb/2665946#LetMeFixItMyselfAlways> " section.
Fix it for me
To fix this problem automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.
Fix this problem <http://go.microsoft.com/?linkid=9805447> 
Microsoft Fix it 50848
I downloaded and ran the file and uninstalled my driver in device manager rebooted and let windows choose an older driver for my 285 ge force card...its all been working smoothly tonight, although I have said that many times for months....
PS it drives me crazy but for those who saw the post about adobe constantly re conforming audio files...the fix in Windows was to go to %appdata% in the search bar, under adobe / under Premier Pro eliminate or rename the cs6 folder, restart and let all the files re conform one time and then I am good for a few weeks.....what drives me nuts is that I have to do this kind of crap at all!!!!
thanks all
Charlie