Lexington crashes during recording in Comping/Sound on Sound

Hi. It seems like ntdll.dll is Windows related.
http://www.computerhope.com/issues/ch000960.htm
All the best.

I opened a file started in Lexington 64 bit the previous day and started to replace my scratch piano part (Ivory Piano). I started at the beginning and played the whole song through 1x and at the end of the song, I hit stop and I got the Sonar Fault reporter box with a crash. I opened 32 bit Ipswich and had no problems for the rest of the day
 
The update right before Lexington had a known bug with some plugins. I would get a loud hiss from my Ivory Piano. Even when Sonar was stopped. I was hoping Lexington with all the hype would be really stable. I've never had any version of Platinum crash like this especially under a very light load (3 audio tracks). I've reverted back to Ipswich.

gswitz
I've been getting crashes once every couple of days. I cannot repeat or explain.

Was this happening with previous updates or just Lexington?

gmp

gswitz
I've been getting crashes once every couple of days. I cannot repeat or explain.

Was this happening with previous updates or just Lexington?

I'm not sure. I began noticing crashes when TH3 first came out, but right now I'm mixing a project without TH3 and it is crashing too. So, since late October? In not sure.

I've suspected TH3, AD2, and Rapture Pro. None of these are in the current project. Do I'm suspicious of the "performance enhancements".

At one point I spent ten hours or so trying to replicate a case where I play guitar through rapture pro past the end of an AD2 midi drum loop. I was not able to replicate, but in my attempts, I did not actually play, I just recorded.

http://forum.cakewalk.com/m/tm.aspx?m=3330958

When playing, I have had this crash case a number of times. I don't know if it is a true true unrelated case or not.

oztadpole
Yep. Similar issues here. Been crashing during audio recording or when you hit the space bar to stop recording.
Happening every day 3 out of 5 takes. Have tried different things - can't work it out. Started happening after I upgraded to Lexington.

The good news is that since you're not alone, it'll get fixed likely soon. Did you turn in a bug report? If not I'll send in one. This may even warrant a hotfix, since there's so much hype about how stable this update is supposed to be and that stability was one of the prime focuses. I've reverted back to Ipswich and after your report I'm glad I did. Thanks for chiming in.

oztadpole
Yep. Submitted a bug report the first few times it happened. I have just reverted back to Ipswich. Will see how it goes. Thanks for the advice.

Now that I recall, when it crashed the Fault Reporter box came up and I got to explain in detail just what I was doing when the crash happened. I even got email notification of it. I like this Fault Reporter. It's a very efficient way of reporting a bug. Hopefully we'll see a hotfix soon.

But wait, I just checked the Windows Application Log and I'm finding lots of this...
 
I right clicked "My Computer/This PC" Icon > Manage > Comp Management > Event Viewer > Windows Logs > Application then filtered for errors and warnings.
 
Faulting application name: SONARPLT.exe, version: 21.11.0.25, time stamp: 0x566ebb2c
Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3
Exception code: 0xe06d7363
Fault offset: 0x000000000002a1c8
Faulting process ID: 0x4354
Faulting application start time: 0x01d142b0f74d6403
Faulting application path: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report ID: 6d80f983-5756-43a3-99ea-1ad314c8d6e5
Faulting package full name:
Faulting package-relative application ID:
 
Also things like...
Activation of application Microsoft.WindowsFeedback_cw5n1h2txyewy!App failed with error: The app didn't start in the required time. See the Microsoft-Windows-TWinUI/Operational log for additional information.
 
Some like this...
The program SONARPLT.exe version 21.11.0.25 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 1cfc
Start Time: 01d140d2796ef6ac
Termination Time: 31
Application Path: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.exe
Report Id: acc99214-aced-11e5-9be4-000f9d0640f0
Faulting package full name:
Faulting package-relative application ID:
 
One of these...
Faulting application name: FaultReporter.exe, version: 2.5.0.0, time stamp: 0x5614000d
Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3
Exception code: 0xe0434352
Fault offset: 0x000000000002a1c8
Faulting process ID: 0x1d44
Faulting application start time: 0x01d142b2c1324b07
Faulting application path: C:\Program Files\Cakewalk\Shared Utilities\FaultReporter.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report ID: 70fc2124-0809-431d-bca3-85f0b7b786e8
Faulting package full name: 
Faulting package-relative application ID:
 
 
If I go back to September and before, I see a few of these...
Faulting application path: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

IN my case with Lexington, I didn't have to wait, in fact the first thing that happened is the Fault Report screen popped up, before it shut down Plat. I answered the questions, filled in the details of how it happened and hit "send" to send the info to Cakewalk. Then it said it will now close sonar.
 
I've actually had lots of crashes with Platinum since June when I got my new studiocat computer and Win 8.1 Pro. I'm still trying to figure out the causes, although recently I've found that Komplete 9 is causing crashing in certain situations. All of these Komplete crashes were total computer freezes where I had to reboot the computer and I didn't get any DMP files.
 
I went to Windows logs and did what you did, but none of my crashes are showing up, I guess because they were complete freezes, where the computer can't even make an error log. Did you have to set something up differently to get those errors logs to show Sonar crashes?  I see in your situation Fault Reporter is even crashing at times.

Lots of instability here as well, no 32 bit anything, but frequent freezing, usually when hitting spacebar to start or stop, or even clicking in FX areas to open a plugin, even if the plugin is disabled. Looks like I'll be taking a walk back a version for the time being.

