Question I'm getting multiple BSODs ?

Toggle sidebar Toggle sidebar
HawKitsune

HawKitsune

Jun 16, 2024
60
2
35
I've been having multiple different blue screens for the last couple of months. A lot have been solved due to finding out that my old motherboard and most of my old parts were fried during a surge but some keep persisting and calling back mostly to Ntoskrnl.exe. I have taken the pc to a tech a few times and he cannot seem to get the pc to blue screen at all. He had it almost a week last time running stress test and had no issue.

I bring it home and a few hours later it has another crash. I have only one original part from the fried motherboard era and that is my CPU which the tech is certain has no issues. He thinks it might be environmental but I got a uninterruptible power supply on his recommendation due to currently living with not so good electrical system (landlord ties his electric fence into the same power as the house). As of now I have no idea what is wrong. I'm not really that good at reading minidumps and nothing I do seems to fix it or find a root issue.

The blue screen codes I get the most of recently are:
DPC_Watchdog_Violation and IRQL-Not_Less_or_Equal with a smattering of System_Service_Exception, System_Thread__Exception_Not_Hanndled and a single Memory_Managment.

My system specs are:
MB: MSI MAG Z790 Tomahawk Max Wifi
CPU: Intel Core i5-12600KF
CPU Cooler: Noctua NH-U12S redux with NF-P12 redux - 1700pwm
RAM: Teamgroup TForce Vulkan Alpha ddr5-5600 32GB (dual channel)
GPU: Nvidia Geforce RTX 3060 ti
Power: Segotep 750w
Drive's: Crucial P3 4TB, Crucial T500 2TB(C drive)

Minidumps:
https://drive.google.com/file/d/1Khk0LYhd0vzl0bcjDl7xryZkvDLsOhbR/view?usp=sharing
https://drive.google.com/file/d/1YSxOYtPOWlrPtHJhaKrM_bJq0SmRWy8M/view?usp=sharing
https://drive.google.com/file/d/1dskVfBivoYiY6vxJ0sJI7ZFcNUB_5zkh/view?usp=sharing
https://drive.google.com/file/d/1_S7G7JU-GcTsXxwEhiSREq-DUu1ldZ_R/view?usp=sharing
https://drive.google.com/file/d/1SXV4S6GPh1whzn1_IXjM4rWnL_VgzeQj/view?usp=sharing
https://drive.google.com/file/d/13qVF9RM0Btrnl_D-RjlMfM1jR-TeUO0A/view?usp=sharing
 
Sort by date Sort by votes
Welcome to the forums, newcomer!

ntkrnlmp.exe
GenuineIntel.sys
are items that I noticed across your 6 .dmp files using WinDBG

Might want to open up Device Manager and see if any items are being flagged with a yellow exclamation mark. BIOS version for your motherboard at this moment of time?

Power: Segotep 750w
Segotep is the brand of the unit while 750W is the advertised wattage of the unit. What is the model of the unit?

A lot have been solved due to finding out that my old motherboard and most of my old parts were fried during a surge but some keep persisting and calling back mostly to Ntoskrnl.exe.
Did you reinstall the OS after the new motherboard came through?
 
Upvote 0 Downvote
Lutfij said:
Welcome to the forums, newcomer!

ntkrnlmp.exe
GenuineIntel.sys
are items that I noticed across your 6 .dmp files using WinDBG

Might want to open up Device Manager and see if any items are being flagged with a yellow exclamation mark. BIOS version for your motherboard at this moment of time?

Power: Segotep 750w
Segotep is the brand of the unit while 750W is the advertised wattage of the unit. What is the model of the unit?

A lot have been solved due to finding out that my old motherboard and most of my old parts were fried during a surge but some keep persisting and calling back mostly to Ntoskrnl.exe.
Did you reinstall the OS after the new motherboard came through?
Click to expand...
I've checked device manager and nothing shows yellow but I'll take another look when I get home.

