The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
This is a new problem that hasn't happened to me before. When I call one of the synchronization routines, like
KeDelayExecutionThread, while debugging, WinDbg breaks and shows
KiSwapContext threw an access violation.
Access violation - code c0000005 (!!! second chance !!!) nt!KiSwapContext+0xf: fffff800`021c81ff 0f29742430 movaps xmmword ptr [rsp+30h],xmm6
The actual driver code goes along something like this:
/*This is DriverEntry */ _disable(); // Do stuff with no interrupts here _enable(); KIRQL old = KeRaiseIrqlToDpcLevel(); //Do stuff with IRQL DISPATCH_LEVEL KeLowerIrql(PASSIVE_LEVEL) KeWaitForSingleObject(threadObject, Executive, KernelMode, FALSE, NULL);
If anyone knows why the last line is causing access violations within
KiSwapContext, that'd be great.
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!||Kernel Debugging||30 Mar 2020||OSR Seminar Space|
|Developing Minifilters||15 Jun 2020||LIVE ONLINE|
|Writing WDF Drivers||22 June 2020||LIVE ONLINE|
|Internals & Software Drivers||28 Sept 2020||Dulles, VA|