BSOD on Windows 7 when running a driver

-4

When I install my test driver on Windows 7 32 bit, the blue screen of death occurs with error number 0x7f(0x0000000d, 0x00000000, 0x00000000, 0x00000000), but this does not happen on other versions of Windows(10x64bit, 10x32bit, 7x64bit, 8x64bit, 8x32bit). I can not understand why this is happening, please help. Any idea is welcomed. Thanks.

    **************************************************************************
* Bugcheck Analysis:


UNEXPECTED_KERNEL_MODE_TRAP (7f) 
This means a trap occurred in kernel mode, and it's a trap of a kind 
that the kernel isn't allowed to have/catch (bound trap) or that 
is always instant death (double fault). The first number in the 
bugcheck params is the number of the trap (8 = double fault, etc) 
Consult an Intel x86 family manual to learn more about what these 
traps are. Here is a *portion* of those codes: 
If kv shows a taskGate 
use .tss on the part before the colon, then kv. 
Else if kv shows a trapframe 
use .trap on that value 
Else 
.trap on the appropriate frame will show where the trap was taken 
(on x86, this will be the ebp that goes with the procedure KiTrap) 
Endif 
kb will then show the corrected stack. 
Arguments: 
Arg1: 0000000d, EXCEPTION_GP_FAULT 
Arg2: 00000000 
Arg3: 00000000 
Arg4: 00000000 

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


BUGCHECK_STR: 0x7f_d 

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT 

PROCESS_NAME: System 

CURRENT_IRQL: 2 

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre 

LOCK_ADDRESS: 827bb540 -- (!locks 827bb540) 

Resource @ nt!PiEngineLock (0x827bb540) Exclusively owned 
Contention Count = 3 
Threads: 852c24c0-01<*> 
1 total locks, 1 locks currently held 

PNP_TRIAGE: 
Lock address : 0x827bb540 
Thread Count : 1 
Thread address: 0x852c24c0 
Thread wait : 0x60ee 

LAST_CONTROL_TRANSFER: from 82730dff to 826cc9d8 

STACK_TEXT: 
807dd0ec 82730dff 00000003 2bab3b55 00000065 nt!RtlpBreakWithStatusInstruction 
807dd13c 827318fd 00000003 9c1fa01b 86306248 nt!KiBugCheckDebugBreak+0x1c 
807dd500 826927af 0000007f 0000000d 00000000 nt!KeBugCheck2+0x68b 
807dd500 9c1fa01b 0000007f 0000000d 00000000 nt!KiSystemFatalException+0xf 
807dd590 9b6219ce 807dd77c 828183ac 86306248 test_driver!__security_init_cookie+0x1b [d:\wbrtm\minkernel\tools\gs_support\kmodefastfail\gs_support.c @ 45] 
807dd598 828183ac 86306248 85451000 c000035f test_driver!GsDriverEntry+0xa [d:\wbrtm\minkernel\tools\gs_support\kmodefastfail\gs_driverentry.c @ 39] 
807dd77c 828048a7 00000000 00000000 807dd7a4 nt!IopLoadDriver+0x7ed 
807dd828 82848c3f 935cf510 00000001 935cf4fc nt!PipCallDriverAddDeviceQueryRoutine+0x34b 
807dd860 828499ac 00000001 807dd92c c0000034 nt!RtlpCallQueryRegistryRoutine+0x2ea 
807dd8cc 82812768 40000000 80000950 807dd948 nt!RtlQueryRegistryValues+0x31d 
807dd9a8 82811ed7 869e9560 807ddbd0 869e4ea8 nt!PipCallDriverAddDevice+0x383 
807ddba4 828e31df 869e9560 869e4ea8 807ddbd0 nt!PipProcessDevNodeTree+0x15d 
807ddbd8 82665dc7 827b9460 852c24c0 8278f4bc nt!PiRestartDevice+0x8a 
807ddc00 826cf37b 00000000 00000000 852c24c0 nt!PnpDeviceActionWorker+0x1fb 
807ddc50 8285e4ef 00000001 2bab36f9 00000000 nt!ExpWorkerThread+0x10d 
807ddc90 82702a19 826cf26e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 


STACK_COMMAND: kb 

FOLLOWUP_IP: 
test_driver!__security_init_cookie+1b [d:\wbrtm\minkernel\tools\gs_support\kmodefastfail\gs_support.c @ 45] 
9c1fa01b cd29 int 29h 

FAULTING_SOURCE_LINE: d:\wbrtm\minkernel\tools\gs_support\kmodefastfail\gs_support.c 

FAULTING_SOURCE_FILE: d:\wbrtm\minkernel\tools\gs_support\kmodefastfail\gs_support.c 

FAULTING_SOURCE_LINE_NUMBER: 45 

FAULTING_SOURCE_CODE: 
No source found for 'd:\wbrtm.public.x86fre\ddk\inc\wdm.h' 


SYMBOL_STACK_INDEX: 4 

SYMBOL_NAME: test_driver!__security_init_cookie+1b 

FOLLOWUP_NAME: MachineOwner 

MODULE_NAME: test_driver 

IMAGE_NAME: test_driver.sys 

DEBUG_FLR_IMAGE_TIMESTAMP: 5c3c6567 

IMAGE_VERSION: 1.2.0.185 

FAILURE_BUCKET_ID: 0x7f_d_test_driver!__security_init_cookie+1b 

BUCKET_ID: 0x7f_d_test_driver!__security_init_cookie+1b 

ANALYSIS_SOURCE: KM 

FAILURE_ID_HASH_STRING: km:0x7f_d_test_driver!__security_init_cookie+1b 

FAILURE_ID_HASH: {9a9fb459-5e53-2ea7-9385-1f646c7857a7} 

Followup: MachineOwner
c++
windows
kernel
driver
kmdf
asked on Stack Overflow Apr 3, 2019 by I. Sejet

0 Answers

Nobody has answered this question yet.


User contributions licensed under CC BY-SA 3.0