1

00:00:00,400 --> 00:00:05,466

Hello everyone, in this lesson, let's take a look at the troubleshooting process for non-running code failures

2

00:00:06,100 --> 00:00:11,400

The non-running code failure is generally caused by the bridge or CPU working conditions not being satisfied.

3

00:00:12,333 --> 00:00:17,700

Working conditions include power supply, clock, reset, program, etc., involving a wide range

4

00:00:19,733 --> 00:00:24,666

However, under normal circumstances, we will use the platform reset signal as an entry point

5

00:00:25,066 --> 00:00:30,833

If the platform reset signal is normal, it means that the working conditions of the bridge are basically satisfied,

6

00:00:31,133 --> 00:00:34,366

and the fault is caused by the CPU.

7

00:00:34,933 --> 00:00:39,266

At this time, we are going to check the working conditions of the CPU

8

00:00:39,966 --> 00:00:46,733

The working conditions of the CPU include all power supplies to the CPU, CPU reset and PG signals

9

00:00:47,866 --> 00:00:53,566

It should be noted here that sometimes the core power supply of the CPU is powered,

10

00:00:53,833 --> 00:00:56,766

but it is not regulated by the SVID bus,

11

00:00:57,500 --> 00:00:59,500

or the regulated voltage is incorrect.

12

00:00:59,866 --> 00:01:06,500

If the voltage supplied by the CPU core is inconsistent with the voltage required by the CPU, the CPU will not work

13

00:01:08,966 --> 00:01:13,433

If there is no platform reset signal, it means that the non-running code fault is generally caused by the bridge,

14

00:01:13,866 --> 00:01:16,700

and it also means that the hard start has not been completed.

15

00:01:18,766 --> 00:01:25,400

At this time, we can follow the hard boot process to check the power supply, PG, reset of the whole board in turn.

16

00:01:26,966 --> 00:01:32,033

Of course, the failure to run the code may also be caused by the BIOS.

17

00:01:32,166 --> 00:01:35,600

We can flash a BIOS and try to see if the fault can be solved

18

00:01:36,666 --> 00:01:41,766

If I checked the mainboard's power supply, clock, reset, program, there is no problem,

19

00:01:41,966 --> 00:01:44,300

but it still doesn't run the code

20

00:01:44,500 --> 00:01:49,700

It means that this failure may be caused by damage to the CPU seat or the bridge.

21

00:01:49,966 --> 00:01:54,966

We can try to add soldering, or replace the CPU seat and bridge

22

00:01:55,533 --> 00:02:00,066

The above is the troubleshooting process for non-running code failures

23

00:02:00,466 --> 00:02:06,600

To put it bluntly, it is to detect the power supply, clock, reset, PG, and program of the mainboard during power-on.