Windows Server 2008 R2: The computer has rebooted from a bugcheck. The bugcheck was: 0x0000007e (0xffffffff80000003, 0xfffff8000326df16, 0xfffff880087937a8, 0xfffff88008793000)

Nizar Ben Messaoud 1 Reputation point
2023-01-05T12:21:51.117+00:00

  •                                                                         *
    
  •                    Bugcheck Analysis                                    *
    
  •                                                                         *
    

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e) This is a very common BugCheck. Usually the exception address pinpoints the driver/function that caused the problem. Always note this address as well as the link date of the driver/image that contains this address. Arguments: Arg1: ffffffff80000003, The exception code that was not handled Arg2: fffff8000326df16, The address that the exception occurred at Arg3: fffff880087937a8, Exception Record Address Arg4: fffff88008793000, Context Record Address

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 4765

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 4794

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

Key  : Analysis.Init.CPU.mSec
Value: 1562

Key  : Analysis.Init.Elapsed.mSec
Value: 22259

Key  : Analysis.Memory.CommitPeak.Mb
Value: 84

Key  : Bugcheck.Code.DumpHeader
Value: 0x7e

Key  : Bugcheck.Code.KiBugCheckData
Value: 0x7e

Key  : Bugcheck.Code.Register
Value: 0x7e

Key  : WER.OS.Branch
Value: win7sp1_gdr

Key  : WER.OS.Timestamp
Value: 2015-02-02T15:26:00Z

Key  : WER.OS.Version
Value: 7.1.7601.18741

FILE_IN_CAB: MEMORY.DMP

VIRTUAL_MACHINE: VMware

BUGCHECK_CODE: 7e

BUGCHECK_P1: ffffffff80000003

BUGCHECK_P2: fffff8000326df16

BUGCHECK_P3: fffff880087937a8

BUGCHECK_P4: fffff88008793000

EXCEPTION_RECORD: fffff880087937a8 -- (.exr 0xfffff880087937a8) ExceptionAddress: fffff8000326df16 (nt! ?? ::FNODOBFM::`string'+0x00000000000313be) ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 1 Parameter[0]: 0000000000000000

CONTEXT: fffff88008793000 -- (.cxr 0xfffff88008793000) rax=0000000000000001 rbx=fffffa8007135b30 rcx=1a5528ad380e0000 rdx=000000000000004e rsi=fffffa800b29f000 rdi=fffff8000343ee80 rip=fffff8000326df16 rsp=fffff880087939e0 rbp=0000000000000000 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=fffff88008793600 r12=0000000000000000 r13=fffff8000343ee80 r14=000000000009e341 r15=0000000000010224 iopl=0 nv up di ng nz na po nc cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000086 nt! ?? ::FNODOBFM::string'+0x313be: fffff8000326df16 cc int 3 Resetting default scope

PROCESS_NAME: System

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.

EXCEPTION_CODE_STR: 80000003

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_STR: 0x80000003

STACK_TEXT:
fffff880087939e0 fffff800032c7d2c : fffffffffd9da600 fffffa8007616160 fffffa8007135b30 fffffa80095c6b58 : nt! ?? ::FNODOBFM::string'+0x313be fffff88008793a50 fffff880056496e5 : 0000000000000007 fffffa8007cb4020 0000000000000000 fffff8800561f110 : nt!ExAcquireResourceExclusiveLite+0x14f fffff88008793ac0 fffff88005692ecf : fffff8a0167e11d4 fffff88005602000 0000000000000000 fffffa8007cb4020 : srv!UnlinkRfcbFromLfcb+0x25 fffff88008793b00 fffff8800569249e : fffffa800b29f060 fffffa8007879cc0 0000000000000000 fffffa800b29f060 : srv!SrvCloseCachedRfcb+0x4f fffff88008793b30 fffff88005649a1f : fffffa8007879cc0 0000000000000000 0000000000000000 fffffa800b29f070 : srv!SrvOplockBreakNotification+0x21e fffff88008793bb0 fffff80003560b8a : fffffa800b29f060 fffffa80095c6a50 0000000000000080 fffffa8003cde9e0 : srv!WorkerThread+0xe9 fffff88008793c00 fffff800032b38e6 : fffff8000343ee80 fffffa80095c6a50 fffffa8007dc8640 0000000000000000 : nt!PspSystemThreadStartup+0x5a fffff88008793c40 0000000000000000 : fffff88008794000 fffff8800878e000 fffff88008793730 00000000`00000000 : nt!KxStartSystemThread+0x16

SYMBOL_NAME: srv!UnlinkRfcbFromLfcb+25

MODULE_NAME: srv

IMAGE_NAME: srv.sys

STACK_COMMAND: .cxr 0xfffff88008793000 ; kb

FAILURE_BUCKET_ID: 0x7E_80000003_srv!UnlinkRfcbFromLfcb+25

OS_VERSION: 7.1.7601.18741

BUILDLAB_STR: win7sp1_gdr

OSPLATFORM_TYPE: x64

OSNAME: Windows 7

FAILURE_ID_HASH: {792b525b-ca32-56e9-40f7-ef62d3d67a69}

Followup: MachineOwner

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,562 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2023-01-05T13:32:17.507+00:00

    Something here could help.
    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x7e--system-thread-exception-not-handled

    the server vendor will be your best resource to trouble shoot problems with the hardware and or drivers.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.