Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Ram Page on January 04, 2017, 03:45:48 am
-
"C0 error code" seems a common topic but I haven't quite found out is C0 actually a sign of a problem or not? I have seen this code since I built my PC, a few times even A0, but I haven't experienced any serious problems. The only problem is the sound... every time I start my computer I have to open Sound Blaster cp and click twice the "Speaker - Headset" slider to get the sounds on. (I have asked help for this issue but so far no replies.) C0 doesn't indicate the sound issue I got, or...? Anyways should I react somehow because of that "C0" or not?
-
C0 could be CPU or memory. What BIOS are you running?
If CPU, bumping Vcore up slightly can help. If related to memory, bumping VTT up can do the same. These are just guess' as the CPU itself could also be the problem. Reseating it and its cooler might also work. I'd inspect for bent pins to rule that out.
The sound issue might be corrupt sound driver or port sense not working with the connected device or speakers.
-
I went thru the next procedures
- Socket pins: OK
- RAM modules: normal order + random order + with only 1 module
- Processor and RAM test programs (no errors)
- Stress test + performance tests (no errors and good scores)
- BIOS cleared (F20d) Tried with and without XMP
- Deleted/reinstalled the sound drivers and the gfx drivers (with DDU) and cleaned the registry (manually)
Nothing changed (except I got way better graphic scores in Fire Strike after using DDU + clean install.) C0 stays but still my PC works perfectly (excluding the sound issue). So looks like, at least in my case, that the code means practically nothing?
-
C0 code is a bug of the F20 bios. This appens also on my Z170X Gaming 7.
-
Can you explain this?
I had some issues with my PC so I ended up to clean the SSD and reinstall Windows. After that I noticed the code was A0. First I thought the reason was the SSD but it wasn't. When I reconnected my storage HDD the code changed back to C0. Then I disconnected it, the code was again A0. And then back, and the code was again C0. Then I decided to format the HDD. After reboot the code has been all the time A0. Nothing else is changed. So could the reason be the file system type (+possible with buggy bios)? Ie. NAT32 = C0 and NTFS = A0 ??
-
Beta bios means you are a beta tester, you are bound to find issues.
Hell i find issues with my F7 "stable" bios, but theyre manageable.
-
Can you explain this?
I had some issues with my PC so I ended up to clean the SSD and reinstall Windows. After that I noticed the code was A0. First I thought the reason was the SSD but it wasn't. When I reconnected my storage HDD the code changed back to C0. Then I disconnected it, the code was again A0. And then back, and the code was again C0. Then I decided to format the HDD. After reboot the code has been all the time A0. Nothing else is changed. So could the reason be the file system type (+possible with buggy bios)? Ie. NAT32 = C0 and NTFS = A0 ??
I can't exclude other causes but I know that C0 code appear to me after F20 upgrade. Anyway I do not have any issue, only the C0 code on the display.
You can also check if there are blended pins on the CPU.