Re: !verifier 3 mydriver.sys gives Contiguous allocations are not displayed

WINDBG
1

Hi Sachin,

Can you load the symbols properly. When the crash happens then check which
function causing the issue.

Regards
Mallesh

On Tue, Dec 15, 2015 at 11:49 AM, wrote:

> Hello,
>
> Wanted some help regarding verifier error forgotten to free memory,
>
> MODULE: 0xfffffa8000c1d8c0 mydriver.sys (Loaded&Unloaded)
>
> Pool Allocation Statistics: ( NonPagedPool / PagedPool )
>
> Current Pool Allocations: ( 0x0000003c / 0x00000000 )
> Current Pool Bytes: ( 0x0001e000 / 0x00000000 )
> Peak Pool Allocations: ( 0x00000041 / 0x00000013 )
> Peak Pool Bytes: ( 0x0001fa50 / 0x00001d48 )
> Contiguous Memory Bytes: 0x00000000
> Peak Contiguous Memory Bytes: 0x00000000
>
> Pool Allocations:
>
> Address Length Tag Caller Address
> ------------------ ---------- ---- ------------------
> 0x0000000000000000 0x00000000 … 0x0000000000000000
> 0x0000000000000000 0x00000000 … 0x0000000000000000
> 0x0000000000000000 0x00000000 … 0x0000000000000000
> 0x0000000000000000 0x00000000 … 0x0000000000000000
> 0x0000000000000000 0x00000000 … 0x0000000000000000
> 0x0000000000000000 0x00000000 … 0x0000000000000000
>
> 0x0000000000000000 0x00000000 … 0x0000000000000000
> 0x0000000000000000 0x00000000 … 0x0000000000000000
>
> Contiguous allocations are not displayed with public symbols.
> Why its giving Function ptr 0x0000000000000000
>
>
> any help would be really helpful.
>
> Thanks,
> ~Sachin
>
>
> —
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:>

2

Thanks Mallesh,

Tried with reloaded symbols but same result, not displaying function pointers as expected.
Address Length Tag Caller Address

0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
…
Contiguous allocations are not displayed with public symbols.

3

Which OS release is this and which version of WinDbg?

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@windbg…

Thanks Mallesh,

Tried with reloaded symbols but same result, not displaying function
pointers as expected.
Address Length Tag Caller Address

0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
0x0000000000000000 0x00000000 … 0x0000000000000000
…
Contiguous allocations are not displayed with public symbols.

4

Hi Scott,

WinDBG version is 6.3.9600
OS is windows 7 64 bit

~Thanks
Sachin

5

I’m getting valid output with a Win7 x86 target and WinDbg v10.0.10586 (from
latest WDK update):

Address Length Tag Caller

0xa0982e00 0x00000200 xxxx 0x9679132d Nothing!DriverEntry+0x8d

I would try upgrading your debugger version.

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@windbg…

Hi Scott,

WinDBG version is 6.3.9600
OS is windows 7 64 bit

~Thanks
Sachin

6

If your loading symbols first time make sure that your are connected to
INTERNET. Because windbg will load the symbols from the MSDN site to
resolve the predefined symbols.
After that while loading follow these steps:
Windbg commands:
1)!symfix
2)Load the symbol path and src path
Symbolpath: start by putting the semicolon.
i.e sym;path
3)!sym noisy
4).reload /f

Regards
Mallesh

On Thu, Dec 17, 2015 at 2:57 AM, Scott Noone wrote:

> I’m getting valid output with a Win7 x86 target and WinDbg v10.0.10586
> (from latest WDK update):
>
>
> Address Length Tag Caller
> ---------- ---------- ---- ----------
> 0xa0982e00 0x00000200 xxxx 0x9679132d Nothing!DriverEntry+0x8d
>
> I would try upgrading your debugger version.
>
> -scott
> OSR
> @OSRDrivers
>
>
>
>
> wrote in message news:xxxxx@windbg…
>
>
> Hi Scott,
>
> WinDBG version is 6.3.9600
> OS is windows 7 64 bit
>
> ~Thanks
> Sachin
>
> —
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer&gt;
></http:>