A printer driver that was written and compiled using NTDDK was working fine
for Windows 2000/XP. After installing XP SP2 the printer driver now causes a
memory access violation in explorer.exe when selecting 'Printer Preferences'
from the printer driver's property page about 4 out of 5 times. After
re-compiling the driver with the current SDK (WINDDK\3790) it still has the
same problem but only 1 in about 10 times does the access violation occur.

Any help is appreciated. Thanks.

RE: Windows XP SP2 Printer Driver problem... by bobbym

bobbym
Mon Sep 20 18:13:19 CDT 2004

------=_NextPart_0001_EB865A10
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Hi Tim,
Have you tried debugging it and looking at the callstack?
Most likely you have a memory overwrite.
Try running the prefast tool on your driver build to see whether it can
detect anything.
Also you can also try enabling pageheap.

--------------------

A printer driver that was written and compiled using NTDDK was working fine
for Windows 2000/XP. After installing XP SP2 the printer driver now causes
a
memory access violation in explorer.exe when selecting 'Printer
Preferences'
from the printer driver's property page about 4 out of 5 times. After
re-compiling the driver with the current SDK (WINDDK\3790) it still has the
same problem but only 1 in about 10 times does the access violation occur.

Any help is appreciated. Thanks.


Hope this helps.

Thank you,
Bobby Mattappally
Microsoft

This posting is provided "AS IS" with no warranties, and confers no rights.

------=_NextPart_0001_EB865A10
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Hi Tim,
\par Have you tried debugging it and looking at the callstack?
\par Most likely you have a memory overwrite.
\par Try running the prefast tool on your driver build to see whether it can detect anything.
\par Also you can also try enabling pageheap.
\par
\par \pard\li720 --------------------
\par
\par A printer driver that was written and compiled using NTDDK was working fine
\par for Windows 2000/XP. After installing XP SP2 the printer driver now causes a
\par memory access violation in explorer.exe when selecting 'Printer Preferences'
\par from the printer driver's property page about 4 out of 5 times. After
\par re-compiling the driver with the current SDK (WINDDK\\3790) it still has the
\par same problem but only 1 in about 10 times does the access violation occur.
\par
\par Any help is appreciated. Thanks.
\par \pard
\par
\par Hope this helps.
\par
\par Thank you,
\par Bobby Mattappally
\par Microsoft
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par }
------=_NextPart_0001_EB865A10--


Re: Windows XP SP2 Printer Driver problem... by Feng

Feng
Tue Sep 21 14:01:05 CDT 2004

Each access violation needs to be invetigated in details individually.

You can start with dumping the register values, a few instructions, and call
stack. Or create a memory dump for debugging.

--
Feng Yuan (www.fengyuan.com)

This posting is provided "AS IS" with no warranties, and confers no rights.


"Tim D" <Tim D@discussions.microsoft.com> wrote in message
news:88426D32-7D92-4A27-AB15-6ECEDD95FC65@microsoft.com...
> A printer driver that was written and compiled using NTDDK was working
fine
> for Windows 2000/XP. After installing XP SP2 the printer driver now causes
a
> memory access violation in explorer.exe when selecting 'Printer
Preferences'
> from the printer driver's property page about 4 out of 5 times. After
> re-compiling the driver with the current SDK (WINDDK\3790) it still has
the
> same problem but only 1 in about 10 times does the access violation occur.



Re: Windows XP SP2 Printer Driver problem... by TimD

TimD
Fri Sep 24 08:13:07 CDT 2004


This problem has been fixed.

It was a simple matter of zeroing out the DLGPAGE data structure before
setting it's values and passing it to COMPROPSHEETUI in the pDlgPage member.

Thanks for the help.



"Feng Yuan [MSFT]" wrote:

> Each access violation needs to be invetigated in details individually.
>
> You can start with dumping the register values, a few instructions, and call
> stack. Or create a memory dump for debugging.
>
> --
> Feng Yuan (www.fengyuan.com)
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Tim D" <Tim D@discussions.microsoft.com> wrote in message
> news:88426D32-7D92-4A27-AB15-6ECEDD95FC65@microsoft.com...
> > A printer driver that was written and compiled using NTDDK was working
> fine
> > for Windows 2000/XP. After installing XP SP2 the printer driver now causes
> a
> > memory access violation in explorer.exe when selecting 'Printer
> Preferences'
> > from the printer driver's property page about 4 out of 5 times. After
> > re-compiling the driver with the current SDK (WINDDK\3790) it still has
> the
> > same problem but only 1 in about 10 times does the access violation occur.
>
>
>