Question Constant Blue screens with ntoskrl.exe as main cause from BlueScreenView

Toggle sidebar Toggle sidebar
xConville

xConville

Sep 19, 2023
11
2
15
I recently created a new PC and everything was running fine for around 3 weeks, now my PC will crash and blue screen at random occasions, I have fully reset and freshly installed windows 11 only to be met with a similar blue screen straight after getting onto the desktop. Have ran memtest86 for a few hours and that passed 3 times, have tried with no GPU installed and still happens. Any help would be appreciated
 
Sort by date Sort by votes
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .


What are specs of the PC?

NTOSKRNL = windows kernel. It handles all driver requests, power management, and memory management. It sits between Hardware and Applications. It got blamed but its not the cause

Bluescreenview shows what crashed... ntoskrnl does almost everything in PC so its often seen as cause. Its unlikely though as windows would not work if it was.
 
Upvote 0 Downvote
Without going into intimate detail, all of the dumps strongly suggest a RAM problem. Two of the dumps fail with 0xC0000005 exception code errors, that's a memory access violation, and for Windows drivers. The other three dumps all contain a misaligned instruction pointer error, and that's also indicative of a memory (RAM) issue.

I can see from the dump that you're running Corsair CMK32GX5M2D6000Z36 6000MHz DDR-5 RAM in slots A2 and B2 (which is correct). At these speeds everything has to work perfectly. I realise that Memtest has found no errors, but no memory tester is 100% accurate, so I suggest you remove one stick of RAM and see whether it's stable on just one stick. If you get a BSOD then swap sticks and try it on just the other stick. It's also worth downclocking a tad to see whether the RAM is more stable at slower speeds.
 
Upvote 0 Downvote
there I was replying and I am beaten to the post... oh well.

have you done a clean install? bsod that survive reinstalls can be hardware as its unlikely you get same drivers twice

report - click run as fiddle to read (mostly for me)


File: 091923-8750-01.dmp (Sep 19 2023 - 21:16:12)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: ntkrnlmp.exe (Process: Starfield.exe)
Uptime: 0 Day(s), 0 Hour(s), 15 Min(s), and 08 Sec(s)

File: 091923-8468-01.dmp (Sep 19 2023 - 18:57:21)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: ntkrnlmp.exe (Process: msedgewebview2)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 09 Sec(s)

File: 091923-8296-01.dmp (Sep 19 2023 - 18:55:52)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: hardware (Process: Starfield.exe)
Uptime: 0 Day(s), 0 Hour(s), 03 Min(s), and 48 Sec(s)

File: 091923-8281-01.dmp (Sep 19 2023 - 19:10:32)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: hardware (Process: Starfield.exe)
Uptime: 0 Day(s), 0 Hour(s), 12 Min(s), and 51 Sec(s)

File: 091923-10296-01.dmp (Sep 19 2023 - 19:32:09)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: hardware (Process: Starfield.exe)
Uptime: 0 Day(s), 0 Hour(s), 21 Min(s), and 18 Sec(s)

process named is victim... sure doesn't like Starfield.
ntkrnlmp is also part of windows kernel

CPU = i7-13700K
MB = MSI PRO Z790-A WIFI (MS-7E07) I assume you have latest BIOS (it is a beta) - https://www.msi.com/Motherboard/PRO-Z790-A-WIFI/support - it has same date as your current one. MSI bios codes don't match up with what shows in reports (they never have)
RAM = 32gb Corsair DDR5
GPU - RTX 4070
Storage
C Drive: Crucial 2tb
1tb Samsung 980
What PSU?

try updating intel lan & wifi drivers, you have ones from 2022, there are newer here - https://www.msi.com/Motherboard/PRO-Z790-A-WIFI/support#driver
 
Upvote 0 Downvote
This is my 3rd clean install I think now haha, PSU is MSI MAG A750GF, I did update my BIOS but have since removed the battery not sure if that resets updates? Will update the drivers now. I did test both my ram sticks individually but that was just through memtest86 as wasn't sure how to force it to blue screen, but I guess I can use Starfield as a test subject haha.
 
Upvote 0 Downvote
First off, the process name in a dump is not a good indicator of the problem location. Remember that the kernel address range is accessible in every address space, so it's quiote often the case that the process in control had nothing at all to do with a bugcheck that the kernel detected and which was caused by a completely different process. The Starfield.exe process might well be at fault, but you can't assume that just because it's named in several dumps.

Secondly, if this is the third clean install you've done (note: NOT a Windows Rest), and you installed ALL necessary drivers each time, then you have a hardware problem.

The three dumps you just uploaded (19th Sept) all point at a hardware problem, and most likely RAM. Two dumps fail with a (fairly rare) 0x20001, HYPERVISOR_ERROR bugcheck. This bugcheck is almost always hardware related. The other dump is a more common 0xA, IRQL_NOT_LESS_OR_EQUAL bugcheck, these are typoically caused by bad third-party drivers. In this case however, the page fault that caused the bugcheck happens the instant the kernel is entered.

All this further strengthens what I said in post #3, that this looks very much like a RAM issue. You said that...
This is the crashes with no RAM overclock, and using just 1 stick at a time
Click to expand...
Are you saying that these three dumps occurred when using a different RAM stick on its own? If it BSODs with either stick when running on its own then I would have to suspect the motherboard, either the memory controller or (more likely) a bad slot. Can you try each stick of RAM on its own in each of the slots?
 
Upvote 0 Downvote
okay, just checking.

have you run this?
www.intel.com

Intel® Processor Diagnostic Tool

This download record installs the Intel® Processor Diagnostic Tool release 4.1.8.40, which is compatible with multiprocessor systems.
www.intel.com www.intel.com

As apart from guessing its often difficult to prove Motherboard is cause. So we check other things as well.

listen to @ubuysa as they know what they talking about :) I am just assisting.
 
Last edited:
Upvote 0 Downvote
Colif said:
okay, just checking.

have you run this?
www.intel.com

Intel® Processor Diagnostic Tool

This download record installs the Intel® Processor Diagnostic Tool release 4.1.8.40, which is compatible with multiprocessor systems.
www.intel.com www.intel.com

As apart from guessing its often difficult to prove Motherboard is cause. So we check other things as well.

listen to @ubuysa as they know what they talking about :) I am just assisting.
Click to expand...
I have downloaded and run that test, it appears to have frozen up at the floating point testing
 
Upvote 0 Downvote
Ouch. I was hoping it was RAM, but it now looks as though your CPU may be bad. For confirmation you might try running Prime95 (https://www.mersenne.org/download/). Run all three tests (smallFFTs, largeFFTs, and Blend) for at least 2 hours per test - if you can.

You'll need to also run a temperature monitor (like CoreTemp - https://www.alcpu.com/CoreTemp/) because Prime95 will make your CPU run hot.

If Prime95 generates errors, if the system BSODs, freezes, of crashes, or if the CPU gets too hot, then stop the test and let us know what happened.
 
Upvote 0 Downvote
www.dropbox.com

minidump3.zip

Shared with Dropbox
www.dropbox.com www.dropbox.com
Prime95 closed shortly after hitting run a few times, then bluescreened on one of them, it froze up the pc the next attempt and the cpu motherboard debug LED came on after pressing the restart button.
 
Upvote 0 Downvote
Ran prime95 again and as soon as it got to the CPU load test it froze up the whole pc, I'm guessing that means it's more than likely cpu issue guaranteed, was caused by Ntfs.sys+ 7784 on that last one
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom