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
On Feb 9, 2018, at 10:47 PM, xxxxx@rolle.name wrote:
>
> 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, xxxxx@probo.com
Providenza & Boekelheide, Inc.