BSOD Waking up from Sleep

[Baba]

Installed Windows 7 Professional x64 today on my HP laptop with ATI Radeon 3400 series graphics and an AMD Turion X2 Ultra 2.10 GHz.

I tried searching for a solution but couldnt find one. I saw one thread about it but no help. I just always get a BSOD when waking from sleep mode, usually right after I try to log back in.


MINIDUMPS:
http://dl.getdropbox.com/u/391553/minidump.zip

if you figure out the problem, can i have a step by step procedure to fix it, not just the cause.

 

[H2SO4]

Curious.

Does the same crash occur irrespective of whether or not you've got an SD card in the laptop's inbuilt SD reader at the point where you send it to sleep and wake it back up?

 

[Baba]

there is nothing in the SD Card Reader. I have never used it. That's really odd lol.

 

[H2SO4]

there is nothing in the SD Card Reader. I have never used it. That's really odd lol.

Do me a favour - whack an SD card in there and test what happens when the machine resumes from sleep. I'd be interested to see the minidump from that crash.

 

[Baba]

um. lol......it didnt crash this time WITH the SD Card in. again...odd.

*EDIT**
i tried it again without the sd card so here's another minidump if it helps:
http://dl.getdropbox.com/u/391553/minidump2.zip

is there a way i can disable the SD Reader or will i have to keep a SD card in all the time?

 

[H2SO4]

um. lol......it didnt crash this time WITH the SD Card in. again...odd.

*EDIT**
i tried it again without the sd card so here's another minidump if it helps:
http://dl.getdropbox.com/u/391553/minidump2.zip

is there a way i can disable the SD Reader or will i have to keep a SD card in all the time?

Is the pattern consistent - it crashes without an SD card but it's fine of there's a card in the reader?

 

[usasma]

Interesting that each crash is blamed on SDBus.sys (SecureDigital Bus Driver from Microsoft)
Also, this driver is outdated: AtiPcie.sys Mon Nov 06 11:59:54 2006 I'd suggest updating it ASAP as it's responsible for some lower level functions on your motherboard.

I wonder if there's a security feature that wasn't installed when Windows 7 was installed? Have you run SFC.EXE /SCANNOW and have you checked Device Manager for unknown/unidentified/malfunctioning devices?

 

[Baba]

Is the pattern consistent - it crashes without an SD card but it's fine of there's a card in the reader?

Yes, the pattern is consistent. Every time WITHOUT the SD Card it crashes, and never crashes WITH an SD Card.

I just disabled the SD Reader's driver so now it doesnt crash anymore. I guess if the problem isnt solved, I'll just enable it if i ever need it but keep it shut off most of the time.

Interesting that each crash is blamed on SDBus.sys (SecureDigital Bus Driver from Microsoft)
Also, this driver is outdated: AtiPcie.sys Mon Nov 06 11:59:54 2006 I'd suggest updating it ASAP as it's responsible for some lower level functions on your motherboard.

I wonder if there's a security feature that wasn't installed when Windows 7 was installed? Have you run SFC.EXE /SCANNOW and have you checked Device Manager for unknown/unidentified/malfunctioning devices?

Ok, i just updated the ATI graphics driver (which im guessing thats what the Atipcie.sys thingamabob was). I have no idea if there was anything not installed during the Windows 7 installation. And i have no idea what SFC.EXE is. I tried running it but i only saw a quick flash of a command prompt screen. So I dunno.

 

[H2SO4]

Is the pattern consistent - it crashes without an SD card but it's fine of there's a card in the reader?

Yes, the pattern is consistent. Every time WITHOUT the SD Card it crashes, and never crashes WITH an SD Card.

Very interesting. I think your laptop's SD reader/controller may be subtly broken. It is indicating the presence of an SD card even when nothing's there, and then going "who? me? Naaah" in response to being asked to do something about it. With the card in the drive, it indicates presence, but is then able to handle it properly, hence the lack of a crash.

I just disabled the SD Reader's driver so now it doesnt crash anymore. I guess if the problem isnt solved, I'll just enable it if i ever need it but keep it shut off most of the time.

Probably a viable workaround, especially if you never use it

It's possible that a (future) BIOS update may help to resolve the problem completely.

 

[Baba]

ok cool. thanks a lot for finding the problem. and updating my graphics card helped me with another problem, since i thought i already updated it.

thanks!!

 

[zigzag3143]

Installed Windows 7 Professional x64 today on my HP laptop with ATI Radeon 3400 series graphics and an AMD Turion X2 Ultra 2.10 GHz.

I tried searching for a solution but couldnt find one. I saw one thread about it but no help. I just always get a BSOD when waking from sleep mode, usually right after I try to log back in.


MINIDUMPS:
http://dl.getdropbox.com/u/391553/minidump.zip

if you figure out the problem, can i have a step by step procedure to fix it, not just the cause.

Baba

This is probably the most obvious dump I have ever seen. Caused by your SD card reader. SDbus.sys. It may not even be compatible with win 7.

Suggestions: uninstall driver and update it. If you want to confirm it just disable the driver and see if you get a BSOD

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