crash when i shutdown system

can you help me please:
WinDbg does not hold myself out the line of my source code and pdb is loaded.
Machine crash when i shutdown system.

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

Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: C:\source\sivaller\vfums\v0.1\sys\vfums\obj\chk\i386;C:\source\sivaller\vfums\v0.1\sys\vfums\debug
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0
Debug session time: Wed Sep 8 21:14:53.968 2010 (GMT+2)
System Uptime: 0 days 0:04:58.765
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols


Loading User Symbols

Loading unloaded module list

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, 804daed1, f545cbd0, f545c8cc}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : vfums.sys ( vfums+2fe4 )

Followup: MachineOwner

*** ERROR: Symbol file could not be found. Defaulted to export symbols for halmacpi.dll -
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.sys
*** WARNING: Unable to verify timestamp for vmx_fb.dll
*** ERROR: Module load completed but symbols could not be loaded for vmx_fb.dll
*** ERROR: Module load completed but symbols could not be loaded for HTTP.sys
*** ERROR: Module load completed but symbols could not be loaded for srv.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxdav.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisuio.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for ipnat.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for rdbss.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for truecrypt.sys -
*** ERROR: Module load completed but symbols could not be loaded for vmhgfs.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for tcpip.sys -
*** ERROR: Module load completed but symbols could not be loaded for ipsec.sys
*** ERROR: Module load completed but symbols could not be loaded for update.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for Dxapi.sys -
*** ERROR: Module load completed but symbols could not be loaded for rdpdr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for psched.sys -
*** ERROR: Module load completed but symbols could not be loaded for ndiswan.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for VIDEOPRT.SYS -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ks.sys -
*** ERROR: Module load completed but symbols could not be loaded for serial.sys
*** ERROR: Module load completed but symbols could not be loaded for parport.sys
*** ERROR: Module load completed but symbols could not be loaded for ws2ifsl.sys
*** ERROR: Module load completed but symbols could not be loaded for Mup.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for NDIS.sys -
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for KSecDD.sys -
*** ERROR: Module load completed but symbols could not be loaded for sr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltMgr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for SCSIPORT.SYS -
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for dmio.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdisk.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for DSFOleaut32.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dsfksvcs.sys -
*** ERROR: Module load completed but symbols could not be loaded for isapnp.sys
*** ERROR: Module load completed but symbols could not be loaded for MountMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for VolSnap.sys
*** ERROR: Module load completed but symbols could not be loaded for disk.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for CLASSPNP.SYS -
*** ERROR: Module load completed but symbols could not be loaded for agp440.sys
*** ERROR: Module load completed but symbols could not be loaded for i8042prt.sys
*** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
*** ERROR: Module load completed but symbols could not be loaded for redbook.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for vmci.sys -
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for rasl2tp.sys
*** ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
*** ERROR: Module load completed but symbols could not be loaded for raspptp.sys
*** ERROR: Module load completed but symbols could not be loaded for msgpc.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for termdd.sys -
*** ERROR: Module load completed but symbols could not be loaded for NDProxy.SYS
*** ERROR: Module load completed but symbols could not be loaded for netbios.sys
*** ERROR: Module load completed but symbols could not be loaded for Fips.SYS
*** ERROR: Module load completed but symbols could not be loaded for wanarp.sys
*** ERROR: Module load completed but symbols could not be loaded for Cdfs.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for PCIIDEX.SYS -
*** ERROR: Module load completed but symbols could not be loaded for PartMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for dsfroot.sys
*** ERROR: Module load completed but symbols could not be loaded for kbdclass.sys
*** ERROR: Module load completed but symbols could not be loaded for mouclass.sys
*** ERROR: Module load completed but symbols could not be loaded for fdc.sys
*** ERROR: Module load completed but symbols could not be loaded for vmx_svga.sys
*** ERROR: Module load completed but symbols could not be loaded for vmxnet.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for TDI.SYS -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ptilink.sys -
*** ERROR: Module load completed but symbols could not be loaded for raspti.sys
*** ERROR: Module load completed but symbols could not be loaded for flpydisk.sys
*** ERROR: Module load completed but symbols could not be loaded for vga.sys
*** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for watchdog.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for BOOTVID.dll -
*** ERROR: Module load completed but symbols could not be loaded for compbatt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for BATTC.SYS -
*** ERROR: Module load completed but symbols could not be loaded for vmscsi.sys
*** ERROR: Module load completed but symbols could not be loaded for serenum.sys
*** ERROR: Module load completed but symbols could not be loaded for CmBatt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ndistapi.sys -
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for rasacd.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for kdcom.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for WMILIB.SYS -
*** ERROR: Module load completed but symbols could not be loaded for intelide.sys
*** ERROR: Module load completed but symbols could not be loaded for dmload.sys
*** ERROR: Module load completed but symbols could not be loaded for vmmouse.sys
*** ERROR: Module load completed but symbols could not be loaded for swenum.sys
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.SYS
*** ERROR: Module load completed but symbols could not be loaded for Beep.SYS
*** ERROR: Module load completed but symbols could not be loaded for mnmdd.SYS
*** ERROR: Module load completed but symbols could not be loaded for RDPCDD.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dump_WMILIB.SYS -
*** ERROR: Module load completed but symbols could not be loaded for ParVdm.SYS
*** ERROR: Module load completed but symbols could not be loaded for vmmemctl.sys
*** ERROR: Module load completed but symbols could not be loaded for audstub.sys
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgthk.sys -
*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804daed1, The address that the exception occurred at
Arg3: f545cbd0, Exception Record Address
Arg4: f545c8cc, Context Record Address

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

ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to set symbol path and load symbols.

MODULE_NAME: vfums

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c87e045

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L’instruction “0x%08lx” emploie l’adresse m moire “0x%08lx”. La m moire ne peut pas tre “%s”.

FAULTING_IP:
nt!memcpy+33
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

EXCEPTION_RECORD: f545cbd0 – (.exr 0xfffffffff545cbd0)
ExceptionAddress: 804daed1 (nt!memcpy+0x00000033)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000160
Attempt to read from address 00000160

CONTEXT: f545c8cc – (.cxr 0xfffffffff545c8cc)
eax=000002c0 ebx=00000000 ecx=00000058 edx=00000000 esi=00000160 edi=f7e80828
eip=804daed1 esp=f545cc98 ebp=f545cca0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!memcpy+0x33:
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f7c23fe4 to 804daed1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f545cca0 f7c23fe4 f7e80828 00000160 00000160 nt!memcpy+0x33
f545cd30 f7c24265 81995300 81e85c28 81e85c98 vfums+0x2fe4
f545cd60 f7c2484b 81995300 81e85c28 81e85c98 vfums+0x3265
f545cdac 80576b24 81995300 00000000 00000000 vfums+0x384b
f545cddc 804eed86 f7c24730 81995300 00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb

FOLLOWUP_IP:
vfums+2fe4
f7c23fe4 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: vfums+2fe4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: vfums.sys

STACK_COMMAND: .cxr 0xfffffffff545c8cc ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804daed1, The address that the exception occurred at
Arg3: f545cbd0, Exception Record Address
Arg4: f545c8cc, Context Record Address

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

ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to set symbol path and load symbols.

MODULE_NAME: vfums

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c87e045

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L’instruction “0x%08lx” emploie l’adresse m moire “0x%08lx”. La m moire ne peut pas tre “%s”.

FAULTING_IP:
nt!memcpy+33
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

EXCEPTION_RECORD: f545cbd0 – (.exr 0xfffffffff545cbd0)
ExceptionAddress: 804daed1 (nt!memcpy+0x00000033)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000160
Attempt to read from address 00000160

