Getting BSOD

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by levi, Mar 18, 2010.

  1. levi

    levi New Member

    Joined:
    Mar 18, 2010
    Messages:
    6
    Likes Received:
    0
    Hi, everyone. I'm new here and recently started a thread in Portuguese, how naive. I'm gonna simplify things out by posting in English right now.
    So, I'm getting a random Blue Screen, it happened 7 times so far and I couldn't identify the problem. Last time I got this message:

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1046

    Additional information about the problem:
    BCCode: d1
    BCP1: FFFFF880041EB0B8
    BCP2: 0000000000000002
    BCP3: 0000000000000008
    BCP4: FFFFF880041EB0B8
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\031810-61152-01.dmp
    C:\Users\Levi\AppData\Local\Temp\WER-127577-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    The minidump files are attached.
    Thanks for reading or any help.
     

    Attached Files:

  2. Trouble

    Trouble Noob Whisperer

    Joined:
    Nov 30, 2009
    Messages:
    13,845
    Likes Received:
    833
    All your dump files are pointing at the same culprint sdbus.sys check device manager see if you have any hardware issues indicated there. The file is apparently a driver for your secure digital card reader, try google, see if there is a driver update from the computer manufacturer or device manufacturer's website.
    Code:
     
    Loading Dump File [C:\Users\WhoEver\Desktop\New folder\012110-47907-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    Symbol search path is: SRV*c:\symbols*[URL=\"http://msdl.microsoft.com/download/symbols\"]Symbol information[/URL]
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
    Machine Name:
    Kernel base = 0xfffff800`02c07000 PsLoadedModuleList = 0xfffff800`02e44e50
    Debug session time: Thu Jan 21 02:40:21.986 2010 (GMT-5)
    System Uptime: 0 days 5:40:50.906
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    ................
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************
    Use !analyze -v to get detailed debugging information.
    BugCheck D1, {fffff8800455f0b8, 2, 8, fffff8800455f0b8}
    Probably caused by : sdbus.sys ( sdbus+100b8 )
    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: fffff8800455f0b8, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff8800455f0b8, address which referenced memory
    Debugging Details:
    ------------------
     
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eaf0e0
    fffff8800455f0b8 
    CURRENT_IRQL: 2
    FAULTING_IP: 
    sdbus+100b8
    fffff880`0455f0b8 ?? ???
    CUSTOMER_CRASH_COUNT: 1
    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
    BUGCHECK_STR: 0xD1
    PROCESS_NAME: System
    TRAP_FRAME: fffff80000b9c390 -- (.trap 0xfffff80000b9c390)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffffa80069e80f0 rbx=0000000000000000 rcx=fffffa80069e8168
    rdx=fffffa80069e80f0 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8800455f0b8 rsp=fffff80000b9c528 rbp=0000000000000001
    r8=00000000fcadb6a8 r9=0000000001ca9a6c r10=00000000000000e3
    r11=fffffa80069e8168 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei pl zr na po nc
    <Unloaded_sdbus.sys>+0x100b8:
    fffff880`0455f0b8 ?? ???
    Resetting default scope
    IP_MODULE_UNLOADED: 
    sdbus+100b8
    fffff880`0455f0b8 ?? ???
    LAST_CONTROL_TRANSFER: from fffff80002c78469 to fffff80002c78f00
    FAILED_INSTRUCTION_ADDRESS: 
    sdbus+100b8
    fffff880`0455f0b8 ?? ???
    STACK_TEXT: 
    fffff800`00b9c248 fffff800`02c78469 : 00000000`0000000a fffff880`0455f0b8 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
    fffff800`00b9c250 fffff800`02c770e0 : fffff880`009e9180 fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000002 : nt!KiBugCheckDispatch+0x69
    fffff800`00b9c390 fffff880`0455f0b8 : fffff800`02c84fa6 00000000`00000000 fffff800`00b9c5d8 00000000`00000000 : nt!KiPageFault+0x260
    fffff800`00b9c528 fffff800`02c84fa6 : 00000000`00000000 fffff800`00b9c5d8 00000000`00000000 00000000`00000003 : <Unloaded_sdbus.sys>+0x100b8
    fffff800`00b9c530 fffff800`02c84326 : fffffa80`069e8128 00000000`001400e3 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
    fffff800`00b9c5a0 fffff800`02c84e7e : 0000002f`9db0aea0 fffff800`00b9cc18 00000000`001400e3 fffff800`02df5ee8 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cbf0 fffff800`02c84697 : 0000000a`59c308c1 0000000a`001400e3 0000000a`59c308e2 00000000`000000e3 : nt!KiTimerExpiration+0x1be
    fffff800`00b9cc90 fffff800`02c816fa : fffff800`02df1e80 fffff800`02dffc40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
    fffff800`00b9cd40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd00 00000000`00000000 : nt!KiIdleLoop+0x5a
     
    STACK_COMMAND: kb
    FOLLOWUP_IP: 
    sdbus+100b8
    fffff880`0455f0b8 ?? ???
    SYMBOL_STACK_INDEX: 3
    SYMBOL_NAME: sdbus+100b8
    FOLLOWUP_NAME: MachineOwner
    MODULE_NAME: sdbus
    IMAGE_NAME: sdbus.sys
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    FAILURE_BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_sdbus+100b8
    BUCKET_ID: X64_0xD1_CODE_AV_BAD_IP_sdbus+100b8
    Followup: MachineOwner
    ---------
    0: kd> lmvm sdbus
    start end module name
    
     
    levi and (deleted member) like this.
  3. levi

    levi New Member

    Joined:
    Mar 18, 2010
    Messages:
    6
    Likes Received:
    0
    thanks for help! A few months ago I noticed that, in Device Manager, the error on the Mass Storage Controller and couldn't solve this that time. Since the SD cards were working I forgot this issue. I did a search in the forum topics, and looks like I have to install the "Chipset Driver - O2Micro OZH24 SD/MMC Host Controller" from Dell. I'm using a Dell Vostro 1320.
    I'll come back for a response. Thanks again!
     

Share This Page

Loading...