Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Windows 10 crashing, but not sure why.

In the last couple of days, Windows 10 fails to start when switching from OS X to Windows in Bootcamp. I recently installed the latest update to OS X El Capitan and Windows started fine from Bootcamp. After about 3-4 mins in Windows -- it was downloading and installing updates -- screen goes black, and then a screen pops up indicating "Attempting Automatic Repairs". Those automatic repairs failed. After several attempts to restart, I eventually got a "no bootable disk found" error.


So I decided to use Bootcamp Assistant to uninstall Windows and remove the partition, and then do a fresh partition and windows reinstall. Same thing happens. Windows installs fine, runs fine for 3-4 mins and then crashes.


I have no idea if this crash is due to a Microsoft issue involving updates, a conflict involving Bootcamp or Apple drivers, or something else. Anyone have ideas?

iMac, OS X El Capitan (10.11.3), iMac 2015 21.5 4k Retina

Posted on Jan 28, 2016 5:42 PM

Reply
100 replies

Jan 28, 2016 9:32 PM in response to Headhunter06

Can remove and re-install W10 and not connect to any network during the W10 installation? Once W10 is completely installed and BC drivers are in place, create a Windows System Restore point. Connect to the Internet and try Windows Update. If it behaves the same way, roll back to the Restore Point without connecting to the network, and disable Windows Automatic Updates. After Automatic Updates are disabled, connect to the network and test.

Jan 28, 2016 9:33 PM in response to Loner T

Yes, this worked. There is some Intel driver that Windows Update downloads -- possibly the Iris Pro 6200 driver or one of the various Chipset updates -- that seems to hang the system.


I did two things: First, I used "Metered Connection" to stop some of the updates, but not the Windows 10 system updates such as the cumulative or Internet Browser, etc. This allowed Windows to successfully activate. Once those updates were installed, I used Control Panel/Administrative Tools/Services to disable Windows Update. I also used a MS Windows tool to "Hide or Show Updates" to select all of the Intel updates -- of which there are many -- to stop those from installing.


Once all of that was done, I created a Restore Point.


Interesting thing: With the above it ran fine for hours. Then on a whim, I turned off the "Metered Connection" setting. Within maybe 3-4 mins, some unknown update was downloaded and crashed the system. When the Repair screen came up, Restore got me back and running.


Best I can figure, one of the many Intel drivers is causing the crash.

Jan 29, 2016 7:32 AM in response to Headhunter06

Headhunter06 wrote:


Best I can figure, one of the many Intel drivers is causing the crash.

I have seen several cases of this so far, where Iris drivers are being applied by Windows Update to Macs, and the VendorID/PID of the Mac versions is included, which should not be. There are enough differences. I do not know if Intel is the issue (not assigning proper VID/PID) or Apple is lazy (using VID/PID without ensuring that they match the regular PC versions). Apple is known to do this with some AMD cards as well. It causes pain and grief for the user.


My recommendation to look very closely at Drivers provided by Windows Update, before you let them in on your Mac.

Jan 29, 2016 3:36 PM in response to falterego

There are three methods: The first is to go into your Windows wifi settings and select the option to make your wifi connection a "metered" connection. This suspends automatic downloads, unless you specifically select them.


The second option, is the Microsoft "Show Hide Updates" tool. https://support.microsoft.com/en-us/kb/3073930. I set it up to suspend updates for all Intel drivers. Unfortunately, I have no idea how long that suspension lasts -- whether permanently until deselected, until next update is posted, or what. The documentation for it is light at best.


Last option is to go into Control Panels/Administrative Tools/Services and manually stop and disable Windows Update. Don't do this for an initial install (or reinstall) of Windows because it needs the update function to activate Windows. But as soon as activated, you can shut it off.


Anyway, it seems the Apple issued Intel Iris Pro 6200 drivers that Bootcamp installs work fine. The newer driver offered through Windows Update seems to be the culprit. My system worked flawlessly until that new driver was issued through the Windows Update.

Jan 31, 2016 8:22 PM in response to Loner T

The last option, "go into Control Panels/Administrative Tools/Services and manually stop and disable Windows Update," is the only one that actually stops the update from installing and makes the system usable. Obviously it's not good for the long term health or stability of the system, but for now it's the only thing I've found that works.

Feb 2, 2016 3:43 AM in response to Headhunter06

Today I found a permanent solution.


I had the same problems as described.
I reinstalled win 10 with no internet connection. I installed the bootcamp software (with the Realtek hanging solution) and before I rebooted the system i installed the drivers for my intel iris 5200 pro (iMac mid 2013) found on the intel website. http://www.intel.com/content/www/us/en/support/graphics-drivers/intel-iris-pro-g raphics-5200-for-4th-generation-intel-core-processors.html Only after reboot i connected to the internet and everything was fine!


Hope this helps!

Feb 2, 2016 4:45 PM in response to Turborg

Did this actually fix the problem permanently for you? When I tried this, Windows Update eventually tried to install its own driver anyway, which again crashed the computer. And there is a thread on Reddit where someone figured out that it might be because Microsoft is pushing a driver that is still in beta.

Feb 3, 2016 7:19 PM in response to jrkagan

Just out of stupidity -- and with nothing better to do with my evening -- I again tried re-enabling Windows Update and doing an update. But before I did so, I again used the Microsoft "Show-Hide Updates Tool" to disable all Intel updates. This time it seemed to work. As soon as updates were complete and the system rebooted, I again turned off and disabled Windows Update in the Services section, and created a Restore Point. So far, no BSOD after an hour or so of hard use. I do notice that if Updates is manually disabled and Windows can't phone home, that it will within a day or two return a "Windows is not Activated" error. For my needs, this is no problem -- all I'm doing is MS Flight Simulator, X-Box, and Steam for me and my son. Fingers crossed this is the best temp fix until the offending drivers are properly re-issued.

Feb 5, 2016 2:49 PM in response to Headhunter06

Thanks for this solution Headhunter06! Your "second option" (29 Jan. 3:36) helped me out after some days of problems with black screens and headache how to solve this.

Hoping that Microsoft and Intel can supply a new driver update (someday) that keeps our systems running. In the meantime: no Intel driver updates via Windows Update for me!

Windows 10 crashing, but not sure why.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.