Boot Camp and Windows 10 - KMODE_EXCEPTION_NOT_HANDLED

Question

Boot Camp and Windows 10 - KMODE_EXCEPTION_NOT_HANDLED

I've just upgraded from a Mac Air to a Macbook Pro (Retina 13-inch, Early 2015) 2.9GHz Intel Core i5, 8G Ram, 512G hard drive, Intel Iris Graphics 6100.

I was very happy with my Mac Air but wanted a bigger hard drive so i could use boot camp to run windows for 2 programs i need that don't run on Mac's.

I did a bit of reading and watched a few youtube videos on the windows install using boot camp before starting.

All went well, i've partitioned my hard drive but when it came to installing the windows 10 software, after formatting the partition and starting the install, the blue screen appears with

"Your PC ran into a problem and needs to restart. We'll restart for you.

"If you'd like to know more, you can search online later for this error.

KMODE_EXCEPTION_NOT_HANDLED

From my research it looks like it's a problem with the windows video driver.

There are solutions for regular windows machines but none of them address a new install on a mac using bootcamp.

Has anyone had the same issue?

Thanks in advance

MacBook Pro with Retina display, OS X Yosemite (10.10.5)

Posted on Sep 1, 2015 12:03 AM

Reply

Answer 1

Loner T

Level 9

59,536 points

Sep 1, 2015 8:58 AM in response to agjfromsydney

You can try the Intel drivers, instead of BC drivers.

Reply

Answer 2

Sep 1, 2015 4:09 PM in response to Loner T

Thanks Loner T.

The Boot Camp assistant downloads drivers during installation setup that include Intel ones.

Are you saying that i should replace that folder with Intel's Windows drivers?

Thanks

Reply

Answer 3

Loner T

Level 9

59,536 points

Sep 2, 2015 4:36 AM in response to agjfromsydney

There is a $WinPEDrivers$ directory on a USB installer that BC Assistant creates. It provide the Windows Installer a Preboot Environment (PE) and AutoUnattend.xml controls the setup of the PE. The drivers in the Bootcamp folder are installed silently once the base Windows installation is complete.

You can add/remove drivers in either location, based on your issue. If the Installer is working properly, leave the PE directory as is and manipulate the other locations.

Reply

Answer 4

Sep 2, 2015 6:38 PM in response to Loner T

Thanks Loner T, i'll give it a go.

Cheers

Reply

Answer 5

Loner T

Level 9

59,536 points

Sep 2, 2015 7:15 PM in response to agjfromsydney

Please post back if you run into any issues.

Reply

Answer 6

Sep 2, 2015 8:34 PM in response to Loner T

Unfortunately i still get the same blue screen and message.

This is exactly what i did.

I downloaded the Intel Drivers from the Intel website here

https://downloadcenter.intel.com/download/25150/Intel-Iris-Iris-Pro-and-HD-Graph ics-Production-Driver-for-Windows-10-64-…

I then replaced the DisplayAudio and Graphics directories in the $WinPEDriver$ / IntelHswBdwGfx64 folder with the ones i downloaded.

I'm not really very skilled at this sort of stuff so apologies if the above was not what you suggested i should do.

If you don't have any more solutions, do you think if i exchanged the Windows 10 software for Windows 8 and installed that then upgraded to Windows 10 it might work?

Thanks

Reply

Answer 7

GhonaZ

Level 3

572 points

Sep 9, 2015 12:17 AM in response to agjfromsydney

I can verify that an update to win10 after you have installed windows 8 works just fine at least for me on my rMPB 15" late 2013. However I would suggest to first try and reinstall windows 10 from scratch again.

Reply

Answer 8

Loner T

Level 9

59,536 points

Sep 9, 2015 12:16 AM in response to agjfromsydney

The PE directory does not impact what is installed by Windows. It only provides the PreBoot environment. My W7/W8-to-W10 upgrades are messy due to the way Apple chose to manage the driver transition from W7/W8 to W10. It works for some, but not for others. Once your W10 is registered with M$, you can do a clean install as GhonaZ suggests. I have had to do the same and then I get a very stable W10 system.

Reply

Answer 9

Sep 8, 2015 6:54 PM in response to Loner T

I'm guessing a clean install means starting the bootcamp process all over again?

I did this, copying the WIN10.iso that i had originally downloaded along with the windows support software from apple to usb.

Then went through the installation process but my machine shut down again with the same KMODE_ message.

I then tried the installation with the Windows 10 usb i received in the original packaging......same message.

1. Do you think it will make a difference if i remove the partition and start the entire process again?

or

2. When i set up my new MacPro i used the migration assistant and thunderbolt cable to transfer and create a clone of my MacAir first. I then partitioned my hard drive and tried to install Windows10. Do you think this may be the cause. If so should i try to erase my MacPro to original factory settings, partition and install Windows 10 then clone my MacAir?

Thanks

Reply

Answer 10

Sep 8, 2015 7:42 PM in response to agjfromsydney

Hi @ Loner T,

just read a post on another thread where you mentioned checking the .iso file is not corrupted.

I've found the md5 checksum hash of the .iso file i downloaded but can't seem to find anything on the microsoft site to compare it with?

Could you point me in the right direction.

Reply

Answer 11

Sep 9, 2015 12:16 AM in response to agjfromsydney

Just removed the partition and started the whole process afresh, maybe this is what you both meant by a clean install.

The whole process went well and fully installed with no problems

Thanks @ Loner T and @ GhonaZ

Reply

Answer 12

Loner T

Level 9

59,536 points

Sep 9, 2015 2:51 AM in response to agjfromsydney

Very nice. Please backup both OSX and Windows for future recovery. Use separate external physical drives, if possible.

Reply

Answer 13

Vick--23

Level 1

0 points

Oct 27, 2015 1:32 PM in response to Loner T

Hey I boot camped my new MacBook Pro (mid 2015) with Windows 10. Partition size 70gb. It worked great for a month or so. Now when I boot to windows it gives me the KMODE_EXCEPTION_NOT_HANDLED error. Really seeking some help Thanks!

Reply