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/
unsigned short addrPort = // has some value in it
unsigned short dataPort = // has some value
unsigned long pciReg = // has some value in it
unsigned long Val = __indword(dataPort);
// do something with Val;
Is this code pattern correct while access a pci device? We sometimes (rarely) see crashes
An exception happened while executing a system service routine.
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80254d0a470, Address of the instruction which caused the bugcheck
Arg3: ffffdb815d8e0920, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Sinse it is an access violation, will adding __try...__except block around the in and out instructions be able to mitigate the blue screen? What is the right way to program this?
|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!|
|Developing Minifilters||24 May 2021||Live, Online|
|Writing WDF Drivers||14 June 2021||Live, Online|
|Internals & Software Drivers||27 September 2021||Live, Online|
|Kernel Debugging||15 November 2021||Live, Online|