Discussion Locked

reboot from bugcheck

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Have a citrix server that reboots avg. 3 times daily. Event log states: The computer has rebooted from a bug check. The bug check was 0x0000007F (0x00000008, 0x00000000, 0x00000000, 0x00000000). MS Windows NT [v15.1381]. A full dump was not saved. Any ideas what is causing the reboot and/or resolution?

5 replies

by spydergst1

First. I have to say good luck! Problem with Citrix are never easy. I looked on Citrix forum and found sever reasons for this error. I suggest you look yourself. In one case i saw on the forum Citrix themselves suggested opening a support call with microsoft. But, there are other solutions others recommended in the forum. Here is the link.

http://206.103.132.14/icaforum.nsf/($All)

Spyder

by fancoms

This NT Tip came from Tech Republic today which seems to suggest that Stop error points to Hardware.

Good Luck.

Today's Windows NT Tip

ANOTHER COMMON BLUE SCREEN ERROR MESSAGE
Keep that troubleshooting hat on while we decipher another common Stop
message category, STOP 0x0000007F (UNEXPECTED_KERNEL_MODE_TRAP).

This error may be caused by either hardware or software problems, but
it most commonly indicates a hardware failure. It means that a trap
occurred in kernel mode and that the trap is either one the kernel is
not allowed to have or it's one that is always fatal. The most common
causes of STOP 0x7F are low-level hardware corruption, such as corrupt
memory (RAM), mismatched memory modules, or a malfunctioning
motherboard.

To determine a probable cause, examine the parameters at the top of the
STOP screen and cross-reference them with any Intel x86 microprocessor
reference manual. Once the cause is determined, hardware can be
replaced or software reinstalled/debugged.

NOTE: All traps that cause a STOP 0x7F error message can be found in
any Intel x86 microprocessor reference manual, as they are specific to
the x86 platform.

This discussion is closed to new replies.