In WinDbg I am getting the following on a checked build of Windows 7
(32-bit):
*** Display Driver Model assertion failure detected @90648031.
Break to debug, Ignore, ignore All (bia)? a
So since the address is different on every boot, I thought perhaps I
can base the address on the dxgkrnl.sys module inside of which the
assertion happens:
kd> !address 0x90648031
Mapping user range …
Mapping system range …
Mapping page tables…
Mapping hyperspace…
Mapping HAL reserved range…
Mapping User Probe Area…
Mapping system shared page…
Mapping VAD regions…
Mapping module regions…
Mapping process, thread, and stack regions…
Mapping system cache regions…
Usage: Module
Base Address: 9063c000
End Address: 9070f000
Region Size: 000d3000
VA Type: DriverImages
Module name: dxgkrnl.sys
Module path: [\SystemRoot\System32\drivers\dxgkrnl.sys]
But that’s how far I can get.
So I *can* issue ahi dxgkrnl+0xC031
in my startup script, but that
will merely give me:
kd> ahi dxgkrnl+0xC031
Couldn’t resolve error at ‘dxgkrnl+0xC031’
… since the module has not been loaded when the debugger connects.
How would I go about to execute this automatically as soon as
dxgkrnl.sys has been loaded? Is there a way?
Thanks,
// Oliver