yeah well, from experience,
any motherboard can go wrong...
regardless of the brand...
with electronics these days, anything can happen...
eskro
Posting Freak Joined: Nov 2010 Reputation: 156 |
2012-05-05 01:11
Post: #21
|
| find quote |
lockdown571
Member Posts: 85 Joined: Apr 2011 Reputation: 0 |
2012-11-13 17:46
Post: #22
Okay, I know this is an old topic, but I essentially had the exactly same problem, and I wanted to avoid this sort of situation for people in the future. I also had an Asrock mobo and was using OpenELEC. I was seeing this error about one in five boots, and now I've booted about 20 times and haven't seen it again. This is how I fixed it:
It began after I reinstalled OpenELEC, and during the install, it asked something like "existing GPT table detected, do you want to keep it? (yes recommended)". Not knowing any better I said yes. Apparently you can see this error if the partition table gets messed up (unfortunately, I have since forgotten where I read that). So I reinstalled again and this time told it not to keep the existing GPT, and the problem has not returned since. |
| find quote |
Dougie Fresh
Member+ Posts: 2,347 Joined: Feb 2009 Reputation: 49 Location: New Hampshire |
2012-11-13 20:41
Post: #23
H67M-ITX is a bad batch, period, IMHO. ::evil::
--- Blog: http://outsidethestb.blogspot.com Website: http://www.ecosmartpc.com Looking for these? Realan E-i5, Realan E-i7, IWill HT80, IWill HT100, IWill S197-H80 |
| find quote |
settings
Junior Member Posts: 32 Joined: May 2011 Reputation: 0 |
2012-11-18 04:32
Post: #24
I replaced the ram in mine today with a kingston 4gb and so far it seems to be good. I did alot of boot ups today as i was installing xbmc aswell as removing thermal paste and re-applying (from re-sitting the cpu in the past thinking it was the cause of that error).
So far so good, I will report back if i get the error but i think it was the RAM. |
| find quote |
newtothis
Member Posts: 65 Joined: Jan 2011 Reputation: 0 |
2012-11-19 23:31
Post: #25
Hi all,
This is what Asrock sent me today about this error! if that is any help! "I tested this and found that when a Windows MCE remote control is used to power down the system, the system will give this error at restart. If you however use the power down option in the menu, then everything works fine. It should be possible to edit the codes from the remote control, but this is caused by Open Elec, it is not a board issue that we can solve." |
| find quote |
mikebzh44
Posting Freak Posts: 1,069 Joined: Nov 2011 Reputation: 19 Location: Nantes - France |
2012-11-28 09:44
Post: #26
Get the same error since I have upgrade my HTPC.
Thanks to Google, I found this thread and your answer. I'm in the same case : power off HTPC with USB MCE remote. I have opened a ticket on OpenELEC GITHUB : https://github.com/OpenELEC/OpenELEC.tv/issues/1517 Hope that this issue can be fixed. |
| find quote |
lanman2000
Junior Member Posts: 4 Joined: Dec 2012 Reputation: 0 |
2013-04-04 05:14
Post: #27
Hey guys,
I finally found a fix for this that actually works. Turns out that UEFI bios doesn't play nice with syslinux 4.05. To fix it I updated to the latest version of xbmc(openelec 3.0) and then ran the following commands in ssh to update extlinux: cd /usr/bin sync mount -o remount,rw /flash ./extlinux -U /flash The output of the update line was: /flash is device /dev/sda1 Then I typed in "reboot" and haven't seen the machine check error since. I didn't figure this out on my own... found it here http://openelec.tv/forum/64-installation...k?start=6. |
| find quote |


Search
Help