OS: Windows XP Pro SP 3
EXE compiled with VS2005 Team Edition SP2
This is the output:
0:000> g
ModLoad: 76390000 763ad000 C:\WINDOWS\system32\IMM32.DLL
ModLoad: 629c0000 629c9000 C:\WINDOWS\system32\LPK.DLL
ModLoad: 74d90000 74dfb000 C:\WINDOWS\system32\USP10.dll
ModLoad: 773d0000 774d3000
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll
ModLoad: 5d360000 5d36e000
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.4053_x-ww_0ccc058c\MFC80ENU.DLL
ModLoad: 03c10000 03c27000 C:\WINDOWS\system32\odbcint.dll
ModLoad: 4e530000 4e59c000 C:\WINDOWS\system32\sqlsrv32.dll
ModLoad: 77120000 771ab000 C:\WINDOWS\system32\OLEAUT32.dll
ModLoad: 774e0000 7761d000 C:\WINDOWS\system32\ole32.dll
ModLoad: 5c1b0000 5c1dd000 C:\WINDOWS\system32\SQLUNIRL.dll
ModLoad: 77c00000 77c08000 C:\WINDOWS\system32\VERSION.dll
ModLoad: 75940000 75948000 C:\WINDOWS\system32\NDDEAPI.DLL
ModLoad: 04140000 04156000 C:\WINDOWS\system32\sqlsrv32.rll
ModLoad: 5fe80000 5fe9b000 C:\WINDOWS\system32\odbccp32.dll
ModLoad: 6d4f0000 6d50b000 C:\WINDOWS\system32\DBNETLIB.DLL
ModLoad: 71f80000 71f84000 C:\WINDOWS\system32\security.dll
ModLoad: 71e50000 71e65000 C:\WINDOWS\system32\msapsspc.dll
ModLoad: 78080000 78091000 C:\WINDOWS\system32\MSVCRT40.dll
ModLoad: 767f0000 76818000 C:\WINDOWS\system32\schannel.dll
ModLoad: 77a80000 77b15000 C:\WINDOWS\system32\CRYPT32.dll
ModLoad: 77b20000 77b32000 C:\WINDOWS\system32\MSASN1.dll
ModLoad: 769c0000 76a74000 C:\WINDOWS\system32\USERENV.dll
ModLoad: 75b00000 75b15000 C:\WINDOWS\system32\digest.dll
ModLoad: 747b0000 747f7000 C:\WINDOWS\system32\msnsspc.dll
ModLoad: 78080000 78091000 C:\WINDOWS\system32\MSVCRT40.dll
ModLoad: 77c70000 77c95000 C:\WINDOWS\system32\msv1_0.dll
ModLoad: 76790000 7679c000 C:\WINDOWS\system32\cryptdll.dll
ModLoad: 76d60000 76d79000 C:\WINDOWS\system32\iphlpapi.dll
ModLoad: 767a0000 767b3000 C:\WINDOWS\system32\ntdsapi.dll
ModLoad: 76f20000 76f47000 C:\WINDOWS\system32\DNSAPI.dll
ModLoad: 76f60000 76f8c000 C:\WINDOWS\system32\WLDAP32.dll
ModLoad: 77a80000 77b15000 C:\WINDOWS\system32\crypt32.dll
ModLoad: 77b20000 77b32000 C:\WINDOWS\system32\MSASN1.dll
ModLoad: 74cd0000 74cd8000 C:\WINDOWS\system32\DBmsLPCn.dll
ModLoad: 7c340000 7c396000 C:\WINDOWS\system32\MSVCR71.dll
ModLoad: 71a50000 71a8f000 C:\WINDOWS\system32\mswsock.dll
ModLoad: 662b0000 66308000 C:\WINDOWS\system32\hnetcfg.dll
ModLoad: 71a90000 71a98000 C:\WINDOWS\System32\wshtcpip.dll
ModLoad: 76fb0000 76fb8000 C:\WINDOWS\System32\winrnr.dll
ModLoad: 76fc0000 76fc6000 C:\WINDOWS\system32\rasadhlp.dll
ModLoad: 4bd70000 4bd77000 C:\WINDOWS\system32\DBnmpNTw.dll
ModLoad: 767f0000 76818000 C:\WINDOWS\system32\schannel.dll
ModLoad: 769c0000 76a74000 C:\WINDOWS\system32\USERENV.dll
ModLoad: 68000000 68036000 C:\WINDOWS\system32\rsaenh.dll
ModLoad: 68100000 68126000 C:\WINDOWS\system32\dssenh.dll
eax=00000000 ebx=00000000 ecx=7c800000 edx=1000fad0 esi=7c90de6e edi=fffe79c2
eip=7c90e514 esp=0012fdfc ebp=0012fe10 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:
7c90e514 c3 ret
Missing image name, possible paged-out or corrupt data.
Missing image name, possible paged-out or corrupt data.
When I do "lmv", this is at the end of the output (skipping loaded module
info.):
Unloaded modules:
Unloaded modules:
71e50000 71e65000 msapsspc.dll
Timestamp: Sun Apr 13 19:11:17 2008 (4802A125)
Checksum: 00015F5F
00000001 48025156 RT40.dll
Timestamp: Wed Mar 04 16:59:25 1970 (0053004D)
Checksum: 00430056
0002ac2e 0065aca1 .dll
Timestamp: Wed Mar 25 05:31:10 1970 (006E006E)
Checksum: 006C0065
Missing image name, possible paged-out or corrupt data.
00520045 00a0008a Unknown_Module_00520045
Timestamp: Mon Mar 23 17:06:28 1970 (006C0064)
Checksum: 0000006C
Missing image name, possible paged-out or corrupt data.
002e0032 009a0096 Unknown_Module_002e0032
Timestamp: unavailable (00000000)
Checksum: 00000000
In the list of loaded modules, there isn't a "RT40.dll" but there are 2
entries for "MSVCRT40.dll".
What would cause "ModLoad: 78080000 78091000
C:\WINDOWS\system32\MSVCRT40.dll" to be loaded twice??
Any ideas as to what would cause this, registry corruption? file
corruptions? VS2005 settings?
Thanks in advance!
Hi J.A.,
There is something fishy going on for a while in this area. I worked
with a Premier Support person from Microsoft (Robert Farrah). At the
time, he found that the problem was caused by the public ntdll32.dll
symbols not containing some needed symbols. Commands like !peb and !
teb won't work either. But at the time, we thought it was specific to
XP64 symbols. My scenario was using XP64 OS to run a 32 bit
application and using the 32 bit windbg.
If you look at the output of the lmvm, the last 64 unloaded DLLs are
reported at the end.
In my case only the first module had a valid load address (DLLs load
address have to have the last four digits as 0000, since a DLL can
only be loaded at a 64Kb address boundary).
I don't know if this is caused by a debugger bug or if the unloaded
module data is getting corrupt, but the values do look very incorrect.
This is not, as far as I know, caused by your program. My program is
built using Dev2008, and same thing happens.
The message "Missing image name, possible paged-out or corrupt data."
is also part of this pattern.
I assume this does not happen when MS people use private symbols for
these DLLs, otherwise it would have been fixed by now. I was working
this with Roberto Farrah early January this year.
Hope this helps,
Osiris
Hi
I’m only debugging 32 bits app on 32 bits XP SP2 or 3.
I’ receive and debug usermode dumps for our apps from customers.
I have also noted that windbg recently has started to complain about
"Missing image name, possible paged-out or
corrupt data", see my post:
http://groups.google.com/group/microsoft.public.windbg/browse_frm/thread/14ff4ad51e9eaa9b?hl=en#
I’m also not sure if this is a sign of application corruption or
windbg error.
I have opened (new) dumps with the old windbg6.7.05.0 and this version
also complains.
I have opened old dumps from 2008, and on these dumps I don’t see this
error even if the app is the same.
If the explanation is an issue with symbol files, that would explain
why both old and new version of windbg are affected.
I hope to hear (in this group) form others who have seen this
problem.
Regards
Kjell Gunnar