Vedratna


hi, everbody

we have recently created account in winqual and also successfully mapped our product over there. We also receive some error reports(buckets) in it. We have downloaded some of them in form of cabinet file. After extracting it we get the file having extension of .mdmp. I have opened it in windbg through open crash dump option. It opens it successfully but I can't see any stacktrace in proper format over there.

After some R & D I come to know that I have to map the imge and symbols to see the stack trace in proper format. I completely unaware about image and symbols and also using winDbg first time. So my quries are

1) what is symbols and images and how can I map them to winDbg also from where I mean what should be the path is It from microsoft server for my application Please describe it in detail.

2)Can anybody tell me the exact procedure to see the complete stack trace in proper format - a format which I can see in my vs.net application through exception's stack trace property

3) How to response any bucket or error report

4) This time I have mapped my whole setup including all files (it's a clickonce setup) through mapping tool ( By generating xml file). is it ok Or can you guide which files are needed to map

Please Reply As Early As Possible.

Thanks in advance.





Re: How can I see the stack trace from the .mdmp file?

Saar Picker - MSFT


Hi,

In this case symbols are the .pdb files that are produced when you compile your application and the images are the .exe/.dll. You have to tell windbg where symbols for every referenced image exist. Microsoft makes available symbols for Windows publically. Combine them with the symbols for your binaries and you're all set to go. This page describes the process. If you've done this properly you should be able to see your stacks using the kb command. The windbg learning curve is steep, but it's a very powerful tool. The help documentation is a great resource so be sure to read through that.

Once you've taken a look at your bucket and determined the proper course of action, the easiest way to file a response is from the Event Details page in the WER Software section of the Winqual site (click on any event id to get there). You will see a large box with a yellow heading at the top of the page. You can set the response for a specific event only, or for a specific file with a min/max version range. Just follow the response creation form and it will file the response for review. We usually review response requests in 2-3 business days, so check back under the WER Software->Response Management section to see if your response was approved. If for some reason there's no change from Pending status after 2-3 days, please let us know.

Great! You've mapped your files and that's exactly what we want! You can map as many as you like, but be sure that you own them. If you bundle other libraries in your application, these may be rejected.

I hope this answers your questions.

-saarp






Re: How can I see the stack trace from the .mdmp file?

Vedratna

Thanks saarp for your quick response.

I will try whatever you suggest here and then come back to you If I will stuck in any problems.

Now what I am going to try is map all the file including setup.exe (and all other dlls and exes from my application's folder, as in setup they are available with .deploy extension so I think I have to map the references without .deploy extension as after installation .deploy extension is removed.). After that I will reference all dlls and exes I have used in my application as images in windbg and all respective .pdb files as symbols (including window's symbols downloaded from it's server.). And then try kb command to see the stacktrace after downloading the cab file from my account in winqual. Is it ok







Re: How can I see the stack trace from the .mdmp file?

Saar Picker - MSFT

Hi Ved,

Glad to be of help. Yes, you'll have to map your files without the .deploy extension. You can create the mapping during build time before the setup distribution is created, or after the application has been installed. I think most of our users use the latter method. Another way is to modify the XML that the AppMap tool produces and remove the .deploy extensions. Whatever works for you environment.

If you're still having issues with Windbg after that, let us know and we'll try and help.

Thanks!

-saarp





Re: How can I see the stack trace from the .mdmp file?

Vedratna

Hi, saarp

I have tried the things as you mentioned, in following manner.

1) Download the symbols for windows vista and windows xp sp2. And store them at E:\windows\symbols by installing them. (Here E is not my OS system drive but I have done it in this way as I don't have enough space on system drive)

2)open gui windbg. Store the symbol paths c:\wer\symbols_967;e:\windows\symbols where first one is my application's symbol path and the other one is windows' symbol path.

3) store the image path c:\wer\images_967 which includes all the dlls and exes used in my application.

Here all images and symbols of my application having the versions that mapping application's dll and exes have.

4) download the cab file from wer and extract the cab and then extract the minidump.mdmp

5)open the minidump in windbg through open crashdump option. It shows following information

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


