1

00:00:00,533 --> 00:00:05,866

Hello everyone, in this lesson we will take a look at how to use the N card memory test software

2

00:00:06,966 --> 00:00:11,466

After entering the test hard disk, you will see an interface like this

3

00:00:12,200 --> 00:00:15,766

The second and third items are N card test procedures

4

00:00:18,133 --> 00:00:21,100

The second item is the test program of the 30 series,

5

00:00:21,300 --> 00:00:24,600

and the third item is the test program before the 30 series

6

00:00:25,500 --> 00:00:30,000

We need to enter different test procedures according to the graphics card to be tested

7

00:00:30,766 --> 00:00:35,366

After entering the test program, there will be different classifications

8

00:00:36,900 --> 00:00:41,566

We need to enter the corresponding test program according to the model of the graphics card

9

00:00:42,300 --> 00:00:47,900

For example, if I want to test a 3060 graphics card, I need to enter this test program

10

00:00:49,333 --> 00:00:52,733

Then I will enter cd 455.107_3060

11

00:00:56,166 --> 00:00:59,333

Press the Enter key to enter the 3060 test program

12

00:00:59,700 --> 00:01:03,766

It should be noted here that the test program of the N card is compatible,

13

00:01:04,266 --> 00:01:08,066

and generally the higher version is compatible with the lower version

14

00:01:09,733 --> 00:01:13,100

If there is no test program with exactly the same model,

15

00:01:13,300 --> 00:01:16,800

you can choose a program with a similar model to test

16

00:01:18,566 --> 00:01:22,000

After entering the test program, you need to enter the command

17

00:01:22,266 --> 00:01:25,300

Here are the commands needed for the N card test program,

18

00:01:25,766 --> 00:01:29,800

divided into two types: shortcut commands and complete commands

19

00:01:30,666 --> 00:01:33,166

If you use the test program we provide,

20

00:01:34,166 --> 00:01:38,533

entering a shortcut command is equivalent to entering a complete command

21

00:01:39,266 --> 00:01:45,000

Of course, all test programs can be run by entering complete commands

22

00:01:46,866 --> 00:01:50,000

Let's look at these commands in turn from top to bottom

23

00:01:51,400 --> 00:01:54,700

The first test command, the direct test command

24

00:01:54,866 --> 00:01:57,133

This command is the most used command,

25

00:01:57,400 --> 00:02:02,000

it refers to the normal test of the video memory of the graphics card

26

00:02:02,633 --> 00:02:05,033

Its command is ./cs, lower case

27

00:02:08,533 --> 00:02:12,066

After the test is completed, if we want to view the results,

28

00:02:12,166 --> 00:02:15,066

we must enter the command to view the results

29

00:02:15,500 --> 00:02:17,733

The shortcut command is ./jg

30

00:02:18,900 --> 00:02:22,466

./cs and ./jg are the most basic test commands

31

00:02:24,066 --> 00:02:28,300

But sometimes we encounter situations where the graphics card cannot display

32

00:02:29,700 --> 00:02:33,566

Graphics card can not display may also be caused by video memory

33

00:02:33,866 --> 00:02:38,400

Therefore, we need to measure the video memory even when the graphics card cannot display it.

34

00:02:38,866 --> 00:02:42,333

At this time, you need to use the integrated display test command

35

00:02:43,333 --> 00:02:47,400

The integrated display test command is actually a common test,

36

00:02:47,566 --> 00:02:49,866

but it is the command used under the integrated display

37

00:02:50,366 --> 00:02:54,566

The command to view the integrated display test results is also ./jg

38

00:02:55,733 --> 00:02:58,533

Let's take a look at the following three commands

39

00:02:58,866 --> 00:03:03,566

These three commands are all DIAG tests, which are more advanced tests

40

00:03:06,400 --> 00:03:11,533

The result of the test will be more accurate than the normal test command

41

00:03:12,333 --> 00:03:14,566

Moreover, this test command does not need to distinguish

42

00:03:14,566 --> 00:03:16,966

between the integrated display and the independent display.

43