CONTEXT: f545c8cc – (.cxr 0xfffffffff545c8cc)
eax=000002c0 ebx=00000000 ecx=00000058 edx=00000000 esi=00000160 edi=f7e80828
eip=804daed1 esp=f545cc98 ebp=f545cca0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!memcpy+0x33:
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f7c23fe4 to 804daed1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f545cca0 f7c23fe4 f7e80828 00000160 00000160 nt!memcpy+0x33
f545cd30 f7c24265 81995300 81e85c28 81e85c98 vfums+0x2fe4
f545cd60 f7c2484b 81995300 81e85c28 81e85c98 vfums+0x3265
f545cdac 80576b24 81995300 00000000 00000000 vfums+0x384b
f545cddc 804eed86 f7c24730 81995300 00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb

FOLLOWUP_IP:
vfums+2fe4
f7c23fe4 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: vfums+2fe4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: vfums.sys

STACK_COMMAND: .cxr 0xfffffffff545c8cc ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************

Did you notice all of the many pages of warnings saying that your symbols are incorrect? Please load the correct kernel symbols and try again. (Check out the documentation for .symfix in the debugger help.)

  • S

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@sivaller.no-ip.org
Sent: Sunday, September 12, 2010 11:46 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] crash when i shutdown system

can you help me please:
WinDbg does not hold myself out the line of my source code and pdb is loaded.
Machine crash when i shutdown system.

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

Loading Dump File [C:\WINDOWS\MEMORY.DMP] Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: C:\source\sivaller\vfums\v0.1\sys\vfums\obj\chk\i386;C:\source\sivaller\vfums\v0.1\sys\vfums\debug
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Built by: 2600.xpsp_sp2_rtm.040803-2158 Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0 Debug session time: Wed Sep 8 21:14:53.968 2010 (GMT+2) System Uptime: 0 days 0:04:58.765
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Loading Kernel Symbols …

Loading User Symbols

Loading unloaded module list

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, 804daed1, f545cbd0, f545c8cc}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : vfums.sys ( vfums+2fe4 )

Followup: MachineOwner

