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???
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???