BSOD with Driver Verifier and Norton Antivirus

NTFSD
1

On 21 Feb 2002, “Tan Sin Lam” wrote that running Driver Verifier on his
filter driver on WinXP with Norton AntiVirus 2002 caused a crash. The
stop code was generated by the verifier (C4 =
DRIVER_VERIFIER_DETECTED_VIOLATION), and the parameter was P1 = 90, which
the DDK tells us indicates “The driver switched stacks, and the current
stack is neither a thread stack nor a DPC stack (Typically, the driver
doing this should be on the stack obtained by the KB debugger command.).”

The replies to this message blamed NAV: “Nicholas Ryan” said he’d
research more into this problem; and “Neal Christiansen” said “is a known
issue with NAV and the verifier if you have deadlock detection enabled”.
Does anyone have more info on this NAV bug? If it is a “known issue”,
have Symantec addressed the problem, and have they released a fix for it?

I’m asking because I’m in a similar situation, having come across a crash
and run Driver Verifier to try to get to the bottom of it. My problem
arises on W2K and XP, with NAV installed; I have a file system filter
driver which attaches to the CD-ROM. I frequently get a BSOD (due to a
page fault) when swapping CD-ROMs, and SYMEVENT, the NAV driver, is most
often in the stack. There are actually four or five different stack
scenarios when the machine BSODs (mostly involving SYMEVENT), which makes
me think that I’m seeing the knock-on effect of some previous bug.

I’d like to be able to blame Symantec, and point customers to a NAV patch
to fix it. Any ideas?

Gavin

2

I had a conversation with Symantec’s CTO earlier this year. He said you
can run Driver Verifier with Symantec, but you shouldn’t turn on
deadlock detection.

On the other hand, I know that you’re not the only one who is having
difficulties with the creativity of Symantec …

Bartjan.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gavin Dempster
Sent: vrijdag 23 augustus 2002 15:27
To: File Systems Developers
Subject: [ntfsd] BSOD with Driver Verifier and Norton Antivirus

On 21 Feb 2002, “Tan Sin Lam” wrote that
> running Driver Verifier on his filter driver on WinXP with
> Norton AntiVirus 2002 caused a crash. The stop code was
> generated by the verifier (C4 =
> DRIVER_VERIFIER_DETECTED_VIOLATION), and the parameter was P1
> = 90, which the DDK tells us indicates “The driver switched
> stacks, and the current stack is neither a thread stack nor a
> DPC stack (Typically, the driver doing this should be on the
> stack obtained by the KB debugger command.).”
>
> The replies to this message blamed NAV: “Nicholas Ryan”
> said he’d research more into this
> problem; and “Neal Christiansen”
> said “is a known issue with
> NAV and the verifier if you have deadlock detection enabled”.
> Does anyone have more info on this NAV bug? If it is a
> “known issue”, have Symantec addressed the problem, and have
> they released a fix for it?
>
> I’m asking because I’m in a similar situation, having come
> across a crash and run Driver Verifier to try to get to the
> bottom of it. My problem arises on W2K and XP, with NAV
> installed; I have a file system filter driver which attaches
> to the CD-ROM. I frequently get a BSOD (due to a page fault)
> when swapping CD-ROMs, and SYMEVENT, the NAV driver, is most
> often in the stack. There are actually four or five
> different stack scenarios when the machine BSODs (mostly
> involving SYMEVENT), which makes me think that I’m seeing the
> knock-on effect of some previous bug.
>
> I’d like to be able to blame Symantec, and point customers to
> a NAV patch to fix it. Any ideas?
>
> Gavin
>
> —
> You are currently subscribed to ntfsd as: xxxxx@zeelandnet.nl
> To unsubscribe send a blank email to %%email.unsub%%
>