I've been having some problems with defender, during the night defender is
scheduled to do a scan and during that time it causes a stop error
(0x0000000A). When i turn off the defender service, there are no issues.

Now the build i am running is a clean build, with latest Nvidia Drivers and
the most recent creative drivers for my Audigy 2 ZS card. I use kasperksy as
my AV and have ZoneAlarm Pro as my Firewall.

I can do a scan manually and there's not a issue but when it is done as a
schedule task it breaks the machine. There are no other problems with the
machine only this one.

I would be most appreciated if i could get a resolution to this problem. is
there a way to enable a debug log for defender so i a better trail to follow
in fixing this.

Are these crashes generating events in the System event log? In addition to
what Engel mentions--look for crash events--they may give the name of the
driver involved.

I don't know what the difference would be between a scheduled scan and a
manually initiated one--that's strange.

However--if this persists, I'd stop running scheduled scans--this is risky.

--

"Lokiarmos" <2198234981234810834@Localhost> wrote in message
news:32B777F2-A560-4A29-86DA-(E-Mail Removed)...
> I've been having some problems with defender, during the night defender is
> scheduled to do a scan and during that time it causes a stop error
> (0x0000000A). When i turn off the defender service, there are no issues.
>
> Now the build i am running is a clean build, with latest Nvidia Drivers
> and
> the most recent creative drivers for my Audigy 2 ZS card. I use kasperksy
> as
> my AV and have ZoneAlarm Pro as my Firewall.
>
> I can do a scan manually and there's not a issue but when it is done as a
> schedule task it breaks the machine. There are no other problems with the
> machine only this one.
>
> I would be most appreciated if i could get a resolution to this problem.
> is
> there a way to enable a debug log for defender so i a better trail to
> follow
> in fixing this.

I have already been through the event logs, it the first thing i do when i
receive a Stop error, the last event posted before the crash event is a
notification of completion of a quick scan. The next event is a crash event.

I haven't been able to pick it yet. At the moment i have removed Microsoft
Desktop Search. And Still Crashes, i plan on remove Kaspersky tonight and see
what happens. After that Zonelabs.

The crash event does not mention what the drivers involved otherwise i could
trace it but it has to do with defender becuase when i disable it the crashes
go away.

"Bill Sanderson" wrote:

> Are these crashes generating events in the System event log? In addition to
> what Engel mentions--look for crash events--they may give the name of the
> driver involved.
>
> I don't know what the difference would be between a scheduled scan and a
> manually initiated one--that's strange.
>
> However--if this persists, I'd stop running scheduled scans--this is risky.
>
> --
>
> "Lokiarmos" <2198234981234810834@Localhost> wrote in message
> news:32B777F2-A560-4A29-86DA-(E-Mail Removed)...
> > I've been having some problems with defender, during the night defender is
> > scheduled to do a scan and during that time it causes a stop error
> > (0x0000000A). When i turn off the defender service, there are no issues.
> >
> > Now the build i am running is a clean build, with latest Nvidia Drivers
> > and
> > the most recent creative drivers for my Audigy 2 ZS card. I use kasperksy
> > as
> > my AV and have ZoneAlarm Pro as my Firewall.
> >
> > I can do a scan manually and there's not a issue but when it is done as a
> > schedule task it breaks the machine. There are no other problems with the
> > machine only this one.
> >
> > I would be most appreciated if i could get a resolution to this problem.
> > is
> > there a way to enable a debug log for defender so i a better trail to
> > follow
> > in fixing this.
>
>
>

I don't know what to suggest. After a scan, there may be a network
event--reporting to spynet, but that should happen regardless of whether the
scan is scheduled or manual.

--

"Lokiarmos" <2198234981234810834@Localhost> wrote in message
news:B2861376-B048-4E32-A4A0-(E-Mail Removed)...
>I have already been through the event logs, it the first thing i do when i
> receive a Stop error, the last event posted before the crash event is a
> notification of completion of a quick scan. The next event is a crash
> event.
>
> I haven't been able to pick it yet. At the moment i have removed Microsoft
> Desktop Search. And Still Crashes, i plan on remove Kaspersky tonight and
> see
> what happens. After that Zonelabs.
>
> The crash event does not mention what the drivers involved otherwise i
> could
> trace it but it has to do with defender becuase when i disable it the
> crashes
> go away.
>
> "Bill Sanderson" wrote:
>
>> Are these crashes generating events in the System event log? In addition
>> to
>> what Engel mentions--look for crash events--they may give the name of the
>> driver involved.
>>
>> I don't know what the difference would be between a scheduled scan and a
>> manually initiated one--that's strange.
>>
>> However--if this persists, I'd stop running scheduled scans--this is
>> risky.
>>
>> --
>>
>> "Lokiarmos" <2198234981234810834@Localhost> wrote in message
>> news:32B777F2-A560-4A29-86DA-(E-Mail Removed)...
>> > I've been having some problems with defender, during the night defender
>> > is
>> > scheduled to do a scan and during that time it causes a stop error
>> > (0x0000000A). When i turn off the defender service, there are no
>> > issues.
>> >
>> > Now the build i am running is a clean build, with latest Nvidia Drivers
>> > and
>> > the most recent creative drivers for my Audigy 2 ZS card. I use
>> > kasperksy
>> > as
>> > my AV and have ZoneAlarm Pro as my Firewall.
>> >
>> > I can do a scan manually and there's not a issue but when it is done as
>> > a
>> > schedule task it breaks the machine. There are no other problems with
>> > the
>> > machine only this one.
>> >
>> > I would be most appreciated if i could get a resolution to this
>> > problem.
>> > is
>> > there a way to enable a debug log for defender so i a better trail to
>> > follow
>> > in fixing this.
>>
>>
>>

Removed Kaspersky as i said i would. Went to bed and woke up, ohh looky no
blue screen.

Therefore the problem lies between kaspersky and defender. i'm going to
reinstall kaspersky then tweak with the scanning options and see what happens.

I would really like some feedback from microsoft here, Guidelines or things
i could try to test this. My housemate has a near exact build to mine but
without updated sound card or nvadia drivers and he never has a issue.

I have reinstalled, installed kaspersky and now my problems have disappeared.
So i don't know, i am stumped. It still doesn't explain why this was
happening in the first place.

I don't either--There was a rev to engine code in the last update--so you've
both reinstalled Kaspersky, and are running different engine code. It's
possible that whatever was the source of the crashes has been fixed.

Keep us posted! Thanks for the troubleshooting effort.

--

"Lokiarmos" <2198234981234810834@Localhost> wrote in message
news:A1812E36-3E21-41D5-A73F-(E-Mail Removed)...
>I have reinstalled, installed kaspersky and now my problems have
>disappeared.
> So i don't know, i am stumped. It still doesn't explain why this was
> happening in the first place.

Do you have the memory.dmp file?

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
"Lokiarmos" <2198234981234810834@Localhost> wrote in message
news:A1812E36-3E21-41D5-A73F-(E-Mail Removed)...
>I have reinstalled, installed kaspersky and now my problems have
>disappeared.
> So i don't know, i am stumped. It still doesn't explain why this was
> happening in the first place.