BSOD ntoskrnl.exe

Question

BSOD ntoskrnl.exe

Vladislav Isakov 5

I started having blue screens of death about two weeks ago. I've tried almost everything, from reinstalling drivers to reinstalling Windows.

The problem mostly occurs in the browser or when watching videos. At first, the image freezes, but I can still move the mouse and hear sounds, but then everything stops and after a while the computer restarts.

https://www.dropbox.com/scl/fo/77pzajqysxrbae2d6enxn/AJNfsWgJTH_8_Hc5a5KVSJA?rlkey=p9td3539f9fne9g3fe5u5mcw3&st=nems3coq&dl=0

0 comments

3 answers

Your answer

Answer 1

David-M 109.9K Independent Advisor

Sorry for the delay in reply. I didn't receive notification of your reply.

Thanks for the clarification.

I suggest doing the following:

Go to the MSI website using the link below, download the latest Chipset driver, and install it.

https://www.msi.com/Motherboard/PRO-B850M-G/support#driver

Driver name: AMD Chipset Driver

Version: 7.12.04.858

(Extract the ZIP file, run the file "AMD_Chipset_Software", and follow the on-screen instructions to install the driver.)

I noticed that the motherboard BIOS is outdated. I suggest you update it by following MSI's instructions.

Then, see if the system will work stably.

If the BSOD occurs again after doing this, please share the minidump it created.

Feel free to ask any questions you may have.

Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

David-M 109.9K Reputation points Independent Advisor

2026-03-22T12:48:56.3466667+00:00

Hello.

Were you able to follow the procedure I suggested?

If yes, is your system stable now?

Looking forward to your reply.

Vladislav Isakov 5

Good evening, all of the above didn't help, so I decided to roll back to the clean 10 pro version, but now the problem is this

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1140

    Key  : Analysis.Elapsed.mSec
    Value: 10550

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29507.1001

    Key  : Analysis.Version.Description
    Value: 10.2511.5.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2511.5.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_DPC_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {88dc98ce-f842-4daa-98d0-858621db6b0f}

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1

    Key  : WER.System.BIOSRevision
    Value: 5.41.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff803760fb320

FILE_IN_CAB:  032426-9156-01.dmp

