Stop screen

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I got a stop screen 0x00000040 TARGET_MDL_TOO_SMALL which relates to a driver bud where some bad programming was involved from msdn

The TARGET_MDL_TOO_SMALL bug check has a value of 0x00000040. This indicates that a driver has improperly used IoBuildPartialMdl

Parameter
Non

Caus
This is a driver bug. A driver has called the IoBuildPartialMdl function and passed it an MDL to map part of a source MDL, but the target MDL is not large enough to map the entire range of addresses requested

The source and target MDLs, as well as the address range length to be mapped, are the arguments to the IoBuildPartialMdl function

IoBuildPartialMdl
IN PMDL SourceMdl
IN OUT PMDL TargetMdl
IN PVOID VirtualAddress
IN ULONG Lengt


How do i find which driver is making this procedure call and crashing my w2k Sp4. Can I use dumpcheck to go thru the dump file to identify the driver concerned???
 
--------------------
Thread-Topic: Stop screen
thread-index: AcRJJxHnngmV3LL5SMuPK8tRWMYKAQ==
X-WN-Post: microsoft.public.win2000.general
From: =?Utf-8?B?U2FyYXZhbmFu?= <[email protected]>
Subject: Stop screen
Date: Wed, 2 Jun 2004 21:56:02 -0700
I got a stop screen 0x00000040 TARGET_MDL_TOO_SMALL which relates to a
driver bud where some bad programming was involved from msdn

The TARGET_MDL_TOO_SMALL bug check has a value of 0x00000040. This
indicates that a driver has improperly used IoBuildPartialMdl.
[SNIP]
Cause
This is a driver bug. A driver has called the IoBuildPartialMdl function
and passed it an MDL to map part of a source MDL, but the target MDL is not
large enough to map the entire range of addresses requested.
[SNIP]

How do i find which driver is making this procedure call and crashing my
w2k Sp4. Can I use dumpcheck to go thru the dump file to identify the
driver concerned???---------------------

**** LINKS ****
Bugcheck Codes and Info:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ddtools/hh/
ddtools/bcintro_3dkj.asp

Debugging Tools Download:
http://www.microsoft.com/downloads/details.aspx?FamilyID=7c6ec49c-a8f7-4323-
b583-6a7a6aeb5e66&displaylang=en

Debugging Tools and Symbols: Getting Started
http://www.microsoft.com/whdc/devtools/debugging/debugstart.mspx

TIP: Entering the "!analyze -v" will analyze the dump. "lvm" will show you
the loaded modules, one of which should be your driver


--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
Back
Top