BugCheck 0x1E with no arguments

Hi all,
I have a memory dump to analyze from a field unit. I’ve never seen BugCheck 0x1E with all zero arguments before though - could it have something to do with the “Page 614f34 not present in the dump file” warning?

It seems the bugcheck happens somewhere inside MmMapLockedPagesWithReservedMapping(), but the addresses and MDL I’m passing it look OK to me.

18: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:

Page 614f34 not present in the dump file. Type “.hh dbgerr004” for details

[…]

fffff8800b7ba810 fffff88002430306 : fffff8800b7aa000 fffff8803170616d fffffa8015ff4b50 0000000000000001 : nt!MmMapLockedPagesWithReservedMapping+0x153

18: kd> dt _MDL 0xfffffa8015ff4b50 nt!_MDL +0x000 Next : (null) +0x008 Size : 0n56 +0x00a MdlFlags : 0n8 +0x010 Process : (null) +0x018 MappedSystemVa : 0xfffffa80309ff000 Void
+0x020 StartVa : 0xfffff880`0b7aa000 Void
+0x028 ByteCount : 0x200
+0x02c ByteOffset : 0

18: kd> db 0xfffff8800b7aa000 fffff8800b7aa000 ?? ?? ?? ?? ?? ?? ?? ??-?? ?? ?? ?? ?? ?? ?? ??
???
(as expected since MmMapLockedPagesWithReservedMapping hasn’t returned)

Show the call stack or !analyze -v