Hi Everyone
I thought I would share my experience with the dreaded Gigabyte bootloop error as I found many others with the same issue, but unresolved and I'm hoping this may shed some light on the situation and potentially help others fix it - not to mention share my dealing with Gigabyte's RMA service.
I believe this all came about shortly after the cheap and nasty PSU in a prebuilt system went pop. I replaced it, but a couple of reboots later, I was faced with the infamous boot loop error on my H81MS2V motherboard: The system switches on, fans power up, no display, then everything shuts down and repeats.
Thankfully the motherboard was under warranty, so after a few email exchanges with Gigabyte, they raised and RMA and I sent the mobo away. I'm not certain how, but this time round they found some bent motherboard pins and deemed that to be the fault. I had heard that a lot of manufacturers will find this problem and blame it on the end user, thus voiding the warranty. Luckily, I took photographs of the socket (with no bent pins) and sent this to them. Either way, they repaired the pins, tested it and set it back free of charge.
Nope! Boot loop still there! No matter what I tried (changed RAM, PSU etc), it still would not work. A few more "tense" emails to Gigabyte and they agreed to collect the motherboard and retest, this time with my CPU and RAM. I was a bit dubious to this at first, but they used a fully insured collection service, so they had it in no time. They confirmed receipt of the hardware and let me know they were now testing.
A couple of days later I received an email saying they have recreated the fault and have isolated the problem. Apparently I had used a "too powerful PSU", which cooked a component on the motherboard - I didn't even think this was possible! The only cause of this I believe, is the original PSU which had fried, had cooked the component on its way out. They replaced said faulty component and fully tested with my hardware.
Received two days later and I'm now in the process of doing a fresh install of Windows 10 - great!
For those wondering what the damage/component was, Gigabyte kindly took a photograph of the culprit and listed the component number for me:
11XH5-225000-33R X'TAL Half 25MHz TXC - whatever that gobbly-gee-gook means!
Here is a photo of the replaced component:
Annoyingly I threw a mobo out recently with this problem, otherwise I would have attempted to repair it once I had sourced the component above.
Thanks to Gigabyte UK repair team - we got there in the end!
I thought I would share my experience with the dreaded Gigabyte bootloop error as I found many others with the same issue, but unresolved and I'm hoping this may shed some light on the situation and potentially help others fix it - not to mention share my dealing with Gigabyte's RMA service.
I believe this all came about shortly after the cheap and nasty PSU in a prebuilt system went pop. I replaced it, but a couple of reboots later, I was faced with the infamous boot loop error on my H81MS2V motherboard: The system switches on, fans power up, no display, then everything shuts down and repeats.
Thankfully the motherboard was under warranty, so after a few email exchanges with Gigabyte, they raised and RMA and I sent the mobo away. I'm not certain how, but this time round they found some bent motherboard pins and deemed that to be the fault. I had heard that a lot of manufacturers will find this problem and blame it on the end user, thus voiding the warranty. Luckily, I took photographs of the socket (with no bent pins) and sent this to them. Either way, they repaired the pins, tested it and set it back free of charge.
Nope! Boot loop still there! No matter what I tried (changed RAM, PSU etc), it still would not work. A few more "tense" emails to Gigabyte and they agreed to collect the motherboard and retest, this time with my CPU and RAM. I was a bit dubious to this at first, but they used a fully insured collection service, so they had it in no time. They confirmed receipt of the hardware and let me know they were now testing.
A couple of days later I received an email saying they have recreated the fault and have isolated the problem. Apparently I had used a "too powerful PSU", which cooked a component on the motherboard - I didn't even think this was possible! The only cause of this I believe, is the original PSU which had fried, had cooked the component on its way out. They replaced said faulty component and fully tested with my hardware.
Received two days later and I'm now in the process of doing a fresh install of Windows 10 - great!
For those wondering what the damage/component was, Gigabyte kindly took a photograph of the culprit and listed the component number for me:
11XH5-225000-33R X'TAL Half 25MHz TXC - whatever that gobbly-gee-gook means!
Here is a photo of the replaced component:
Annoyingly I threw a mobo out recently with this problem, otherwise I would have attempted to repair it once I had sourced the component above.
Thanks to Gigabyte UK repair team - we got there in the end!
Last edited:
