Share via

Constant BSODs

Anonymous
2023-10-14T16:08:52+00:00

Edit: Here is minidumps:

https://drive.google.com/file/d/1OB9TAa-EGPe3BU0JIiF_EaxaB9lcHPQy/view?usp=sharing

Hi, I'm receiving constant BSODs, usually while playing more intense video games. Seems to happen randomly, but usually when I'm putting on a heavier load. One thing to note is that it happens more frequently when I'm saving the game, but not only when I'm saving. The BSODs do not appear to happen when I'm doing low-intensity things like browsing the internet, or playing a less-intensive game. Also, sometimes after blue-screening, the computer will restart, and then immediately blue screen again. I will need to restart sometimes 7-8 times before I'm able to log into Windows. The blue screen also occurs with a different error each time. The most recent error is this:DRIVER_IRQL_NOT_LESS_OR_EQUAL for what failed:MpKslDrv.sys

I've tried updating all of the drivers, running DISM and sfc, neither seem to work.

My Machine:

Windows 10

16 gb ram, overclocked to standard XMP profile

Intel 9900k overclocked

NVidia 2070 super

nvme ssd

MEMORY.dmp file is here: https://drive.google.com/file/d/1_f2trSFqMQamJk3_6FXmCAoK3yjECEgm/view?usp=sharing 

Appreciate any help offered, thanks!!

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 000000004bece58a, memory referenced
Arg2: 000000000000000f, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff802e8ef79ca, address which referenced memory

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2015

    Key  : Analysis.Elapsed.mSec
    Value: 2042

    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: 780

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

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

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0xd1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Failure.Bucket
    Value: AV_MpKslDrv!unknown_function

    Key  : Failure.Hash
    Value: {6edae0dc-9dc2-be77-fe82-074577005d71}

    Key  : Hypervisor.Enlightenments.Value
    Value: 0

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 0

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 0

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 0

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 0

    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: 0

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 0

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 0

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 131072

    Key  : Hypervisor.Flags.ValueHex
    Value: 20000

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 0

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 0

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 0

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 0

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 0

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 0

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 0

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 0

    Key  : Hypervisor.RootFlags.Value
    Value: 0

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0

    Key  : SecureKernel.HalpHvciEnabled
    Value: 0

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

BUGCHECK_CODE:  d1

BUGCHECK_P1: 4bece58a

BUGCHECK_P2: f

BUGCHECK_P3: 0

BUGCHECK_P4: fffff802e8ef79ca

FILE_IN_CAB:  MEMORY.DMP

READ_ADDRESS:  000000004bece58a 

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  Cyberpunk2077.exe

TRAP_FRAME:  ffff9380952d2c00 -- (.trap 0xffff9380952d2c00)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000004bece58a rbx=0000000000000000 rcx=ffff9380952d2e08
rdx=0000000000004bd4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802e8ef79ca rsp=ffff9380952d2d90 rbp=ffff9380952d2e59
 r8=0000004669e87d4b  r9=0000000000000000 r10=fffff80270365590
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
MpKslDrv+0x179ca:
fffff802`e8ef79ca 488b05df1a0200  mov     rax,qword ptr [MpKslDrv+0x394b0 (fffff802`e8f194b0)] ds:fffff802`e8f194b0={nt!PsGetCurrentProcessId (fffff802`702104f0)}
Resetting default scope

STACK_TEXT:  
ffff9380`952d2ab8 fffff802`70411729     : 00000000`0000000a 00000000`4bece58a 00000000`0000000f 00000000`00000000 : nt!KeBugCheckEx
ffff9380`952d2ac0 fffff802`7040d2e3     : ffffba05`38403000 ffffba05`3ad2eff8 ffff9380`952d2c88 ffffcb0a`0ec3fa00 : nt!KiBugCheckDispatch+0x69
ffff9380`952d2c00 fffff802`e8ef79ca     : 01d9feb3`d623cfe1 08000000`0000000b b9277e3f`a5f98eb0 00004bd4`4bdfc624 : nt!KiPageFault+0x463
ffff9380`952d2d90 fffff802`e8ef7b8c     : ffffba05`2bce9c00 ffffba05`2bce9d90 ffffcb0a`0ec3fa00 ffffba05`2bce9d90 : MpKslDrv+0x179ca
ffff9380`952d2ec0 fffff802`e8eedd12     : fffffffd`00000002 00000000`00000001 ffffba05`2bce9c00 00004bd4`4bd1a7da : MpKslDrv+0x17b8c
ffff9380`952d2ef0 fffff802`704bf1ea     : 00000000`00000286 fffff802`70242e2a ffffba05`2bcea040 ffffcb0a`0ec3fa80 : MpKslDrv+0xdd12
ffff9380`952d2f20 fffff802`702a7765     : ffffba05`2bce9ce0 fffff802`7034ea57 00000000`00000000 00000000`00000000 : nt!HalpPerfInterrupt+0xfa
ffff9380`952d2f60 fffff802`703ff5da     : ffffcb0a`0ec3fa80 ffffba05`2bce9ce0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9380`952d2fb0 fffff802`703ffda7     : 00007ffd`d6d830e0 000001bc`bdefe800 00000000`00000000 00000000`00000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffcb0a`0ec3fa00 00007ffe`558e4400     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
0000007c`adffdae8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`558e4400

SYMBOL_NAME:  MpKslDrv+179ca

MODULE_NAME: MpKslDrv

IMAGE_NAME:  MpKslDrv.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  179ca

FAILURE_BUCKET_ID:  AV_MpKslDrv!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6edae0dc-9dc2-be77-fe82-074577005d71}

Followup:     MachineOwner
---------
Windows for home | Windows 10 | 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

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-10-15T15:42:52+00:00

    One of the minidump files points to "GenuineIntel.sys". It is the Intel Procesor driver.

    It might be also driven to fault by another driver, software or hardware.

    You can try the following.

    1. Update BIOS if it's available, If not try to reset its default.
    2. Update the chipset and all device drivers.
    3. Disable any overclocking settings.

    I hope this helps. Feel free to ask back any questions and keep me posted.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-10-14T17:19:31+00:00

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-10-14T17:06:49+00:00

    Hi Eric,

    I'm Paul and I'm here to help you with your concern.

    The "MpKslDrv.sys" is a system file driver. Since it's a system file it means something else drove it into a fault. It could be hardware, software, or driver.

    We need further analysis.

    Can you share other minidump files that you have?

    1. Open Windows File Explorer
    2. Go to C:\Windows\Minidump
    3. Zip those files
    4. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.).
    5. Then share the link here.

    Thanks.

    Was this answer helpful?

    0 comments