Loading Dump File [C:\WER\Cabinets\minidump.mdmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Windows Vista Version 6000 UP Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Thu Apr 5 18:35:09.000 2007 (GMT+5)
System Uptime: 0 days 4:08:04.206
Process Uptime: 0 days 0:03:43.000
Symbol search path is: E:\Windows\Symbols;C:\WER\Symbols_967
Executable search path is: C:\WER\images_967
.....................................................................................................................
Loading unloaded module list
....
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
eax=c0c0c0c0 ebx=774c817b ecx=00000005 edx=00000000 esi=0024cecc edi=00000000
eip=77830f34 esp=0024ce6c ebp=0024ce84 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
Unable to load image C:\Windows\System32\ntdll.dll, Win32 error 2
*** WARNING: Unable to verify timestamp for ntdll.dll
ntdll!RtlUsageHeap+0x24c:
77830f34 c3 ret

6) Here it shows unable to load imgae c:\win.......... so what should I do to solve this error.

7) I have also tried .ecxr in following manner.

open command browser by View-> Command browser. and type .ecxr it shows me following information.

eax=000001ff ebx=70bcaff0 ecx=777f14cd edx=00000000 esi=00000000 edi=000001ff
eip=77812ea8 esp=0024e0c0 ebp=0024e2c0 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!RtlQueueApcWow64Thread+0x30:
77812ea8 cc int 3

It is still not in readable for me so what should I do to make it readable or where I mistaken

When I tried kb command in same manner it shows me following information

*** Stack trace for last set context - .thread/.cxr resets it
ChildEBP RetAddr Args to Child
0024e2c0 70bc6fa3 70bca530 00000013 00000000 ntdll!RtlQueueApcWow64Thread+0x30
*** WARNING: Unable to verify timestamp for vfbasics.dll
*** ERROR: Module load completed but symbols could not be loaded for vfbasics.dll
WARNING: Stack unwind information not available. Following frames may be wrong.
0024e2e4 6d8a3229 00000013 6d8933a8 00000000 vrfcore+0x6fa3
0024e314 6d8996d9 00000013 6d8933a8 00000000 vfbasics+0x13229
0024e378 6d898e08 0024e3a0 0024e3a0 0024e3b0 vfbasics+0x96d9
0024e388 777dc41b 0024e3a0 0024e44c 0024e44c vfbasics+0x8e08
0024e3b0 777f2b3a 00000000 024f8ff0 778954b8 ntdll!$$VProc_ImageExportDirectory+0x8ae7
0024e3b8 024f8ff0 778954b8 0024e434 777f2960 ntdll!WmipInitializeDll+0x9
0024e3c4 777f2960 0024e44c 0024e468 04043d0c 0x24f8ff0
0024e434 77830e97 0024e44c 0024e468 0024e44c ntdll!RtlInitializeCriticalSectionAndSpinCount+0x58
0024e7e4 075901d7 02fdb562 0442a548 0024ea40 ntdll!RtlUsageHeap+0x1af
0024e804 0759017a 00000000 00000002 03fd534c 0x75901d7
0024e808 00000000 00000002 03fd534c 0442a548 0x759017a

it is also not readble. So please tell me where I mistaken






Re: How can I see the stack trace from the .mdmp file?

Saar Picker - MSFT

Hi Ved,

Seems like you may still be having some symbol resolution problems. Could you try the following and post the output This will help diagnose the cause.

  1. .sympath srv*E:\Windows\Symbols*http://msdl.microsoft.com/download/symbols;C:\WER\Symbols_967
  2. !sym noisy
  3. .reload /f /i ntdll.dll
  4. !sym quiet
  5. !lmi

Thanks,

-saarp





Re: How can I see the stack trace from the .mdmp file?

Vedratna

Hi saarp,

Thanks for your quick response.

I have tried the commands you gave, in command browser of windbg. The output of each is given as below.

1) command: .sympath srv*E:\Windows\Symbols*http://msdl.microsoft.com/download/symbols;C:\WER\Symbols_967

output: Symbol search path is: *E:\Windows\Symbols*http://msdl.microsoft.com/download/symbols;C:\WER\Symbols_967

2)command: !sym noisy

output: noisy mode - symbol prompts on

3) command: .reload /f /i ntdll.dll

output:

DBGHELP: D:\Program Files\Debugging Tools for Windows\ntdll.dll - file not found
DBGHELP: ntdll.dll not found in C:\WER\images_967
SYMSRV: The server name or address could not be resolved
SYMSRV: The server name or address could not be resolved
SYMSRV: E:\Windows\Symbols\ntdll.dll\4549BDC911e000\ntdll.dll not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntdll.dll/4549BDC911e000/ntdll.dll not found
DBGHELP: D:\Program Files\Debugging Tools for Windows\ntdll.dll - file not found
DBGHELP: ntdll.dll not found in C:\WER\Symbols_967
DBGENG: C:\Windows\System32\ntdll.dll image header does not match memory image header.
DBGENG: C:\Windows\System32\ntdll.dll - Couldn't map image from disk.
Unable to load image C:\Windows\System32\ntdll.dll, Win32 error 2
DBGENG: ntdll.dll - Partial symbol image load missing image info
DBGHELP: No header for ntdll.dll. Searching for dbg file
DBGHELP: C:\WER\Symbols_967\ntdll.dbg - file not found
DBGHELP: C:\WER\Symbols_967\symbols\dll\ntdll.dbg - path not found
DBGHELP: C:\WER\Symbols_967\dll\ntdll.dbg - path not found
DBGHELP: .\ntdll.dbg - file not found
DBGHELP: .\symbols\dll\ntdll.dbg - path not found
DBGHELP: .\dll\ntdll.dbg - path not found
DBGHELP: ntdll.dll missing debug info. Searching for pdb anyway
DBGHELP: Can't use symbol server for ntdll.pdb - no header information available
DBGHELP: C:\WER\Symbols_967\ntdll.pdb - file not found
DBGHELP: C:\WER\Symbols_967\symbols\dll\ntdll.pdb - file not found
DBGHELP: C:\WER\Symbols_967\dll\ntdll.pdb - file not found
DBGHELP: ntdll.pdb - file not found
*** WARNING: Unable to verify timestamp for ntdll.dll
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
DBGHELP: ntdll - no symbols loaded

4) Command: !sym quiet

Output: quiet mode - symbol prompts on

5) Command: !lmi

Output: You must specify a module

Here why is it going to load ntdll.dll as I have serched in my installed application there is no ntdll.dll is available






Re: How can I see the stack trace from the .mdmp file?

Saar Picker - MSFT

Hi Ved,

I think your problem is related to the following messages:

SYMSRV: The server name or address could not be resolved

:

SYMSRV: http://msdl.microsoft.com/download/symbols/ntdll.dll/4549BDC911e000/ntdll.dll not found

Can you make sure you can resolve and connect to 'msdl.microsoft.com' on the machine running the debugger

There is also a tool you can use to try and diagnose why you can't download symbols that's distributed with the debugger package called symchk.

To use symchk:

    1. Create a file with lines like this: <filename>,<fileindex>,0

      Here the FileIndex is the big hex number ("4549BDC911e000" in this case) after the filename in the download link.

      One way to do this is:

      %> echo ntdll.dll,4549BDC911e000,0 > GetIt.txt

    2. Then run:

      %> symchk /im GetIt.txt /s <sympath> /v

If you can't download the symbols, check your Internet connectivity. You should also be able to download complete x86 Vista symbols here.

Hope that helps,

-saarp





Re: How can I see the stack trace from the .mdmp file?

Vedratna

hi saarp, thanks for your response.

I have made some changes.

We have seen that it shows the error "unable to load ntdll.dll from c:\windows\system32".

Actually my vista is installed in D drive. In C drive I have installed windows server 2003.

I have Edit the image path as follows

C:\WER\images_967;D:\Windows\System32

and my symbol paths are

E:\Windows\Symbols;C:\WER\Symbols_967

after that when I open the crash dump the verbose output is as follows.


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


Loading Dump File [C:\WER\Cabinets\minidump.mdmp]
User Mini Dump File: Only registers, stack and portions of memory are available

Windows Vista Version 6000 UP Free x86 compatible
Product: WinNt, suite: SingleUserTS
Debug session time: Thu Apr 5 18:35:09.000 2007 (GMT+5)
System Uptime: 0 days 4:08:04.206
Process Uptime: 0 days 0:03:43.000
Symbol search path is: E:\Windows\Symbols;C:\WER\Symbols_967
Executable search path is: C:\WER\images_967;D:\Windows\System32
.....................................................................................................................
Loading unloaded module list
....
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
eax=c0c0c0c0 ebx=774c817b ecx=00000005 edx=00000000 esi=0024cecc edi=00000000
eip=77830f34 esp=0024ce6c ebp=0024ce84 iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
ntdll!KiFastSystemCallRet:
77830f34 c3 ret
Verbose mode ON.

so there is no error of unable to load.

I have also tried the steps you given as follows

1).sympath E:\Windows;C:\WER\Symbols_967 ( Here I have used E:\Windows instead of microsoft server path you gave, as I have already download the vista symbols overthere)

OUTPUT: DBGHELP: Symbol Search Path: E:\Windows;C:\WER\Symbols_967
Symbol search path is: E:\Windows;C:\WER\Symbols_967