00:03:17,266 --> 00:03:21,333

The commands under the integrated display are the same as those under the independent display.

44

00:03:22,266 --> 00:03:25,633

And the DIAG test can also overclock

45

00:03:25,900 --> 00:03:32,366

Some faults that are difficult to detect by ordinary tests may be detected by overclocking tests

46

00:03:32,733 --> 00:03:36,200

Next, let's take a look at the test process of ordinary tests

47

00:03:36,200 --> 00:03:39,866

First, we need to enter the corresponding test program

48

00:03:40,266 --> 00:03:45,733

If you use a separate display, you can directly enter ./cs

49

00:03:46,200 --> 00:03:49,766

When testing, there will be an interface similar to Huaping

50

00:03:50,066 --> 00:03:55,566

After the test is complete, it will output a green PASS, or a red FAIL

51

00:03:56,133 --> 00:03:59,466

PASS means passed, FAIL means not passed

52

00:03:59,766 --> 00:04:05,966

If FAIL appears, it means that there is a problem in the test, and we need to check the test results

53

00:04:06,133 --> 00:04:10,166

Enter ./jg to view the test results

54

00:04:11,100 --> 00:04:14,000

And its result is usually like this

55

00:04:14,466 --> 00:04:17,833

The front here is the channel of the video memory

56

00:04:18,300 --> 00:04:21,900

The A 0-31 on the left is A0

57

00:04:24,300 --> 00:04:28,600

The following A 32-63 is A1

58

00:04:28,866 --> 00:04:30,266

And so on

59

00:04:30,700 --> 00:04:34,700

The one on the right is A0 A1 B0 B1, clearly written

60

00:04:35,066 --> 00:04:39,333

And the latter area is the test result of the graphics card

61

00:04:39,566 --> 00:04:42,566

Under normal circumstances, all of them should be 0.

62

00:04:42,866 --> 00:04:45,500

If there are numbers, it means that there is an error.

63

00:04:46,000 --> 00:04:51,533

But sometimes, all channels of the test results will have a small error

64

00:04:51,600 --> 00:04:53,566

This is normal

65

00:04:53,766 --> 00:04:57,800

This error is caused by the incompatibility of the video memory test software

66

00:04:58,133 --> 00:05:01,666

But if all channels report errors, but one channel reports a very large error,

67

00:05:02,066 --> 00:05:04,500

it means that there is a problem with this channel.

68

00:05:08,500 --> 00:05:12,400

For example, the picture on the right shows that there is a problem with the memory of A0

69

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

We are going to repair the A0 memory

70

00:05:16,200 --> 00:05:18,200

Next let's try

71

00:05:18,300 --> 00:05:20,766

Let's take a look at the independent test

72

00:05:21,533 --> 00:05:24,433

The graphics card currently tested is 1060

73

00:05:24,866 --> 00:05:30,433

So we need to enter the third directory, the independent display test

74

00:05:33,100 --> 00:05:37,866

After entering the test program, it will automatically conduct a test

75

00:05:38,233 --> 00:05:41,533

But we don't care about the test results

76

00:05:41,933 --> 00:05:47,066

We directly enter ls to see what files are under the home directory

77

00:05:47,800 --> 00:05:50,966

As you can see, there are so many test programs under the home directory

78

00:05:51,200 --> 00:05:57,166

My graphics card is 1060, so I need to enter the test directory of 367.56.4_1060

79

00:05:57,866 --> 00:06:03,800

Enter cd 367, press the TAB key, auto-completion

80

00:06:04,000 --> 00:06:06,533

Press enter

81

00:06:06,900 --> 00:06:11,566

Enter the 1060 test program now

82

00:06:12,133 --> 00:06:15,100

At this time, I will do a normal test first.

83

00:06:15,266 --> 00:06:17,466

Type ./cs

84

00:06:19,800 --> 00:06:21,466

It's testing right now

85

00:06:21,600 --> 00:06:23,100

Let's fast forward

86

00:06:28,566 --> 00:06:31,066

After the test is completed, a result will be output

87

