TechSpot

Bluescreen when closing Cubase 5

By Jainternet12345
Apr 11, 2010
  1. I hope someone can help me here. The problem i have is that when closing music sequencer Cubase 5 i sometimes, not always, get a Blue Screen. The soundcard i have is a M-Audio Delta Audiophile 2496 PCI card. I have read elsewhere that people have gotten bluescreens with the same soundcard, and hopefully someone on here can tell of that is my problem as well.
    I have attached the text file that pops up as well as two DMP.files.
    Do you need any more info to possibly find out what is causing this problem?
     

    Attached Files:

  2. webscaper

    webscaper TS Rookie Posts: 51

    The problem is with the driver of your soundcard M-Audio Delta Audiophile 2496. The driver is MAudioDelta.sys. Look for an update here: ww.m-audio.com/index.php?do=support&tab=driver&serie_ID=1&PID=adf95efc30b88aba043fa8b83343bfb8&OS=x91#tabs

    I cannot post links right now so I had to leave a w off the webpage above.

    I have underlined the offending driver.

    Code:
    Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\Webscaper\AppData\Local\Temp\Rar$DI00.617\040810-20872-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: /symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c63000 PsLoadedModuleList = 0xfffff800`02ea0e50
    Debug session time: Thu Apr  8 10:44:54.467 2010 (GMT-4)
    System Uptime: 0 days 1:43:06.417
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .............
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {ffffffff8166bd08, 0, fffff80002cf4e60, 5}
    
    Unable to load image \SystemRoot\system32\DRIVERS\MAudioDelta.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MAudioDelta.sys
    *** ERROR: Module load completed but symbols could not be loaded for MAudioDelta.sys
    
    Could not read faulting driver name
    [U]Probably caused by : MAudioDelta.sys ( MAudioDelta+207f )[/U]
    
    Followup: MachineOwner
    ---------
    
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except,
    it must be protected by a Probe.  Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: ffffffff8166bd08, memory referenced.
    Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
    Arg3: fffff80002cf4e60, If non-zero, the instruction address which referenced the bad memory
    	address.
    Arg4: 0000000000000005, (reserved)
    
    Debugging Details:
    ------------------
    
    
    Could not read faulting driver name
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f0b0e0
     ffffffff8166bd08 
    
    FAULTING_IP: 
    nt!MmProbeAndLockPages+130
    fffff800`02cf4e60 410fb601        movzx   eax,byte ptr [r9]
    
    MM_INTERNAL_CODE:  5
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0x50
    
    PROCESS_NAME:  Cubase5.exe
    
    CURRENT_IRQL:  0
    
    TRAP_FRAME:  fffff88002bbb220 -- (.trap 0xfffff88002bbb220)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80002cf4e60 rsp=fffff88002bbb3b0 rbp=fffffa800575aa38
     r8=fffffa80057cd740  r9=ffffffff8166bd08 r10=0000000000000000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz ac po nc
    nt!MmProbeAndLockPages+0x130:
    fffff800`02cf4e60 410fb601        movzx   eax,byte ptr [r9] ds:b5b0:ffffffff`8166bd08=??
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002d52b91 to fffff80002cd4f00
    
    STACK_TEXT:  
    fffff880`02bbb0b8 fffff800`02d52b91 : 00000000`00000050 ffffffff`8166bd08 00000000`00000000 fffff880`02bbb220 : nt!KeBugCheckEx
    fffff880`02bbb0c0 fffff800`02cd2fee : 00000000`00000000 ffffffff`ffffffff 0000000f`ffffff00 fffff800`02d07b9e : nt! ?? ::FNODOBFM::`string'+0x40f5b
    fffff880`02bbb220 fffff800`02cf4e60 : 00000000`00000000 fffff800`02f7d201 ffffe1ce`0849424d 00000001`00000410 : nt!KiPageFault+0x16e
    fffff880`02bbb3b0 fffff880`042f107f : fffffa80`057cd710 00000000`00000000 00000000`00000001 ffffffff`8166bd08 : nt!MmProbeAndLockPages+0x130
    fffff880`02bbb4c0 fffffa80`057cd710 : 00000000`00000000 00000000`00000001 ffffffff`8166bd08 00000000`00000000 : MAudioDelta+0x207f
    fffff880`02bbb4c8 00000000`00000000 : 00000000`00000001 ffffffff`8166bd08 00000000`00000000 fffffa80`05716001 : 0xfffffa80`057cd710
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    MAudioDelta+207f
    fffff880`042f107f ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  MAudioDelta+207f
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: MAudioDelta
    
    IMAGE_NAME:  MAudioDelta.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a6e118e
    
    FAILURE_BUCKET_ID:  X64_0x50_MAudioDelta+207f
    
    BUCKET_ID:  X64_0x50_MAudioDelta+207f
    
    Followup: MachineOwner
    ---------
    
    7: kd> lmvm MAudioDelta
    start             end                 module name
    fffff880`042ef000 fffff880`04350000   MAudioDelta T (no symbols)           
        Loaded symbol image file: MAudioDelta.sys
        Image path: \SystemRoot\system32\DRIVERS\MAudioDelta.sys
        Image name: MAudioDelta.sys
        Timestamp:        Mon Jul 27 16:43:58 2009 (4A6E118E)
        CheckSum:         00069621
        ImageSize:        00061000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    
     
  3. Jainternet12345

    Jainternet12345 TS Rookie Topic Starter

    Thanks a lot for the quick reply:)
    As i suspected it was the M-audio driver. I have the lastest drivers, but now i know that i can contact M-audio and ask them for more help.
    Thanks again!
     
  4. webscaper

    webscaper TS Rookie Posts: 51

    The timestamp on your driver is July 27,2009:

    Code:
    Loaded symbol image file: MAudioDelta.sys
        Image path: \SystemRoot\system32\DRIVERS\MAudioDelta.sys
        Image name: MAudioDelta.sys
        Timestamp:        Mon Jul 27 16:43:58 2009 (4A6E118E)
    
    If you are using Vista or Windows 7 a newer driver is on the M-Audio site with a timestamp of November 14, 2009:

    Code:
    Product  	       Date  	             Version  	                 File Name
    Delta Audiophile 2496	11/14/2009	6.0.2_5.10.0.5074	Delta_6.0.2_5.10.0.5074.exe
     
  5. Jainternet12345

    Jainternet12345 TS Rookie Topic Starter

    Hmm...that's strange since the latest driver was installed. I will uninstall the driver and install the new one again to see if that will help.
    Thank you:)
     
  6. Jainternet12345

    Jainternet12345 TS Rookie Topic Starter

    I have now uninstalled and installed the latest M-audio driver for the soundcard. But how can i check what timestamp it has now? I have looked at the device manager, but there it says driverdate: 30/04/2009. Is that the timestamp?
     
  7. webscaper

    webscaper TS Rookie Posts: 51

    From the dump I can see that you are using Windows 7 64 bit. Therefore you should have installed the driver from here: www.m-audio.com/index.php?do=support.drivers&f=1061

    The release date is 11/14/2009. So that does not seem right. The version is 6.0.2_5.10.0.5074 if that makes any difference.

    The driver is in folder c:\windows\system32\drivers\MAudioDelta.sys. You can hover over it with your mouse to get the file information(version and release date).

    Edit:

    There is mention of resolving a shutdown problem.
     
  8. Jainternet12345

    Jainternet12345 TS Rookie Topic Starter

    The bluescreen is back, even after reinstalling the driver and updating the BIOS. I have attached the crash file and the dmp.file.

    M-audio have suggested the following:
    Some suggestions to try are going into BIOS and looking for CPC C-State, and disabling that. Also, try disabling any power management features if your motherboard has them. If you can't locate the CPC C-State, look around and see if there is a C1E state, and Intel EIST. Those should be disabled. Also, if you have HPET as an option, try disabling that.

    IRQ information:
    IRQ 16 Intel(R) ICH10 Family PCI Express Root port 5 - 3a48
    IRQ 16 M-Audio Delta Audiophile
    IRQ 16 Intel(R) 5520/5500/X58 I/O Hub PCI Express root port 1 - 3408
    IRQ 16 Intel(R) 5520/5500/X58 I/O Hub PCI Express root port 2 - 3409
    IRQ 16 Intel(R) 5520/5500/X58 I/O Hub PCI Express root port 3 - 340A
    IRQ 16 Intel(R) 5520/X58 I/O Hub PCI Express root port 5 - 340C
    IRQ 16 Intel(R) 5520/5500/X58 I/O Hub PCI Express root port 7 - 340E
    IRQ 16 Intel(R) ICH10 Family PCI Express Root port 1 - 3A40
    IRQ 16 Standard Dual channel PCI IDE controller
    IRQ 16 Intel(R) 5520/5500/X58 I/O Hub PCI Express root port 9 - 3410
    IRQ 16 Intel(R) ICH10 Family USB Universal Host controller - 3A37

    Can this give you any information about the problem?
     
  9. Jainternet12345

    Jainternet12345 TS Rookie Topic Starter

    Hmmmm...strange. After uninstalling and reinstalling the absolutely latest driver from M-Audio for 64-bit Windows i check the driver at c:\windows\system32\drivers\MAudioDelta.sys, and the date on it is 07/27/2009! Even though the releasedate for the new driver is 11/14/2009....
     
  10. Jainternet12345

    Jainternet12345 TS Rookie Topic Starter

    forgot the new attachments....
     

    Attached Files:

  11. webscaper

    webscaper TS Rookie Posts: 51

    So you have the new driver installed?

    Have you had this problem with Cubase 5 from day 1? I am not familiar with that software. Sometimes reinstalling the software will correct the problem.

    Did you have the problem with Vista or any other Windows OS? If not it could be that
    the hardware is not compatible with Windows 7. Try running the Windows 7 Upgrade advisor: http://www.microsoft.com/downloads/...90-7659-4BD9-9E51-2497C146AF15&displaylang=en.

    Edit:

    The dump is the same.

    It could be that the software is to blame and the driver is taking the hit. The dump says Probably caused by : MAudioDelta.sys ( MAudioDelta+207f ). So nothing is certain.
     
     
  12. Jainternet12345

    Jainternet12345 TS Rookie Topic Starter

    Yes, the new driver is now installed.
    I have had the problem the whole time. I know that Cubase is fully compatible with Windows 7, and the hardware should be as well.

    I will continue talking to the guys at M-Audio and hopefully they can tell me exactly what the problem is.
     
  13. Jainternet12345

    Jainternet12345 TS Rookie Topic Starter

    I have now gotten the BSOD when starting/loading Cubase. I have attached two dmp.files, one that describes a crash when starting Cubase, and one that describes the crash when closing Cubase.
    Maybe someone can take a look and see if it is still the M-Audio driver that causes the crashes at different times?
     

    Attached Files:

    • dmp.zip
      File size:
      41.5 KB
      Views:
      3
  14. webscaper

    webscaper TS Rookie Posts: 51

    What is interesting about the dump is that it could not pinpoint the faulty driver exactly. It blamed the M-Audio driver because it was nearest to the scene of the crime. The actual exception occurred in a kernel thread because it was passed corrupted data. The driver called the thread directly before the exception occurred.

    The process running at the time was Cubase5 and appears in the dump as such.

    It is possible that Cubase5 caused the chain of events that caused the exception to ultimately occur in a kernel thread (kernel threads are generally excepted as stable).

    It is also possible the M-Audio driver is solely responsible for the corruption which brought down the kernel thread.

    There is no way to be 100% certain with the data from the dump.

    I would suggest re-seating and reinstalling the card as you did on day one with the original software and try again. If you continue to have the problem update the driver to the most current available.

    If still no luck reinstall and update the cubase software.

    You could also try a different card. Sometimes software from one company is not compatible with hardware of another company.
     
  15. Jainternet12345

    Jainternet12345 TS Rookie Topic Starter

    I now got a bluescreen when changing the buffer size on the M-Audio Delta Control Panel while Cubase was running. Does this give you any new information?
     

    Attached Files:

  16. webscaper

    webscaper TS Rookie Posts: 51

    This one doesn't show any trace of Cubase5. The exception occurred in the M-Audio driver unlike the other ones that occurred in a nt(kernel) thread.

    It looks like the M-audio driver is at fault but you can't be 100% sure.

    The driver is not a signed driver because Microsoft has no symbols for it. Meaning that Microsoft hasn't done any extensive testing with it.


    Code:
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\webscaper\AppData\Local\Temp\Rar$DI00.957\042010-17031-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c5e000 PsLoadedModuleList = 0xfffff800`02e9be50
    Debug session time: Tue Apr 20 09:16:09.730 2010 (UTC - 4:00)
    System Uptime: 0 days 2:31:35.808
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {fffff88000a03000, 2, 0, fffff88004f788f0}
    
    Unable to load image \SystemRoot\system32\DRIVERS\MAudioDelta.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MAudioDelta.sys
    *** ERROR: Module load completed but symbols could not be loaded for MAudioDelta.sys
    Probably caused by : MAudioDelta.sys ( MAudioDelta+128f0 )
    
    Followup: MachineOwner
    ---------
    
    6: 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: fffff88000a03000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88004f788f0, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f060e0
     fffff88000a03000 
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    MAudioDelta+128f0
    fffff880`04f788f0 8b01            mov     eax,dword ptr [rcx]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800313b850 -- (.trap 0xfffff8800313b850)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff88000a03000
    rdx=0000000000000050 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88004f788f0 rsp=fffff8800313b9e0 rbp=0000000000000009
     r8=fffff88005b68380  r9=0000000000000000 r10=fffff88005b64000
    r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po nc
    MAudioDelta+0x128f0:
    fffff880`04f788f0 8b01            mov     eax,dword ptr [rcx] ds:fffff880`00a03000=????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff80002ccf469 to fffff80002ccff00
    
    STACK_TEXT:  
    fffff880`0313b708 fffff800`02ccf469 : 00000000`0000000a fffff880`00a03000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0313b710 fffff800`02cce0e0 : fffff800`02cdcbac fffffa80`063a42b0 00000000`00000000 fffff880`0313b8e0 : nt!KiBugCheckDispatch+0x69
    fffff880`0313b850 fffff880`04f788f0 : 00000000`00000022 00000000`00000000 fffffa80`06643500 fffff880`04fbc348 : nt!KiPageFault+0x260
    fffff880`0313b9e0 00000000`00000022 : 00000000`00000000 fffffa80`06643500 fffff880`04fbc348 00000000`00000000 : MAudioDelta+0x128f0
    fffff880`0313b9e8 00000000`00000000 : fffffa80`06643500 fffff880`04fbc348 00000000`00000000 00000000`00000004 : 0x22
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    MAudioDelta+128f0
    fffff880`04f788f0 8b01            mov     eax,dword ptr [rcx]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  MAudioDelta+128f0
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: MAudioDelta
    
    IMAGE_NAME:  MAudioDelta.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a6e118e
    
    FAILURE_BUCKET_ID:  X64_0xD1_MAudioDelta+128f0
    
    BUCKET_ID:  X64_0xD1_MAudioDelta+128f0
    
    Followup: MachineOwner
    ---------
    
    
     
Topic Status:
Not open for further replies.


Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.