*** ERROR: Symbol file could not be found. Defaulted to export symbols for halmacpi.dll -
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.sys
*** WARNING: Unable to verify timestamp for vmx_fb.dll
*** ERROR: Module load completed but symbols could not be loaded for vmx_fb.dll
*** ERROR: Module load completed but symbols could not be loaded for HTTP.sys
*** ERROR: Module load completed but symbols could not be loaded for srv.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxdav.sys
*** ERROR: Module load completed but symbols could not be loaded for ndisuio.sys
*** ERROR: Module load completed but symbols could not be loaded for dump_atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for ipnat.sys
*** ERROR: Module load completed but symbols could not be loaded for mrxsmb.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for rdbss.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for truecrypt.sys -
*** ERROR: Module load completed but symbols could not be loaded for vmhgfs.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for netbt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for tcpip.sys -
*** ERROR: Module load completed but symbols could not be loaded for ipsec.sys
*** ERROR: Module load completed but symbols could not be loaded for update.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for Dxapi.sys -
*** ERROR: Module load completed but symbols could not be loaded for rdpdr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for psched.sys -
*** ERROR: Module load completed but symbols could not be loaded for ndiswan.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for VIDEOPRT.SYS -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ks.sys -
*** ERROR: Module load completed but symbols could not be loaded for serial.sys
*** ERROR: Module load completed but symbols could not be loaded for parport.sys
*** ERROR: Module load completed but symbols could not be loaded for ws2ifsl.sys
*** ERROR: Module load completed but symbols could not be loaded for Mup.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for NDIS.sys -
*** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for KSecDD.sys -
*** ERROR: Module load completed but symbols could not be loaded for sr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltMgr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for SCSIPORT.SYS -
*** ERROR: Module load completed but symbols could not be loaded for atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for dmio.sys
*** ERROR: Module load completed but symbols could not be loaded for ftdisk.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
*** ERROR: Module load completed but symbols could not be loaded for ACPI.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for DSFOleaut32.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dsfksvcs.sys -
*** ERROR: Module load completed but symbols could not be loaded for isapnp.sys
*** ERROR: Module load completed but symbols could not be loaded for MountMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for VolSnap.sys
*** ERROR: Module load completed but symbols could not be loaded for disk.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for CLASSPNP.SYS -
*** ERROR: Module load completed but symbols could not be loaded for agp440.sys
*** ERROR: Module load completed but symbols could not be loaded for i8042prt.sys
*** ERROR: Module load completed but symbols could not be loaded for cdrom.sys
*** ERROR: Module load completed but symbols could not be loaded for redbook.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for vmci.sys -
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for rasl2tp.sys
*** ERROR: Module load completed but symbols could not be loaded for raspppoe.sys
*** ERROR: Module load completed but symbols could not be loaded for raspptp.sys
*** ERROR: Module load completed but symbols could not be loaded for msgpc.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for termdd.sys -
*** ERROR: Module load completed but symbols could not be loaded for NDProxy.SYS
*** ERROR: Module load completed but symbols could not be loaded for netbios.sys
*** ERROR: Module load completed but symbols could not be loaded for Fips.SYS
*** ERROR: Module load completed but symbols could not be loaded for wanarp.sys
*** ERROR: Module load completed but symbols could not be loaded for Cdfs.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for PCIIDEX.SYS -
*** ERROR: Module load completed but symbols could not be loaded for PartMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for dsfroot.sys
*** ERROR: Module load completed but symbols could not be loaded for kbdclass.sys
*** ERROR: Module load completed but symbols could not be loaded for mouclass.sys
*** ERROR: Module load completed but symbols could not be loaded for fdc.sys
*** ERROR: Module load completed but symbols could not be loaded for vmx_svga.sys
*** ERROR: Module load completed but symbols could not be loaded for vmxnet.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for TDI.SYS -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ptilink.sys -
*** ERROR: Module load completed but symbols could not be loaded for raspti.sys
*** ERROR: Module load completed but symbols could not be loaded for flpydisk.sys
*** ERROR: Module load completed but symbols could not be loaded for vga.sys
*** ERROR: Module load completed but symbols could not be loaded for Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for watchdog.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for BOOTVID.dll -
*** ERROR: Module load completed but symbols could not be loaded for compbatt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for BATTC.SYS -
*** ERROR: Module load completed but symbols could not be loaded for vmscsi.sys
*** ERROR: Module load completed but symbols could not be loaded for serenum.sys
*** ERROR: Module load completed but symbols could not be loaded for CmBatt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ndistapi.sys -
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for rasacd.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for kdcom.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for WMILIB.SYS -
*** ERROR: Module load completed but symbols could not be loaded for intelide.sys
*** ERROR: Module load completed but symbols could not be loaded for dmload.sys
*** ERROR: Module load completed but symbols could not be loaded for vmmouse.sys
*** ERROR: Module load completed but symbols could not be loaded for swenum.sys
*** ERROR: Module load completed but symbols could not be loaded for Fs_Rec.SYS
*** ERROR: Module load completed but symbols could not be loaded for Beep.SYS
*** ERROR: Module load completed but symbols could not be loaded for mnmdd.SYS
*** ERROR: Module load completed but symbols could not be loaded for RDPCDD.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dump_WMILIB.SYS -
*** ERROR: Module load completed but symbols could not be loaded for ParVdm.SYS
*** ERROR: Module load completed but symbols could not be loaded for vmmemctl.sys
*** ERROR: Module load completed but symbols could not be loaded for audstub.sys
*** ERROR: Module load completed but symbols could not be loaded for Null.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgthk.sys -
*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804daed1, The address that the exception occurred at
Arg3: f545cbd0, Exception Record Address
Arg4: f545c8cc, Context Record Address

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

ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to set symbol path and load symbols.

MODULE_NAME: vfums

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c87e045

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L’instruction “0x%08lx” emploie l’adresse m moire “0x%08lx”. La m moire ne peut pas tre “%s”.

