This repo contains driver samples prepared for use with Microsoft Visual Studio and the Windows Driver Kit (WDK). It contains both Universal Windows Driver and desktop-only driver samples.
On one of out tests setups we are experiencing bugcheck 7F EXCEPTION_DOUBLE_FAULT as shown below. The user mode context of the faulting thread is our .net GUI application i.e. when it is in the process of being terminated via script (using pskill). The crash is random in that sometimes pskill on the process does not bugcheck the system. Earlier I came across this post which looks similar to the issue we are facing.
Since this is an automation setup I am nor sure exactly what is the UI state of the application. Presumably there are several error popups which could be active at the point when pskill is initiated on our process. Just wanted to understand if there's any way in which we could circumvent this issue ? With that I am assuming that generally and under no circumstance should UM code be able to trigger a KM bugcheck.
The OS is Windows Server 2009 standard edition and is up to date with the latest patchs as of this writing. Earlier there was wdfilter,sys also in the call stack which I disable via local group policy. But the crash persists even without wdfilter in the call stack.
12: kd> vertarget
Windows 10 Kernel Version 17763 MP (24 procs) Free x64
Product: Server, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff8013da08000 PsLoadedModuleList = 0xfffff8013de21710
Debug session time: Mon Feb 10 17:05:28.677 2020 (UTC - 8:00)
System Uptime: 0 days 11:47:46.778
On one of out tests setups we are experiencing bugcheck 7F EXCEPTION_DOUBLE_FAULT as shown below. The user mode context of the faulting thread is our .net GUI application i.e. when it is in the process of being terminated via script (using pskill). The crash is random in that sometimes pskill on the process does not bugcheck the system. Earlier I came across this post which looks similar to the issue we are facing.
http://kitrap08.blogspot.com/2015/02/
Since this is an automation setup I am nor sure exactly what is the UI state of the application. Presumably there are several error popups which could be active at the point when pskill is initiated on our process. Just wanted to understand if there's any way in which we could circumvent this issue ? With that I am assuming that generally and under no circumstance should UM code be able to trigger a KM bugcheck.
The OS is Windows Server 2009 standard edition and is up to date with the latest patchs as of this writing. Earlier there was wdfilter,sys also in the call stack which I disable via local group policy. But the crash persists even without wdfilter in the call stack.
12: kd> vertarget Windows 10 Kernel Version 17763 MP (24 procs) Free x64 Product: Server, suite: TerminalServer SingleUserTS Built by: 17763.1.amd64fre.rs5_release.180914-1434 Machine Name: Kernel base = 0xfffff8013da08000 PsLoadedModuleList = 0xfffff8013de21710 Debug session time: Mon Feb 10 17:05:28.677 2020 (UTC - 8:00) System Uptime: 0 days 11:47:46.778
12: kd> .bugcheck Bugcheck code 0000007F Arguments 0000000000000008 ffffde801ff4ce50 ffffc30318ce3eb0 fffff8013dbcf6d4
12: kd> !sysinfo machineid Machine ID Information [From Smbios 2.7, DMIVersion 0, Size=5393] BiosMajorRelease = 0 BiosMinorRelease = 0 FirmwareMajorRelease = 0 FirmwareMinorRelease = 0 BiosVendor = Intel Corporation BiosVersion = SE5C610.86B.01.01.0014.121820151719 BiosReleaseDate = 12/18/2015 SystemManufacturer = Intel Corporation SystemProductName = S2600WT2R SystemFamily = Family SystemVersion = .................... SystemSKU = SKU Number BaseBoardManufacturer = Intel Corporation BaseBoardProduct = S2600WT2R BaseBoardVersion = H21573-366
12: kd> !sysinfo cpuinfo [CPU Information] ~MHz = REG_DWORD 2394 Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0 Identifier = REG_SZ Intel64 Family 6 Model 63 Stepping 2 ProcessorNameString = REG_SZ Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz Update Status = REG_DWORD 0 VendorIdentifier = REG_SZ GenuineIntel MSR8B = REG_QWORD 3c00000000