Windows 10: Bsod - machine_check_exception

Hello Ladies & Gents!

I'm a SevenForums member, DreadStar/DreadStarX! It's been a long time since I've been on here, and found that SF/EF/TF is one of the best resources for OS Problems.

So, here's the problem.

When I boot up VMWare Workstation, and attempt to install a Ubuntu 15.xx 32bit/64bit, it bluescreens after about 5 minutes. I thought at first it was because of my Dual GFX Cards, but that wasn't the case. I have plenty of memory/hdd/gfx memory.

I've uploaded my BSOD Report from the nifty tool z3r0 posted.

Attachment 50711

:)

 

Machine_check_exception BSOD

Download then run the
AVG and
Kaspersky removal tool if both were installed. And if both have been uninstalled.

If you havent yet

 

Machine_check_exception BSOD

Driver verifier came back with errors from kl1.sys. A Kaspersky related driver.

I always assumed it was hardware related. How do I go about repairing that troublesome driver? A clean uninstall/reinstall of Kaspersky?

 

Hi BinaryData,

Welcome to the 10forums.

The intel processor driver is causing the crashes.
Please check your manufacturer, MSI, for driver updates.
Code: 3: kd> k Child-SP RetAddr Call Site ffffd000`f1efc828 fffff800`94e89ee1 nt!KeBugCheckEx ffffd000`f1efc830 fffff800`94e8a2a8 hal!HalpMcaReportError+0xf5 ffffd000`f1efc980 fffff800`94e8a450 hal!HalpMceHandlerWithRendezvous+0xb0 ffffd000`f1efc9b0 fffff800`9475ae7b hal!HalHandleMcheck+0x40 ffffd000`f1efc9e0 fffff800`9475ac31 nt!KxMcheckAbort+0x7b ffffd000`f1efcb20 fffff800`a1782778 nt!KiMcheckAbort+0x171 ffffd000`f1f1c858 00000000`00000000 intelppm!MWaitIdle+0x18[/quote] Code: 3: kd> lmvm intelppm start end module name fffff800`a1780000 fffff800`a17a9000 intelppm (pdb symbols) d:\symbols\intelppm.pdb\89FABBD09556447FB6B157B5A3A81CD91\intelppm.pdb Loaded symbol image file: intelppm.sys Mapped memory image file: d:\symbols\intelppm.sys\559F383B29000\intelppm.sys Image path: \SystemRoot\System32\drivers\intelppm.sys Image name: intelppm.sys Timestamp: Fri Jul 10 05:12:59 2015 (559F383B) CheckSum: 0001FAC6 ImageSize: 00029000 File version: 10.0.10240.16384 Product version: 10.0.10240.16384 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 3.7 Driver File date: 00000000.00000000 Translations: 0409.04b0 CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: intelppm.sys OriginalFilename: intelppm.sys ProductVersion: 10.0.10240.16384 FileVersion: 10.0.10240.16384 (th1.150709-1700) FileDescription: Processor Device Driver LegalCopyright: © Microsoft Corporation. All rights reserved.[/quote]

 

Thanks a bunch! Now I'll have to figure that part out. Which driver specifically? I've never owned a laptop before *Tongue

 

As I said, the intel processor driver *Wink

 

Updated to the latest, tried to run the VMWare, and it still crashed. Want me to upload that BSOD too?

 

Please fill in the system specs correctly of the pc that has the problems
According to the logs you have a laptop, but according to your system specs you have a desktop.Please follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

Ok, I filled that info out based on my Desktop at home.

My laptop is a MSI Leopard Gaming Series GP72.

I will post my specs here, for the laptop.

CPU: Intel(R) Core(TM) i7-5700HQ CPU @ 2.70GHz
MOBO: Micro-Star International Co., Ltd. MS-1793
BIOS: E1793IMS.107
RAM: 8.00 GB
Usable RAM: 7.92 GB
HDD: (1) SDHC Card (2) HGST HTS721010A9E630
Sound: (1) Realtek High Definition Audio (2) NVIDIA Virtual Audio Device (Wave Extensible) (WDM)
GFX: (1) NVIDIA GeForce GTX 950M (2) Intel(R) HD Graphics 5600
OS: Microsoft Windows 10 Home 64-bit 10240 Multiprocessor Free

 

A 0x9C(machine_check_exception) is similar to a 0x124(WHEA_UNCORRECTABLE_ERROR), meaning both are usually caused by hardware problems (hardware, drivers, dust, loosy components etc.). A lot can't be (properly) checked with a laptop, like loosy components, dust, broken cables etc., so for now we just skip them and try the possible onces as one of the last options.

I suggest to test the CPU.





Diagnostic Test

CPU TEST


Run Prime95 - Stress Test Your CPU - Windows 10 Forums



Note If you're overclocking anything, please stop it and set everything back to default while troubleshooting


Warning Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.

 

Seems as if it wasn't a drivers problem, but a BIOS problem. I did a driver update on everything, no suffice. I did a BIOS Flash, and no more BSOD. I'll monitor it for the next few weeks, and go from there.

I will mark your post "Solved", once I'm 100% sure this is the cause.

On a side note, knowing how to read BSODs can be handy, who did you learn from or is there a tutorial?

 

I started learning it by myself, sometimes I get support from some amazing people when I ask for it, but I have mainly done it all myself.