- Joined
- Jun 30, 2016
- Messages
- 163
- Motherboard
- GA-H110M-A
- CPU
- i5-6500
- Graphics
- RX 560
- Mac
- Mobile Phone
Thank you P1LGRIM for you help!
Can you please share your knowledge on how to decipher stack trace error?
You are right that the Serial port under SuperIO of the Advance tab in my BIOS settings is enabled!
I was able to boot into the GUI of OS X installation after I have disabled the Serial port.
But I haven't installed OS X yet. I have to get another SSD for the installation so as not to mess up the current system that is installed.
Can't thank you enough! I have been struggling with this issue for many months now.
Cool, glad you have it sorted out, thanks P1LGRIM! I have updated the original post to include making sure the I/O controller (i.e. Super I/O) is disabled in the BIOS. I think this is in the installation guide, but it is best to include here as well since the controller may or may not be enabled by default on some boards.
As far as how to decipher the stack trace, this isn't something that is easy to teach as they will be different and specific to the fault and module where it occurred. It is essentially a report of what was going on at the point in time at which the issue occurred. These types of errors are meant for programmers and are not meant to be friendly for end-users. They are given so that end-users can report the error back to programmers and they can link the info back up with the code. As an end-user, you can locate the reported error in the stack trace and do some Google searches to find out if others have reported the same error for the module that reported it, but this can be tedious. I have programmed and worked on computers, linux kernels etc. for over 30 years, so what I may see and understand when I read a stack trace will be different than the average user. Even then, if I am not familiar with the module and error reported to give me some idea of what is happening, I have search and dig deeper to try to understand what is happening. So, the best thing you can do is provide the complete error text (or take a picture) and post it so others can try to help out. Good luck with the Hack!