FAULTING_IP:
nt!memcpy+33
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

EXCEPTION_RECORD: f545cbd0 – (.exr 0xfffffffff545cbd0)
ExceptionAddress: 804daed1 (nt!memcpy+0x00000033)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000160
Attempt to read from address 00000160

CONTEXT: f545c8cc – (.cxr 0xfffffffff545c8cc)
eax=000002c0 ebx=00000000 ecx=00000058 edx=00000000 esi=00000160 edi=f7e80828
eip=804daed1 esp=f545cc98 ebp=f545cca0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!memcpy+0x33:
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f7c23fe4 to 804daed1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f545cca0 f7c23fe4 f7e80828 00000160 00000160 nt!memcpy+0x33
f545cd30 f7c24265 81995300 81e85c28 81e85c98 vfums+0x2fe4
f545cd60 f7c2484b 81995300 81e85c28 81e85c98 vfums+0x3265 f545cdac 80576b24 81995300 00000000 00000000 vfums+0x384b f545cddc 804eed86 f7c24730 81995300 00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb

FOLLOWUP_IP:
vfums+2fe4
f7c23fe4 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: vfums+2fe4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: vfums.sys

STACK_COMMAND: .cxr 0xfffffffff545c8cc ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804daed1, The address that the exception occurred at
Arg3: f545cbd0, Exception Record Address
Arg4: f545c8cc, Context Record Address

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

ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to set symbol path and load symbols.

MODULE_NAME: vfums

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c87e045

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L’instruction “0x%08lx” emploie l’adresse m moire “0x%08lx”. La m moire ne peut pas tre “%s”.

FAULTING_IP:
nt!memcpy+33
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

EXCEPTION_RECORD: f545cbd0 – (.exr 0xfffffffff545cbd0)
ExceptionAddress: 804daed1 (nt!memcpy+0x00000033)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000160
Attempt to read from address 00000160

CONTEXT: f545c8cc – (.cxr 0xfffffffff545c8cc)
eax=000002c0 ebx=00000000 ecx=00000058 edx=00000000 esi=00000160 edi=f7e80828
eip=804daed1 esp=f545cc98 ebp=f545cca0 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
nt!memcpy+0x33:
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f7c23fe4 to 804daed1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f545cca0 f7c23fe4 f7e80828 00000160 00000160 nt!memcpy+0x33
f545cd30 f7c24265 81995300 81e85c28 81e85c98 vfums+0x2fe4
f545cd60 f7c2484b 81995300 81e85c28 81e85c98 vfums+0x3265 f545cdac 80576b24 81995300 00000000 00000000 vfums+0x384b f545cddc 804eed86 f7c24730 81995300 00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb

FOLLOWUP_IP:
vfums+2fe4
f7c23fe4 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: vfums+2fe4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: vfums.sys

STACK_COMMAND: .cxr 0xfffffffff545c8cc ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

i solved my problem.
But I do not know why the windbg don’ty show line source code fault with number line

I put the correct directory PDB file of my project driver and its not working.
Still I success solved my problem about crash

Fix your symbols.

Gary G. Little
H (952) 223-1349
C (952) 454-4629
xxxxx@comcast.net

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@sivaller.no-ip.org
Sent: Sunday, September 12, 2010 1:46 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] crash when i shutdown system

can you help me please:
WinDbg does not hold myself out the line of my source code and pdb is
loaded.
Machine crash when i shutdown system.

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

Loading Dump File [C:\WINDOWS\MEMORY.DMP] Kernel Summary Dump File: Only
kernel address space is available

Symbol search path is:
C:\source\sivaller\vfums\v0.1\sys\vfums\obj\chk\i386;C:\source\sivaller\vfum
s\v0.1\sys\vfums\debug
Executable search path is:
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlmp.exe - Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS Built by:
2600.xpsp_sp2_rtm.040803-2158 Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805644a0 Debug session time:
Wed Sep 8 21:14:53.968 2010 (GMT+2) System Uptime: 0 days 0:04:58.765
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ntkrnlmp.exe - Loading Kernel Symbols


