You're experiencing several crashes due to BSODs?
You're experiencing several crashes due to BSODs?
I've experienced several blue screen occurrences over the past few months. Many were resolved after discovering that my old motherboard and several components had been damaged by a surge, often returning to Ntoskrnl.exe. I've visited a technician multiple times, but he consistently fails to reproduce the blue screen issue. Recently, after bringing the PC home, it crashed again within a few hours. The only remaining original part from that period is my CPU, which the technician believes is unaffected and suspects environmental factors. I obtained an uninterruptible power supply at his advice because of the unreliable electrical system in our home (the landlord connects his fence to the same power as the house). At this point, I still don't know what's causing the problem. I'm not very skilled at interpreting minidumps, and nothing I try seems to resolve the issue or identify the root cause.
The blue screen messages I encounter most frequently are:
DPC_Watchdog_Violation and IRQL-Not_Less_or_Equal with a few System_Service_Exception, System_Thread__Exception_Not_Hanndled and a single Memory_Managment.
System specifications:
- 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
- Drives: Crucial P3 4TB, Crucial T500 2TB(C drive)
- Minidumps:
https://drive.google.com/file/d/1Khk0LYh...sp=sharing
https://drive.google.com/file/d/1YSxOYtP...sp=sharing
https://drive.google.com/file/d/1dskVfBi...sp=sharing
https://drive.google.com/file/d/1_S7G7JU...sp=sharing
https://drive.google.com/file/d/13qVF9RM...sp=sharing
Welcome to the forums, newcomer!
ntkrnlmp.exe
GenuineIntel.sys
are things I observed in your 6 .dmp files with WinDBG.
Would you like to check Device Manager and look for any warnings marked with a yellow exclamation?
BIOS version for your motherboard right now?
Power: Segotep 750w
Segotep is the brand, and 750W is the claimed power output. What model are you using?
Many issues have been resolved after discovering that my old motherboard and several components failed due to a surge, yet some still persist and often reference Ntoskrnl.exe.
Have you reinstalled the operating system after replacing the new motherboard?
I've reviewed the device manager and found no yellow indicators, though I'll check again at home.
The BIOS version is A.50, which is the latest MB model I could obtain that wasn't experimental.
I don't recall the exact model name; it seems to be related to GM gold modular. The documentation mentions it on the box. The technician who handled it had it in stock and swapped it with my old one. I'll need to verify this again.
The remaining component is the CPU, and the tech confirms it's in good condition. My friend and I aren't entirely confident yet, but I want to be sure before spending money on a replacement.
I've reinstalled the OS twice since then.
Thanks for the welcome.
Received a new minidump file. Restarted the PC and waited while I finished dinner, then returned to the boot sector. The time from turning it on to reaching the boot sector took around 30 minutes. During this period I was idle with only startup services running.
Have you checked whether the crashes cease when XMP is turned off? Intel does not officially back your CPU for memory configurations exceeding DDR5-4800.
I don't have XMP. When checking bios, all I see is iEXPO and I can't locate any XMP profile. It's confusing since I have an Intel CPU and chipset on my motherboard. The bsods also occur whether the iEXPO profile is loaded or not.
Played a game for a few hours prior, then my computer crashed after roughly three minutes, displaying a blue screen error. DPC_Wacthdog_Violation.
The previous two entries were:
- A memory management issue linked to ntkrnlmp.exe, showing a registry change.
- A system service exception tied to ntkrnlmp.exe within chrome.exe, with short uptime.
- Another memory management problem connected to ntkrnlmp.exe and System, lasting 12 minutes.
- A DPC watchdog violation involving ntkrnlmp.exe, indicating a system-level error.
- A crash report noting ntkrnlmp.exe as the cause, with details about Windows Defender and possible LAN driver issues.
I saved and set up the drivers. I had them before but reinstalled to verify everything was functioning properly.
I removed the download manager. This was due to past issues with extremely slow download speeds.