Bunch of Random BSODs that seem unrelated

I actually was going to suggest testing your RAM by running two modules at a time today if the manual settings did not resolve the problem. Test with your current two modules for a while and see if the system remains stable. Then test with the other two. See if maybe you have a bad RAM module. If you find that a pair does not work, then try one at a time to determine which. Also, test the slots themselves with a good module. If you crash with a known good module in a different slot, it may be a bad motherboard slot.

Make sure you practice safe ElectroStatic Discharge (ESD) practices. Avoid Static Damage to Your PC | PCWorld



With all four modules, you may also need to bump the QPI/VTT voltage to 1.15 Volts.

ntkrnlmp is on all systems.

H2SO4 said:

NTKRNLMP = "NT KeRNeL, Multi-Processor version"

That file is the most important one in the entire OS, seeing as it contains the vast majority of its low-level internals. BSODs frequently get attributed to ntkrnlmp, but that's because it was dealing with bad data at the time of the crash.

My impression from a quick look through these minidumps is that you've got a hardware problem. There are at least 5 or 6 different crash patterns, and they're all fairly exotic. It's possible that some of them have software causes, but that's not what you should focus on in the suspected presence of bad hardware.

The fact that it also used to crash under Vista is telling. The fact that it doesn't happen when you remove some of the RAM virtually seals it - this is a hardware issue and continued looking at minidumps or BSOD info will not be particularly useful.

Were your RAM sticks all from the same set? Corsair are notorious for varying timings and other details even between batches of the (supposedly) same product.

Quote taken from https://www.sevenforums.com/crashes-d...tml#post290509



It is in C:\symbols. See the attached picture.

writhziden said:

ntkrnlmp is on all systems.

H2SO4 said:

NTKRNLMP = "NT KeRNeL, Multi-Processor version"

That file is the most important one in the entire OS, seeing as it contains the vast majority of its low-level internals. BSODs frequently get attributed to ntkrnlmp, but that's because it was dealing with bad data at the time of the crash.

My impression from a quick look through these minidumps is that you've got a hardware problem. There are at least 5 or 6 different crash patterns, and they're all fairly exotic. It's possible that some of them have software causes, but that's not what you should focus on in the suspected presence of bad hardware.

The fact that it also used to crash under Vista is telling. The fact that it doesn't happen when you remove some of the RAM virtually seals it - this is a hardware issue and continued looking at minidumps or BSOD info will not be particularly useful.

Were your RAM sticks all from the same set? Corsair are notorious for varying timings and other details even between batches of the (supposedly) same product.

Quote taken from https://www.sevenforums.com/crashes-d...tml#post290509


I should mention I also cannot find ntkrnlmp.exe on my system, but I know it is there. I will have to do research to find out why it does not show up in a search or through processes. My guess is that it goes by another name or multiple names that make up the overall process.

Like i said, i am a beginner. I look at DMP's cause i think it's fun in my own weird way. UPDATE: Still suspicious of it, searched my entire hard drive and it didn't find anything.

Yea I have serious doubts that its virus related especially as these started with a build with only the drivers installed and a few random known benchmark programs. I am not putting it as 10% driver related and the rest memory incompatibilities with my motherboard or some combination there of. This driver vagueness is why I thought it might be software and why I am here as I know basically nothing about the BSOD process.

The more we delved into it the more it seems like this is the best answer. You are of course welcome to go through all the dump files. I ended up emailing corsair tech support to see what they recommend doing so if you guys want to hear the end of this tale ill update it with what they say.

Just noticed recommendation for QPI voltage. I'll look into that when I am in front if the computer again.