User profile for user: roynestle
roynestle Author
User level: Level 1
15 points

FCP 12 locks up entire MacBook Pro when rendering a file to share.

Why does Final Cut Pro 12 constantly freeze my ENTIRE SYSTEM every time I try to render a file? At about 25% it locks up the ENTIRE computer.


Rendering to the internal SSD or to and external HD, it doesn't matter. The length of the file being rendered doesn't matter. The encoding doesn't matter. Nothing makes any sense!


The crash brings back an error report with "WindowsServer" as the title, and another (usually, but not all the time) that is a system failure report. It has been almost two months since this began. Even reporting these issues via Feedback Assistant has gotten me no answers. Does anyone HERE know anything about this time and money wasting set of errors?


Tahoe 26.3 installed. FCP v. 12.


If it helps, I have the full error report text saved. First is the initial info for the error. Then comes a portion of the error report showing a notable change in data. I added the bold highlight to certain numbers, but the text is the same otherwise:


{"name":"WindowServer","roots_installed":0,"timestamp":"2026-03-03 13:36:52.00 -0800","os_version":"macOS 26.3 (25D125)","incident_id":"166AE836-378C-429E-84B7-0F772E6C6994","share_with_app_devs":1,"bug_type":"409","app_name":"WindowServer","bundleID":"WindowServer"}

