Probably caused by : sdbus.sys ( sdbus+d124 ) Co to oznacza?


(Lepperpl) #1

Microsoft ® Windows Debugger Version 6.6.0003.5

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:symbols*http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx#d

Executable search path is:

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Windows Vista Kernel Version 7600 MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7600.16385.x86fre.win7_rtm.090713-1255

Kernel base = 0x82806000 PsLoadedModuleList = 0x8294e810

Debug session time: Fri Oct 30 21:09:45.465 2009 (GMT+1)

System Uptime: 0 days 0:00:59.539

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 2

*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe

Loading Kernel Symbols

.....................................................................................................................................................

Loading User Symbols

Loading unloaded module list

.......

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8fda9124, 2, 8, 8fda9124}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

*************************************************************************

Probably caused by : sdbus.sys ( sdbus+d124 )

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: 8fda9124, memory referenced

Arg2: 00000002, IRQL

Arg3: 00000008, value 0 = read operation, 1 = write operation

Arg4: 8fda9124, address which referenced memory

Debugging Details:


***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************

*** ***

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

*************************************************************************

MODULE_NAME: sdbus

FAULTING_MODULE: 82806000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get nt!MmPoolCodeStart

unable to get nt!MmPoolCodeEnd

8fda9124

CURRENT_IRQL: 2

FAULTING_IP:

sdbus+d124

8fda9124 ?

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_BETA2

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 8fda9124 to 8284c7eb

STACK_TEXT:

WARNING: Stack unwind information not available. Following frames may be wrong.

8292cac8 8fda9124 badb0d00 02000000 8701e030 nt+0x467eb

8292cb7c 8286fff1 8292fd20 8292cca8 00000003 +0xd124

8292cc68 8286feae 8292fd20 8292cca8 00000000 nt+0x69ff1

8292ccdc 8286e20e 00000ee8 84fc8d48 82939280 nt+0x69eae

8292cd20 8286e038 00000000 0000000e 00000000 nt+0x6820e

84f46d40 00000000 84f46d48 84f46d48 84f46d50 nt+0x68038

STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:

sdbus+d124

8fda9124 ?

FAULTING_SOURCE_CODE:

SYMBOL_STACK_INDEX: 1

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: sdbus+d124

IMAGE_NAME: sdbus.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner


(p@wel) #2

Karta SD...


(Semtex) #3

Jeżeli to przez czytnik kart SD,to zapoznaj się z tym artykułem,zainstaluj łatkę,która jest tam podlinkowana i sprawdź czy wszystko gra.


(Lepperpl) #4

OK:) Wielkie dzięki:)

Sciągnąlem odpowiednie sterowniki do tej karty SD i działa:)