my pc got black screen when playing game

Anonymous
2024-11-30T15:27:02+00:00

my pc keep getting blackscreen when playing MHW and here is the dump file

Loading unloaded module list ......... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803f1cb87e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff828aa52f4dd0=000000000000013a 19: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

KERNEL_MODE_HEAP_CORRUPTION (13a) The kernel mode heap manager has detected corruption in a heap. Arguments: Arg1: 0000000000000017, Type of corruption detected Arg2: ffffe687ab100380, Address of the heap that reported the corruption Arg3: ffffe687cdca8a70, Address at which the corruption was detected Arg4: 0000000000000000

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 1296

Key  : Analysis.Elapsed.mSec
Value: 11850

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

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

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

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

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

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

Key  : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key  : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key  : Analysis.Version.Ext
Value: 1.2408.27.1

Key  : Bugcheck.Code.LegacyAPI
Value: 0x13a

Key  : Bugcheck.Code.TargetModel
Value: 0x13a

Key  : Dump.Attributes.AsUlong
Value: 21808

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: 0x13a\_17\_nt!RtlpHeapHandleError

Key  : Failure.Hash
Value: {b1500314-0083-90bd-d812-716f3060523d}

Key  : Hypervisor.Enlightenments.ValueHex
Value: 7497cf94

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key  : Hypervisor.Flags.ApicEnlightened
Value: 1

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key  : Hypervisor.Flags.Phase0InitDone
Value: 1

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 1

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 38408431

Key  : Hypervisor.Flags.ValueHex
Value: 24a10ef

Key  : Hypervisor.Flags.VpAssistPage
Value: 1

Key  : Hypervisor.Flags.VsmAvailable
Value: 1

Key  : Hypervisor.RootFlags.AccessStats
Value: 1

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 1

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key  : Hypervisor.RootFlags.Value
Value: 1015

Key  : Hypervisor.RootFlags.ValueHex
Value: 3f7

BUGCHECK_CODE: 13a

BUGCHECK_P1: 17

BUGCHECK_P2: ffffe687ab100380

BUGCHECK_P3: ffffe687cdca8a70

BUGCHECK_P4: 0

FILE_IN_CAB: 111724-8421-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x21808 Kernel Generated Triage Dump