The bios version is A.50 which is the newest for the MB that I could get that wasn't experimental.

I honestly don't remember the model. I think something about GM gold modular. The box has just that on it. The tech I took it to had it in stock and replaced it with my old one. I'll have to look it up again.

The only part left is the CPU and the tech assures me it's fine. My buddy and I aren't that sure that's it's fine but I need to be sure it's gone/bad before I spend the money for a new one.

Yes I've had the OS reinstalled twice since then.

Also thanks for the welcome.
 
Last edited:
Upvote 0 Downvote
cwsink said:
Have you tried to see if the crashes stop with XMP disabled? Intel doesn't officially support your CPU at memory settings above DDR5-4800.
Click to expand...
I don't have XMP. When looking at bios all I see is iEXPO and I cannot find any XMP profile. It confuses me quite a bit as I have an Intel CPU and an Intel chipset on my MB.

The bsods also happen with that iEXPO profile loaded or not loaded.
 
Upvote 0 Downvote
Was the last two: (until you posted another one)
File: 061824-7656-01.dmp (Jun 19 2024 - 11:01:26)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: ntkrnlmp.exe (Process: Registry)
Uptime: 2 Day(s), 3 Hour(s), 14 Min(s), and 28 Sec(s)

File: 061824-14843-01.dmp (Jun 19 2024 - 11:36:04)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: ntkrnlmp.exe (Process: chrome.exe)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 51 Sec(s)

report

remainder:
File: 061624-7562-01.dmp (Jun 17 2024 - 07:46:13)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 1 Hour(s), 27 Min(s), and 02 Sec(s)

File: 061624-17937-01.dmp (Jun 17 2024 - 04:26:23)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: ntkrnlmp.exe (Process: MsMpEng.exe)
Uptime: 0 Day(s), 2 Hour(s), 24 Min(s), and 24 Sec(s)

