This issue will be fixed in RCM at a future date.  In the mean time, the following steps can be taken to bind xudad.exe to a single processor to avoid the crash (when trace logging is enabled):

1. Select the "Processes" tab in Windows Task Manager
2. Right mouse click on xudad.exe process and select "Set Affinity..."
3. Select a single CPU you want xudad.exe to run in

Note:  When attempting to set process affinity you may get the following error message:
    Unable to Access or Set Process Affinity
    The operation could not be completed
    Access is denied

If you get the above error, stop Task Manager, and follow these steps:

1. Open a command prompt (cmd.exe), run the following command to start Windows Task Manager
2. ntsd -c qd taskmgr
3. Right click on xudad.exe process and select "Set Affinity..."
4. Select a single CPU you want xudad.exe to run in

See solution How do you bind the RCM xudad process to a single CPU? for more information on binding RCM to single CPU