Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.More Info on Driver Writing and Debugging
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/
Bug check IRQL_NOT_LESS_OR_EQUAL
Michael_Rolle
Member - All Emails Posts: 135
in NTDEV
Any ideas what this would be about?
I had my own driver loaded, which has been misbehaving. Then suddenly I got the BSOD, not while I was using the driver.
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x8743D)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80288EACB3F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\win32kbase.sys
I had my own driver loaded, which has been misbehaving. Then suddenly I got the BSOD, not while I was using the driver.
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x8743D)
Bugcheck code: 0xA (0x0, 0x2, 0x1, 0xFFFFF80288EACB3F)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\win32kbase.sys
Howdy, Stranger!
| 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! | ||
| Internals & Software Drivers | 7 February 2022 | Live, Online |
| Kernel Debugging | 21 March 2022 | Live, Online |
| Developing Minifilters | 23 May 2022 | Live, Online |
| Writing WDF Drivers | 12 September 2022 | Live, Online |
Comments
>
> Any ideas what this would be about?
>
> I had my own driver loaded, which has been misbehaving. Then suddenly I got the BSOD, not while I was using the driver.
>
> This was probably caused by the following module: win32kbase.sys (win32kbase+0x8743D)
That's the kernel portion of GDI. It derefenced a null pointer. If your misbehaving driver could possibly have written data outside its bounds, it could easily have trashed memory in a way that wasn't detected until long after.
—
Tim Roberts, [email protected]
Providenza & Boekelheide, Inc.
Tim Roberts, [email protected]
Providenza & Boekelheide, Inc.