Premiere Pro freezes and causes my computer to crash by re-writing the permissions inside my computer

Question

Premiere Pro re-writes my permissions inside my computer and causes premiere to crash, run slow, restarts my computer in the middle of rendering, and freezes my whole computer.  I have a brand new 2013 Mac Pro with 12core, 16 GB of ram, and 6GB of GPUs.  I will even try and and edit very small HD files from a DSLR whether they are H264 or Pro Res files.  I will do something simple like a distortion correction on those files that are a minute long and it takes it 40 plus minutes to render if it makes it through without crashing the program or the computer.  If I run it for a while without restoring the permissions in the disk utility it makes my whole computer freeze and crash from just about every program.  I have spent many hours on the phone with apple re-installing my operating system thinking that hardware was my issue.  After doing so and installing programs like avid and final cut with Adobe products off the computer it worked perfectly.  Then when I install Adobe products like Premiere Pro on the very first render they will start to have the issues I have explained above.  I have contacted Adobe support and have spent like 20 hours over the last few weeks with them remote logging onto my computer trying to fix the issue.  Towards the end of the last call the guy I was talking too wanted to collect all the information he could to ask the engineers about my problem. He asked me over a dozen times if I had re-installed my operating system and I responded with yes I have each time.  He then changed his tune to the only way he will continue to help me is if I will again re-install my operating system and only put Premiere Pro on the computer just to see if that will work.  I have crazy deadlines and do not have time to go through that process again and again.  He also told me that lots of people with my same computer have the same issues but still wants me to re-install my operating system again.  I explained to him that I am extremely behind with my work (because of this issue) and do not have the time to re-install again since the first re-install didn't work.  I had told him multiple times that I can get around using Adobe products but am huge fan of them(when they work) and would like to find a way to solve the problem.  He then told me that I should go ahead and cancel my subscription and and use that work around since he can not figure it out.  Is there anybody at Adobe that cares about losing my business?  Or anybody out there that may help with the solution of my problem?
Thanks,
Cody

Answer 1

WOW!!!! Adobe only cares about there reputation and not their customers!
Response:  I said multiple times in the last thread that I already did a clean install of my operating system.
Response:  I use DaVinci 10 times more than Premiere Pro and never have had one issue with it ever!  Must not be the issue?!?
Response: Changing the read and write permissions was the first thing the guy tried two weeks ago.  I have done a clean install of Mavericks and it did not solve my problem(as I said in my first post).
(Please do not create new posts in response to an earlier post. That post was deleted).
Hi Cody,
Really sorry you're so upset. I'm only trying to help, though. I suggested that the number one fix is to make sure that your permissions are set to read/write. You did not mention that agents tried this at all in your original response so that's why I mentioned it. Also, I was not completely clear that a clean installation was done as most people install the original OS and then update it, which can cause the issue. Sorry for the confusion.
You did say that you use Resolve all the time with no issues. Resolve can mistakenly install CUDA on your machine which has AMD GPUs. This can cause serious issues. I would remove CUDA from your machine and see if you get better results: Avoid installing NVIDIA CUDA drivers on computers with AMD GPUs
If you want further help, please let me know and I'll do what I can do to assist.
Thanks,
Kevin