BSODs on Startup

T


My apologies. I just plain didnt see it. Has H2SO4 made suggestions for you to do?

Ken

Nope

TClarke91 said:

Nope

DID you post this somewhere else? I have already looked at these exact dumps.

the cause is the SD card reader. This file (sdbus.sys) caused it, Both dumps are identical.
You need to find a newer driver to install. To prove it to yourself disable that device in device manager and see if you BSOD then

Ken



Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\102409-35708-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*Symbol information
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`02a61000 PsLoadedModuleList = 0xfffff800`02c9ee50
Debug session time: Sat Oct 24 19:16:03.713 2009 (GMT-4)
System Uptime: 0 days 0:11:26.630
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff880043ee0b8, 2, 8, fffff880043ee0b8}

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: fffff880043ee0b8, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: fffff880043ee0b8, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d090e0
fffff880043ee0b8

CURRENT_IRQL: 2

FAULTING_IP:
sdbus+100b8
fffff880`043ee0b8 ?? ???

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: svchost.exe

TRAP_FRAME: fffff80003fcf600 -- (.trap 0xfffff80003fcf600)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000200 rbx=0000000000000000 rcx=fffffa800596b168
rdx=fffffa800596b0f0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880043ee0b8 rsp=fffff80003fcf798 rbp=0000000000000001
r8=00000000f4fda103 r9=0000000001ca54ff r10=fffff80002a61000
r11=fffff80003fcf7e0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
<Unloaded_sdbus.sys>+0x100b8:
fffff880`043ee0b8 ?? ???
Resetting default scope

IP_MODULE_UNLOADED:
sdbus+100b8
fffff880`043ee0b8 ?? ???

LAST_CONTROL_TRANSFER: from fffff80002ad2469 to fffff80002ad2f00

FAILED_INSTRUCTION_ADDRESS:
sdbus+100b8
fffff880`043ee0b8 ?? ???

STACK_TEXT:
fffff800`03fcf4b8 fffff800`02ad2469 : 00000000`0000000a fffff880`043ee0b8 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff800`03fcf4c0 fffff800`02ad10e0 : fffffa80`0548a1a0 fffff800`03fcf830 fffffa80`04b0adb8 fffff880`01682730 : nt!KiBugCheckDispatch+0x69
fffff800`03fcf600 fffff880`043ee0b8 : fffff800`02adefa6 00000000`00000000 fffffa80`05d808f0 00000000`00000000 : nt!KiPageFault+0x260
fffff800`03fcf798 fffff800`02adefa6 : 00000000`00000000 fffffa80`05d808f0 00000000`00000000 00000000`00000000 : <Unloaded_sdbus.sys>+0x100b8
fffff800`03fcf7a0 fffff800`02ade326 : fffffa80`0621f350 fffffa80`0621f350 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`03fcf810 fffff800`02adee7e : 00000001`99436f2e fffff800`03fcfe88 00000000`0000abee fffff800`02c50048 : nt!KiProcessExpiredTimerList+0xc6
fffff800`03fcfe60 fffff800`02ade697 : fffff800`02c4bec3 fffffa80`0000abee fffffa80`05656f90 00000000`000000ee : nt!KiTimerExpiration+0x1be
fffff800`03fcff00 fffff800`02ad9065 : 00000000`00000000 fffffa80`0669d060 00000000`00000000 fffff880`0144a0c0 : nt!KiRetireDpcList+0x277
fffff800`03fcffb0 fffff800`02ad8e7c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
fffff880`0297e230 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND: kb

FOLLOWUP_IP:
sdbus+100b8
fffff880`043ee0b8 ?? ???

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
---------

Awesome. I'm updating the drivers now. Thanks!

That didn't work.. I did another installation of Windows and I'm gonna upload the new memory dump. This was the error that crippled my system before.

Here's the new dmp file:

tp://rapidshare.com/files/297811818/MEMORYTClarke91.rar.html

Hopefully it can be solved once and for all!

TClarke91 said:

Awesome. I'm updating the drivers now. Thanks!

My pleasure

BTW just as a precaution. run a system file checker to do that
start>search>cmd>right click and run as admin> sfc /scannow


let us now how it turns out

Ken

i tried to use the toshiba software installer to try to get my drivers, but that failed, so I have to reinstall windows before scanning.. Can you read the second dump file I posted while I reinstall windows? Thanks

i tried to use the toshiba software installer to try to get my drivers, but that failed, so I have to reinstall windows before scanning.. Can you read the second dump file I posted while I reinstall windows? Thanks

and I did that scan, and it says Windows Resource Protection did not find any integrity violations.