2)!sym noisy

OUTPUT:noisy mode - symbol prompts on

3).reload /f /i ntdll.dll

OUTPUT:

Force unload of C:\Windows\System32\ntdll.dll
DBGHELP: D:\Windows\System32\ntdll.dll - OK
DBGENG: D:\Windows\System32\ntdll.dll - Mapped image memory
Loading symbols for 777d0000 ntdll.dll ->
DBGHELP: E:\Windows\ntdll.pdb - file not found
ntdll.dll
DBGHELP: ntdll - public symbols
E:\Windows\symbols\dll\ntdll.pdb
ModLoad: 777d0000 778ee000 C:\Windows\System32\ntdll.dll

4)!sym quiet

quiet mode - symbol prompts on

5)!lmi ntdll.dll

Loaded Module Info: [ntdll.dll]
Module: ntdll
Base Address: 777d0000
I mage Name: ntdll.dll
Machine Type: 332 (I386)
Time Stamp: 4549bdc9 Thu Nov 02 15:13:37 2006
Size: 11e000
CheckSum: 128171
Characteristics: 2102 perf
Debug Data Dirs: Type Size VA Pointer
CODEVIEW 22, c34a8, c28a8 RSDS - GUID: {C0A498F0- 36E-4D4F-B5CB-F690 5B0F924}
Age: 2,

Pdb: ntdll.pdb
CLSID 4, c34a4, c28a4 [Data not mapped]
Image Type: FILE - Image read successfully from debugger.
ntdll.dll
Symbol Type: PDB - Symbols loaded successfully from symbol search path.
E:\Windows\symbols\dll\ntdll.pdb
Load Report: public symbols , not source indexed
E:\Windows\symbols\dll\ntdll.pdb

so there is no error of unloading but my query is same

still .ecxr give me following output

eax=000001ff ebx=70bcaff0 ecx=777f14cd edx=00000000 esi=00000000 edi=000001ff
eip=77812ea8 esp=0024e0c0 ebp=0024e2c0 iopl=0 nv up ei pl nz na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
ntdll!DbgBreakPoint:
77812ea8 cc int 3

and .kb gives

*** Stack trace for last set context - .thread/.cxr resets it
ChildEBP RetAddr Args to Child
0024e0bc 70bc3760 0024ea08 024f8ff8 024f8ff0 ntdll!DbgBreakPoint
WARNING: Stack unwind information not available. Following frames may be wrong.
0024e2c0 70bc6fa3 70bca530 00000013 00000000 vrfcore!VerifierStopMessageEx+0x4b5
*** ERROR: Module load completed but symbols could not be loaded for vfbasics.dll
0024e2e4 6d8a3229 00000013 6d8933a8 00000000 vrfcore!VerifierRegisterLayerEx+0x11b
0024e314 6d8996d9 00000013 6d8933a8 00000000 vfbasics+0x13229
0024e378 6d898e08 0024e3a0 0024e3a0 0024e3b0 vfbasics+0x96d9
0024e388 777dc41b 0024e3a0 0024e44c 0024e44c vfbasics+0x8e08
0024e3b0 777f2b3a 00000000 024f8ff0 778954b8 ntdll!RtlpCallVectoredHandlers+0x57
0024e3c4 777f2960 0024e44c 0024e468 04043d0c ntdll!RtlCallVectoredExceptionHandlers+0x15
0024e434 77830e97 0024e44c 0024e468 0024e44c ntdll!RtlDispatchException+0x19
0024e434 0759024b 0024e44c 0024e468 0024e44c ntdll!KiUserExceptionDispatcher+0xf
0024e730 00000000 174a2fe0 0ff8006c 00000000 0x759024b

so what should I do to get it in readable format

please reply as early as possible.






Re: How can I see the stack trace from the .mdmp file?

Saar Picker - MSFT

Hi Ved,

Looks like the symbol problem is fixed and you can at least see the stack trace. You're still missing symbols for vfbasics.dll (I assume this is one of yours).

From the looks of it this isn't a real exception but a debugger break call in vrfcore!VerifierStopMessageEx().

You can try the .exr -1 command after .ecxr. This may display the info you want. Once you get an error code the !error command is useful for translating that to an error message.

-saarp





Re: How can I see the stack trace from the .mdmp file?

Vedratna

Hi saarp, thanks for your response.

