Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Sign in to follow this  

A Strange Predicament

1 post in this topic

Recommended Posts

Somewhere, something has gone terribly wrong.

After installing OSX Mavericks everything seems to be running fine, bar a few hiccups. My Windows installation, however, has decided to stop playing nice and throw its toys out the pram. Now Windows will only boot if the SSD that it is installed on is the only disk connected to my motherboard, the second I try to attach anything it fails to boot.

Not only that, but the process of failing to boot is nothing like I've seen before. When another disk is connected it attempts to boot, it makes it to the Windows boot screen and then multiple mult-coloured lines appear at the top of the screen (similar to GPU artifacting). It will do this regardless of whether I start it in safe mode and the diagnostic tools think that nothing is wrong. Just to clear things up, this is not a problem that occurred immediately after installation, all drives were disconnected bar the SSD that I had designated to Mavericks. I was booting into Windows without a problem until fairly recently, and I have a feeling that it may be down to the NTFS driver I was using on OSX. To reiterate, I have OS X on a different SSD to the Windows installation, and everything was working perfectly a few days ago.


I have tried doing a system restore via Windows just to make sure that it wasn't a problem I had caused there, and everything appears to work perfectly when all other drives are disconnected, but simply not using my 4TB worth of data on Windows is simply not an option.


Does anyone have any suggestions as to what would cause this? I'm going to reinstall Windows today and see if the problem persists, but I really don't want this occurring again.


Thanks in advance.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.