Blue Screen of Death where Ntoskrll is causing the problem, according to BlueScreenView.
Blue Screen of Death where Ntoskrll is causing the problem, according to BlueScreenView.
I just bought a brand new PC and it worked well for about three weeks now. It started crashing and showing the blue screen of death again at random times. I completely reset my computer and just reinstalled Windows 11, but it's happening right after I turn on the desktop. I tested my memory with memtest86 three times and all tests passed. Even without a graphics card installed, this still happens. Do you have any advice?
Open your computer's File Explorer, go to this spot: C:\Windows\Minidump. Copy the mini-dump files and move them to your Desktop. Don't use Winzip; just use what Windows already has built in. Pick those files on your desktop and right-click them, then choose "Send To" - Compressed (zipped) folder. Upload that zip file to a cloud storage site like OneDrive or Dropbox. Then post a link here so we can see the file for you. What are the specs of the computer? NTOSKRNL = Windows Kernel. It handles all driver requests, power saving settings, and memory management. It sits between your Hardware and your Apps. It got blamed but it's not really the cause. BluescreenView shows exactly what crashed... ntoskrnl does almost everything in a PC so its often seen as the root cause. Its unlikely though since Windows wouldn't work at all if that thing was broken.
Here is the link to minidumps from minidumps.zip that I shared with Dropbox at www.dropbox.com. Also, I downloaded speccy and made a snapshot of my PC to show its specs here: http://speccy.piriform.com/results/WdNnZ...kCWl7QkE8l
Without digging too deep, all of these errors point to a RAM problem. Two dumps show 0xC0000005 messages, which means Windows drivers are having trouble reading memory. The other three shows an instruction pointer error that also suggests the RAM is acting up. From what I can see, you're using Corsair CMK32GX5M2D6000Z36 6000MHz DDR-5 RAM in slots A2 and B2 (which is set up right). At these speeds, everything should work perfectly. I know that Memtest found no problems, but a memory checker isn't perfect, so try taking out one stick to see if it works on just one stick instead. If you get a BSOD error when switching sticks, swap them around and test the other one alone. It's also a good idea to slow down your speed a bit to check if the RAM is more stable at lower frequencies.
I was trying to reply when I got really beaten up to the post. Oh well, did you do a clean install? BSODs that happen after reinstalls can be hardware related since it's unlikely you get the 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...ort#driver
Here are some crashes without turning up the RAM speed or using just one stick of memory. The most recent crash happened right away when I tried typing in a password. I had to force restart the computer, which then turned on a red light on my Mother Board. I'm not sure if that light means anything.
First off, the name of a dump file doesn't really tell you where the problem is. Remember that the kernel address space can be used everywhere, so it's very common for the process running things to have nothing at all when a bugcheck happens and gets reported back. The Starfield.exe process might actually be responsible, but just because its name shows up in several dumps doesn't mean it did everything. If you've done this clean install three times (and not with Windows Rest), then maybe your hardware is broken. The three dumps you sent over from September 19th all point to a hardware issue, and most likely the RAM stick. Two of those dumps crash right away with a rare error code, 0x20001, which usually means something isn't working properly inside the memory itself. The other one shows up as an IRQL_NOT_LESS_OR_EQUAL error (code 0xA), but these are often caused by bad drivers from third-party software. In this situation though, the crash happens right when the kernel starts running. All of this points back to what I said in post #3, which is that it looks like a RAM problem. You mentioned... Are you saying those three dumps happened while using just one stick of RAM on its own? If that same stick crashes with either stick when used alone then I'd have to suspect the motherboard, specifically the memory controller or (more likely) a bad slot. Can you try each stick of RAM in each slot separately?
The last three came from me testing only one stick of RAM out of two that I own. I'll put them in each slot and check if they keep crashing again.