Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Author
Post
Essentials Only Full Version
jm24
Max Output Level: -54 dBFS
  • Total Posts : 2127
  • Joined: 2003/11/12 10:41:12
  • Status: offline
2012/02/07 12:05:25 (permalink)

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Getting a sonar crash occassionally with this event info:
 
Faulting application name: SONARPDR.exe, version: 17.5.3.282, time stamp: 0x4b7b3272
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b60
Exception code: 0xc0000374
Fault offset: 0x000c380b
Faulting process id: 0x9dc
Faulting application start time: 0x01cce5a41675e314
Faulting application path: C:\SONAR 8.5\SONARPDR.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 01c9ec3e-51a8-11e1-9bf6-00248cd20a12
 
Anybody got some vowels I can buy?
 
J
#1

4 Replies Related Threads
    Bristol_Jonesey
    Max Output Level: 0 dBFS
    • Total Posts : 16775
    • Joined: 2007/10/08 15:41:17
    • Location: Bristol, UK
    • Status: offline
    Re:Faulting module path: C:\Windows\SYSTEM32\ntdll.dll 2012/02/07 12:14:05 (permalink)
    System spec?

    Might help.

    CbB, Platinum, 64 bit throughout
    Custom built i7 3930, 32Gb RAM, 2 x 1Tb Internal HDD, 1 x 1TB system SSD (Win 7), 1 x 500Gb system SSD (Win 10), 2 x 1Tb External HDD's, Dual boot Win 7 & Win 10 64 Bit, Saffire Pro 26, ISA One, Adam P11A,
    #2
    sock monkey
    Max Output Level: -80 dBFS
    • Total Posts : 547
    • Joined: 2011/11/06 12:12:08
    • Location: Tree Top Studios
    • Status: offline
    Re:Faulting module path: C:\Windows\SYSTEM32\ntdll.dll 2012/02/07 13:14:32 (permalink)
    ntdll.dll,

     A google search of this will tell you what happened, It's a windows issue not Sonar.
    #3
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re:Faulting module path: C:\Windows\SYSTEM32\ntdll.dll 2012/02/07 16:15:48 (permalink)
    ntdll.dll,  A google search of this will tell you what happened, It's a windows issue not Sonar.

    Probably not, on both counts.


    ntdll.dll is the main gateway into Windows native functions for many applications. Because user apps call it often, many errors in the calling application are likely to be raised by ntdll.dll. That might lead a user to think that ntdll is prone to errors, but it's not; it's just reporting that the calling program did something wrong. The DLL is simply passing the error back to the calling application, which is supposed to deal with it. But because those errors arise from typically unusual and unanticipated scenarios, the application often cannot handle it and crashes.


    Because calls to ntdll are so ubiquitous, googling it will indeed return lots of information, but it's unlikely any of it will be applicable. The error is most likely caused by a bug in either SONAR or (more likely) in a plugin.


    Your best bet would be to open a support ticket with CW and then send them your minidump. There is a good chance they'll be able to narrow it to a specific plugin or SONAR function.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #4
    jm24
    Max Output Level: -54 dBFS
    • Total Posts : 2127
    • Joined: 2003/11/12 10:41:12
    • Status: offline
    Re:Faulting module path: C:\Windows\SYSTEM32\ntdll.dll 2012/02/07 19:06:16 (permalink)
    Thank you all for the stuff.

    I always attempt google self help before asking directions. Sort of a manly thing,...

    No mini-dumps for these crashes. 

    Bit: thanks for the tip about plugins. I have had a couple of crashes related to these in the last 6 months: vsampler, dimension, and vst scan at startup.

    I have removed a bunch of accumulated plugs i know I will never look upon. Just deleted another dozen of sorta redundant things. Just not enough time to play with everything.

    I will review what is active for each project in anticipation. But, a watched app never boils, so they say.

    Using WhoCrashed for some dmps for the plugin crashes it is reported an unidentified driver may be at fault.  Midi? Using LoopBe1, and Maple pipes, and MusicLab midi connection center to connect some midi tracks to muliple instruments. Time to reassess that stuff.

    thanks all

    j
    #5
    Jump to:
    © 2024 APG vNext Commercial Version 5.1