Q: Getting BSOD's with different error messages, help?

I've been having this problem for some time and I can't remember when it started.
First of all, my computer crashes whenever doing something more active, like playing a video game. The computer also crashes from a slight touch. For example, last day I plugged out the mouse, and the computer got a BSOD.
I get a variety of error messages, but the computer also acts strangely.
Here's how it goes:
I'm playing the game, and suddenly the computer crashes. Sometimes it just freezes with a buzzing sound coming from the speakers, and I have to force restart it, but most of the time it just crashes with a MEMORY_MANAGEMENT BSOD, and then the strange behavior starts to happen. My computer powers down, then turns on again and shuts down after ~2 seconds, then attempts to do the same again multiple times. It feels like it keeps losing power for some reason. Then it goes to the windows loading screen (I have Windows 8 64-bit pro), but the spinning loading icon does not appear. Instead, I get a BSOD after a couple of seconds displaying KERNEL_SECURITY_CHECK_FAILURE. After a couple of attempts like that the computer tries to do automatic repair, but crashes in the middle of the loading with the same security check BSOD. Finally, after ~10 attempts to boot up it finally manages to do so, and I can return to work. I am currently writing this from that computer.

Event viewer always displays "Event-41 Kernel Power" critical error after each BSOD, but now for the first time I got a different error.
I was playing a video game called Minecraft, and my computer suddenly got a BSOD. I wasn't surprised, but I noticed a different error - UNEXPECTED_KERNEL_MODE_TRAP, and the even viewer displays BUGCHECK this time instead of kernel power. This happened for the first time.

Here's a link to the dumps:

In both bugchecks I get "It's probably  ntkrnlmp.exe"

I may suspect my ram (2x 2GB kingston sticks and 2x 2GB crucial sticks), but memtest got all the passes clean without any errors. Although, if I try to boot after removing any stick of ram, the PC won't boot anymore, it just goes to the windows loading screen and the restarts without any errors infinitely, unless I put all 8GB back, so I can't check the sticks one by one.

The CPU and GPU are acting fine, I did some stress testing, they're in great shape and never overheat, there's no overclocking on my PC.

This problem has been bothering me for a very long time, any kind of help would be very appreciated.

Thank you.



To find the definitive cause please run these two tests.

These crashes were caused by memory corruption (probably a driver).  Please run these two tests to verify your memory and find which driver is causing the problem.  

*Dont forget to upload any further DMP files (especially those when verifier is running)

*If you are overclocking anything reset to default before running these tests.
In other words STOP!!!   If you dont know what this means you probably arent

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. 
*Boot from the CD, and leave it running for at least 5 or 6 passes.
*Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
*Test the sticks individually, and if you find a good one, test it in all slots.

Any errors are indicative of a memory problem.
If a known good stick fails in a motherboard slot it is probably the slot.

2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is.

*But sometimes it'll crash and won't tell you the driver.
*Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.
*I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise.
*Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Here is the procedure:

- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
*Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
*Reboot the system and wait for it to crash to the Blue Screen.
*Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.
*If you can't get into Windows because it crashes too soon, try it in Safe Mode.
*If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

*Further Reading

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT

Did this solve your problem?

Sorry this didn't help.

Question Info

Views: 3,525 Last updated: July 8, 2018 Applies to: