Newbie - Help Understanding Crash Code

I'm new to this forum and actually joined up because of an issue I'm having with Sonar Producer X1.  The guys over at the home recording forum suggested there might be more knowledge here than there.
 
So here's the quick background.  Been using X1 for about 3 or 4 years and it's never been super stable.  But I make back-ups frequently and have been lucky that none of the crashes have cost me anything notable... until last week.
 
I feel like my PC has plenty of oompf:
Pentium Dual-Core CPU E6700 @3.2GHZ 3.20 GHz
Installed memory(RAM): 8.00GB
System type: 64-bit Operating System
And it's running on Windows 7 Home Premium
 
So today I was working in the Plug-in Manager and it crashed.
 
The Even Viewer gave me this:
Faulting application name: SONARPDR.exe, version: 18.0.5.533, time stamp: 0x4f4e651e
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x8e4
Faulting application start time: 0x01d1a22308e04c1a
Faulting application path: C:\Program Files (x86)\Cakewalk\SONAR X1 Producer\SONARPDR.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: 63b40672-0e18-11e6-bc4d-1c6f65abb064

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: SONARPDR.exe
P2: 18.0.5.533
P3: 4f4e651e
P4: StackHash_03fd
P5: 6.1.7601.17725
P6: 4ec49b8f
P7: c0000374
P8: 000ce6c3
P9:
P10:
Attached files:
C:\Users\Computer\AppData\Local\Temp\WERCD0F.tmp.appcompat.txt
C:\Users\Computer\AppData\Local\Temp\WERCE57.tmp.WERInternalMetadata.xml
C:\Users\Computer\AppData\Local\Temp\WERCE68.tmp.hdmp
C:\Users\Computer\AppData\Local\Temp\WERDD57.tmp.mdmp
These files may be available here:
C:\Users\Computer\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_SONARPDR.exe_6be88d356e86e6cbec8fc5db8b4b8f2cabc7cb80_cab_08dfddf0
Analysis symbol:
Rechecking for solution: 0
Report Id: 63b40672-0e18-11e6-bc4d-1c6f65abb064
Report Status: 6
 
 
Not being a super savvy computer guy, I have no clue if there's any info here that might be able to help figure out what's going on.  I also realize that there might be multiple reasons and this might just represent one.
 
Any thoughts or input would be most appreciated.
 
Thanks in advance!
 

hi nate, unfortunately that's a pretty generic event log entry, but there are a few things you can try
 
first, make sure you're fully patched to the last x1 version;
second, try & remember what you were doing in sonar when it crashed;
third, be aware that even the most recent x1 version was abandoned with at least 2 CTD bugs (clicking the wrong part of the pro-channel header; ctrl-dragging fx from one track to another) that were only fixed in x2 (but the less said about x2 the better ;-)
 
if you can provide some detail wrt the second point, someone here will most likely be able to help
 
good luck!

Wow, lots of good stuff here.  I'll take 'em one by one.
 

JonD
What's your audio interface?  Using latest firmware/drivers?

 
I'm currently using a Steinberg UR824.  I've had it about a week now and did indeed download the latest firmware and drivers when I got it and installed them.
 

pwalpwal
hi nate, unfortunately that's a pretty generic event log entry, but there are a few things you can try
 
first, make sure you're fully patched to the last x1 version;
second, try & remember what you were doing in sonar when it crashed;
third, be aware that even the most recent x1 version was abandoned with at least 2 CTD bugs (clicking the wrong part of the pro-channel header; ctrl-dragging fx from one track to another) that were only fixed in x2 (but the less said about x2 the better ;-)
 
if you can provide some detail wrt the second point, someone here will most likely be able to help
 
good luck!

 
First point - I have downloaded and installed up to ProducerX1dPatch, which I believe is the most recent.
Second point - I'm fairly sure most of my problems have been related to VST plugins.  This most recent time I was in the Plug In Manager looking at all the plugins in there and deciding which ones to take out of my scan folder.  I haven't tracked specifically which plugins seem to be at issue, mostly because I've downloaded way too many freebies to keep good track of, thus my recent efforts to thin them out to just what I really use.  But I do believe plugins have a big part to do with my issues.
Third point - Not sure if I crossed paths with either of those CTD bugs, but good to know.
 

JonD
Okay, I found your thread over at HomeRecording.  Nate74, correct?
 
I'd start with downloading and running DPC Latency Checker:
 

 
Then come back and tells us what it says.

 
Yes, Nate74 there.  Had trouble signing up as Nate74 here so came up with the lame SlyNate instead :(
 
If you found the thread about Sonar, that tells the story.  You may have stumbled onto the one about my attempts to use a Mackie ONYX 1620 with Firewire as well, which is now no longer in my setup and back to live use only.
 
But I will download and run the DPC Latency Checker just the same and post the results.

Thanks all for the help and input.  Liking this forum already :)

I think something might not be updated to whatever the most current level is though I did find a thread where Cakewalk did indeed have a bug in Take Lanes UI processing - so the bottom line as I see it is to make sure that you have all available maintenance applied to Windows, as well as drivers and Sonar, as well as plugins.  Do Windows Update until no more critical/high importance patches are available, and then update your drivers and applications.
 
IF it ends up after the above, that this remains - and the issue cannot be methodically traced to either a plugin or to some certain user combination of performed actions within Sonar, then it is possible that the error is within Sonar and perhaps was not fixed in the version of Sonar that you are currently running.
 
I would suggest you also consider contacting Cakewalk Technical Support - in case they are aware of a coding deficiency within that version of Sonar, or in case they have an understanding of why this particular situation is happening for you.
 
Bob Bone
 
 

How is your VST scan setup? Automatic? Also, when you say "moving from your scan path" do you mean moving the DLL files from that directory? I am wondering if the above combination would cause the crash. If using this method you could set the scan to either Manual or On Startup so it is not trying to keep up with DLLs moving without registry changes.

While in the Plugin Manager you can also simply disable plugins there, but leave them in the VST folder.

Do you happen to have any update to how things are working (or not) with your system?
 
Bob Bone
 

fitzj
The failing file is ntdll.dll   
Check  if this is a cakewalk  or system dell  loads  of tools online for this.  If a systems dell update and if a cakewalk file send them a dump and see what they say. 

ntdll is a windows dll, the error is very generic, for example:
http://pcsupport.about.com/od/fixtheproblem/a/ntdlldll.htm