Strange error - unexpected_kernel_mode_trap

[Ikke]

Hi everybody,

My machine: Windows 2000 on Pentium 4, 2.4Ghz, 512Mb RAM.

This evening when I turned on my computer, something very strange happened.
After loggin in, I was welcomed with a blue screen, displaying an
UNEXPECTED_KERNEL_MODE_TRAP error. After rebooting the machine, the error
appeared again.

On to the safe mode, then - I rebooted the machine, starting it in safe
mode without network support. I ran AVG Anti Virus on the machine, and
checked the event viewer - nothing strange in the latter. AVG however, told
me that it could not read the Master Boot Record.

Meanwhile I used another machine to check the UNEXPECTED_KERNEL_MODE_TRAP
error on the internet. It turns out that code 07FH (0H) is a divide by zero
error, probably caused by faulty hardware/software.

I've used a Norton Ghost boot disk to reboot the machine in DOS mode, and
performed an FDISK /MBR . After starting the machine again, everything
worked fine!

But suddenly Windows 2000 mentioned "system setting changes", telling me
that it had installed new hardware and needed to reboot. Each time I
reboot, the situation is back to where I started. After starting from a
floppy and fdisk'ing again, I can work again, until the next boot.

Does anybody recognize this situation? I have not installed new hardware
lately, although I have replaced a faulty hard drive about a month ago.
Something tells me that it might be a controller/motherboard error, but
that does not explain why it works normally after fdisk'ing.

If anybody could help me on my way to return my system to normal, I'd
appreciate it very much.

Thanks in advance,

Ikke

 

[Chuck]

From MS . . .
--
Chuck

Stop message 0x0000007F Descriptive text: UNEXPECTED_KERNEL_MODE_TRAP
Usual cause: There is a hardware or software problem. This is usually caused
by a hardware failure.

Solution:

1. Use the Online Crash Analysis tool at the Microsoft Web site
http://go.microsoft.com/fwlink/?linkID=3941 . You can use this tool to send
error reports to Microsoft and track their status by using your Microsoft
Passport information. You can access the Online Crash Analysis Web site by
using the Error Reporting service or by using your Web browser. When it is
enabled, the Error Reporting service monitors your system for kernel and
user mode faults that are related to operating system components and
applications. With kernel-mode reporting, you can obtain more information
about the problem or condition that caused the Stop error. For more
information, see System and program error reporting overview.
http://technet2.microsoft.com/WindowsServer/en/library/52fc29db-aa2f-4f89-a6a9-65ba90d5e57b1033.mspx

2. Run system diagnostics supplied by your hardware vendor, especially a
memory check. This Stop message is often displayed in the case of faulty or
mismatched memory.

3. Disable memory caching in the BIOS (for x86-based and x64-based
computers) or EFI (for Itanium architecture-based computers). Contact your
hardware manufacturer if you need assistance in performing this step.

4. Confirm that your hardware is designed for the Windows Server 2003
family by clicking the appropriate link in Support resources .
http://technet2.microsoft.com/WindowsServer/en/library/07bb2619-68b5-4a1a-825d-dbb9093559161033.mspx

5.
If the computer will not start normally, try starting it in Last Known Good
Configuration or in Safe Mode, and then remove or disable newly added
programs or drivers. For information about how to start your computer in
Safe Mode, see Start the computer in Safe Mode.
http://technet2.microsoft.com/WindowsServer/en/library/e14bf84d-d2f7-42c3-9fae-2af3db3f806c1033.mspx For more information about how to start your
computer in Last Known Good Configuration, see Start the computer using the
last known good configuration .
http://technet2.microsoft.com/WindowsServer/en/library/accae9ed-c2e0-44d7-81ad-0f705d142b251033.mspx

Important

.. When you use Last Known Good Configuration, system setting changes made
after the last successful startup are lost.


Note

.. You can search the Microsoft Web site for updated information on this Stop
message. To do this, see Welcome to Microsoft Help and Support at the
Microsoft Web site http://go.microsoft.com/fwlink/?linkID=281 , click a
search option, and then follow the instructions on the page. When typing
keywords, use stop 0x0000007F.

For more information about articles, troubleshooting wizards, and items you
can download, see Updated technical information .
http://technet2.microsoft.com/WindowsServer/en/library/27ca9529-30bd-411b-8fb4-7bffbd58233c1033.mspx


Source:
http://technet2.microsoft.com/Windo...4ea6-4068-9f55-40801292ec6d1033.mspx?mfr=true

 

[Ikke]

From MS . . .
Chuck

Thanks for the reply, Chuck - I've already checked with Microsoft but
their solutions were useless as always. Unfortunately, I've yet to
discover a single piece of advice on their website or help center that is
correct.

I've managed to solve it, but I'll still comment on the Microsoft
solution if anyone cares to read it. At the end, the solution is given.

By the way, Chuck, you've left in comment characters just below your
name. If anyone replies to the message, the original text is snipped.
Very annoying. As is top-posting, although I'm forced to semi-TP this
message as well.

Stop message 0x0000007F Descriptive text: UNEXPECTED_KERNEL_MODE_TRAP
Usual cause: There is a hardware or software problem. This is usually
caused
by a hardware failure.

It can't be a hardware failure, but hey, let's give it a try.

Solution:

1. Use the Online Crash Analysis tool at the Microsoft Web site
http://go.microsoft.com/fwlink/?linkID=3941 . You can use this tool to
send
error reports to Microsoft and track their status by using your
Microsoft
Passport information. You can access the Online Crash Analysis Web site
by
using the Error Reporting service or by using your Web browser. When it
is
enabled, the Error Reporting service monitors your system for kernel
and
user mode faults that are related to operating system components and
applications. With kernel-mode reporting, you can obtain more
information
about the problem or condition that caused the Stop error. For more
information, see System and program error reporting overview.
http://technet2.microsoft.com/WindowsServer/en/library/52fc29db-aa2f-
4f89-a6a9-65ba90d5e57b1033.mspx

As said before, I have checked the Microsoft site, but no useful
information was found. Hence my post.

2. Run system diagnostics supplied by your hardware vendor, especially
a
memory check. This Stop message is often displayed in the case of
faulty or
mismatched memory.

I ran a memory check during the night, no errors there. Disabled some
hardware (second disc, floppy, network card, CD/DVD), no faults there.

System diagnostics supplied by your vendor? Now that's a laugh!

3. Disable memory caching in the BIOS (for x86-based and x64-based
computers) or EFI (for Itanium architecture-based computers). Contact
your
hardware manufacturer if you need assistance in performing this step.

Disabled and re-enabled. Nothing new.

4. Confirm that your hardware is designed for the Windows Server 2003
family by clicking the appropriate link in Support resources .
http://technet2.microsoft.com/WindowsServer/en/library/07bb2619-68b5-
4a1a-825d-dbb9093559161033.mspx

I couldn't care less if it was designed for Windows Server 20003, since
I'm running Windows 2000 Pro.

5.
If the computer will not start normally, try starting it in Last Known
Good
Configuration or in Safe Mode, and then remove or disable newly added
programs or drivers. For information about how to start your computer
in
Safe Mode, see Start the computer in Safe Mode.
http://technet2.microsoft.com/WindowsServer/en/library/e14bf84d-d2f7-
42c3-9fae-2af3db3f806c1033.mspx For more information about how to
start your
computer in Last Known Good Configuration, see Start the computer using
the
last known good configuration .
http://technet2.microsoft.com/WindowsServer/en/library/accae9ed-c2e0-
44d7-81ad-0f705d142b251033.mspx

Last Known Good configurations are saved after the boot process - so
EVERY LKGC will be faulty, since the error occurs after the boot process!

Important

. When you use Last Known Good Configuration, system setting changes >
made
after the last successful startup are lost.
Duh.

Note

. You can search the Microsoft Web site for updated information on this
Stop
message. To do this, see Welcome to Microsoft Help and Support at the
Microsoft Web site http://go.microsoft.com/fwlink/?linkID=281 , click a
search option, and then follow the instructions on the page. When
typing
keywords, use stop 0x0000007F.

Been there, done that, seen nothing of value.

For more information about articles, troubleshooting wizards, and items
you
can download, see Updated technical information .
http://technet2.microsoft.com/WindowsServer/en/library/27ca9529-30bd->
411b-8fb4-7bffbd58233c1033.mspx

Source:
http://technet2.microsoft.com/WindowsServer/en/library/fc8efbed-4ea6->
4068-9f55-40801292ec6d1033.mspx?mfr=true

For those who still want to know what the error was: it was the
virusscanner. It's new update was unable to read both the boot sector and
the MBR, and chose to self-destroy and take the machine down with it upon
startup. Well, at least the machine can't be infected that way.

My solution was very simple:
- fdisk /mbr the drive
- reboot, ignore reboot message from Windows 2000
- uninstall AVG
- reboot

I'm now waiting until they fix it. Probably a few days, and it'll all be
ok again.

Thanks,

Ikke

 

[Frank Booth Snr]

Hi everybody,

My machine: Windows 2000 on Pentium 4, 2.4Ghz, 512Mb RAM.

This evening when I turned on my computer, something very strange happened.
After loggin in, I was welcomed with a blue screen, displaying an
UNEXPECTED_KERNEL_MODE_TRAP error. After rebooting the machine, the error
appeared again.

On to the safe mode, then - I rebooted the machine, starting it in safe
mode without network support. I ran AVG Anti Virus on the machine, and
checked the event viewer - nothing strange in the latter. AVG however, told
me that it could not read the Master Boot Record.

Meanwhile I used another machine to check the UNEXPECTED_KERNEL_MODE_TRAP
error on the internet. It turns out that code 07FH (0H) is a divide by zero
error, probably caused by faulty hardware/software.

I've used a Norton Ghost boot disk to reboot the machine in DOS mode, and
performed an FDISK /MBR . After starting the machine again, everything
worked fine!

But suddenly Windows 2000 mentioned "system setting changes", telling me
that it had installed new hardware and needed to reboot. Each time I
reboot, the situation is back to where I started. After starting from a
floppy and fdisk'ing again, I can work again, until the next boot.

Does anybody recognize this situation? I have not installed new hardware
lately, although I have replaced a faulty hard drive about a month ago.
Something tells me that it might be a controller/motherboard error, but
that does not explain why it works normally after fdisk'ing.

If anybody could help me on my way to return my system to normal, I'd
appreciate it very much.

At what stage do you get the BSOD on booting up. You mention that you
manage to get to Safe Mode. Can you get that far each time?

 

[Ikke]

At what stage do you get the BSOD on booting up. You mention that you
manage to get to Safe Mode. Can you get that far each time?

In the original message I stated that this happened after the login
process.

It doesn't matter anymore, since the problem is solved now.

Thanks anyway,

Ikke