Question Can someone help me to know what driver causes the BSOD

Aug 9, 2022
1
0
10
0
Hi here it is the analysis of the dump file by windbg :

*
  • *
  • Bugcheck Analysis *
  • *
***

INVALID_MDL_RANGE (12e)
A driver has called the IoBuildPartialMdl() function and passed it an MDL
to map part of a source MDL, but the virtual address range specified is
outside the range in the source MDL. This is a driver bug. The source
and target MDLs, as well as the address range length to be mapped are the
arguments to the IoBuildPartialMdl() function, i.e.;
IoBuildPartialMdl(
IN PMDL SourceMdl,
IN OUT PMDL TargetMdl,
IN PVOID VirtualAddress,
IN ULONG Length
)
Arguments:
Arg1: ffffcf05353cd110
Arg2: ffffcf052ab3d430
Arg3: 000001e49f120600
Arg4: 000000000000013d

Debugging Details:
------------------

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3499

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3576

Key : Analysis.Init.CPU.mSec
Value: 1328

Key : Analysis.Init.Elapsed.mSec
Value: 3361

Key : Analysis.Memory.CommitPeak.Mb
Value: 102

Key : Bugcheck.Code.DumpHeader
Value: 0x12e

Key : Bugcheck.Code.KiBugCheckData
Value: 0x12e

Key : Bugcheck.Code.Register
Value: 0x12e

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 12e

BUGCHECK_P1: ffffcf05353cd110

BUGCHECK_P2: ffffcf052ab3d430

BUGCHECK_P3: 1e49f120600

BUGCHECK_P4: 13d

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: Shatterline.exe

STACK_TEXT:
ffffee8eec986688 fffff8026da6ab65 : 000000000000012e ffffcf05353cd110 ffffcf052ab3d430 000001e49f120600 : nt!KeBugCheckEx
ffffee8eec986690 fffff8026f79bce5 : 000000000000013d ffffcf052ab3d430 0000000000000000 000000000000013d : nt!IoBuildPartialMdl+0x155da5
ffffee8eec9866d0 fffff8026f79b984 : 000001e49f120600 000000000000013d ffffcf0531b10390 0000000000000000 : tcpip!UdpCreateDatagram+0x155
ffffee8eec986740 fffff8026f79b05a : 0000000000008a75 ffffcf0524837280 ffffcf0524838a75 ffffcf0524837280 : tcpip!UdpSegmentMessage+0x164
ffffee8eec986870 fffff8026f79a70c : 0000000000000000 0000000000000000 000000480a1070f6 0000000000000004 : tcpip!UdpSendMessagesOnPath+0x2ca
ffffee8eec986d10 fffff8026f79a455 : ffffcf05341e1401 fffff8026f79a440 ffffee8eec987190 ffffee8eec987190 : tcpip!UdpSendMessages+0x29c
ffffee8eec987080 fffff8026d87ca68 : ffffee8eec9872c0 0000000000000000 f6e3c51200000000 000000000000000c : tcpip!UdpTlProviderSendMessagesCalloutRoutine+0x15
ffffee8eec9870b0 fffff8026d87c9dd : fffff8026f79a440 ffffee8eec987190 0000000000000000 fffff805b4bac996 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffffee8eec987120 fffff8026f7e67ab : 00000001ffffffff fffffff600000011 ffffee8eec987290 fffff805b4bac915 : nt!KeExpandKernelStackAndCalloutEx+0x1d
ffffee8eec987160 fffff805b4ba9cb8 : 0000000000000000 ffffee8eec987b40 ffffcf0534b93660 ffffee8eec987b40 : tcpip!UdpTlProviderSendMessages+0x7b
ffffee8eec9871e0 fffff805b4ba9175 : ffffcf0535243c10 000000000000003f ffffcf0534b93660 ffffcf0532980df0 : afd!AfdRioFlushDgramSend+0x644
ffffee8eec987420 fffff805b4bca2e8 : ffffcf0532980df0 0000000000000000 000000a7e64ff700 0000000000000000 : afd!AfdRioFastIo+0x5f1
ffffee8eec987500 fffff8026dbf4bb8 : 00000000000047e0 ffff88813e981440 ffffcf0531e7a080 ffffcf0535243c10 : afd!AfdFastIoDeviceControl+0x7268
ffffee8eec9878a0 fffff8026dbf4476 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!IopXxxControlFile+0x728
ffffee8eec9879e0 fffff8026da09fb8 : 0000000000000000 000001e539ccc2f8 0000000000000000 ffff88813eba6180 : nt!NtDeviceIoControlFile+0x56
ffffee8eec987a50 00007ffa72f8d024 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000a7e64ff5a8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffa`72f8d024


SYMBOL_NAME: tcpip!UdpCreateDatagram+155

MODULE_NAME: tcpip

IMAGE_NAME: tcpip.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 155

FAILURE_BUCKET_ID: 0x12E_VRF_tcpip!UdpCreateDatagram

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c4dd91ca-2e30-62d8-8c8d-e365e04a250f}

Followup: MachineOwner
---------

Tried installing the latest version of Ethernet drivers - didn't help
 

Ralston18

Titan
Moderator
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): Make, model, capacity, how full?

Look in Reliability History and Event Viewer for error codes, warnings, or even informational events that are captured just before or at the time of the BSODs.

Reliability History is easier to use so start there. The time line format can be very revealing with respect to errors and patterns.

You can also try running the built in Windows troubleshooters. The troubleshooters may find and fix something.

Also try "sfc /scannow" and "dism".

References:

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image
 

Colif

Win 11 Master
Moderator
Jun 12, 2015
58,099
4,713
161,190
10,348
INVALID_MDL_RANGE (12e)
thats a new one. can't say I seen that BSOD before

Error appears to be internet related
tcpip.sys - transmission control protocol/internet protocol
afd.sys - anciliary function driver for winsock.

both used by windows to talk to lan drivers so that is where I would start... I see you did.

DXDiag doesn't show Motherboard details.

my 1st reaction to bsod I haven't seen before is
Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors. Memtest is created as a bootable USB so that you don’t need windows to run it

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
 

ASK THE COMMUNITY