Yeah as other comments say, that USB-C internal header is a real pain for new PC builders, it looks like the connector can be inserted in any orientation but its keyed so slightly that just a quick glance you won't be able to see it. The user might have installed it the wrong way but not physically damage the internal connector on the motherboard unlike xQc's situation.
Yea this happened to me. I think i shorted our a speaker. And then i finally noticed that it was slightly keyed. Wish it was keyed not as slight. That would help out
This happened to me just a few weeks ago, plugged in the header backwards and got this exact error message. In fact, despite having built several PCs with USB-C front panel connections, it was the first time I realized the cable was keyed. Either the keying was more defined on those other cables or I just got lucky. :)
Yeah, I had a case with a USB-C front-panel port but only a regular two-type-A header on the motherboard, so I got an adapter from Amazon, and had--almost--the same issue. It would fit either way, and I didn't get overcurrent warnings, but the adapter board would get hot if it wasn't plugged in the right way. Later, I did a platform upgrade and made sure the new motherboard had a type-C header.
watching these fix or flop series makes me hopeful that i can troubleshoot any pc problems if i get into any. but i'm afraid if i try i will mess things up even more
@@swampfox1732 very true. I started from a pentium 2 to replace a ram now i am able (and brave enough) to disassemble a gpu to replace thermal paste and pads.
6 หลายเดือนก่อน +1
Learning what NOT to do will take you a long way towards the goal. Once you know how you can do damage and what to avoid, troubleshooting becomes a much less stressful endeavor.
Had this exact same problem when I first connected a USB-C connector, had it "in" backwards somehow. The key for the MB USB-C isn't good enough I guess to prevent it going in backwards. Had no issue once I flipped it around, didn't short anything thank goodness.
Same when I did my latest pc upgrade/changes. No issues after troubleshooting & found it was the USB-C cable from the case I pushed in the wrong way on the motherboard. At least it didn’t even turn on, but just lighted up. Always thought USB-C worked both ways, also within a case to a motherboard. But then it should not be possible to push it in the wrong way at all.
When I saw the error I immediately thought of the front panel I/O. Then you unplugged all the cables and I was about to think of something else. Then you said oh wait, I forgot this front panel connector 😂
I have this same issue going on right now. Exact same issue with the USB overvolt then to freezing at the Windows loading. I replaced the Asus Mobo and it did the same thing. I told my customer to just take my back up PC for now cuz I am lost. This video has been a huge help! Thanks Greg!!!
I would check for a Bios update, you shouldn't have to resort to changing it to CSM to install the OS. I would reset the bios by clearing it and putting it all back to factory settings. If that fails update the bios to the most current one and try that. Somethings not right there not too major but a pain that should be fixed lol.
CSM had to be turned on or Secure Boot had to be turned off probably because the system used to boot another OS and had another CPU/TPM (since it was bought used). You are correct in that resetting the BIOS would probably have worked. That or resetting the fTPM perhaps.
I have seen this exact issue several times...It happens more on the passthrough style cables for whatever reason...Its easy to damage the internal header by inserting it backwards or it could be debris in the outside connector...
I've had this same sort of issue twice- once with an NZXT internal usb hub, and once with a corsair lighting node. Both were new, right out of the box.
At the beginning of the video, I was pretty certain that the CPU had been overclocked and damaged, or there was a short on the motherboard. Glad to see it was a much simpler issue!
Thanks for this video, Bro! I've seen this sort of problem before with my own custom gaming/productivity build. However, the USB overcurrent fault I discovered was the result of a smashed pin in one of the USB front panel connectors on a Thermaltake case, which randomly occurred while inserting a USB thumb drive. Booting wasn't an issue since I was l already in Windows when it happened. I'd never experienced this sort of fault before, but as a result, I'll never buy another Thermaltake case again. Thanks again for all that you do. Love this series, Bro!
I had the same error when I first built my PC. The front panel USB-C cable has to be plugged into the header in the correct orientation, but the connector can fit in backwards. Obviously a faulty cable here, but in my case once I plugged it in correctly, the error was fixed.
Great Video Greg (as always) - as for getting a replacement part from NZXT - I'm sure they'll do it - I've had more than 1 replacement parts from them for FREE.
@@BREEZYM6015 wasnt trying to spoil it in the first Comment but.. The USB C frontpanel cable can be put in the wrong way, so the wrong pin layout will Overcurrent the 5V Rail.
My troubleshooting instinct would lead me to the PSU first, and then the mother board. Cabling is always a consideration, and is relatively simple to eliminate. Your senses did not fail you, and led you to the cause quickly. Well done, Greg!
USB over current does *not* sound like a PSU issue. It sounds like a short. If that short was in the PSU the mobo wouldn't know it and the PSU just wouldn't stay on (or it would burn itself out if OCP didn't work).
I had this same issue before on a desktop. the type c was plugged in flipped backwards. flipping it fixed the over current alert and allowed the system to boot normally.
their ports and cables are so shit and can potentially cause this. board and case manufacturers need to talk this one out. this cant be a standard for the following years.
I thought maybe a cable malfunction, but I was more leaning at incorrect/mismatched PSU cables being installed rather than from the case itself. So easy to see why issues are never solved outside of complete hardware replacement unless you are 100% thorough with checking cables.
Hello from Western Australia! I had this same error message come up on one of the kids’ computers a few years back and I worked out that one of the USB ports was completely mangled from multiple accidental kickings of the attached thumb drive. Removed the cable and all good from there
Eliminating all extra connections followed by visual port inspection, is where i'd start too. If that didn't work a rebuild outside the case. I've seen many a random thing occur because of wonky ports. Don't think i've ever had a dead internal USB wire tho. Could just be a bridged pin on the wire or something. 👍
The minute I saw that error I knew it was the case, my cousin broke his USB port and the bios gave a similar error. Had to rip out the port from the case to get it to boot safely.
Yeah, I have seen that error before. Definitely could be a short on the motherboard but pretty common just USB devices, or like here a short in a USB cable or front panel board. I would have been interested to see if Greg could have pulled the cable out and inspected it for damage, or even the front panel board.
I think it was just backwards. I also did this when I get my first usb-c case. It was little more tight but you can insert it backwards to motherboard and get this error.
@@LimbaZero to be honest I haven't worked on anything with a front panel USB C, so I don't know much about that specific connector, but seems like a pretty bad design if it can be plugged in backwards, especially after most other cables have been designed to make that impossible.
It was bent because the 24-pin was pressing on it. Moved it over as best I could, but it's very crammed in there and will likely continue to bend in the future.
I had the same overcurrent error on my B650 AORUS PRO AX. It was my USB DAC/AMP being plugged into the top row of USB ports... Worked fine every since I moved it to the lower ports...
Wow I was expecting the motherboard to be faulty. I've had two Asus AM4 boards that had the same usb overcurrent errors, and it even happens when absolutely nothing is plugged in. They might be fixable but I have no idea how to work on a board like that. This was a very lucky outcome because nice ITX boards like the z590 are really expensive. I'm sure the owner will be totally fine without a front type-c, since they already have two.
USB C is such a scam anyway. It is just a connector, and a mediocre one at that. Have to buy several new USB-C charging cables a year for my phone now. You can use any type of connector for high speed USB and there are plenty of USB C ports and devices that are not fast at all. The fact you could even plug the header in backwards is proof of just how little effort they put into the design. As for the MB you describe, the first thing I would check is how the headers are soldered. They may have bridged a couple of pins when installing them. Could also have a similar issue with the chipset. Beyond that, the chipset could actually be internally shorted or you could have damaged MB traces.
Not bad as a fix and good to hear the customer got a storage upgrade! Personally if it was my PC I'd be looking at rebuilding it in a different case, as I wouldn't want a non-functional port (even if it is Type C, which I don't currently have a use for).
I had an error message like that waaaay back on my Athlon x4 system. mine was a dead or dying usb controller. 4 out of 6 of my Usb port could not be used lol.
This is the SECOND time that I've seen a PC build either restarting over and over or never going into Windows because of a case cable. The first time, it was the power switch.
That's wild. I wonder if it's the cable or if there is a short on the PCB for the front panel connectors? You had the shot of the front panel PCB being loose, I wonder if something was broken on it?
at first was thinking a bad psu or a cable touching a metal piece shorting the mb. didn’t seem like there were many other issues to me. just glad it was a faulty cable in general… guess the cable could be specific to case type since the case can have different wire patterns vs the standardized port on the mb (much like psu cables) ???
Check the front-panel connectors downstream of the USB-C connector, this is often caused by damage to the USB port or cable resulting in a short, triggering shutdown. Most often when someone's sheared off a USB device while plugged in.
I've seen USB-C leads plugged in backwards, and not complete seated, before. It's easy to miss that, and never notice that it was backwards or done wrong. People sometimes don't realize that it's keyed.
i had this exact same issue last week on an nzxt case as well. Guess the cables are just trash. I knew right away because the machine worked perfect until that cable was plugged in. ripped it out and it worked like a charm.
I have seen this error before and it was due to a faulty USB3 3.0 type A connector. Also the Audio port didnt work on it either, so Phanteks exchanged the Audio and USB cables for me. It was a Phanteks P400A. I tried the bad connector on another motherboard, it would boot and go to Windows, but as soon as i plugged a USB stick into the port, it would immediately shut the system off. So there is indeed a short somewhere.
Greg, the one thing I don't think I saw was if you tried to use the Antec's (white) cable to connect the MB to the NZXT's front case USB. So, while you are probably right that the actual NZXT cable has a short, the question remains if the USB connector is somehow bad. Other than that, really nice detective work 😁 and stick-to-itiveness.
Thank God, someone else besides me has issues with secure boot, CSM and all of those other "security" settings. What a nightmare those things have been for me.
I had the same issue few years ago, only difference in my case was that the error was caused by a shorted usb-a port on my motherboard, I just pulled the shorted pins apart and that was it :)
Good start on the diagnosis of the problem. Simplify by removing any connection that isn't needed for the motherboard to pass POST. I was a bit confused that you didn't remove the type C connection directly, but it also looked as if the connector wasn't placed among the others. But yea, the USB overcurrent warning was pretty straight forward. Now as several has posted this connector should be keyed so it can only be inserted the correct way, but it's also been posted that it is possible to force it in the wrong way. This is one thing I don't like about some of these more modern connectors. So was it turned the right way? Another possibility is that there's some kind of problem with the cable connection to the port. I'm not sure about that part, but it might be worth removing the board with the connection and see if there is a visible problem there. Now I have to agree that sometimes BIOS settings can really screw things up for OS install. It's been probably six or seven years since I last installed an OS on a new machine, and back then the BIOS settings were a little simpler to understand. Basically I always started with a clear CMOS so it would start at zero, and then go through the bios making any modification I new was necessary such as setting the boot sequence to something decent, especially if there were a lot of drives in the system. But other than that my opinion is that a basic CMOS standard setup should work. It might not be optimal but it should boot and install the OS. If that's not working then the motherboard manufacturer really haven't made a good BIOS version.
I knew exactly what the problem was soon as i saw that error because I've faced it before. In my case it was a faulty USB2.0 from the front IO of the case.
With it being an overcurrent I would say it isn't as likely as the cable as it is the Front Panel Array. Either way it's why you disconnect and reconnect everything until it doesn't work.
my initial thought was the front panel usb cables because I have had this happen to to cases now, but they would not even post. the motherboards were older an so were the case only having usb 2.0.
This happened to me on my personal build. the front panel type C motherboard cable was plugged in the wrong way, I flipped it around and it worked and got past the boot cycle. You might wanna try and ask the owner to plug in the type C cable again, if it doesn't go through POST, flip it. That's what I did and it worked.
When I built in one of these cases, RAM size was something that I had to take into account. I wasn't using very large RAM originally, but I had collision problems too. I ended up going with some lower-profile RAM... definitely something that had no RGB.
I thought it was user error, so some cabling problem, which it turned to be true. Maybe he forced the usb c cable and caused the overcurrent. This case is not for beginners. I recently build a rig in NZXT H1 v1 which is a bit smaller than this and it was harder than expected. Nice video, Greg!
You probably already checked, but I had to get a replacement GPU adapter for my NZXT H1 case, because the original that shipped with it could short and even cause a fire. It's not entirely out of the realm of possibility that the GPU adapter is what fried the cable or USB port. Even if it didn't, owner will want to make sure that they have the appropriate replacement cable. Even better, they may want to just purchase a 3rd party replacement, as the one that shipped with the H1 was only rated for Gen 3 and not Gen 4.
I know this problem; I had it once with front USB 2.0 in a “Thermaltake Soprano” case. Simply remove the cable from the header on the mainboard and the PC is up and running again.
I had a NZXT case that I really liked, but it wasn't too long before the front panel connections started going bad. Also, the fan cables were terribly put together. No quality control it seems.
A similar thing happened to Linus in the video where he went to XQC's house to figure out why he was having issues with his new computer. It turns out that XQC was forcing the front panel type-c connector in the wrong way and that ended up shorting out the board and it gave the same error message of "USB overcurrent protection."
At 1st i thought this was a contact issue with this particular model. If i recall, Jayztwocents had a video on this or maybe it was an earlier version. Glad it wasn't that big of a deal and freebie for the owner on the storage. :P
I get that with the Ryzen 9 5900x once in a blue moon when the FL storms hit or or the power goes out yes its on a surge protector I find clearing the cmos always does the trick for me but then I have to re enter the same values got it memorized.
Love this series and your vidoes Greg, I also notice you like watches and wear a few different ones. Would you ever do a video about your watch collection? I know that isn't tech, but I would be interested!
At first I thought oh... THAT CASE... then you said it's the fixed ver. I had this issue because of a front panel usb 3.0 cable, that's all I had to unplug and the overcurrent was gone, I got rid of my case ever since though.
I started having this issue intermitently six months ago. In my case It was a shorted usb cable from the logitech headphones G432. I had them always conected and depending on the bent of the cable it worked just fine, the computer refused to boot or the motherboard turned off when it detected the short if it was already in windows.
Meanwhile I realized that the ASUS ROG 16:00 B550 Board I bought does not even have a USB C header...kinda wanted one, since my case has a front USB C, but alas, here we are. Thought that is basically the standard nowadays anyway, so I did not check :(
"Posted one minute ago" this PC sure didn't
ok, this was funny lol
Best comment
Hehe, nice one xD that gave me a good laugh
Ok this took me several glances before I got it. 🤣😅
oofff. BURN
Yeah as other comments say, that USB-C internal header is a real pain for new PC builders, it looks like the connector can be inserted in any orientation but its keyed so slightly that just a quick glance you won't be able to see it. The user might have installed it the wrong way but not physically damage the internal connector on the motherboard unlike xQc's situation.
Yea this happened to me. I think i shorted our a speaker. And then i finally noticed that it was slightly keyed. Wish it was keyed not as slight. That would help out
@@johnmaddox8017 I agree, it should be design that it only inserts in one orientation or like the actual USB-C connection itself be reversible.
This happened to me just a few weeks ago, plugged in the header backwards and got this exact error message. In fact, despite having built several PCs with USB-C front panel connections, it was the first time I realized the cable was keyed. Either the keying was more defined on those other cables or I just got lucky. :)
Yep! When building some PC, I came across this situation multiple times. It only go one way and we need to pay attention to it.
Yeah, I had a case with a USB-C front-panel port but only a regular two-type-A header on the motherboard, so I got an adapter from Amazon, and had--almost--the same issue. It would fit either way, and I didn't get overcurrent warnings, but the adapter board would get hot if it wasn't plugged in the right way. Later, I did a platform upgrade and made sure the new motherboard had a type-C header.
Great work Greg, and kudos to Tech Dad for building a PC for his kid!
This reminds me to XQC's PC problem. He had Linus on stream fixing his PC and He absolutely destroyed the Type C port lol
I was going to comment this but its already 9 hours ago behind me
But I definitely remember that video from LTT fixing xqc's pc
I wouldn't take any electronics into the same city as Linus. I'd rather not have them destroyed or stolen.
watching these fix or flop series makes me hopeful that i can troubleshoot any pc problems if i get into any. but i'm afraid if i try i will mess things up even more
Trial and error my friend. You never know until you try.
@@swampfox1732 very true. I started from a pentium 2 to replace a ram now i am able (and brave enough) to disassemble a gpu to replace thermal paste and pads.
Learning what NOT to do will take you a long way towards the goal. Once you know how you can do damage and what to avoid, troubleshooting becomes a much less stressful endeavor.
If I clean my PC it will not turn on for sure
@@madhup151 if you do not clean it, that is a sure thing eventually it will not turn on. Just use compressed air and be gentle with it.
Had this exact same problem when I first connected a USB-C connector, had it "in" backwards somehow. The key for the MB USB-C isn't good enough I guess to prevent it going in backwards. Had no issue once I flipped it around, didn't short anything thank goodness.
Indeed this connector can be pushed in the wrong way
Exactly that.
Nvmd, after watching further I'm pretty sure that Greg knows how to connect the type-c cable properly.
Same problem I had on my last build
Same when I did my latest pc upgrade/changes. No issues after troubleshooting & found it was the USB-C cable from the case I pushed in the wrong way on the motherboard. At least it didn’t even turn on, but just lighted up. Always thought USB-C worked both ways, also within a case to a motherboard. But then it should not be possible to push it in the wrong way at all.
Ironic considering type c can be plugged in either way 😅
When I saw the error I immediately thought of the front panel I/O. Then you unplugged all the cables and I was about to think of something else. Then you said oh wait, I forgot this front panel connector 😂
Same.
You have to simplify to identify . Works almost every time nice job Greg.
Type C motherboard connectors can be installed backwards/reversed and cause this error. Ask me how I know! ;)
We do not need to ask bro. We got you!
i just recently built a new pc and i did not know that, im glad i installed it right the first time i guess
Greg being like, "I'm sure it's not this." Aaaaand it was that.
Dramatic effect 😂
I have this same issue going on right now. Exact same issue with the USB overvolt then to freezing at the Windows loading. I replaced the Asus Mobo and it did the same thing. I told my customer to just take my back up PC for now cuz I am lost. This video has been a huge help! Thanks Greg!!!
I would check for a Bios update, you shouldn't have to resort to changing it to CSM to install the OS. I would reset the bios by clearing it and putting it all back to factory settings. If that fails update the bios to the most current one and try that. Somethings not right there not too major but a pain that should be fixed lol.
CSM had to be turned on or Secure Boot had to be turned off probably because the system used to boot another OS and had another CPU/TPM (since it was bought used). You are correct in that resetting the BIOS would probably have worked. That or resetting the fTPM perhaps.
Greg: "Stay with me."
Me: Don't worry Greg I'm not leaving! I'm here for all of it
It's impressive how you can keep the content so engaging and fresh after so many episodes, keep it going! Hope to see you at 1M subs soon!
I appreciate that! Will do!
Thanks! Love this series man.
I appreciate that!
I have seen this exact issue several times...It happens more on the passthrough style cables for whatever reason...Its easy to damage the internal header by inserting it backwards or it could be debris in the outside connector...
I've had this same sort of issue twice- once with an NZXT internal usb hub, and once with a corsair lighting node. Both were new, right out of the box.
At the beginning of the video, I was pretty certain that the CPU had been overclocked and damaged, or there was a short on the motherboard. Glad to see it was a much simpler issue!
Thanks for this video, Bro! I've seen this sort of problem before with my own custom gaming/productivity build. However, the USB overcurrent fault I discovered was the result of a smashed pin in one of the USB front panel connectors on a Thermaltake case, which randomly occurred while inserting a USB thumb drive. Booting wasn't an issue since I was l already in Windows when it happened. I'd never experienced this sort of fault before, but as a result, I'll never buy another Thermaltake case again.
Thanks again for all that you do. Love this series, Bro!
I had the same error when I first built my PC. The front panel USB-C cable has to be plugged into the header in the correct orientation, but the connector can fit in backwards. Obviously a faulty cable here, but in my case once I plugged it in correctly, the error was fixed.
I called that as soon as I saw the error. It’s a simple usb c connection error. Not plugged in right
Great Video Greg (as always) - as for getting a replacement part from NZXT - I'm sure they'll do it - I've had more than 1 replacement parts from them for FREE.
Nicely done. USB C cable, who would have thought, I've never seen that before. Its great also what dad is doing for his son.
Once i saw the Error Message i knew exactly what it was, this happened Linus trying to fix xQc's Pc. gave me straight Vietnam Flashbacks 😂
same for me lol
Same
What was it? Are you going to tell us? 😂
@@BREEZYM6015 wasnt trying to spoil it in the first Comment but..
The USB C frontpanel cable can be put in the wrong way, so the wrong pin layout will Overcurrent the 5V Rail.
My troubleshooting instinct would lead me to the PSU first, and then the mother board. Cabling is always a consideration, and is relatively simple to eliminate. Your senses did not fail you, and led you to the cause quickly. Well done, Greg!
USB over current does *not* sound like a PSU issue. It sounds like a short. If that short was in the PSU the mobo wouldn't know it and the PSU just wouldn't stay on (or it would burn itself out if OCP didn't work).
''usb over current'' would lead you to the psu? Are you dense? xD
I had this same issue before on a desktop. the type c was plugged in flipped backwards. flipping it fixed the over current alert and allowed the system to boot normally.
It never ceases to amaze me how often front panel connectors can cause these kinds of problems. Thanks for the info!
their ports and cables are so shit and can potentially cause this. board and case manufacturers need to talk this one out. this cant be a standard for the following years.
I thought maybe a cable malfunction, but I was more leaning at incorrect/mismatched PSU cables being installed rather than from the case itself. So easy to see why issues are never solved outside of complete hardware replacement unless you are 100% thorough with checking cables.
I love this series Greg! Keep it up!
Thanks! Will do!
Hello from Western Australia! I had this same error message come up on one of the kids’ computers a few years back and I worked out that one of the USB ports was completely mangled from multiple accidental kickings of the attached thumb drive. Removed the cable and all good from there
God I love fix or flop, this was a fun one! I guessed the issue pretty quickly this time around 😊
Eliminating all extra connections followed by visual port inspection, is where i'd start too. If that didn't work a rebuild outside the case.
I've seen many a random thing occur because of wonky ports. Don't think i've ever had a dead internal USB wire tho. Could just be a bridged pin on the wire or something. 👍
The minute I saw that error I knew it was the case, my cousin broke his USB port and the bios gave a similar error. Had to rip out the port from the case to get it to boot safely.
Yeah, I have seen that error before. Definitely could be a short on the motherboard but pretty common just USB devices, or like here a short in a USB cable or front panel board. I would have been interested to see if Greg could have pulled the cable out and inspected it for damage, or even the front panel board.
I think it was just backwards. I also did this when I get my first usb-c case. It was little more tight but you can insert it backwards to motherboard and get this error.
@@LimbaZero to be honest I haven't worked on anything with a front panel USB C, so I don't know much about that specific connector, but seems like a pretty bad design if it can be plugged in backwards, especially after most other cables have been designed to make that impossible.
nice find. always fun to watch. question, did you fix the memory hitting the fan and getting bent at all or did you leave that alone?
It was bent because the 24-pin was pressing on it. Moved it over as best I could, but it's very crammed in there and will likely continue to bend in the future.
First time watching one of these without skipping. Its great and I regret being impatient before. Keep it up and I sure think gear up 3 will be 🔥
I had the same overcurrent error on my B650 AORUS PRO AX. It was my USB DAC/AMP being plugged into the top row of USB ports... Worked fine every since I moved it to the lower ports...
Wow I was expecting the motherboard to be faulty. I've had two Asus AM4 boards that had the same usb overcurrent errors, and it even happens when absolutely nothing is plugged in. They might be fixable but I have no idea how to work on a board like that.
This was a very lucky outcome because nice ITX boards like the z590 are really expensive. I'm sure the owner will be totally fine without a front type-c, since they already have two.
USB C is such a scam anyway. It is just a connector, and a mediocre one at that. Have to buy several new USB-C charging cables a year for my phone now. You can use any type of connector for high speed USB and there are plenty of USB C ports and devices that are not fast at all. The fact you could even plug the header in backwards is proof of just how little effort they put into the design.
As for the MB you describe, the first thing I would check is how the headers are soldered. They may have bridged a couple of pins when installing them. Could also have a similar issue with the chipset. Beyond that, the chipset could actually be internally shorted or you could have damaged MB traces.
Once again great video, do not think I have ever had a front panel cable go bad.Good catch.
Without watching the whole video, I gotta admit I've never seen that "USB Device Overcurrent" message either.
Not bad as a fix and good to hear the customer got a storage upgrade! Personally if it was my PC I'd be looking at rebuilding it in a different case, as I wouldn't want a non-functional port (even if it is Type C, which I don't currently have a use for).
I had an error message like that waaaay back on my Athlon x4 system. mine was a dead or dying usb controller. 4 out of 6 of my Usb port could not be used lol.
Man almost season 6. Love these videos man always something new to learn.
This is the SECOND time that I've seen a PC build either restarting over and over or never going into Windows because of a case cable. The first time, it was the power switch.
OMG Greg I haven't seen you in my list for a minute! 😮 Great video man!
Nice Greg that was good to see you problem solve well done never seen that on any pc i have fixed to
That's wild. I wonder if it's the cable or if there is a short on the PCB for the front panel connectors? You had the shot of the front panel PCB being loose, I wonder if something was broken on it?
Great work Greg ! It was nice of you to upgrade the storage!!!!!
at first was thinking a bad psu or a cable touching a metal piece shorting the mb. didn’t seem like there were many other issues to me. just glad it was a faulty cable in general… guess the cable could be specific to case type since the case can have different wire patterns vs the standardized port on the mb (much like psu cables) ???
Check the front-panel connectors downstream of the USB-C connector, this is often caused by damage to the USB port or cable resulting in a short, triggering shutdown. Most often when someone's sheared off a USB device while plugged in.
Cool new glass Greg! Awesome video as always.
I appreciate it!
I've seen USB-C leads plugged in backwards, and not complete seated, before. It's easy to miss that, and never notice that it was backwards or done wrong. People sometimes don't realize that it's keyed.
Carey holzman had a faulty case cable a while back and I bought a second hand coolermaster cube with a similar issue!
i had this exact same issue last week on an nzxt case as well. Guess the cables are just trash. I knew right away because the machine worked perfect until that cable was plugged in. ripped it out and it worked like a charm.
I have seen this error before and it was due to a faulty USB3 3.0 type A connector. Also the Audio port didnt work on it either, so Phanteks exchanged the Audio and USB cables for me. It was a Phanteks P400A.
I tried the bad connector on another motherboard, it would boot and go to Windows, but as soon as i plugged a USB stick into the port, it would immediately shut the system off. So there is indeed a short somewhere.
Very nice to do this for people. Keep up the good and entertaining work
Greg, the one thing I don't think I saw was if you tried to use the Antec's (white) cable to connect the MB to the NZXT's front case USB. So, while you are probably right that the actual NZXT cable has a short, the question remains if the USB connector is somehow bad. Other than that, really nice detective work 😁 and stick-to-itiveness.
Thank God, someone else besides me has issues with secure boot, CSM and all of those other "security" settings. What a nightmare those things have been for me.
That was a weird one. I hope NZXT can help this person out. Great diag Greg!
I had the same issue few years ago, only difference in my case was that the error was caused by a shorted usb-a port on my motherboard, I just pulled the shorted pins apart and that was it :)
Good start on the diagnosis of the problem. Simplify by removing any connection that isn't needed for the motherboard to pass POST. I was a bit confused that you didn't remove the type C connection directly, but it also looked as if the connector wasn't placed among the others. But yea, the USB overcurrent warning was pretty straight forward.
Now as several has posted this connector should be keyed so it can only be inserted the correct way, but it's also been posted that it is possible to force it in the wrong way. This is one thing I don't like about some of these more modern connectors. So was it turned the right way?
Another possibility is that there's some kind of problem with the cable connection to the port. I'm not sure about that part, but it might be worth removing the board with the connection and see if there is a visible problem there.
Now I have to agree that sometimes BIOS settings can really screw things up for OS install. It's been probably six or seven years since I last installed an OS on a new machine, and back then the BIOS settings were a little simpler to understand. Basically I always started with a clear CMOS so it would start at zero, and then go through the bios making any modification I new was necessary such as setting the boot sequence to something decent, especially if there were a lot of drives in the system. But other than that my opinion is that a basic CMOS standard setup should work. It might not be optimal but it should boot and install the OS. If that's not working then the motherboard manufacturer really haven't made a good BIOS version.
Bios did report USB error so I would have pulled it as a basic setup ?
Glad u got there
I absolutely LOVE your videos! Small defect big problem ^^
Nice vid! I always set bios to default settings when repairing. That usually works for me. I'm sure you do that too though. Love the content!
Just did a fresh install of windows 10. Couldn't be happier.
I knew exactly what the problem was soon as i saw that error because I've faced it before. In my case it was a faulty USB2.0 from the front IO of the case.
i like this.that was cool to watch the repair process move along.subscribed
*Ralph Wiggum voice* I'm helping by watching!
Motherboard was my first guess... bad cable #2. Good job!
With it being an overcurrent I would say it isn't as likely as the cable as it is the Front Panel Array. Either way it's why you disconnect and reconnect everything until it doesn't work.
my initial thought was the front panel usb cables because I have had this happen to to cases now, but they would not even post. the motherboards were older an so were the case only having usb 2.0.
Nice always a fan of this series❤❤❤
This happened to me on my personal build. the front panel type C motherboard cable was plugged in the wrong way, I flipped it around and it worked and got past the boot cycle.
You might wanna try and ask the owner to plug in the type C cable again, if it doesn't go through POST, flip it. That's what I did and it worked.
Awesome fix Greg ✌
When I built in one of these cases, RAM size was something that I had to take into account. I wasn't using very large RAM originally, but I had collision problems too. I ended up going with some lower-profile RAM... definitely something that had no RGB.
Learning something new from these videos.
I thought it was a bios issue.
Looking forward to the next video :D
I learn so much from this series thank you for doing these.
I thought it was user error, so some cabling problem, which it turned to be true. Maybe he forced the usb c cable and caused the overcurrent. This case is not for beginners. I recently build a rig in NZXT H1 v1 which is a bit smaller than this and it was harder than expected. Nice video, Greg!
Keep up the good work Greg 👏 🙌 👍
I appreciate it!
Had this exact problem a few years ago. I had somehow managed to plug the usb 3.0 cable backwards.
I had wires touching under the daughter board a little black tape fixed it right up.
My first thought was a short on the back of the board. Helpful video.
You probably already checked, but I had to get a replacement GPU adapter for my NZXT H1 case, because the original that shipped with it could short and even cause a fire. It's not entirely out of the realm of possibility that the GPU adapter is what fried the cable or USB port. Even if it didn't, owner will want to make sure that they have the appropriate replacement cable. Even better, they may want to just purchase a 3rd party replacement, as the one that shipped with the H1 was only rated for Gen 3 and not Gen 4.
I know this problem; I had it once with front USB 2.0 in a “Thermaltake Soprano” case. Simply remove the cable from the header on the mainboard and the PC is up and running again.
check the io plate shorting out the usb port............That was fun to find.
That white antec case is just majestic
I had a NZXT case that I really liked, but it wasn't too long before the front panel connections started going bad. Also, the fan cables were terribly put together. No quality control it seems.
11:35-12:08 that's an awful long time to be on the windows splash screen, especially with a gen 4 nvme. Was it frozen?
A similar thing happened to Linus in the video where he went to XQC's house to figure out why he was having issues with his new computer. It turns out that XQC was forcing the front panel type-c connector in the wrong way and that ended up shorting out the board and it gave the same error message of "USB overcurrent protection."
I had this exact same issue recently on a clients computer. Front panel USBC being weird I guess
usb-c internal headder installed back to front, plain and simple, turn it around if not damaged but if the connection is damaged leave it disconected.
At 1st i thought this was a contact issue with this particular model. If i recall, Jayztwocents had a video on this or maybe it was an earlier version. Glad it wasn't that big of a deal and freebie for the owner on the storage. :P
I get that with the Ryzen 9 5900x once in a blue moon when the FL storms hit or or the power goes out yes its on a surge protector I find clearing the cmos always does the trick for me but then I have to re enter the same values got it memorized.
These videos are awesome! I dont even have problems with my PC but if i ever do, im referring to these vids lol
Love this series and your vidoes Greg, I also notice you like watches and wear a few different ones. Would you ever do a video about your watch collection? I know that isn't tech, but I would be interested!
At first I thought oh... THAT CASE... then you said it's the fixed ver. I had this issue because of a front panel usb 3.0 cable, that's all I had to unplug and the overcurrent was gone, I got rid of my case ever since though.
Good job on this one, can't wait for the next episode.
I started having this issue intermitently six months ago. In my case It was a shorted usb cable from the logitech headphones G432. I had them always conected and depending on the bent of the cable it worked just fine, the computer refused to boot or the motherboard turned off when it detected the short if it was already in windows.
Great video as always!
Meanwhile I realized that the ASUS ROG 16:00 B550 Board I bought does not even have a USB C header...kinda wanted one, since my case has a front USB C, but alas, here we are.
Thought that is basically the standard nowadays anyway, so I did not check :(
i love these. great lessons in trouble shooting.
Nice Fix Greg - Mine had NO Type C connected as on test bench