vfbasics.dll is not my application's file. I have found it at d:\windows\system32. But its symbol is not available at e:\windows\symbols - a place where I install the windows vista symbols. To download all the symbols again is very combersome and lengthy process so is there any other way through which I can only download the symbols I don't have And what should be the reason I mean why the symbol for vfbasics.dll is not available to me even after the installation has been done for WindowsVista.6000.061101-2205.x86fre.Symbols.






Re: How can I see the stack trace from the .mdmp file?

Saar Picker - MSFT

Hi Ved,

vfbasics.dll appears to be part of application verifier. You can download this package at http://www.microsoft.com/downloads/details.aspx FamilyID=bd02c19c-1250-433c-8c1b-2619bd93b3a2&DisplayLang=en if you don't have it already. It comes with symbols for vfbasics.dll. You may need to do an !lmi vfbasics.dll to make sure you get the correct version.

Did .exr -1 give you the exception information you wanted

Thanks,

-saarp





Re: How can I see the stack trace from the .mdmp file?

Vedratna

hi saarp, thanks for response.

.pdb files are also there in d:\windows\system32. Mapped that path for symbol also and it solved the problem of unloading.

after .ecxr, .exr -1 gives me following

ExceptionAddress: 77812ea8 (ntdll!DbgBreakPoint)
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 3
Parameter[0]: 00000000
Parameter[1]: 839315c0
Parameter[2]: 00000000

!error 80000003 gives me following

Error code: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

so it gives me the error but not the complete stacktrace. How can I see the complete statcktrace in redable format(in english like language like here it gives one or mor arguments are invalid.)






Re: How can I see the stack trace from the .mdmp file?

John Brown

!error is not telling you the truth. The exception code 0x80000003 is not an HRESULT. The "One or more arguments are invalid" interpretation of this exception code is itself not valid. This exception code means that a breakpoint instruction (INT 3) was encountered, just as the initial report of the exception says.

It isn't reasonable to expect a trackback to be presented to you in readable english. The convention for every debugger I have ever worked with is to present code locations in tracebacks in the same way that code locations are specified in breakpoints.

What you want in each line of a traceback is a module name, a function name, and a line number, not english prose.

You need to take a step back and make sure that you are actually debugging a dump that's associated with your product. Do an 'lm' command and look closely at all the module names. Is one of them yours





Re: How can I see the stack trace from the .mdmp file?

Vedratna

Hi john

Thanks for your response and sorry for late reply.

I have also tried 'lm' command and it gives me the following result. Investar.exe is my main app. It is also available there and other dlls are also from my applications.

Result:

