[SOLVED]OS X 10.10.3 Suddenly not starting

So I have a separate 200gb HDD that I installed 10.10 via unibeast, and multibeast after setup. Installed sound kexts, usb wireless dongle, steam, and kextwizard.

It started up multiple times 6-8 without doing any changes, but suddenly it wont boot all the way.
Normally the apple symbol pops up gets a third of the way, then the screen turns black and the progress bar starts over, then to the sign in screen.
Now the apple symbol comes up, goes a third of the way like normal then it disconnects from my screen...like I pulled a cable.

I booted in verbose mode and there doesn't seem to be any kernel panic, it just goes to boot then the screen goes off again.

Any ideas on how to get it to boot? I tried safe mode...

OS X 10.10.3 Suddenly not starting

Did you get any software update notifications?

For what it's worth, the same thing happened to me and I checked the BIOS, (just for giggles) and found that the VT-d option had changed back to enabled, all on it's ow, so it might be worth double checking that the BIOS settings are OK, and maybe even reapplying them.

OS X 10.10.3 Suddenly not starting

JohnVella said:

Did you get any software update notifications?

For what it's worth, the same thing happened to me and I checked the BIOS, (just for giggles) and found that the VT-d option had changed back to enabled, all on it's ow, so it might be worth double checking that the BIOS settings are OK, and maybe even reapplying them.

Click to expand...

I did update the software and update to 10.10.3, but I booted a couple times after that and it was fine. Unless something auto updated.

I did check the bios, but maybe something else needs to be checked. I haveACHI settings and Vt-d disabled.

OS X 10.10.3 Suddenly not starting

Jiub said:

I did update the software and update to 10.10.3, but I booted a couple times after that and it was fine. Unless something auto updated.

I did check the bios, but maybe something else needs to be checked. I haveACHI settings and Vt-d disabled.

Click to expand...

It was a bios setting that was changed, thanks.

Jiub said:

It was a bios setting that was changed, thanks.

Click to expand...

Just seen this reply, as I haven't been online for a while, so just wanted to say glad it's now working and you're welcome!