BSOD after waking up from sleep.


  1. Posts : 3
    Windows 7 64 bit
       #1

    BSOD after waking up from sleep.


    I have been having a reoccurring issue lately, the problem started shortly after installing both an SSD (Samsung 840 EVO) and a sound card (Asus Xonar DGX). There are times where the computer will wake from sleep correctly, and other times where it will show the BSOD and I will have to restart the computer to log on to Windows. The following is the zip created from the DM Log Collector:

    Attachment 322656

    Thank you!
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi Stannis.

    Can you uninstall the installed version of the driver to your ASUS Xonar DGX Audio Device and install the Version 7.0.8.1821 (earlier than what you have installed but latest as per the official page) from ASUSTeK Computer Inc. -Support- Drivers and Download Xonar DGX ?

    Let us know the situation after doing it. It is important.
    ___________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck D1, {0, 2, 0, fffff88005d17d91}
    
    *** WARNING: Unable to verify timestamp for cmudaxp.sys
    *** ERROR: Module load completed but symbols could not be loaded for cmudaxp.sys
    Probably caused by : cmudaxp.sys ( cmudaxp+2f7d91 )
    
    Followup: MachineOwner
    ---------
    
    0: 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: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88005d17d91, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032f9100
    GetUlongFromAddress: unable to read from fffff800032f91c0
     0000000000000000 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    cmudaxp+2f7d91
    fffff880`05d17d91 488b01          mov     rax,qword ptr [rcx]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0xD1
    
    PROCESS_NAME:  System
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    DPC_STACK_BASE:  FFFFF8000380DFB0
    
    TRAP_FRAME:  fffff800038071f0 -- (.trap 0xfffff800038071f0)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=00000000c0000001 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88005d17d91 rsp=fffff80003807380 rbp=0000000000000000
     r8=0000000000000000  r9=0000000001cf8dac r10=00000000000000b2
    r11=fffffa800ae3a558 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na pe nc
    cmudaxp+0x2f7d91:
    fffff880`05d17d91 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800030c1169 to fffff800030c1bc0
    
    STACK_TEXT:  
    fffff800`038070a8 fffff800`030c1169 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff800`038070b0 fffff800`030bfde0 : fffffa80`0c13f348 00000000`00000001 00000000`00000000 fffffa80`0ae33440 : nt!KiBugCheckDispatch+0x69
    fffff800`038071f0 fffff880`05d17d91 : 00000000`00000000 fffffa80`0b00aca0 00000000`00000180 00000000`00000000 : nt!KiPageFault+0x260
    fffff800`03807380 00000000`00000000 : fffffa80`0b00aca0 00000000`00000180 00000000`00000000 fffffa80`0b00ab80 : cmudaxp+0x2f7d91
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    cmudaxp+2f7d91
    fffff880`05d17d91 488b01          mov     rax,qword ptr [rcx]
    
    SYMBOL_STACK_INDEX:  3
    
    SYMBOL_NAME:  cmudaxp+2f7d91
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: cmudaxp
    
    IMAGE_NAME:  cmudaxp.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51ec89b4
    
    FAILURE_BUCKET_ID:  X64_0xD1_cmudaxp+2f7d91
    
    BUCKET_ID:  X64_0xD1_cmudaxp+2f7d91
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0xd1_cmudaxp+2f7d91
    
    FAILURE_ID_HASH:  {a3a29dfc-eac6-6a08-0369-bcbf00df8243}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm cmudaxp
    start             end                 module name
    fffff880`05a20000 fffff880`05d4e000   cmudaxp  T (no symbols)           
        Loaded symbol image file: cmudaxp.sys
        Image path: \SystemRoot\system32\drivers\cmudaxp.sys
        Image name: cmudaxp.sys
        Timestamp:        Mon Jul 22 06:54:04 2013 (51EC89B4)
        CheckSum:         002A3BAA
        ImageSize:        0032E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 3
    Windows 7 64 bit
    Thread Starter
       #3

    Hi Arc,

    Yes I will do so immediately and see if that fixes the issue. I currently use the UNi Xonar modified drivers for my sound card but will uninstall completely and reinstall the official from Asus. I will keep you updated on the status of my issues, thank you.
      My Computer


  4. Posts : 3
    Windows 7 64 bit
    Thread Starter
       #4

    Update: After a couple of days of NO BSOD I can confirm that using the official Asus drivers for the Xonar DGX have fixed my issues, thank you. I will now mark this thread as solved. Thanks again, Arc.
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    You are welcome mate. :)

    Let us know for any further issue.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 16:02.
Find Us