Share via

PC suddenly reboot with error code 0x0000007f (0x0000000000000008, 0xffffe581d935ae50, 0xffffd00200000000, 0xfffff8053622aa3b)

Anonymous
2024-11-28T19:54:25+00:00

My pc suddenly freeze and reboot without any sign.

Here is the minidump file:

https://drive.google.com/file/d/1pFNElFm3hpi2neGtWqMmryDUwFNPO89I/view?usp=drive_link

Windbg analysis:

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault).  The first number in the
BugCheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
        use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
        use .trap on that value
Else
        .trap on the appropriate frame will show where the trap was taken
        (on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: ffffe581d935ae50
Arg3: ffffd00200000000
Arg4: fffff8053622aa3b

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3046

    Key  : Analysis.Elapsed.mSec
    Value: 11889

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27704.1001

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000007f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1000007f

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x7f_8_nt!KiSystemServiceExit

    Key  : Failure.Hash
    Value: {fb373f56-645c-4df3-0cad-bd0825371625}

    Key  : Stack.Pointer
    Value: Invalid

BUGCHECK_CODE:  7f

BUGCHECK_P1: 8

BUGCHECK_P2: ffffe581d935ae50

BUGCHECK_P3: ffffd00200000000

BUGCHECK_P4: fffff8053622aa3b

FILE_IN_CAB:  112924-16859-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffd105d713c040

BAD_STACK_POINTER:  ffffd00200000000

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffd002`00000000 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x42b

SYMBOL_NAME:  nt!KiSystemServiceExit+42b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.4455

STACK_COMMAND:  .process /r /p 0xffffd105d70fe040; .thread 0xffffd105d713c040 ; kb

BUCKET_ID_FUNC_OFFSET:  42b

FAILURE_BUCKET_ID:  0x7f_8_nt!KiSystemServiceExit

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {fb373f56-645c-4df3-0cad-bd0825371625}

Followup:     MachineOwner
Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Jonathan Deives 74,060 Reputation points Independent Advisor
    2024-11-28T21:57:04+00:00

    My name is Jonathan Deives. I'm an Independent Advisor and I will be happy to help you.

    The minidump file do not indicate any driver or hardware causes, only memory corruption.

    Do you have more minidump files ?

    Was this answer helpful?

    0 comments No comments