I'm glad I found this thread. I'm also having the same, or at least a similar problem with SONAR Platinum x64 Lexington.  The three conditions mentioned at the top of this post are the same (take lanes on, sound on sound mode, existing data in the previous take lanes).  I was recording a MIDI track, and I reproduced it a total of four times (and never saw a situation with these conditions in which it did not occur) in the course of trying to see if there was some plugin conflict involved.  I record as short or long as I like, hit the space bar to stop recording, and boom!  In my case, SONAR's Fault Reporter dialog never comes up, just a normal Windows application crash, and the Event Viewer shows a heap corruption crash in ntdll.dll.  (Despite pointing to an operating system library, heap corruption crashes are usually bugs in applications in managing their dynamically allocated memory.)  I'll paste the event information at the bottom of this post.
 
I initially thought it might be something relating to using my Akai EWI USB since today was the first time I plugged it in since upgrading to Windows 10, but trying that with a simpler project and a fresh track did not have the same issue.  (Interestingly, though, trying to remove the EWI plugin from that simple project, without deleting the associated track, hung.  However, then trying again with the same plugin I'd been using in my original project, Arturia's AnalogLab, didn't have an issue removing the track in the simpler project.) I've also verified that, if I turn the take lanes off, there is no crash on stopping recording, so I'm going to guess that the issue comes in allocating memory to hold the new take lane (which makes me wonder if the crash will just end up being delayed to when I show take lanes again later).  In any event, there does at least seem to be a workaround at this point (i.e. just turn take lanes off while recording).
 
Here is the application event info:
------------------------------
Log Name:      Application
Source:        Application Error
Date:          1/10/2016 3:42:15 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      RP-Studio
Description:
Faulting application name: SONARPLT.exe, version: 21.11.0.25, time stamp: 0x566ebb2c
Faulting module name: ntdll.dll, version: 10.0.10586.20, time stamp: 0x56540c3b
Exception code: 0xc0000374
Fault offset: 0x00000000000ee00c
Faulting process id: 0x2f68
Faulting application start time: 0x01d14bffaa374f99
Faulting application path: C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 2eaf8265-ab40-4348-88d5-615bef92299e
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-01-10T23:42:15.652426000Z" />
    <EventRecordID>6308</EventRecordID>
    <Channel>Application</Channel>
    <Computer>RP-Studio</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SONARPLT.exe</Data>
    <Data>21.11.0.25</Data>
    <Data>566ebb2c</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.10586.20</Data>
    <Data>56540c3b</Data>
    <Data>c0000374</Data>
    <Data>00000000000ee00c</Data>
    <Data>2f68</Data>
    <Data>01d14bffaa374f99</Data>
    <Data>C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>2eaf8265-ab40-4348-88d5-615bef92299e</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
 

And just to add a little bit more, there are three scenarios I saw with the simpler case:
 
1) The one described above with the access violation happening before I could even press the spacebar to stop recording.  I saw this twice in 4 tries to recreate the problem.
2) The same heap corruption issue I saw consistently with my real life project, where the heap corruption occurs after pressing the spacebar to stop recording.  I saw this 1 time in my 4 attempts.
3) A scenario that did not crash at all.  Specifically, in my second attempt to recreate the problem with the simpler project, I got delayed in juggling my computer keyboard and MIDI controller, and I didn't actually start recording the new MIDI part until after the end of the first one (a few lines from "Mary Had a Little Lamb").  Thus, the two takes did not overlap, so it just put the second part in the same take lane as the first one.
 
#3 would seem to reinforce the notion of the problem occurring at the point of creating a new take lane.  However, I haven't figured out what is different about #1 and #2 -- perhaps something relating to whether I start playing notes before or during the first take's left clip boundary?  In any event, my different results on this same project may serve to reinforce some of the different results noted above.  I never once got the Fault Reporter, though.  But maybe that is more likely to happen if using the Comp setting instead of Sound-on-Sound or something.  Or maybe it matters if you're using 32-bit versus 64-bit?  Or...?
 
Time to submit a bug report, then try to get back to work on my real project, hoping the workaround will, you know, work...
 
EDIT:  Well, I *tried* to submit a bug report, including uploading a small project.  At the end of it, it told me, "the Internet is Broken.  Well at least our little corner of it is."  I'm not sure if that means the report didn't get submitted at all, got submitted without the sample file, or...  It's too much of a pain going through the steps to try again, so hopefully others' reports, along with this forum entry, will get the problem fixed. 
 
One other thing I should add is that I have "store takes in a single track" and "create new lanes on overlap" set. For those who are not seeing the problem, perhaps there could be a difference in this area?  These are the settings I always use, but I think the last time I was doing tracking like this was approximately November 22nd -- I'm not sure what iteration of SONAR Platinum was the latest at that point, so I don't know if this issue is new with Lexington or possibly crept in somewhere between the Ipswich noted above and Lexington.

Hi Noel, yes, I confirmed earlier that the workaround worked, and it's good to hear a fix is in the works. 
 
However, and I don't know if this is related to the bug you found and fixed or not, once it got to the point of editing the same project, the project was all of a sudden painfully slow on the UI front (e.g. expanding the height of take lanes, zooming in and out horizontally, etc. -- in fact, during the process of using the workaround it was even slow stopping recording of a take to be able to open the take lanes, mute the most recent take, close the take lanes, then start recording the next take, but there did not seem to be any audio engine issues in doing that recording, and the MIDI takes came out fine), and it ended up having some other issues. 
 
In the latter category, trying to do splits with the split tool within takes sometimes behaved consistently weird (e.g. doing a "lasso split" across all the takes only split the tracks that had data inside the lasso area, rather than splitting all of them, for example to split the start portion of the clip from the end portion of the clip -- the user-level idea was to split phrases, where a few of the takes had "noise" between phrases) and sometimes less consistently weird (sorry, it's harder to describe this as I was just trying to find workarounds for the consistently weird one to do the same trick, and the slowness in the UI was also making it tough to figure out what was going on).
 
Looking forward to the fix.