start end module name
06b30000 06b3a000 OriginalMenuButtons (deferred)
108f0000 10b08000 Investar (deferred)
11000000 1101c000 Eyefinder (deferred)
15970000 16116000 Microsoft_mshtml (deferred)
548e0000 54920000 msdbg2 (deferred)
54b20000 54b5f000 pdm (deferred)
5e3a0000 5e429000 diasymreader (deferred)
60510000 60529000 dfshim (deferred)
637a0000 63d02000 System_Xml_ni (deferred)
64020000 64033000 mscorsec (deferred)
64890000 6498a000 System_Configuration_ni (deferred)
64e70000 65139000 System_Data (deferred)
65140000 6579e000 System_Data_ni (deferred)
67770000 6783c000 System_Runtime_Remoting_ni (deferred)
6c810000 6c884000 riched20 (deferred)
6c8d0000 6c8fe000 XPExplorerBar (deferred)
6c900000 6c96c000 Easychart_Finance (deferred)
6c970000 6c9b6000 Easychart_Finance_Win (deferred)
6c9c0000 6ca52000 DevExpress_XtraTreeList3 (deferred)
6ca70000 6cace000 DevExpress_Data3 (deferred)
6cad0000 6cc74000 DevExpress_Utils3 (deferred)
6cfd0000 6d0da000 DevExpress_XtraEditors3 (deferred)
6d0e0000 6d11c000 SandDock (deferred)
6d120000 6d15e000 ProChartCore (deferred)
6d890000 6d8cd000 vfbasics (deferred)
6da70000 6da96000 Easychart_Finance_Objects (deferred)
6dfb0000 6e31f000 mshtml (deferred)
6e330000 6e33a000 UIToolbox (deferred)
6e410000 6e441000 verifier (deferred)
6e690000 6ec5a000 ieframe (deferred)
6fab0000 6fbf5000 browseui (deferred)
6fc00000 6fc0a000 CProgressBar (deferred)
70280000 702b0000 mlang (deferred)
70710000 70718000 BackgroundWorkerComponent (deferred)
709c0000 709e9000 msls31 (deferred)
70bc0000 70be0000 vrfcore (deferred)
70be0000 70c40000 tiptsf (deferred)
71bf0000 71c09000 cryptnet (deferred)
71f90000 71f98000 ProChartCommon (deferred)
720d0000 720d3000 security (deferred)
72140000 72146000 SensApi (deferred)
72260000 72265000 shfolder (deferred)
72750000 72756000 dciman32 (deferred)
72780000 72786000 softpub (deferred)
72830000 72842000 pnrpnsp (deferred)
72cb0000 72cbf000 NapiNSP (deferred)
72cf0000 72cf8000 winrnr (deferred)
72ec0000 72ec6000 rasadhlp (deferred)
73160000 731fb000 msvcr80 (deferred)
73f70000 73ff6000 comctl32_73f70000 (deferred)
744b0000 74567000 propsys (deferred)
748e0000 74a8a000 GdiPlus (deferred)
74aa0000 74aaf000 nlaapi (deferred)
74b80000 74b94000 cabinet (deferred)
74e30000 74fc4000 comctl32 (deferred)
75040000 7504b000 msimtf (deferred)
75100000 75130000 duser (deferred)
75130000 7516f000 uxtheme (deferred)
75230000 7525d000 wintrust (deferred)
753c0000 753c6000 WSHTCPIP (deferred)
75400000 75421000 ntmarta (deferred)
75460000 75475000 gpapi (deferred)
75480000 754b8000 rsaenh (deferred)
754f0000 75535000 schannel (deferred)
756f0000 7572b000 mswsock (deferred)
75750000 75756000 wship6 (deferred)
75760000 75768000 version (deferred)
757f0000 757f7000 credssp (deferred)
75810000 75854000 bcrypt (deferred)
75860000 75892000 ncrypt (deferred)
758b0000 758d0000 dhcpcsvc6 (deferred)
758d0000 758d7000 winnsi (deferred)
758e0000 75915000 dhcpcsvc (deferred)
75920000 75939000 IPHLPAPI (deferred)
75a10000 75a49000 SLC (deferred)
75a50000 75b41000 crypt32 (deferred)
75b90000 75ba2000 msasn1 (deferred)
75bb0000 75c1a000 netapi32 (deferred)
75dd0000 75e2f000 sxs (deferred)
75e40000 75e51000 samlib (deferred)
75e60000 75e8b000 dnsapi (deferred)
75e90000 75ebc000 apphelp (deferred)
75f20000 75f34000 secur32 (deferred)
75f40000 75f5e000 userenv (deferred)
76080000 76087000 psapi (deferred)
76090000 7614f000 advapi32 (deferred)
76150000 76159000 lpk (deferred)
76160000 761a9000 Wldap32 (deferred)
76230000 762ff000 wininet (deferred)
76300000 7637d000 usp10 (deferred)
76380000 7641e000 user32 (deferred)
76420000 7644d000 ws2_32 (deferred)
76450000 7646e000 imm32 (deferred)
76470000 764fc000 oleaut32 (deferred)
76500000 76506000 nsi (deferred)
76510000 76539000 imagehlp (deferred)
76540000 76607000 msctf (deferred)
76610000 76694000 clbcatq (deferred)
766a0000 766eb000 gdi32 (deferred)
766f0000 76878000 setupapi (deferred)
76880000 769a4000 urlmon (deferred)
769b0000 7747e000 shell32 (deferred)
77480000 77558000 kernel32 (deferred)
77560000 77623000 rpcrt4 (deferred)
77630000 77774000 ole32 (deferred)
77780000 777c5000 iertutil (deferred)
777d0000 778ee000 ntdll (pdb symbols) E:\Windows\symbols\dll\ntdll.pdb
778f0000 778f3000 normaliz (deferred)
77900000 77955000 shlwapi (deferred)
77960000 77a0a000 msvcrt (deferred)
79000000 79045000 mscoree (deferred)
79060000 790b3000 mscorjit (deferred)
790c0000 79bde000 mscorlib_ni (deferred)
79e70000 7a3d6000 mscorwks (deferred)
7a440000 7ac0c000 System_ni (deferred)
7ade0000 7af70000 System_Drawing_ni (deferred)
7afd0000 7bc5e000 System_Windows_Forms_ni (deferred)

Unloaded modules:
60340000 60348000 culture.dll
76470000 764fc000 OLEAUT32.dll
766f0000 76878000 setupapi.dll
6d0e0000 6d154000 RichEd20.dll
so now what should I do Here what is the meaning of deferred