Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Reverting back to Windows 8.1 Pro to enjoy my Windows applications/games and not to be constantly frustrated with this upgrade/activation issues, to put it very MILD!

I'll sit out the ride with Win8.1 atm, untill issues are ironed out a bit more!

Cheer

W8.1 ran pretty nice on my MP 5,1 but I often had little issues. Finally I got tired of the occasional fiddling and bought an HP Z230 for about the price of an upscale mini. What a wonderful improvement. All the Windows stuff works great, choice of equipment is enormous and I've got more USB3 ports than I can possibly use.

I upgraded to W10 last week. There is a bunch of unfinished business there such as Photos and Music but it runs really great. No improvement in Geekbench scores but the 3.6GHz i7 quad seems to run every bit as fast as my 3.45GHz six-core MP. I've got Bitlocker working on all drives and an actual, working built-in USB3 card reader. Love my Mac Pro but I am also really glad to be back to a genuine Windows PC.
 
W8.1 ran pretty nice on my MP 5,1 but I often had little issues.

I've no need for a PC as Windows 8.x is my best MS experience ever and runs great on my cMP 3.1 & 5.1 with no issues what so ever! Remembring the days of Vista? :-\

I need my fast booting and joyful Win8.1 back right away! Leaving the Windows 10 upgrade for "what could have been!" **** happens!

Untill I again meet with Windows 10!

Cheers
 
I'm not going back to 8.1. I like tracking down problems and eliminating them.

Disk access related crashes were definitely down to Samsung Magician. The screensaver related crash isn't new, it has been reported by users for years and depends on power management/video driver bugs. I can wait for updates and patches to fix it. Until then I disable screen savers.
 
Just installed 10 yesterday, on a separate HD, and now that drive won't appear at all under Yosemite. Disk Utility is unable to mount it. Option key startup shows the drive just fine, no problem booting it. Any ideas?
 
Just installed 10 yesterday, on a separate HD, and now that drive won't appear at all under Yosemite. Disk Utility is unable to mount it. Option key startup shows the drive just fine, no problem booting it. Any ideas?
Reset pram will probably work. Sounds like the 'bless' drive issue some have.
 
Yet another totally random BSOD. I am now learning how to read those minidump crash logs, it's all alien right now.

My next test is completely remove Steam as that and one game had issues with saving passwords and data. Let's see if that was hurting the system. Now in Windows install there is only, Photoshop, Office, FIFA, Skype, Dropbox, GeForce driver, Wacom driver, Bootcamp drivers, Sonnet Tempo Pro (AHCI), and USB 3.1 card (XHCI).
 
Can probably eliminate the GeForce and Wacom drivers as the BSOD source. Got those on mine and it's a solid tank thus far.
 
My next test is completely remove Steam as that and one game had issues with saving passwords and data. Let's see if that was hurting the system. Now in Windows install there is only, Photoshop, Office, FIFA, Skype, Dropbox, GeForce driver, Wacom driver, Bootcamp drivers, Sonnet Tempo Pro (AHCI), and USB 3.1 card (XHCI).

I'm having an odd issue where the GeForce framerate counter partially appears within the minimize/maximize/close buttons of many windows.

Skype is interesting to me. I had daily crashes with it under 8.1, but no crashes yet on 10. So if anything, that has actually improved.

Steam, Dropbox, Bootcamp drivers all working fine for me.

My USB card is substantially different than yours, but just for anyone else looking--the Fresco Logic USB 3.0 drivers work fine in Windows 10. Tested with an external USB 3.0 hard drive and a USB 3.0 thumb drive.

The Sonnet kind of stands out, plus they list support for Windows 7 and 8, but not 10. It's probably fine, but nevertheless it might be worth an email inquiry to Sonnet support. I sent an email on a different topic and they got back to me in a couple of days.
 
Aaaand another random BSOD. The developer debugging tool WinDBG tells me each crash is occurring at the kernel level so I'm going to do a complete clean reinstall and test out a clean system with no apps and no drivers. This gives me a chance to try EFI install and see if the crashes occur because of something in my most basic hardware configuration.
 
Before I decide on the clean install I'm removing the USB 3.1 card. This is the newest piece of hardware in the system and therefore has the least mature driver. It wasn't even made with X58 motherboards in mind. Historically ASMEDIA USB controllers have caused many BSOD to PC users. Just google 'Asmedia USB BSOD'

So I have taken it out and am stress testing Windows to see if I can get the same BSODs with the same crash logs.
 
Last edited:
Also remove all drives except the Windows boot drive to prevent partition shenanigans. I prepped mine by erasing it with the diskpart clean command on a separate computer, then let the Windows 10 installer format it and handle all the MS-Reserved and EFI partitions.
 
  • Like
Reactions: hfg and m4v3r1ck
Also remove all drives except the Windows boot drive to prevent partition shenanigans. I prepped mine by erasing it with the diskpart clean command on a separate computer, then let the Windows 10 installer format it and handle all the MS-Reserved and EFI partitions.

I don't have mixed partition drives. I tried to crash Windows for four hours last night and it stayed solid. So far so good.
 
No crashes or system instability since removing the ASUS USB 3.1 card. I have been stress testing the system by running over a dozen apps and multiple videos and websites simultaeonously for 36 hours now. I will keep testing like this for a few more days and if it remains stable that mean the USB card was the culprit. The driver is very immature and frankly if you google you will see many people over the years have had problems with Asmedia USB and SATA drivers crashing their computers. Here's a screenshot.
 

Attachments

  • image.jpeg
    image.jpeg
    599.1 KB · Views: 158
Ok, so. Apple have released an update to BootCamp for Windows10 and guess what.
No official support for anything oldr than the ’13 Mac Pro.

A**HOLES!!!
 
  • Like
Reactions: mtasquared
Ok, so. Apple have released an update to BootCamp for Windows10 and guess what.
No official support for anything oldr than the ’13 Mac Pro.

A**HOLES!!!

That's because there are no newer drivers for those models. Boot camp 5.1 already supports Windows 10, just not 'officially'. If Apple included the drivers for he older and newer models the BootCamp driver package would be over 3GB. It's pointless.
 
That's because there are no newer drivers for those models. Boot camp 5.1 already supports Windows 10, just not 'officially'. If Apple included the drivers for he older and newer models the BootCamp driver package would be over 3GB. It's pointless.
Then why not make it official?
 
Because if someone busts their old computer using Windows 10 with 'official support' then it can be argued the computer is covered by Apple. But most owners of those Macs don't even have Apple Care anymore.
Well it’s either covered or it isn’t. You can’t say that the old drivers need no updating but it’s not covered.
 
Went back to 8.1. The Windows drive is still not mounting on Yosemite, either from my primary startup disk (SSD on a PCI card) or HD, though the recovery partition can see it (?!!!). Option-key is the only way to boot it.....
 
Well it’s either covered or it isn’t. You can’t say that the old drivers need no updating but it’s not covered.
A lot of the components in machines are manufactured by Intel, Broadcom, etc. Driver development for those components ended a while ago and are included with Windows 10 and Windows Update anyway. The only things we need specifically from Apple are keyboard, mouse, trackpad, BootCamp control panel.
 
Try Bootchamp 1.7 beta. If it works, then you've got a bless problem.
Went back to 8.1. The Windows drive is still not mounting on Yosemite, either from my primary startup disk (SSD on a PCI card) or HD, though the recovery partition can see it (?!!!). Option-key is the only way to boot it.....

Try the Bootchamp 1.7 beta. If this works in OS X to successfully reboot into Windows, I know what the problem is (but I haven't found a solution for it yet).
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.