{

"deployVersion" : 210,

"variant" : "stackshot",

"incident" : "166AE836-378C-429E-84B7-0F772E6C6994",

"crashReporterKey" : "1B5807E3-0D83-DEED-42A1-D28649828CFE",

"modelCode" : "MacBookPro16,1",

"cpuType" : "00000000",

"osVersion" : {

"train" : "macOS 26.3",

"build" : "25D125",

"releaseType" : "User"

},

"variantVersion" : 2,

"captureTime" : "2026-03-03 13:36:52.9700 -0800",

"pid" : 297,

"bug_type" : "409",

"trmStatus" : 2105856,

"procName" : "WindowServer",

"bundleInfo" : {"CFBundleIdentifier":"WindowServer"},

"termination" : {"flags":0,"indicator":"monitoring timed out for service","code":1,"namespace":"WATCHDOG","details":["(1 monitored services unresponsive): checkin with service: WindowServer (0 induced crashes) returned not alive with context:","unresponsive work processor(s): WindowServer main thread","40 seconds since last successful checkin, 5923 total successful checkins since 59272 seconds ago, has not exited since first loaded"]},

"bootSessionUUID" : "E67F923C-0119-4D1A-9FF6-9F18BF956D95",

"uptime" : 59000,

"thermalPressureLevel" : "ThermalPressureLevelModerate (1)",

"displayState" : "OFF",

"stackshot" : {

"processByPid" : {


DATA CHANGE?

da1b74dd7f5d",4361170944,"P"],["03ea1c1e-42c0-3d44-a2f2-da1b74dd7f5d",4305747968,"P"]]

},

"reportNotes" : [

"task_read_for_pid(150) for resampling backtraces failed",


etc, etc, etc.

MacBook Pro 16″, macOS 26.3

Posted on Mar 3, 2026 2:08 PM

Reply
Question marked as Top-ranking reply
User profile for user: joema
joema
User level: Level 4
1,453 points

Posted on Mar 4, 2026 1:29 PM

OK I've analyzed your files. This is a system-level issue, nothing related to FCP or which can be fixed by FCP changes. The only involvement by FCP is that it incidentally puts normal pressure on an unstable system that sets in motion the crash. But don't worry, we will try to help you here before sending you anywhere else.


I have a 2019 MacBook Pro 16 similar to yours so I can run tests if needed.


The system-layer nature of your problem explains why the entire system sometimes locks up. FCP cannot lock up the entire machine.


Observations from your crash logs:


  • macOS process WindowServer apparently hung while blocked on a kernel mutex. This was a last-ditch attempt by macOS to prevent further problems.
  • Kernel thread 3119 named AMDRadeonX6000_AMDAccelEventMachine. It holds the kernel mutex that WindowServer was blocked on. It is in an unstable state and won't release the mutex.
  • Kernel thread 3120 (AMDRadeonX6000_AMDNavi14GraphicsAccelerator is also blocked on the same mutex.
  • DumpGPURestart throttled after exit() thread is present in kernel_task. This indicates that a GPU restart was attempted.
  • Multiple IOGraphics work threads are stalled, because the GPU driver itself is deadlocked.
  • Cause of system hang: The GUI is frozen because WindowServer can't service any Mach messages while its main thread is stuck in an uninterruptible kernel wait behind the hung AMD driver.


You have some anti-virus software on the machine that could be contributing to the problem. This includes:


  • CCleaner, made by Piriform
  • 360SafeTray, made by Qihoo 360 Security (Chinese AV/security software)


Immediate Suggestions:


  • Remove or disable 360 Security / 360SafeTray completely. This is Chinese AV software with possible kernel extensions.
  • Remove or disable CCleaner.
  • Uninstall or update the CorelDRAW suite (or at least disable its Quick Look thumbnail generator) to stop the many, many CDRThumbnail crashes. Possible removal procedure: System Settings → Privacy & Security → Extensions → (find CorelDRAW or CDRThumbnail under the Quick Look / Finder Extensions section) → uncheck it.


If that does not immediately produce better results, run Apple Diagnostics: https://support.apple.com/en-us/102550


Note: This is a lightweight test, so an error-free pass does not guarantee a "clean bill of health." However, it is easy to run, so it's a good idea in cases like this where your crash logs show various GPU errors.


If that shows no problems please download the utility EtreCheck Pro. It is free and safe. It gathers info about your system which can help us understand the problem. https://etrecheck.com/en/index.html


After downloading and running EtreCheck Pro, it builds a report about your system, which you then post here. Click "Share Report" to copy it to your clipboard. You then make a post and use the "additional text" button on the toolbar (looks like a sheet of paper). Just paste the report contents there. We use it all the time on this forum.


We don't work for Apple but are FCP users like yourself who volunteer to help others. But don't worry -- we will do everything possible to help you.







View in context

Similar questions

5 replies
Question marked as Top-ranking reply
User profile for user: joema
joema
User level: Level 4
1,453 points

Mar 4, 2026 1:29 PM in response to roynestle

OK I've analyzed your files. This is a system-level issue, nothing related to FCP or which can be fixed by FCP changes. The only involvement by FCP is that it incidentally puts normal pressure on an unstable system that sets in motion the crash. But don't worry, we will try to help you here before sending you anywhere else.


I have a 2019 MacBook Pro 16 similar to yours so I can run tests if needed.


The system-layer nature of your problem explains why the entire system sometimes locks up. FCP cannot lock up the entire machine.


Observations from your crash logs:


  • macOS process WindowServer apparently hung while blocked on a kernel mutex. This was a last-ditch attempt by macOS to prevent further problems.
  • Kernel thread 3119 named AMDRadeonX6000_AMDAccelEventMachine. It holds the kernel mutex that WindowServer was blocked on. It is in an unstable state and won't release the mutex.
  • Kernel thread 3120 (AMDRadeonX6000_AMDNavi14GraphicsAccelerator is also blocked on the same mutex.
  • DumpGPURestart throttled after exit() thread is present in kernel_task. This indicates that a GPU restart was attempted.
  • Multiple IOGraphics work threads are stalled, because the GPU driver itself is deadlocked.
  • Cause of system hang: The GUI is frozen because WindowServer can't service any Mach messages while its main thread is stuck in an uninterruptible kernel wait behind the hung AMD driver.


You have some anti-virus software on the machine that could be contributing to the problem. This includes:


  • CCleaner, made by Piriform
  • 360SafeTray, made by Qihoo 360 Security (Chinese AV/security software)


Immediate Suggestions:


  • Remove or disable 360 Security / 360SafeTray completely. This is Chinese AV software with possible kernel extensions.
  • Remove or disable CCleaner.
  • Uninstall or update the CorelDRAW suite (or at least disable its Quick Look thumbnail generator) to stop the many, many CDRThumbnail crashes. Possible removal procedure: System Settings → Privacy & Security → Extensions → (find CorelDRAW or CDRThumbnail under the Quick Look / Finder Extensions section) → uncheck it.


If that does not immediately produce better results, run Apple Diagnostics: https://support.apple.com/en-us/102550


Note: This is a lightweight test, so an error-free pass does not guarantee a "clean bill of health." However, it is easy to run, so it's a good idea in cases like this where your crash logs show various GPU errors.


If that shows no problems please download the utility EtreCheck Pro. It is free and safe. It gathers info about your system which can help us understand the problem. https://etrecheck.com/en/index.html


After downloading and running EtreCheck Pro, it builds a report about your system, which you then post here. Click "Share Report" to copy it to your clipboard. You then make a post and use the "additional text" button on the toolbar (looks like a sheet of paper). Just paste the report contents there. We use it all the time on this forum.


We don't work for Apple but are FCP users like yourself who volunteer to help others. But don't worry -- we will do everything possible to help you.







Reply
User profile for user: roynestle
roynestle Author
User level: Level 1
15 points

Mar 30, 2026 4:58 PM in response to roynestle

I should have done one step at a time, but I just dove it and followed up with the suggestions here. I have used the 360 and Ccleaner for years without issue (they both have options I like to use aside from virus protection). I still went ahead and removed the 360 software along with a bunch of other stuff I hadn't used in forever. I can gladly say that Final Cut Pro is again working, and I greatly appreciate the help you gave in making it so. Thank you joema and Luis Sequeira1 very much!!!

Reply
User profile for user: joema
joema
User level: Level 4
1,453 points

Mar 3, 2026 3:09 PM in response to roynestle

This is apparently a macOS problem with the "WindowServer" component. However, if you send me the complete log file or crash report, I'll analyze it. https://we.tl/r-bAQQU51kIi


If you run the Console app, then in the left sidebar click on Crash Reports, look for WindowServer or Final Cut Pro. For any crash report, right-click and pick "Reveal in Finder." That will be an .ips file for each one. Use Finder to right-click and Compress each one and send it to the above URL.


If you have somehow saved the report some other way, also compress it and send that entire report.


Please also verify you have plenty of free space on your system drive, at least 20% free space.



Reply
User profile for user: roynestle
roynestle Author
User level: Level 1
15 points

Mar 4, 2026 11:27 AM in response to joema

I've sent the requested information. I did not find the system report which often comes up with the WindowsServer report. I guess Console doesn't keep the records in perpetuity.


I did see a lot of errors while the system tried to generate previews and thumbnails for my CDR files, PenTablet errors (bad access errors since the tablet is off, I suppose), and some kind of error with my Pirform 360 system protection (the error said a library was missing, but everything functions properly).


I have always had those two installations on this MacBook Pro. I never had an issue before, but I figured that I had better give you a heads up on them in case it makes a difference.


Attached is a full list of errors found in the Console app.

Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

FCP 12 locks up entire MacBook Pro when rendering a file to share.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up