Loading User Symbols

Loading unloaded module list

****************************************************************************
***
*
*
* Bugcheck Analysis
*
*
*
****************************************************************************
***

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, 804daed1, f545cbd0, f545c8cc}

***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : vfums.sys ( vfums+2fe4 )

Followup: MachineOwner

*** ERROR: Symbol file could not be found. Defaulted to export symbols for
halmacpi.dll -
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for
win32k.sys
*** WARNING: Unable to verify timestamp for dxg.sys
*** ERROR: Module load completed but symbols could not be loaded for dxg.sys
*** WARNING: Unable to verify timestamp for vmx_fb.dll
*** ERROR: Module load completed but symbols could not be loaded for
vmx_fb.dll
*** ERROR: Module load completed but symbols could not be loaded for
HTTP.sys
*** ERROR: Module load completed but symbols could not be loaded for srv.sys
*** ERROR: Module load completed but symbols could not be loaded for
mrxdav.sys
*** ERROR: Module load completed but symbols could not be loaded for
ndisuio.sys
*** ERROR: Module load completed but symbols could not be loaded for
dump_atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for
ipnat.sys
*** ERROR: Module load completed but symbols could not be loaded for
mrxsmb.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
rdbss.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
truecrypt.sys -
*** ERROR: Module load completed but symbols could not be loaded for
vmhgfs.sys
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
*** ERROR: Module load completed but symbols could not be loaded for
netbt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
tcpip.sys -
*** ERROR: Module load completed but symbols could not be loaded for
ipsec.sys
*** ERROR: Module load completed but symbols could not be loaded for
update.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
Dxapi.sys -
*** ERROR: Module load completed but symbols could not be loaded for
rdpdr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
psched.sys -
*** ERROR: Module load completed but symbols could not be loaded for
ndiswan.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
VIDEOPRT.SYS -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ks.sys -
*** ERROR: Module load completed but symbols could not be loaded for
serial.sys
*** ERROR: Module load completed but symbols could not be loaded for
parport.sys
*** ERROR: Module load completed but symbols could not be loaded for
ws2ifsl.sys
*** ERROR: Module load completed but symbols could not be loaded for Mup.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
NDIS.sys -
*** ERROR: Module load completed but symbols could not be loaded for
Ntfs.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
KSecDD.sys -
*** ERROR: Module load completed but symbols could not be loaded for sr.sys
*** ERROR: Module load completed but symbols could not be loaded for
fltMgr.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
SCSIPORT.SYS -
*** ERROR: Module load completed but symbols could not be loaded for
atapi.sys
*** ERROR: Module load completed but symbols could not be loaded for
dmio.sys
*** ERROR: Module load completed but symbols could not be loaded for
ftdisk.sys
*** ERROR: Module load completed but symbols could not be loaded for pci.sys
*** ERROR: Module load completed but symbols could not be loaded for
ACPI.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
DSFOleaut32.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
dsfksvcs.sys -
*** ERROR: Module load completed but symbols could not be loaded for
isapnp.sys
*** ERROR: Module load completed but symbols could not be loaded for
MountMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for
VolSnap.sys
*** ERROR: Module load completed but symbols could not be loaded for
disk.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
CLASSPNP.SYS -
*** ERROR: Module load completed but symbols could not be loaded for
agp440.sys
*** ERROR: Module load completed but symbols could not be loaded for
i8042prt.sys
*** ERROR: Module load completed but symbols could not be loaded for
cdrom.sys
*** ERROR: Module load completed but symbols could not be loaded for
redbook.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
vmci.sys -
*** ERROR: Module load completed but symbols could not be loaded for
intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for
rasl2tp.sys
*** ERROR: Module load completed but symbols could not be loaded for
raspppoe.sys
*** ERROR: Module load completed but symbols could not be loaded for
raspptp.sys
*** ERROR: Module load completed but symbols could not be loaded for
msgpc.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
termdd.sys -
*** ERROR: Module load completed but symbols could not be loaded for
NDProxy.SYS
*** ERROR: Module load completed but symbols could not be loaded for
netbios.sys
*** ERROR: Module load completed but symbols could not be loaded for
Fips.SYS
*** ERROR: Module load completed but symbols could not be loaded for
wanarp.sys
*** ERROR: Module load completed but symbols could not be loaded for
Cdfs.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
PCIIDEX.SYS -
*** ERROR: Module load completed but symbols could not be loaded for
PartMgr.sys
*** ERROR: Module load completed but symbols could not be loaded for
dsfroot.sys
*** ERROR: Module load completed but symbols could not be loaded for
kbdclass.sys
*** ERROR: Module load completed but symbols could not be loaded for
mouclass.sys
*** ERROR: Module load completed but symbols could not be loaded for fdc.sys
*** ERROR: Module load completed but symbols could not be loaded for
vmx_svga.sys
*** ERROR: Module load completed but symbols could not be loaded for
vmxnet.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
TDI.SYS -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ptilink.sys -
*** ERROR: Module load completed but symbols could not be loaded for
raspti.sys
*** ERROR: Module load completed but symbols could not be loaded for
flpydisk.sys
*** ERROR: Module load completed but symbols could not be loaded for vga.sys
*** ERROR: Module load completed but symbols could not be loaded for
Msfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for
Npfs.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
watchdog.sys -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
BOOTVID.dll -
*** ERROR: Module load completed but symbols could not be loaded for
compbatt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
BATTC.SYS -
*** ERROR: Module load completed but symbols could not be loaded for
vmscsi.sys
*** ERROR: Module load completed but symbols could not be loaded for
serenum.sys
*** ERROR: Module load completed but symbols could not be loaded for
CmBatt.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
ndistapi.sys -
*** ERROR: Module load completed but symbols could not be loaded for
mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for
rasacd.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
kdcom.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
WMILIB.SYS -
*** ERROR: Module load completed but symbols could not be loaded for
intelide.sys
*** ERROR: Module load completed but symbols could not be loaded for
dmload.sys
*** ERROR: Module load completed but symbols could not be loaded for
vmmouse.sys
*** ERROR: Module load completed but symbols could not be loaded for
swenum.sys
*** ERROR: Module load completed but symbols could not be loaded for
Fs_Rec.SYS
*** ERROR: Module load completed but symbols could not be loaded for
Beep.SYS
*** ERROR: Module load completed but symbols could not be loaded for
mnmdd.SYS
*** ERROR: Module load completed but symbols could not be loaded for
RDPCDD.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
dump_WMILIB.SYS -
*** ERROR: Module load completed but symbols could not be loaded for
ParVdm.SYS
*** ERROR: Module load completed but symbols could not be loaded for
vmmemctl.sys
*** ERROR: Module load completed but symbols could not be loaded for
audstub.sys
*** ERROR: Module load completed but symbols could not be loaded for
Null.SYS
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
dxgthk.sys -
*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************
kd> !analyze -v
****************************************************************************
***
*
*
* Bugcheck Analysis
*
*
*
****************************************************************************
***

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck.
Usually the exception address pinpoints the driver/function that caused the
problem. Always note this address as well as the link date of the
driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804daed1, The address that the exception occurred at
Arg3: f545cbd0, Exception Record Address
Arg4: f545c8cc, Context Record Address

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

ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to
set symbol path and load symbols.