File: 061624-17390-01.dmp (Jun 15 2024 - 20:40:36)
BugCheck: [DPC_WATCHDOG_VIOLATION (133)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 6 Hour(s), 18 Min(s), and 56 Sec(s)

File: 061424-13750-01.dmp (Jun 15 2024 - 12:17:06)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: memory_corruption (Process: SystemSettings.exe)
Uptime: 0 Day(s), 0 Hour(s), 03 Min(s), and 18 Sec(s)

File: 061424-13406-01.dmp (Jun 15 2024 - 12:13:11)
BugCheck: [DPC_WATCHDOG_VIOLATION (133)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 12 Min(s), and 08 Sec(s)

File: 061324-7328-01.dmp (Jun 14 2024 - 13:04:56)
BugCheck: [DPC_WATCHDOG_VIOLATION (133)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 11 Hour(s), 00 Min(s), and 18 Sec(s)


report
last crash:

File: 061924-9234-01.dmp (Jun 19 2024 - 16:39:29)
BugCheck: [DPC_WATCHDOG_VIOLATION (133)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 5 Hour(s), 01 Min(s), and 34 Sec(s)
report

ntkrnlmp - NT Kernal Multi Processor (part of windows, victim, not cause)
Lutfij said:
GenuineIntel.sys
Click to expand...
That is not a driver, its just an identifier proving its a genuine Intel CPU.
Processes named are victims. Parts of windows don't generally cause BSOD, they are just following faulty instructions from drivers.
MsMpEng.exe = Windows Defender.. its the one clue I had to suggest LAN drivers.
Chrome also crashing could also mean lan drivers

try updating your intel lan drivers
https://www.msi.com/Motherboard/MAG-Z790-TOMAHAWK-MAX-WIFI/support#driver
if you use wifi, I would do those as well.
this can cause problems as well
Nov 19 2023idmwfp.sysInternet Download Manager WFP driver (Tonec Inc.)
 
Last edited:
Upvote 0 Downvote
Upvote 0 Downvote
File: 061324-7328-01.dmp (Jun 14 2024 - 13:04:56)
BugCheck: [DPC_WATCHDOG_VIOLATION (133)]
Probably caused by: ntkrnlmp.exe (Process: System)
Uptime: 0 Day(s), 11 Hour(s), 00 Min(s), and 18 Sec(s)

report

Nov 19 2023idmwfp.sysInternet Download Manager WFP driver (Tonec Inc.)

its still running.

try running this
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns
it can see everything loaded with windows. There is a driver tab
YzWkxrf.jpeg


You can stop it loading using the blue ticks, or right click the driver and uninstall from here
 
Upvote 0 Downvote
Colif said:
It might not be cause but it is one less possibility.
Click to expand...
Whatever helps. I just want to finally be done with this one day. I'm hoping with y'all's helps the cause can be narrowed down so it can be fixed if it's software or replaced if it's hardware and I get the money saved. Really hoping it's software.

I'm going to leave my PC running today while at work and see if anything happens.
 
Upvote 0 Downvote
Colif said:
dpc latency. I can guess it would fail a latencymon run.
its why i looked at internet as most of the time the cause can be network drivers

Do you use wifi or Ethernet?
disabling the one you don't use can help with latency.
Click to expand...
I use Ethernet now. The wifi is turned off via network settings. Unless I need to disable the wifi device via device manager.
 
Upvote 0 Downvote
From the two most recent dumps this looks very much like a RAM problem. One of the bugchecks is even a 0x1A MEMORY_MANAGEMENT with an argument 1 value of 0x8886, indicating that two standby RAM pages that should have had similar priority values are in fact different.

The other dump is a 0x3B SYSTEM_SERVICE_EXCEPTIOn with an exception indicating that an attempt was made to execute an illegal instruction, you can see this in the trap frame...
Code: 
4: kd> .trap ffffbc83`5f216620
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb00004e96ea0 rbx=0000000000000000 rcx=7fffffffffffffff
rdx=ffffb00180023e70 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8035f43d28d rsp=ffffbc835f2167b0 rbp=00000000001a324f
 r8=ffffb000174a80f0  r9=f07fffffffffffff r10=00000000007c3805
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!MiUnlinkPageFromListEx+0x7ad:
fffff803`5f43d28d ff              ???
The instruction pointer (RIP register) is pointing at the opcode 0xFF, which does not exist, hence the BSOD. If I disassemble the relevant part of the nt!MiUnlinkPageFromListEx function you'll see what went wrong...
Rich (BB code): 
nt!MiUnlinkPageFromListEx+0x79e:
fffff803`5f43d27e 80bc244801000000 cmp     byte ptr [rsp+148h],0
fffff803`5f43d286 48b9ffffffffffffff7f mov rcx,7FFFFFFFFFFFFFFFh     <===The RIP register is pointing 8 bytes further on than it should be!
fffff803`5f43d290 740d            je      nt!MiUnlinkPageFromListEx+0x7bf (fffff803`5f43d29f)  Branch
I can see from the dump that you're running your two sticks of Teamgroup UD5-5600 DDR5 RAM at the rated speed of 5600MT/s. The problem is that your Intel i5-12600KF CPU cannot handle DDR5 RAM faster than 4800 MT/s - see https://ark.intel.com/content/www/u...600kf-processor-20m-cache-up-to-4-90-ghz.html.

I suggest you disable the XMP profile you have and run the RAM at the stock speed of 4800MT/s that the CPU can handle.
 
  • Like
Reactions: Dark Lord of Tech
Upvote 0 Downvote
At work and was just sent a picture of my PC blue screened again. A "DPC_Watchdog_Violation". I was running Intel's processor diagnostic tool in a loop while I am not home. Will provide the mini dump when I get home.
 
Upvote 0 Downvote
Both those 0x133 dumps happened because a collection of DPCs (the back end of device interrupt processing) ran for too long. The only way to debug that particular BSOD is with the kernel dump, it's the file C:\Windows\Memory.dmp. Upload that to a cloud service and I'll take a look.
 
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