- Joined
- Dec 7, 2011
- Messages
- 545
- Motherboard
- Razer Blade 15 - Clover
- CPU
- i7-8750H
- Graphics
- UHD 630/GTX 1060 - 1920x1080
- Mac
- Mobile Phone
Ever since I installed the 10.6.8 update I have to boot with the -f flag at my bootloader otherwise I get a white screen after the Apple Logo and OS X never starts up.
Has anyone had this issue or possibly have a fix for it?
Could it possibly be graphics related? I'm running Intel HD3000 integrated graphics off my Gigabyte Z68Mobo for now until my actual graphics card comes in. OS X doesn't fully recognize the Intel HD3000 and I can't run it at full resolution.
Here's my system specs.
Gigabyte Z68MX-UD2H-B3 Mobo - F9 Bios Version (installed the DSDT for this mobo that was provided by the TonyMac Site)
Intel i5 2500k Sandy Bridge Processor, overclocked to 4.5Ghz.
8GB Ram
700Watt ModXtreme Pro Power Supply
80GB Western Digital HD (Main Drive OS X is installed on)
500GB Segate HD(2 partitions one for Windows 7 the other for a storage that both windows and OS X can access with read/write privileges)
Snow Leopard OS X 10.6.8
The issue was present before I added in the Segate HD and installed Windows 7 on it.
I'm using the bootloader that's off the latest version of MultiBeast v.3.10.1
Thanks in advanced.
-Mike
Has anyone had this issue or possibly have a fix for it?
Could it possibly be graphics related? I'm running Intel HD3000 integrated graphics off my Gigabyte Z68Mobo for now until my actual graphics card comes in. OS X doesn't fully recognize the Intel HD3000 and I can't run it at full resolution.
Here's my system specs.
Gigabyte Z68MX-UD2H-B3 Mobo - F9 Bios Version (installed the DSDT for this mobo that was provided by the TonyMac Site)
Intel i5 2500k Sandy Bridge Processor, overclocked to 4.5Ghz.
8GB Ram
700Watt ModXtreme Pro Power Supply
80GB Western Digital HD (Main Drive OS X is installed on)
500GB Segate HD(2 partitions one for Windows 7 the other for a storage that both windows and OS X can access with read/write privileges)
Snow Leopard OS X 10.6.8
The issue was present before I added in the Segate HD and installed Windows 7 on it.
I'm using the bootloader that's off the latest version of MultiBeast v.3.10.1
Thanks in advanced.
-Mike