Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unable to enumerate user-mode unloaded modules

2,088 views
Skip to first unread message

Nidhi Malik

unread,
Sep 19, 2007, 7:27:03 AM9/19/07
to
Hi all,
My WinDbg is started behaving differently.First it give messsage "Unable to
enumerate user-mode unloaded modules, Win32 error 0n30". When i try to
debug the driver of test machine ,it does not alow me . Giving following
error:

1: kd> .reload
Connected to Windows Vista 6000 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.......................................................................................................................................
Loading User Symbols
............................................................
Loading unloaded module list
......Unable to enumerate user-mode unloaded modules, Win32 error 0n30
*** ERROR: Module load completed but symbols could not be loaded for
Wipe.sys
*** ERROR: Module load completed but symbols could not be loaded for
diskfilter.sys
1: kd> .reload
Connected to Windows Vista 6000 x86 compatible target, ptr64 FALSE
Loading Kernel Symbols
.......................................................................................................................................
Loading User Symbols
............................................................
Loading unloaded module list
......Unable to enumerate user-mode unloaded modules, Win32 error 0n30
*** ERROR: Module load completed but symbols could not be loaded for
Wipe.sys
*** ERROR: Module load completed but symbols could not be loaded for
diskfilter.sys
1: kd> bl
0 eu 0001 (0001) (install!StartDriver)
1 eu 0001 (0001)
(@@masm(`Wipe!c:\winddk\6001\src\extra\wipenew\sys\wipe.c:178+`))
2 eu 0001 (0001) (kbfiltr!DriverEntry)
3 eu 0001 (0001) (diskfilter!DriverEntry)
4 eu 0001 (0001) (Wipe!DriverEntry)
6 eu 0001 (0001) (nonpnp!DriverEntry)
7 eu 0001 (0001) (wdffltr!DriverEntry)

1: kd> g
Breakpoint 3's offset expression evaluation failed.
Check for invalid symbols or bad syntax.
WaitForEvent failed
nt!RtlpBreakWithStatusInstruction+0x1:
81c35499 c20400 ret 4
1: kd> g
Breakpoint 3's offset expression evaluation failed.
Check for invalid symbols or bad syntax.
WaitForEvent failed
nt!RtlpBreakWithStatusInstruction+0x1:
81c35499 c20400 ret 4
1: kd> g
Breakpoint 3's offset expression evaluation failed.
Check for invalid symbols or bad syntax.
WaitForEvent failed
nt!RtlpBreakWithStatusInstruction+0x1:
81c35499 c20400 ret 4


If anybody can help me out
Thanks in advance
Nidhi

Pat Styles [MSFT]

unread,
Sep 24, 2007, 2:16:03 PM9/24/07
to
Hello Nidhi.

This looks like a simple case that symbols are not loaded for the module in
question. That would cause all the breakpoints within that module to go
unresolved. This is also backed up by the error message you are seeing.
Have you examined the debugger help on "symbols"? It contains a lot of
information on how to triage symbol problems.

.pat styles [microsoft}

"Nidhi Malik" <nidhi...@stellarinfo.com> wrote in message
news:eRtrb$q#HHA...@TK2MSFTNGP06.phx.gbl...

0 new messages