00:06:31,200 --> 00:06:34,866

PASS means pass, there is no problem with the video memory

88

00:06:35,200 --> 00:06:38,566

If we want to see the result, then type ./jg

89

00:06:40,700 --> 00:06:43,533

You can see that there are all zeros in the back

90

00:06:43,800 --> 00:06:46,133

Zero means normal

91

00:06:46,933 --> 00:06:53,300

If we want to quit viewing the results, we must press Ctrl and x

92

00:06:56,800 --> 00:06:58,766

This is the solo test

93

00:06:59,366 --> 00:07:02,800

Let's try the following DIAG test command

94

00:07:03,533 --> 00:07:07,733

The first command, mods118

95

00:07:08,566 --> 00:07:12,266

Type ./mods118 and press Enter

96

00:07:13,733 --> 00:07:16,333

it will automatically start testing

97

00:07:17,200 --> 00:07:21,966

It should be noted that the DIAG test is more selective for graphics cards

98

00:07:22,500 --> 00:07:28,400

Some graphics cards may be tested, but some cannot be tested, and an error will be reported directly.

99

00:07:29,533 --> 00:07:33,966

If an error is reported, we can only try a few more test programs to try

100

00:07:33,966 --> 00:07:37,600

The test time for the DIAG test will be slightly longer

101

00:07:39,200 --> 00:07:41,300

Let's fast forward

102

00:07:51,133 --> 00:07:56,366

It can be seen that PASS has been tested, indicating that there is no problem

103

00:07:57,066 --> 00:07:59,333

Let's try the overclocking test again

104

00:07:59,900 --> 00:08:01,200

Type ./cp

105

00:08:01,933 --> 00:08:06,066

The number followed by cp refers to the percentage of overclocking

106

00:08:06,400 --> 00:08:10,566

The general graphics card exceeds 130% and it is already the limit.

107

00:08:10,866 --> 00:08:13,500

Let's try to exceed 120% first.

108

00:08:15,366 --> 00:08:18,800

Overclocking tests are slow, let's fast forward

109

00:08:23,866 --> 00:08:26,700

No problem with overclocking test

110

00:08:27,666 --> 00:08:36,533

Of course, we can also test multiple times, because some faults cannot be detected once

111

00:08:38,666 --> 00:08:41,900

Next, let's try the integrated display test command

112

00:08:42,866 --> 00:08:47,333

We changed the boot mode to the integrated display boot in the BIOS

113

00:08:49,366 --> 00:08:52,700

After entering the test software, the operation method is still the same

114

00:08:52,866 --> 00:08:56,700

We first entered the 1060 test program

115

00:08:58,200 --> 00:09:06,900

Then we enter the ./jx set display environment command to grab the graphics card

116

00:09:11,466 --> 00:09:18,000

Next, regardless of whether it outputs PASS or FAIL, we will then enter ./jxcs, or ./jxcsk

117

00:09:20,733 --> 00:09:25,400

If a command reports an error, we try another command

118

00:09:25,866 --> 00:09:27,933

Let's do it in action

119

00:09:28,766 --> 00:09:30,600

Enter ./jxcs

120

00:09:33,333 --> 00:09:37,266

This status means that the test has started.

121

00:09:37,366 --> 00:09:42,700

It's just that there is no picture in the integrated display test, we just wait patiently

122

00:09:43,200 --> 00:09:47,766

OK, PASS has been output, which means there is no problem with the test

123

00:09:48,300 --> 00:09:53,033

At the same time, DIAG test can also be used under integrated display test, the command is the same

124

00:09:55,266 --> 00:09:58,333

Type ./mods118 directly

125

00:10:02,866 --> 00:10:09,666

Also, there is no picture during the DIAG test, we just wait patiently for the result

126

00:10:11,100 --> 00:10:16,466

You can see that PASS has been output, which means the test has passed and there is no problem

127

00:10:16,933 --> 00:10:21,966

If FAIL is output, we have to check the result to see which video memory reported an error

128

00:10:22,566 --> 00:10:26,266

The above is the use process of N card test software