STOP Error 0x0000007f BSOD using Windows Defender Beta2

[Guest]

Hello,

I have been receiving a STOP 0x0000007F UNEXPECTED_KERNAL_MODE_TRAP BSOD
for a couple of weeks. The full error code as described in the system event
log follows:

****START EVENT LOG ENTRY***
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f
(0x00000000, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows 2000
[v15.2195]. A dump was saved in: D:\WINNT\Minidump\Mini060106-08.dmp.
***END EVENT LOG ENTRY***

I am using Windows 2000 Server SP4, dual CPU @750MHz Intel PIII, SCSI I/O.

This would happen at irregular intervals post boot into a user profile. This
would *always* happen when any virtual console is launched using Microsoft
Virtual PC SP1 v5.3.582.27.

Unfortunately, within this time frame two changes to my system took place.
Firstly, I installed some new memory and secondly, I installed Windows
Defender Beta2. The STOP error led me to believe that the new RAM could be
the culprit but after many RAM configuration changes, including returning to
my old RAM, the issue remained.

I used the MS Configuration Tool (msconfig.exe) to make many (many….)
iterations of system boots with increasing numbers of enabled services and
startup programs. Ultimately I found that booting the computer *without* the
Windows Defender service and user extension prevented this STOP error from
occurring.

I will, of course, be uninstalling Windows Defender Beta2 but I figured it
might be worthwhile posting this to:
1. Provide a fault history for newsgroup searches on similar issues
2. Perhaps have the issue addressed by the Windows Defender development team

With regards,
David.

 

[Bill Sanderson MVP]

I have an XP SP2 machine which runs VPC SP1 as well as Windows Defender, and
haven't seen such crashes, FWIW.

Are you submitting these crash reports to Microsoft? I'm never sure which
of these get automatic prompts to submit and which do not.

If you haven't or are uncertain--and you have the crash reports, the
development team would very much like to see them.

If you've got the minidump files, and can zip them up--let me know via this
thread, or via private email (remove .plug.org)--about the sizes of files
involved, and I can see how to best get them to Microsoft.

 

[Bill Sanderson MVP]

One other thought--check in Help, About in Windows defender for version
number 1.1.1347.0 (first version number)

If yours is lower, do a new download from:

http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&DisplayLang=en

and just run it--this will upgrade what you have in place. The idea would
be to then attempt to replicate the issue if indeed this is different code
than you've been using. I hesitate to ask that on a Server OS with this
kind of crash, but that would probably be helpful...

 

[Guest]

I welcome your response

In terms of the Windows Defender version, I downloaded from the main
Microsoft page a couple of weeks ago and succesfully updated it using Windows
Update (I had no problems but I understand it to be an issue with others)

Don't worry about he Server O/S. To be honest I have the Server O/S
installed becasue I'm putting myself through MCSE and it's useful having AD,
TS, IIS, RRAS et al

Happy to submit bug reports. I've only the minidump configured at the mo but
I you need the full dump I can change this. The minidumps are 64KB.

Not sure to how to attach files - I'm using the web front end although I
could switch to Outlook Express or similar. On your private email should I
assume any @ prefix and remove the space between 'remove' and 'plug' - I'm
assuming this is a newsgroup method to avoid email harvesters.

Cheers,
Dave.

One other thought--check in Help, About in Windows defender for version
number 1.1.1347.0 (first version number)

If yours is lower, do a new download from:

http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&DisplayLang=en

and just run it--this will upgrade what you have in place. The idea would
be to then attempt to replicate the issue if indeed this is different code
than you've been using. I hesitate to ask that on a Server OS with this
kind of crash, but that would probably be helpful...

--

Hello,

I have been receiving a STOP 0x0000007F UNEXPECTED_KERNAL_MODE_TRAP BSOD
for a couple of weeks. The full error code as described in the system
event
log follows:

****START EVENT LOG ENTRY***
The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007f
(0x00000000, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows 2000
[v15.2195]. A dump was saved in: D:\WINNT\Minidump\Mini060106-08.dmp.
***END EVENT LOG ENTRY***

I am using Windows 2000 Server SP4, dual CPU @750MHz Intel PIII, SCSI I/O.

This would happen at irregular intervals post boot into a user profile.
This
would *always* happen when any virtual console is launched using Microsoft
Virtual PC SP1 v5.3.582.27.

Unfortunately, within this time frame two changes to my system took place.
Firstly, I installed some new memory and secondly, I installed Windows
Defender Beta2. The STOP error led me to believe that the new RAM could be
the culprit but after many RAM configuration changes, including returning
to
my old RAM, the issue remained.

I used the MS Configuration Tool (msconfig.exe) to make many (many..)
iterations of system boots with increasing numbers of enabled services and
startup programs. Ultimately I found that booting the computer *without*
the
Windows Defender service and user extension prevented this STOP error from
occurring.

I will, of course, be uninstalling Windows Defender Beta2 but I figured it
might be worthwhile posting this to:
1. Provide a fault history for newsgroup searches on similar issues
2. Perhaps have the issue addressed by the Windows Defender development
team

With regards,
David.

 

[Bill Sanderson MVP]

I wouldn't post the files here--any dump file can contain confidential
data--you'll already be taking some level of risk sending it via me!
So--zip what you have up, password protect the zip--use "crash" as the
password--and send it to:

bill_sanderson @ msn.com

remove the spaces!
(These groups are carried via both NNTP and the HTML groups, and the risk
with NNTP is both spam and, more importantly, viruses like SWEN that
harvested news message headers for valid emails.)

I'll pass this stuff on to Steve Dodson--you could probably have done this
yourself, or I could have posted how to unmunge his address, but let's do it
this way--and see where it goes from there--thanks very much!

--

I welcome your response

In terms of the Windows Defender version, I downloaded from the main
Microsoft page a couple of weeks ago and succesfully updated it using
Windows
Update (I had no problems but I understand it to be an issue with others)

Don't worry about he Server O/S. To be honest I have the Server O/S
installed becasue I'm putting myself through MCSE and it's useful having
AD,
TS, IIS, RRAS et al

Happy to submit bug reports. I've only the minidump configured at the mo
but
I you need the full dump I can change this. The minidumps are 64KB.

Not sure to how to attach files - I'm using the web front end although I
could switch to Outlook Express or similar. On your private email should I
assume any @ prefix and remove the space between 'remove' and 'plug' - I'm
assuming this is a newsgroup method to avoid email harvesters.

Cheers,
Dave.

One other thought--check in Help, About in Windows defender for version
number 1.1.1347.0 (first version number)

If yours is lower, do a new download from:

http://www.microsoft.com/downloads/...e7-da2b-4a6a-afa4-f7f14e605a0d&DisplayLang=en

and just run it--this will upgrade what you have in place. The idea
would
be to then attempt to replicate the issue if indeed this is different
code
than you've been using. I hesitate to ask that on a Server OS with this
kind of crash, but that would probably be helpful...

--

Hello,

I have been receiving a STOP 0x0000007F UNEXPECTED_KERNAL_MODE_TRAP
BSOD
for a couple of weeks. The full error code as described in the system
event
log follows:

****START EVENT LOG ENTRY***
The computer has rebooted from a bugcheck. The bugcheck was:
0x0000007f
(0x00000000, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows
2000
[v15.2195]. A dump was saved in: D:\WINNT\Minidump\Mini060106-08.dmp.
***END EVENT LOG ENTRY***

I am using Windows 2000 Server SP4, dual CPU @750MHz Intel PIII, SCSI
I/O.

This would happen at irregular intervals post boot into a user profile.
This
would *always* happen when any virtual console is launched using
Microsoft
Virtual PC SP1 v5.3.582.27.

Unfortunately, within this time frame two changes to my system took
place.
Firstly, I installed some new memory and secondly, I installed Windows
Defender Beta2. The STOP error led me to believe that the new RAM could
be
the culprit but after many RAM configuration changes, including
returning
to
my old RAM, the issue remained.

I used the MS Configuration Tool (msconfig.exe) to make many (many..)
iterations of system boots with increasing numbers of enabled services
and
startup programs. Ultimately I found that booting the computer
*without*
the
Windows Defender service and user extension prevented this STOP error
from
occurring.

I will, of course, be uninstalling Windows Defender Beta2 but I figured
it
might be worthwhile posting this to:
1. Provide a fault history for newsgroup searches on similar issues
2. Perhaps have the issue addressed by the Windows Defender development
team

With regards,
David.