Hi Folks,
I have a Gigabyte Z390I AORUS PRO WIFI on the bench, this board had probably an electrical surge, as a few chips were burned, i.e. chipset, SIO, LAN chip and an OPAMP for generationg VCCSA and VCCIO. Now I replaced all the parts, including a chipset from another Gigabyte Z390 ATX board, and the board started to boot, but the boot process halts at debug code 18 (PCH LED active during the "18" code). The board after that restarts from scratch, and does this in an endless loop.
Would aprreciate if anybody could provide some raliable info what this debug code means, there are some lists on the net, but they tell either "reserved" or are for different vendors or much older bios versions, so no real help in the net. Maybe there is some Gigabyte BIOS developer under us ?
Definitely this code has something to do with the PCH, maybe another burned chip on the board can't be initialised, but it would be good to have some hint which device/process it could have to do with.
Another suspition I have, is that the Management Engine in the chipset coming from a different ATX Gigabyte board does not work correctly with the BIOS of that Z390I board ?
I have a Gigabyte Z390I AORUS PRO WIFI on the bench, this board had probably an electrical surge, as a few chips were burned, i.e. chipset, SIO, LAN chip and an OPAMP for generationg VCCSA and VCCIO. Now I replaced all the parts, including a chipset from another Gigabyte Z390 ATX board, and the board started to boot, but the boot process halts at debug code 18 (PCH LED active during the "18" code). The board after that restarts from scratch, and does this in an endless loop.
Would aprreciate if anybody could provide some raliable info what this debug code means, there are some lists on the net, but they tell either "reserved" or are for different vendors or much older bios versions, so no real help in the net. Maybe there is some Gigabyte BIOS developer under us ?
Definitely this code has something to do with the PCH, maybe another burned chip on the board can't be initialised, but it would be good to have some hint which device/process it could have to do with.
Another suspition I have, is that the Management Engine in the chipset coming from a different ATX Gigabyte board does not work correctly with the BIOS of that Z390I board ?
