Re: [printer rendering driver] KERNEL_MODE_EXCEPTION_NOT_HANDLED in vSrcCopyS24D24Identity
- From: "Dan Mihai [MSFT]" <dmihai@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 4 Jan 2008 12:43:19 -0800
Driver Verifier can catch various driver bugs regardless of what kind of kernel driver you are testing (including GDI drivers). We recently fixed the Verifier documentation (http://msdn2.microsoft.com/en-us/library/ms792857.aspx) to stop discouranging folks from verifying GDI drivers. Of course, Verifier doesn't catch *every* driver bug.
If you want to give it another try, Driver Verifier Standard Settings are the most appropriate for most testers:
verifier.exe /standard /driver yourdriver.sys
Then reboot and if you have a kernel debugger attached, you should see a message in the debugger similar to "Driver Verifier enabled for driver yourdriver.sys...".
"verifier.exe /reset" will disable Verifier.
Dan
--
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Tim Roberts" <timr@xxxxxxxxx> wrote in message news:2uhbn3pt2lu37kjfsbrrd5urt4jeffokmf@xxxxxxxxxx
Francesco Montorsi <fr_m@xxxxxxxxxxx> wrote:
Volodymyr Shcherbyna ha scritto:Could be a memory corruption problem in your code. Run your driver underI've added my driver to the list of drivers to check in verifier.exe with full
verifier.exe with full check options ON.
check options ON. However even after I try to print to the driver from e.g.
notepad/wordpad, the verifier still says that the driver has never been loaded.
This also after several reboots...
Verifier works with WDM drivers. GDI drivers are not WDM drivers. You
can't use verifier with it.
I doubt this can be the cause since my driver is not writing anything in memory;
just files on the hard disk.
Could it be that even if I create an opaque surface in DrvEnableSurface,
How did you do that?
...GDI somehow tries to access the surface's memory itself (and in this case,
since the surface has no real bits associated it crashes with a BSOD)?
Assuming you have a device-managed surface, GDI will only do this if you
punt to the Eng calls.
--
Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.
.
- Prev by Date: Re: DeviceIoControl problem in vista
- Next by Date: Re: [OT] Did you try ReactOS?
- Previous by thread: [OT] Did you try ReactOS?
- Next by thread: Re: Illegal instruction - code c000001d (!!! second chance !!!)
- Index(es):
Relevant Pages
|
