BSOD (0x0000000a) with driver verifier - looking for some confirmation


  1. Posts : 3
    windows 7
       #1

    BSOD (0x0000000a) with driver verifier - looking for some confirmation


    Hello, while working one evening I got my first BSOD on this machine, so I enabled driver verifier and have been getting an 0x0000000a on start up infrequently.

    I'm assuming this is going to have something to do with the drivers for my mobo, as I ended up grabbing a lot of Intel Smart connect and crap. I've been updating/uninstalling unnecessary drivers, but I'm no good at analyzing dumps, so could anyone help point me in the right direction here?
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck A, {0, 2, 0, fffff8000327d315}
    
    *** WARNING: Unable to verify timestamp for MBfilt64.sys
    *** ERROR: Module load completed but symbols could not be loaded for MBfilt64.sys
    Probably caused by : MBfilt64.sys ( MBfilt64+1817 )
    
    Followup: MachineOwner
    ---------
    
    4: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    IRQL_NOT_LESS_OR_EQUAL (a)
    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 a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 0000000000000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, bitfield :
    	bit 0 : value 0 = read operation, 1 = write operation
    	bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: fffff8000327d315, address which referenced memory
    
    Debugging Details:
    ------------------
    
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800034b0100
    GetUlongFromAddress: unable to read from fffff800034b01c0
     0000000000000000 Nonpaged pool
    
    CURRENT_IRQL:  2
    
    FAULTING_IP: 
    nt!KeSetEvent+1e3
    fffff800`0327d315 488b00          mov     rax,qword ptr [rax]
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
    
    BUGCHECK_STR:  0xA
    
    PROCESS_NAME:  System
    
    TRAP_FRAME:  fffff8800374e950 -- (.trap 0xfffff8800374e950)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=fffff880029c9210
    rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8000327d315 rsp=fffff8800374eae0 rbp=0000000000000000
     r8=0000000000000000  r9=fffff880009b3180 r10=0000000000000000
    r11=fffff80003430260 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl nz na po cy
    nt!KeSetEvent+0x1e3:
    fffff800`0327d315 488b00          mov     rax,qword ptr [rax] ds:00000000`00000000=????????????????
    Resetting default scope
    
    LAST_CONTROL_TRANSFER:  from fffff800032781a9 to fffff80003278c00
    
    STACK_TEXT:  
    fffff880`0374e808 fffff800`032781a9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0374e810 fffff800`03276e20 : 00000000`00000160 00000000`00000000 00000000`0000000d fffff880`029c9208 : nt!KiBugCheckDispatch+0x69
    fffff880`0374e950 fffff800`0327d315 : fffffa80`07f53702 fffffa80`07f53710 00000000`00000000 fffff980`07a94ea0 : nt!KiPageFault+0x260
    fffff880`0374eae0 fffff880`07119817 : fffff880`00000000 fffff980`00000008 fffff800`03426d00 fffffa80`0ac29f50 : nt!KeSetEvent+0x1e3
    fffff880`0374eb50 fffff880`00000000 : fffff980`00000008 fffff800`03426d00 fffffa80`0ac29f50 fffffa80`07f53710 : MBfilt64+0x1817
    fffff880`0374eb58 fffff980`00000008 : fffff800`03426d00 fffffa80`0ac29f50 fffffa80`07f53710 fffff800`037213fb : 0xfffff880`00000000
    fffff880`0374eb60 fffff800`03426d00 : fffffa80`0ac29f50 fffffa80`07f53710 fffff800`037213fb fffffa80`07f53710 : 0xfffff980`00000008
    fffff880`0374eb68 fffffa80`0ac29f50 : fffffa80`07f53710 fffff800`037213fb fffffa80`07f53710 fffffa80`07f53710 : nt!ViPendingWorkers
    fffff880`0374eb70 fffffa80`07f53710 : fffff800`037213fb fffffa80`07f53710 fffffa80`07f53710 fffff980`07a95000 : 0xfffffa80`0ac29f50
    fffff880`0374eb78 fffff800`037213fb : fffffa80`07f53710 fffffa80`07f53710 fffff980`07a95000 fffff980`07a94ea0 : 0xfffffa80`07f53710
    fffff880`0374eb80 fffff800`0372147c : fffff800`03426dc0 00000000`00000080 fffffa80`069eb740 a12b7da2`00000100 : nt!ViPendingCompleteAfterWait+0x7b
    fffff880`0374ebc0 fffff800`03516ede : e2f595ea`ea63e22b c1c37f08`c4081bfe f2a80f45`b6e003ab 90800f0f`13225ab9 : nt!ViPendingWorkerThread+0x2c
    fffff880`0374ec00 fffff800`03269906 : fffff880`009b3180 fffffa80`07642660 fffff880`009be0c0 85409b15`69f0fec9 : nt!PspSystemThreadStartup+0x5a
    fffff880`0374ec40 00000000`00000000 : fffff880`0374f000 fffff880`03749000 fffff880`0374e8d0 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    MBfilt64+1817
    fffff880`07119817 ??              ???
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  MBfilt64+1817
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: MBfilt64
    
    IMAGE_NAME:  MBfilt64.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4a7267b0
    
    FAILURE_BUCKET_ID:  X64_0xA_VRF_MBfilt64+1817
    
    BUCKET_ID:  X64_0xA_VRF_MBfilt64+1817
    
    Followup: MachineOwner
    ---------
    
    4: kd> lmvm MBfilt64
    start             end                 module name
    fffff880`07118000 fffff880`07126000   MBfilt64 T (no symbols)           
        Loaded symbol image file: MBfilt64.sys
        Image path: \SystemRoot\system32\drivers\MBfilt64.sys
        Image name: MBfilt64.sys
        Timestamp:        Fri Jul 31 09:40:32 2009 (4A7267B0)
        CheckSum:         0000FF02
        ImageSize:        0000E000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Caused by Driver Description: Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver)
    Update to latest version available, disable verifier and let us know if the bsods continue.

    And if you get them again, grab all files following the Blue Screen of Death (BSOD) Posting Instructions
      My Computer


  3. Posts : 3
    windows 7
    Thread Starter
       #3

    koolkat77 said:
    Caused by Driver Description: Realtek HiDefinition Audio driver (file labelled as Creative Audio Driver)Update to latest version available, disable verifier and let us know if the bsods continue.

    And if you get them again, grab all files following the Blue Screen of Death (BSOD) Posting Instructions

    Thank you, much appreciated.

    My driver version appears to be up to date with the manufacturer -- their site lists 6559 as the latest version (ASRock > Z77 Extreme6)

    But I will try R2.71 from realtek. Disabling verifier now, fingers crossed, will keep you posted
      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 05:01.
Find Us