FAULTING_THREAD: ffffe687ab573400

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff828aa52f4dc8 fffff803f1db0698 : 000000000000013a 0000000000000017 ffffe687ab100380 ffffe687cdca8a70 : nt!KeBugCheckEx ffff828aa52f4dd0 fffff803f1db06f8 : 0000000000000017 0000000000000244 ffffe687ab100380 fffff803f1b8ca89 : nt!RtlpHeapHandleError+0x40 ffff828aa52f4e10 fffff803f1b91071 : ffffe687cdc79000 ffffe687ab100380 ffffe687ab107ee8 0000000000000002 : nt!RtlpHpHeapHandleError+0x58 ffff828aa52f4e40 fffff803f1b8fd91 : 0000000000001000 ffffe687ab100140 ffffe687ab100380 00000000ffffffff : nt!RtlpLogHeapFailure+0x45 ffff828aa52f4e70 fffff803f1b8d0e9 : ffffe687cdc79000 0000000000000259 ffffe687ab100380 0000000000000000 : nt!RtlpHpLfhReportError+0x21 ffff828aa52f4eb0 fffff803f1b8ccb8 : ffffe687cdc79000 0000000000000150 0000000001000115 000ffffe687cdc79 : nt!RtlpHpLfhSubsegmentDelayFreeListProcess+0x255 ffff828aa52f4f30 fffff803f1c31372 : 0000000000000007 0000000001000115 ffffe687ab100380 ffffe687ab104600 : nt!RtlpHpLfhOwnerRunMaintenance+0x174 ffff828aa52f4f90 fffff803f1c3144f : 0000000000000000 ffffe687ab104600 ffffe687ab104600 ffff828aa52f5140 : nt!RtlpHpLfhOwnerCompact+0xc2 ffff828aa52f5110 fffff803f1c3111f : 0000000000000001 fffff803f1c314d6 0001000000000000 0000000000000000 : nt!RtlpHpLfhOwnerCompact+0x19f ffff828aa52f5290 fffff803f1c31055 : ffffe687ab100000 0000000000000000 0000000000000000 fffff803f20b919c : nt!RtlpHpLfhContextCompact+0xa3 ffff828aa52f52d0 fffff803f1c30ff3 : 0000000000000001 0000000000000000 0000000000000001 ffffe687ab573440 : nt!RtlpHpHeapCompact+0x21 ffff828aa52f5300 fffff803f1c716e5 : 0000000000000001 0000000000000001 0000000000000000 fffff803f1b14d48 : nt!ExpHpCompactHeapCallback+0x23 ffff828aa52f5330 fffff803f1c71645 : 0000000000000001 ffff828aa52f54c0 ffffe687ab597c60 ffffe687ab597c60 : nt!ExpHpEnumerateHeaps+0x71 ffff828aa52f5390 fffff803f1b146a2 : ffffe687ab573400 ffff828aa52f5400 ffffe687ab597c00 fffff80300000000 : nt!ExpHpCompactionRoutine+0x15 ffff828aa52f53c0 fffff803f1c5652a : ffffe687ab573400 ffffe687ab573400 fffff803f1b144f0 ffffe687ab597c60 : nt!ExpWorkerThread+0x1b2 ffff828aa52f5570 fffff803f1e77d24 : ffff898040c51180 ffffe687ab573400 fffff803f1c564d0 4800001baa850fe0 : nt!PspSystemThreadStartup+0x5a ffff828aa52f55c0 0000000000000000 : ffff828aa52f6000 ffff828aa52ef000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nt!RtlpHeapHandleError+40

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.2314

STACK_COMMAND: .process /r /p 0xffffe687ab565040; .thread 0xffffe687ab573400 ; kb

BUCKET_ID_FUNC_OFFSET: 40

FAILURE_BUCKET_ID: 0x13a_17_nt!RtlpHeapHandleError

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b1500314-0083-90bd-d812-716f3060523d}

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
Answer accepted by question author
Jonathan Deives 81,190 Reputation points Independent Advisor
2024-12-01T16:43:57+00:00

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

Try forcing Windows to show failed drivers and produce minidump files, enable Driver Verifier for this.

Make the BSOD happen 3 times and then see if the files were created.

Before running Driver Verifier, create a new system restore point.

https://answers.microsoft.com/en-us/windows/for...

If you have problems starting Windows after enabling Driver Verifier, follow these steps:

Start your PC, as soon as Windows tries to load (spinning dots appear), press and hold the power button for 5 to 10 seconds to perform a forced shutdown

Do this two or three times.

Windows will boot into the Recovery Environment.

Go to Troubleshoot > Advanced Option > Startup Settings and click Restart.

When restarting, press 4 to enter safe mode.

Open command prompt as administrator, run these two commands and restart your PC.

verifier /reset

verifier /bootmode resetonbootfail

Was this answer helpful?

1 person found this answer helpful.
0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-12-01T14:40:13+00:00

    let check it

    https://drive.google.com/file/d/1VhWJOL2sJGwbIWvXHGtG6-PSX5IkNUL-/view?usp=drivesdk

    also i suspecting my vga maybe broken because sometimes it will booting with no display

    Was this answer helpful?

    0 comments
  2. Jonathan Deives 81,190 Reputation points Independent Advisor
    2024-11-30T16:58:36+00:00

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

    See if your computer is creating minidump files.

    To find these files, this is the path "C:\Windows\Minidump".

    First copy and paste all the minidump files you have to another folder and then zip it. Then upload the ZIP file to the cloud on a website like OneDrive, Google Drive or Dropbox.

    Choose to share or right click and get the share link.

    Please post the link to the ZIP file here so it can be reviewed.

    Was this answer helpful?

    0 comments