FAULTING_THREAD:  ffffd2800bcef440

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff60492e2efd0 -- (.trap 0xfffff60492e2efd0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000005305794f rbx=0000000000000000 rcx=fffff60492e2f1a0
rdx=fffff60492e2f1c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8037561b79b rsp=fffff60492e2f160 rbp=fffff60492e2f2e0
 r8=ffffd2800bce4280  r9=0000000000000000 r10=0000fffff80375da
r11=ffffc27ff6400000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!KeYieldProcessorEx+0x1b:
fffff803`7561b79b 5b              pop     rbx
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffd280`0bd36e18 fffff803`75841b7a     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd280`0bd36e20 fffff803`75667f33     : 0000134a`6d1a0e4b ffffd280`0bce4180 00000000`00000000 ffffd280`0bce4180 : nt!KeAccumulateTicks+0x1d73ca
ffffd280`0bd36e80 fffff803`75667a1a     : ffffae82`70fb9480 fffff604`92e2f050 fffff803`7a1b3c00 00000000`00009501 : nt!KeClockInterruptNotify+0x453
ffffd280`0bd36f30 fffff803`756d7e65     : ffffae82`70fb9480 00000000`00000000 00000000`00000000 ffff5d00`ebe219a8 : nt!HalpTimerClockIpiRoutine+0x1a
ffffd280`0bd36f60 fffff803`7580092a     : fffff604`92e2f050 ffffae82`70fb9480 00001336`ddb7f77f 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffd280`0bd36fb0 fffff803`75801157     : fffff604`00000000 00001f80`00800264 00000000`53046a8e fffff604`92e2f1a0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff604`92e2efd0 fffff803`7561b79b     : fffff604`92e2f1c0 fffff803`75db1599 ffffae82`789c4318 ffffd280`0bce4180 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff604`92e2f160 fffff803`75db1599     : ffffae82`789c4318 ffffd280`0bce4180 ffffae82`789c4660 fffff604`92e2f4b4 : nt!KeYieldProcessorEx+0x1b
fffff604`92e2f170 fffff803`75dafe75     : fffff604`5305794f ffffd280`0bce4180 ffffae82`952ebce0 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange+0x2d
fffff604`92e2f1a0 fffff803`7561417e     : ffffd280`0bce7240 fffff604`92e2f2e0 00000000`00000000 ffffd280`00000002 : nt!IopLiveDumpCorralDpc+0x55
fffff604`92e2f1e0 fffff803`75613464     : 00000000`00000000 fffff803`7560e3f5 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff604`92e2f350 fffff803`758033ee     : ffffffff`00000000 ffffd280`0bce4180 ffffd280`0bcef440 ffffae82`96f130c0 : nt!KiRetireDpcList+0x1f4
fffff604`92e2f5e0 00000000`00000000     : fffff604`92e30000 fffff604`92e29000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KeAccumulateTicks+1d73ca

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.5369

STACK_COMMAND: .process /r /p 0xfffff80376124a00; .thread 0xffffd2800bcef440 ; kb

BUCKET_ID_FUNC_OFFSET:  1d73ca

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup:     MachineOwner

Answer 2

David-M 109.9K Independent Advisor

Hi. I'm David, and I'm happy to help you.

The link you shared only contains images with information seemingly gathered by BlueScreenView, correct? However, BlueScreenView has not been providing reliable details lately.

Please share the minidump files.

These files are in C:\Windows\Minidump.

Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

Then, post the link to the ZIP file here so I can have a look.

Looking forward to your reply.

Vladislav Isakov 5 Reputation points

2026-03-20T02:52:41.1533333+00:00

Unfortunately, the minidumps were damaged and when trying to open them with another program, it doesn’t work, just like archiving them.
David-M 109.9K Reputation points Independent Advisor

2026-03-20T12:06:01.4166667+00:00

Sorry for the delay in reply. I've been offline.

Thanks for the clarification.

The images you shared only point to a generic system file, but the actual cause of the crash is something else. Without valid minidumps, it's difficult to identify the root problem.

In this case, the best option is to follow the standard troubleshooting steps for BSOD issues.

Could you confirm what your motherboard is?

With the identifier in the information you collected with DxDiag, I found the B850M GAMING WIFI and PRO B850M-G.

Looking forward to your reply.
Vladislav Isakov 5 Reputation points

2026-03-20T16:41:28.7933333+00:00

PRO B850M-G.

Answer 3

Based on the symptoms (freeze while browsing or watching video, sound continues briefly, then full lock and reboot with ntoskrnl.exe in the crash), this is consistent with a Windows stop error (blue screen) that can be caused by faulty drivers, hardware, or system corruption.

Follow these steps in order:

Remove or disconnect any recently added hardware
- Power off the PC completely.
- Unplug or remove any new USB devices, external drives, or internal cards added in the last weeks.
- Boot again and test if the crashes still occur.
Boot into Safe Mode and test
- Start Windows in Safe Mode as described in "Start your PC in safe mode in Windows 10" (the same procedure applies conceptually in Windows 11).
- In Safe Mode, use the browser and play videos for a while.
- If the system is stable in Safe Mode, the cause is likely a third‑party driver or software (for example, GPU utilities, overclocking tools, or browser extensions).
Check Device Manager for driver issues
- Right‑click Start > Device Manager.
- Look for any devices with a yellow exclamation mark (!).
- For each such device:
  - Right‑click > Update driver.
  - If updating does not help, right‑click > Disable device and test, or Uninstall device and then reboot so Windows can reinstall a clean driver.
Ensure enough free disk space
- Check that the system drive (usually C:) has at least 10–15% free space.
- If space is low, remove unnecessary files or apps so Windows can create paging and temporary files reliably.
Install all current Windows updates
- Go to Start > Settings > Windows Update.
- Select "Check for updates" and install everything offered.
- Reboot when prompted and test again.
Use System Restore or other recovery options if crashes persist
- If the problem started recently, use a restore point from before the first BSOD.
- Open Settings > System > Recovery and choose the recovery option that best matches the situation (for example, System Restore or a repair install) as described under "Recovery options in Windows 10" (the same concepts apply to Windows 11).
If still failing, proceed with advanced BSOD diagnostics
- For advanced users or IT professionals, analyze the bug check (stop) codes and crash dumps using the guidance under "Advanced troubleshooting steps for Windows blue screens and stop code errors." This can help identify whether a specific driver (such as GPU, storage, or network) is triggering ntoskrnl.exe.

If after these steps the system continues to crash with different stop codes or with no clear driver indicated, hardware (RAM, GPU, storage, or motherboard) should be tested with dedicated diagnostics tools or by swapping components.

References:

Share via

BSOD ntoskrnl.exe

3 answers

Your answer