Win 7 64bit
Dell Latitude 7240
Dell Wireless 5808 LTE Mobile Broadband
We have several users with Latitude 7240's which are experiencing BSOD's and pointing to a driver for the Sierra Wireless card. Users will all experience the same thing:
Upon boot up they get a Blue Screen (sometimes 2 or 3) and upon subsequent restarts are able to pass through. I've already tried a number of things such as using different versions of the driver in question, delaying services etc. but nothing appears to be working. Has anyone seen this behavior or know of a problem with this driver and Win 7 compatability issues?
******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************
SYSTEM_PTE_MISUSE (da) A driver has corrupted system PTEs. Set HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackPtes to a DWORD 3 value and reboot. If the same bugcheck occurs again the stack trace will identify the offending driver. Arguments: Arg1: 0000000000000006, The MDL being freed was never (or is currently not) mapped. Arg2: 0000000000000000, The MDL specified by the driver. Arg3: fffff880069ed000, The virtual address specified by the driver. Arg4: 0000000000000002, The number of PTEs to free (specified by the driver).
Debugging Details: ------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0xDA
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER: from fffff8000316e96d to fffff800030bda40
STACK_TEXT: fffff880`06959288 fffff800`0316e96d : 00000000`000000da 00000000`00000006 00000000`00000000 fffff880`069ed000 : nt!KeBugCheckEx fffff880`06959290 fffff800`03123a8c : fffff880`069edb90 00000000`000011d6 00000000`00000002 fffff880`07c00000 : nt!MiRemovePteTracker+0xed fffff880`069592f0 fffff880`079ee0fa : 00000000`00000001 fffffa80`0c6091a0 fffffa80`0c272960 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2611d fffff880`06959340 00000000`00000001 : fffffa80`0c6091a0 fffffa80`0c272960 00000000`00000000 fffff880`079f6100 : swg3kser05+0x380fa fffff880`06959348 fffffa80`0c6091a0 : fffffa80`0c272960 00000000`00000000 fffff880`079f6100 00000000`c0000034 : 0x1 fffff880`06959350 fffffa80`0c272960 : 00000000`00000000 fffff880`079f6100 00000000`c0000034 00000000`000ecb90 : 0xfffffa80`0c6091a0 fffff880`06959358 00000000`00000000 : fffff880`079f6100 00000000`c0000034 00000000`000ecb90 ffffffff`80000294 : 0xfffffa80`0c272960
STACK_COMMAND: kb
FOLLOWUP_IP: swg3kser05+380fa fffff880`079ee0fa ?? ???
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: swg3kser05+380fa
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: swg3kser05
IMAGE_NAME: swg3kser05.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 54207102
FAILURE_BUCKET_ID: X64_0xDA_swg3kser05+380fa
BUCKET_ID: X64_0xDA_swg3kser05+380fa
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_0xda_swg3kser05+380fa
FAILURE_ID_HASH: {958810fe-9484-b470-a5e7-5929dd62f67b}
Followup: MachineOwner ---------