MODULE_NAME: vfums

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c87e045

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L’instruction “0x%08lx” emploie
l’adresse m moire “0x%08lx”. La m moire ne peut pas tre “%s”.

FAULTING_IP:
nt!memcpy+33
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

EXCEPTION_RECORD: f545cbd0 – (.exr 0xfffffffff545cbd0)
ExceptionAddress: 804daed1 (nt!memcpy+0x00000033)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000160
Attempt to read from address 00000160

CONTEXT: f545c8cc – (.cxr 0xfffffffff545c8cc)
eax=000002c0 ebx=00000000 ecx=00000058 edx=00000000 esi=00000160
edi=f7e80828
eip=804daed1 esp=f545cc98 ebp=f545cca0 iopl=0 nv up ei pl nz na pe
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010206
nt!memcpy+0x33:
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f7c23fe4 to 804daed1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
f545cca0 f7c23fe4 f7e80828 00000160 00000160 nt!memcpy+0x33
f545cd30 f7c24265 81995300 81e85c28 81e85c98 vfums+0x2fe4
f545cd60 f7c2484b 81995300 81e85c28 81e85c98 vfums+0x3265 f545cdac 80576b24
81995300 00000000 00000000 vfums+0x384b f545cddc 804eed86 f7c24730 81995300
00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb

FOLLOWUP_IP:
vfums+2fe4
f7c23fe4 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: vfums+2fe4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: vfums.sys

STACK_COMMAND: .cxr 0xfffffffff545c8cc ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************
kd> !analyze -v
****************************************************************************
***
*
*
* Bugcheck Analysis
*
*
*
****************************************************************************
***

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common bugcheck.
Usually the exception address pinpoints the driver/function that caused the
problem. Always note this address as well as the link date of the
driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 804daed1, The address that the exception occurred at
Arg3: f545cbd0, Exception Record Address
Arg4: f545c8cc, Context Record Address

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

ADDITIONAL_DEBUG_TEXT:
Use ‘!findthebuild’ command to search for the target build information.
If the build information is available, run ‘!findthebuild -s ; .reload’ to
set symbol path and load symbols.

MODULE_NAME: vfums

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4c87e045

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L’instruction “0x%08lx” emploie
l’adresse m moire “0x%08lx”. La m moire ne peut pas tre “%s”.

FAULTING_IP:
nt!memcpy+33
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]

EXCEPTION_RECORD: f545cbd0 – (.exr 0xfffffffff545cbd0)
ExceptionAddress: 804daed1 (nt!memcpy+0x00000033)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000160
Attempt to read from address 00000160

CONTEXT: f545c8cc – (.cxr 0xfffffffff545c8cc)
eax=000002c0 ebx=00000000 ecx=00000058 edx=00000000 esi=00000160
edi=f7e80828
eip=804daed1 esp=f545cc98 ebp=f545cca0 iopl=0 nv up ei pl nz na pe
nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010206
nt!memcpy+0x33:
804daed1 f3a5 rep movs dword ptr es:[edi],dword ptr [esi]
Resetting default scope

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from f7c23fe4 to 804daed1

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
f545cca0 f7c23fe4 f7e80828 00000160 00000160 nt!memcpy+0x33
f545cd30 f7c24265 81995300 81e85c28 81e85c98 vfums+0x2fe4
f545cd60 f7c2484b 81995300 81e85c28 81e85c98 vfums+0x3265 f545cdac 80576b24
81995300 00000000 00000000 vfums+0x384b f545cddc 804eed86 f7c24730 81995300
00000000 nt!PsCreateSystemThread+0x70
00000000 00000000 00000000 00000000 00000000 nt!KeInitializeTimerEx+0x1eb

FOLLOWUP_IP:
vfums+2fe4
f7c23fe4 83c40c add esp,0Ch

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: vfums+2fe4

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: vfums.sys

STACK_COMMAND: .cxr 0xfffffffff545c8cc ; kb

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner

*************************************************************************
*** ***
*** ***
*** 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: PPARAMVDF ***
*** ***
*************************************************************************


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

>I put the correct directory PDB file of my project driver and its not working.

Read the section “Debuggers/Symbols/Symbols Problems While Debugging” in WinDbg documentation .

Igor Sharovar

ok i will read