Does my driver cause "Access Violation in svchost.exe" ?

Hi,

I have an Ndis driver for Windows XP. It seems to work fine.
But the Windbg might catch an "access violation in svchost.exe" error during
the XP shutdown every thundreds times.

Is the error caused by my Ndis driver? Or, it's a bug of svchost.exe?
Below lists the windbg messages:
=====================================================================
*** An Access Violation occurred in C:\WINDOWS\System32\svchost.exe -k
netsvcs:

The instruction at 00650066 tried to read from an invalid address, 00650066

*** enter .exr 0189F9DC for the exception record
*** enter .cxr 0189F9F8 for the context
*** then kb to get the faulting stack

Break instruction exception - code 80000003 (first chance)
*** WARNING: symbols timestamp is wrong 0x41109494 0x4060f0f2 for ntdll.dll
ntdll!DbgSsHandleKmApiMsg+0x14e:
001b:7c921230 cc int 3
kd>

pavel_a
Wed Mar 16 15:57:04 CST 2005

"Charles" wrote:
> I have an Ndis driver for Windows XP. It seems to work fine.

Does this "access violation in svchost.exe" occur without your driver?
Does this driver also seem to pass ndistest fine?

--PA

> But the Windbg might catch an "access violation in svchost.exe" error during
> the XP shutdown every thundreds times.
>
> Is the error caused by my Ndis driver? Or, it's a bug of svchost.exe?
> Below lists the windbg messages:
> =====================================================================
> *** An Access Violation occurred in C:\WINDOWS\System32\svchost.exe -k
> netsvcs:
>
> The instruction at 00650066 tried to read from an invalid address, 00650066
>
> *** enter .exr 0189F9DC for the exception record
> *** enter .cxr 0189F9F8 for the context
> *** then kb to get the faulting stack
>
> Break instruction exception - code 80000003 (first chance)
> *** WARNING: symbols timestamp is wrong 0x41109494 0x4060f0f2 for ntdll.dll
> ntdll!DbgSsHandleKmApiMsg+0x14e:
> 001b:7c921230 cc int 3
> kd>

Mark
Wed Mar 16 21:31:44 CST 2005

Charles wrote:
> Hi,
>
> I have an Ndis driver for Windows XP. It seems to work fine.
> But the Windbg might catch an "access violation in svchost.exe" error during
> the XP shutdown every thundreds times.
>
> Is the error caused by my Ndis driver? Or, it's a bug of svchost.exe?
> Below lists the windbg messages:
> =====================================================================
> *** An Access Violation occurred in C:\WINDOWS\System32\svchost.exe -k
> netsvcs:
>
> The instruction at 00650066 tried to read from an invalid address, 00650066
>
> *** enter .exr 0189F9DC for the exception record
> *** enter .cxr 0189F9F8 for the context
> *** then kb to get the faulting stack
>
> Break instruction exception - code 80000003 (first chance)
> *** WARNING: symbols timestamp is wrong 0x41109494 0x4060f0f2 for ntdll.dll
> ntdll!DbgSsHandleKmApiMsg+0x14e:
> 001b:7c921230 cc int 3
> kd>
>
>
svchost is a container for a multitude of services. One of those
services is croaking as a result of something unexpected that your
driver is doing. You might want to try to isolate which service that is,
perhaps by using a debugger. A checked install of the entire
distribution might helpful.

--

=====================
Mark Roddy DDK MVP
Windows 2003/XP/2000 Consulting
Hollis Technology Solutions 603-321-1032
www.hollistech.com

Alexander
Thu Mar 17 23:58:08 CST 2005

This seems to be a bug caused by a patch of late. I see this quite often,
too.

"Charles" <charles_lin@dummy.jadecom.com.tw> wrote in message
news:uqhUVngKFHA.3076@tk2msftngp13.phx.gbl...
> Hi,
>
> I have an Ndis driver for Windows XP. It seems to work fine.
> But the Windbg might catch an "access violation in svchost.exe" error
> during
> the XP shutdown every thundreds times.
>
> Is the error caused by my Ndis driver? Or, it's a bug of svchost.exe?
> Below lists the windbg messages:
> =====================================================================
> *** An Access Violation occurred in C:\WINDOWS\System32\svchost.exe -k
> netsvcs:
>
> The instruction at 00650066 tried to read from an invalid address,
> 00650066
>
> *** enter .exr 0189F9DC for the exception record
> *** enter .cxr 0189F9F8 for the context
> *** then kb to get the faulting stack
>
> Break instruction exception - code 80000003 (first chance)
> *** WARNING: symbols timestamp is wrong 0x41109494 0x4060f0f2 for
> ntdll.dll
> ntdll!DbgSsHandleKmApiMsg+0x14e:
> 001b:7c921230 cc int 3
> kd>
>
>