up vote 0 down vote favorite
share [g+] share [fb]

I have a big problem with a Backup Server. During a file share backup i get a bluescreen. Here is the attached dumpfile (i cannot work with it:( i tried the debug tools but i don't understand it)

Microsoft (R) Windows Debugger Version 6.2.8102.0 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [XXX] Mini Kernel Dump File: Only registers and stack trace are available

Invalid directory table base value 0x0 Symbol search path is: * Invalid *

  • Symbol loading may be unreliable without a symbol search path. *
  • Use .symfix to have the debugger choose a symbol path. *
  • After setting your symbol path, use .reload to refresh symbol locations. *

Executable search path is:

  • Symbols can not be loaded because symbol path is not initialized. *
  • *
  • The Symbol Path can be set by: *
  • using the _NT_SYMBOL_PATH environment variable. *
  • using the -y argument when starting the debugger. *
  • using .sympath and .sympath+ *

Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address Windows 7 Kernel Version 7601 (Service Pack 1) MP (12 procs) Free x64 Product: Server, suite: TerminalServer SingleUserTS Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506 Machine Name: Kernel base = 0xfffff80002408000 PsLoadedModuleList = 0xfffff800`0264d670 Debug session time: Mon Jan 30 10:35:40.867 2012 (UTC + 1:00) System Uptime: 3 days 17:50:58.534

  • Symbols can not be loaded because symbol path is not initialized. *
  • *
  • The Symbol Path can be set by: *
  • using the _NT_SYMBOL_PATH environment variable. *
  • using the -y argument when starting the debugger. *
  • using .sympath and .sympath+ *

Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000 WARNING: .reload failed, module list may be incomplete Debugger can not determine kernel base address Loading Kernel Symbols .Unable to load image Unknown_Module_0000000000000000, Win32 error 0n2 * WARNING: Unable to verify timestamp for Unknown_Module_0000000000000000 Unable to add module at 0000000000000000

Loading User Symbols TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\triage\oca.ini, error 2 TRIAGER: Could not open triage file : C:\Program Files\Windows Kits\8.0\Debuggers\x64\winxp\triage.ini, error 2

  • *
  • Bugcheck Analysis *
  • *

Use !analyze -v to get detailed debugging information.

BugCheck 40, {fffffa80164ca000, fffffa80164b9000, fffff88008801d28, 4cf048}

* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

0: kd> !analyze -v

  • *
  • Bugcheck Analysis *
  • *

TARGET_MDL_TOO_SMALL (40) A driver has called the IoBuildPartialMdl() function and passed it an MDL to map part of a source MDL, but the target MDL is not large enough to map the entire range of addresses requested. This is a driver bug. The source and target MDLs, as well as the address range length to be mapped are the arguments to the IoBuildPartialMdl() function, i.e.; IoBuildPartialMdl( IN PMDL SourceMdl, IN OUT PMDL TargetMdl, IN PVOID VirtualAddress, IN ULONG Length ) Arguments: Arg1: fffffa80164ca000 Arg2: fffffa80164b9000 Arg3: fffff88008801d28 Arg4: 00000000004cf048

Debugging Details:

* Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT_SERVER

BUGCHECK_STR: 0x40

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800024daaad to fffff80002484c40

STACK_TEXT:
fffff80002298d08 fffff800024daaad : 0000000000000040 fffffa80164ca000 fffffa80164b9000 fffff88008801d28 : 0xfffff80002484c40 fffff80002298d10 0000000000000040 : fffffa80164ca000 fffffa80164b9000 fffff88008801d28 00000000004cf048 : 0xfffff800024daaad fffff80002298d18 fffffa80164ca000 : fffffa80164b9000 fffff88008801d28 00000000004cf048 0000000000000fb8 : 0x40 fffff80002298d20 fffffa80164b9000 : fffff88008801d28 00000000004cf048 0000000000000fb8 fffffa80164ca000 : 0xfffffa80164ca000 fffff80002298d28 fffff88008801d28 : 00000000004cf048 0000000000000fb8 fffffa80164ca000 fffff88005934e54 : 0xfffffa80164b9000 fffff80002298d30 00000000004cf048 : 0000000000000fb8 fffffa80164ca000 fffff88005934e54 fffffa8018ddbac0 : 0xfffff88008801d28 fffff80002298d38 0000000000000fb8 : fffffa80164ca000 fffff88005934e54 fffffa8018ddbac0 fffffa8018ddb9a0 : 0x4cf048 fffff80002298d40 fffffa80164ca000 : fffff88005934e54 fffffa8018ddbac0 fffffa8018ddb9a0 0000000000000000 : 0xfb8 fffff80002298d48 fffff88005934e54 : fffffa8018ddbac0 fffffa8018ddb9a0 0000000000000000 fffff80002298da8 : 0xfffffa80164ca000 fffff80002298d50 fffffa8018ddbac0 : fffffa8018ddb9a0 0000000000000000 fffff80002298da8 fffffa8017af9730 : 0xfffff88005934e54 fffff80002298d58 fffffa8018ddb9a0 : 0000000000000000 fffff80002298da8 fffffa8017af9730 fffff80002298db0 : 0xfffffa8018ddbac0 fffff80002298d60 0000000000000000 : fffff80002298da8 fffffa8017af9730 fffff80002298db0 fffff80002298db8 : 0xfffffa80`18ddb9a0

STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

Followup: MachineOwner

Blockquote

I know that it is a network problem but i need to know which driver is the source of the problem!

link|improve this question
feedback

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
or
required, but never shown
discard

Browse other questions tagged or ask your own question.