Cannot end sonarpdr.exe process without a spontaneous reboot/BSOD

Author
skeewiff
Max Output Level: -85 dBFS
  • Total Posts : 265
  • Joined: 2004/01/12 19:10:46
  • Location: London, England
  • Status: offline
2010/04/16 06:50:08 (permalink)

Cannot end sonarpdr.exe process without a spontaneous reboot/BSOD

Hi all. Trying to get to the bottom of some serious issues and have discovered that whatever I do I cannot end sonarpdr.exe process without causing a spontaneous reboot. Reproducible every time.
 
1. Load Sonar. No need to open any project or anything.
2. End process "sonarpdre.exe" in Task manager.
3. Machine sponataneously reboots.
 
Anyone else seeing this?
 
 
Spec in sig.
post edited by skeewiff - 2010/04/20 09:49:00

MOTU PCI 424 24IO
Biostar Tpower i45 MOBO
Intel Q9550,8gb Corsair RAM
1x Crucial M225 SSD - System
1x Samsung F2 1Tb - Audio
2x Samsung F2 1.5Tb - Storage
2x ATI 4550 (not crossfire - 3 monitors)
W7 64 bit
Sonar PE 8.5.3
#1

6 Replies Related Threads

    uncleswede
    Max Output Level: -78 dBFS
    • Total Posts : 638
    • Joined: 2005/06/06 12:53:08
    • Location: Essex, UK
    • Status: offline
    Re:Cannot end sonarpdr.exe process without a spontaneous reboot 2010/04/16 07:12:08 (permalink)
    Had something similar-ish where my MIDI interface's drivers weren't unloading for some reason when Sonar tried to shutdown. I just unplugged the USB cable from the MIDI interface (M-Audio midisport 2x2) and Sonar shut down cleanly.

    ---------------------------------------------------------
    How to fly - throw yourself at the ground and miss
    S8.5PE, i7-920 (XP), 6Gb RAM, Phonic Helix 12, Axiom 61 controller, JM VC3Q and mic, plus more...
    #2
    fireberd
    Max Output Level: -38 dBFS
    • Total Posts : 3704
    • Joined: 2008/02/25 14:14:28
    • Location: Inverness, FL
    • Status: offline
    Re:Cannot end sonarpdr.exe process without a spontaneous reboot 2010/04/16 07:16:34 (permalink)
    What happens if you end Sonar under Applications rather than Processes?

    If you use this for more than a DAW, run a complete spyware scan with a program such as the free Malwarebytes. 



    "GCSG Productions"
    Franklin D-10 Pedal Steel Guitar (primary instrument). Nashville Telecaster, Bass, etc. 
    ASUS ROG Maximus VIII Hero M/B, i7 6700K CPU, 16GB Ram, SSD and conventional hard drives, Win 10 Pro and Win 10 Pro Insider Pre-Release
    Sonar Platinum/CbB. MOTU 896MK3 Hybrid, Tranzport, X-Touch, JBL LSR308 Monitors,  
    Ozone 5,  Studio One 4.1
    ISRC Registered
    Member of Nashville based R.O.P.E. Assn.
    #3
    Butch
    Max Output Level: -87 dBFS
    • Total Posts : 175
    • Joined: 2005/07/13 08:17:27
    • Location: Asheville, NC
    • Status: offline
    Re:Cannot end sonarpdr.exe process without a spontaneous reboot 2010/04/16 07:26:44 (permalink)
    I had a very simular problem involving my Frontier Design Tranzport (also midi driven).  I would agree to look into what midi drivers and such are loading when you start sonar.  Maybe look through the list of processes and try to find the culprit.

    Butch
    Let's make some art!
    #4
    SilverfoxUK
    Max Output Level: -85 dBFS
    • Total Posts : 257
    • Joined: 2006/08/27 12:45:53
    • Status: offline
    Re:Cannot end sonarpdr.exe process without a spontaneous reboot 2010/04/16 07:53:55 (permalink)
    I too had similar issue.

    Unplug midi/usb devices before ending task.

    X3 64bit (final update)
    Windows 7 Ultimate x64
    Gigabyte SKT-1155 P67A-UD5 B3    
    Intel i5 2400 Sandybridge Quad core    
    6 GB Corsair RAM
    V-STUDIO 100 (Driver 1.50)
    M-AudioAxiom 49
    Korg PadKontrol
    BCF2000 



    #5
    skeewiff
    Max Output Level: -85 dBFS
    • Total Posts : 265
    • Joined: 2004/01/12 19:10:46
    • Location: London, England
    • Status: offline
    Re:Cannot end sonarpdr.exe process without a spontaneous reboot 2010/04/17 04:47:58 (permalink)
    Thanks all!
     
    I tried everyones suggestions and disconnected my midi controller (a novation xiosynth), checked in Sonar that there it was no longer listed in midi devices, and that there were no others, and then tried to end the sonarpdr.exe process: Same problem, rebooted immediately.
     
    I also tried ending the app rather than the process, which worked without rebooting. Sadly this does not manage to end Sonar when I run into my memory leak issue.
     
    Is it likely to be the MOTU PCI424 then? Is anyone else running a MOTU 424 64bit?
     
    Cheers for the advice...

    MOTU PCI 424 24IO
    Biostar Tpower i45 MOBO
    Intel Q9550,8gb Corsair RAM
    1x Crucial M225 SSD - System
    1x Samsung F2 1Tb - Audio
    2x Samsung F2 1.5Tb - Storage
    2x ATI 4550 (not crossfire - 3 monitors)
    W7 64 bit
    Sonar PE 8.5.3
    #6
    skeewiff
    Max Output Level: -85 dBFS
    • Total Posts : 265
    • Joined: 2004/01/12 19:10:46
    • Location: London, England
    • Status: offline
    Re:Cannot end sonarpdr.exe process without a spontaneous reboot 2010/04/20 08:30:15 (permalink)
    A clean install later and I now have a BSOD instead of a spontaneous reboot. Now thats progress!
     
    At least now I have dumps to analyse. Pretty obvious where the problem is - MOTUAW64.sys.
     
    Is anyone else running a MOTU 424 system? If so are you 64 bit? Are you seeing these BSODs/spontaneous reboots?
     
    Ta in advance
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {0, 2, 1, fffffa8008df7e58}
    Unable to load image \SystemRoot\system32\drivers\MotuAW64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MotuAW64.sys
    *** ERROR: Module load completed but symbols could not be loaded for MotuAW64.sys
    Probably caused by : MotuAW64.sys ( MotuAW64+23378 )
    Followup: MachineOwner
    ---------
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high.  This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffffa8008df7e58, address which referenced memory
    Debugging Details:
    ------------------
    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0f0e0
     0000000000000000
    CURRENT_IRQL:  2
    FAULTING_IP:
    +630b952f0614dc8c
    fffffa80`08df7e58 0000            add     byte ptr [rax],al
    CUSTOMER_CRASH_COUNT:  1
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    BUGCHECK_STR:  0xD1
    PROCESS_NAME:  WerFault.exe
    TRAP_FRAME:  fffff88002f93b80 -- (.trap 0xfffff88002f93b80)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffffa8008df7ecf
    rdx=0000000000000005 rsi=0000000000000000 rdi=0000000000000000
    rip=fffffa8008df7e58 rsp=fffff88002f93d18 rbp=0000000000000002
     r8=fffff88002f93d90  r9=0000000000000050 r10=fffffa8009c886e0
    r11=0000000000000258 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    fffffa80`08df7e58 0000            add     byte ptr [rax],al ds:52a0:00000000`00000000=??
    Resetting default scope
    LAST_CONTROL_TRANSFER:  from fffff80002ad6b69 to fffff80002ad7600
    STACK_TEXT: 
    fffff880`02f93a38 fffff800`02ad6b69 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
    fffff880`02f93a40 fffff800`02ad57e0 : 00000000`00000000 fffffa80`098441d0 fffffa80`09232d80 fffff880`03f13bef : nt!KiBugCheckDispatch+0x69
    fffff880`02f93b80 fffffa80`08df7e58 : fffff880`0487b378 fffff880`05a08ad0 fffff880`0486a27b 00000000`00000000 : nt!KiPageFault+0x260
    fffff880`02f93d18 fffff880`0487b378 : fffff880`05a08ad0 fffff880`0486a27b 00000000`00000000 00000000`ff000bc8 : 0xfffffa80`08df7e58
    fffff880`02f93d20 fffff880`05a08ad0 : fffff880`0486a27b 00000000`00000000 00000000`ff000bc8 fffffa80`08d7a000 : MotuAW64+0x23378
    fffff880`02f93d28 fffff880`0486a27b : 00000000`00000000 00000000`ff000bc8 fffffa80`08d7a000 fffff880`0486a6bb : 0xfffff880`05a08ad0
    fffff880`02f93d30 00000000`00000000 : 00000000`ff000bc8 fffffa80`08d7a000 fffff880`0486a6bb fffff880`02f93da0 : MotuAW64+0x1227b
    STACK_COMMAND:  kb
    FOLLOWUP_IP:
    MotuAW64+23378
    fffff880`0487b378 ??              ???
    SYMBOL_STACK_INDEX:  4
    SYMBOL_NAME:  MotuAW64+23378
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: MotuAW64
    IMAGE_NAME:  MotuAW64.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5b5773
    FAILURE_BUCKET_ID:  X64_0xD1_MotuAW64+23378
    BUCKET_ID:  X64_0xD1_MotuAW64+23378
    Followup: MachineOwner
    ---------
     
    #7
    Jump to:
    © 2025 APG vNext Commercial Version 5.1