[NickM]

Miralius, СМАРТ ж/д смотрели, в норме?
Ф/с на томах ж/д на ошибки проверяли?

[Miralius]

Да, со SMARTом, кажется, все хорошо. Проблемы возникают на системном диске, т.е. на SSD.

Проверял дважды позавчера chkdsk системный диск. Находил одну ошибку.

chkdsk

Checking file system on C:
The type of the file system is NTFS.
Volume label is System.

The volume is dirty.

Stage 1: Examining basic file system structure ...
File 0x7410 has bad reparse point attribute.
ReparseDataLength, 0x1000, inconsistence with the attribute length 0x171.
Deleting corrupt attribute record (0xC0, "")
from file record segment 0x7410.
Cleaning up instance tags for file 0x36a21.
Cleaning up instance tags for file 0x36ab2.
Cleaning up instance tags for file 0x36c5a.
Cleaning up instance tags for file 0x36c78.
Cleaning up instance tags for file 0x36c88.
1550336 file records processed.
File verification completed.
Phase duration (File record verification): 17.04 seconds.
8496 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 1.40 milliseconds.

Stage 2: Examining file name linkage ...
The reparse flag in standard information attribute in file 0x7410
should not be set.
Correcting reparse point file record segment 7410.
The reparse point index entry in file 0x1a points to file 0x7410
but the file has no reparse point in it.
Deleting an index entry from index $R of file 1A.
26116 reparse records processed.
The file reference 0x66000000016c25 of index entry {2ACD1~1 of index $I30
with parent 0x17e36 is not the same as 0x77000000016c25.
Deleting index entry {2ACD1~1 in index $I30 of file 17E36.
The file reference 0x3b00000001ba30 of index entry {46A83~1 of index $I30
with parent 0x17e36 is not the same as 0x7000000001ba30.
Deleting index entry {46A83~1 in index $I30 of file 17E36.
1819588 index entries processed.
Index verification completed.
Phase duration (Index verification): 44.53 seconds.
CHKDSK is scanning unindexed files for reconnect to their original directory.
1 unindexed files scanned.
0 unindexed files recovered to original directory.
Phase duration (Orphan reconnection): 0.00 milliseconds.
CHKDSK is recovering remaining unindexed files.
1 unindexed files recovered to lost and found.
Lost and found is located at \found.000

Phase duration (Orphan recovery to lost and found): 0.00 milliseconds.
26116 reparse records processed.
Phase duration (Reparse point and Object ID verification): 60.60 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 4525 unused index entries from index $SII of file 0x9.
Cleaning up 4525 unused index entries from index $SDH of file 0x9.
Cleaning up 4525 unused security descriptors.
Security descriptor verification completed.
Phase duration (Security descriptor verification): 63.81 milliseconds.
134627 data files processed.
Phase duration (Data attribute verification): 1.66 milliseconds.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.

Windows has made corrections to the file system.
No further action is required.

249283580 KB total disk space.
152643100 KB in 821662 files.
415872 KB in 134629 indexes.
0 KB in bad sectors.
1629796 KB in use by the system.
65536 KB occupied by the log file.
94594812 KB available on disk.

4096 bytes in each allocation unit.
62320895 total allocation units on disk.
23648703 allocation units available on disk.
Total duration: 1.11 minutes (67158 ms).

chkdsk c: /f /r

Checking file system on C:
The type of the file system is NTFS.
Volume label is System.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
1550336 file records processed.
File verification completed.
Phase duration (File record verification): 14.48 seconds.
8493 large file records processed.
Phase duration (Orphan file record recovery): 0.00 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 1.39 milliseconds.

Stage 2: Examining file name linkage ...
26116 reparse records processed.
1819586 index entries processed.
Index verification completed.
Phase duration (Index verification): 57.00 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 2.52 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 6.57 milliseconds.
26116 reparse records processed.
Phase duration (Reparse point and Object ID verification): 44.91 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 22 unused index entries from index $SII of file 0x9.
Cleaning up 22 unused index entries from index $SDH of file 0x9.
Cleaning up 22 unused security descriptors.
Security descriptor verification completed.
Phase duration (Security descriptor verification): 44.62 milliseconds.
134626 data files processed.
Phase duration (Data attribute verification): 1.55 milliseconds.
CHKDSK is verifying Usn Journal...
2670768 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 29.36 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
1550320 files processed.
File data verification completed.
Phase duration (User file recovery): 26.35 minutes.

Stage 5: Looking for bad, free clusters ...
23584160 free clusters processed.
Free space verification is complete.
Phase duration (Free space recovery): 0.00 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

249283580 KB total disk space.
152898156 KB in 818986 files.
415904 KB in 134627 indexes.
0 KB in bad sectors.
1632880 KB in use by the system.
65536 KB occupied by the log file.
94336640 KB available on disk.

4096 bytes in each allocation unit.
62320895 total allocation units on disk.
23584160 allocation units available on disk.
Total duration: 27.59 minutes (1655753 ms).

UPD:
Сейчас снова запустил проверку диска через ПКМ по диску → свойства → инструменты → Проверить диск.
Сразу после запуска проверки ноутбук снова завис на 2 минуты. Во время зависания прогресс проверки стоял на месте. После отвисания проверка пошла, была большая активность от dllhost.
В журнале событий записалось:

Windows Error reporting 1001

Fault bucket 1409744833567330181, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: dllhost.exe
P2: 10.0.19041.1
P3: 10.0.19041.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

Attached files:
\\?\C:\Users\F-Mir\AppData\Local\Temp\RDRE1B3.tmp\empty.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE1B4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE1D4.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE1CF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE20F.tmp.txt

These files may be available here:


Analysis symbol:
Rechecking for solution: 0
Report Id: dbd49ab4-45f0-46ea-8323-7dea9cac37cc
Report Status: 268435456
Hashed bucket: 0d81c094a7fe188bc3906b74fcb90f85
Cab Guid: 0

[freese]

а что вообще с температурой по датчикам у вас? На мостах?
А то 62 у хдд, не очень хорошо

[Miralius]

Вот температуры через AIDA64. 62 градуса было у NVMe SSD, у HDD 38 градусов.

[NickM]

Находил одну ошибку »

И это есть нехорошо...

СМАРТ второго также покажите пжлст.

[Miralius]

SMART второго диска (HDD):

[NickM]

Miralius, здесь все чинно-красиво, спс.

[Miralius]

NickM, а мне что делать? Есть какие-либо версии программных багов? Сам я думаю на SSD, и пока ноутбук на гарантии, хотелось бы его в случае брака заменить по гарантии.

[NickM]

Miralius, пробуйте пару-тройку дней проверять ф/с на загрузочном томе, если будет биться, тогда грешите на твердотельник, ведь на ровном месте ошибки не появляются (к слову, твердотельник так Себе, при 12WTB уже почти 20% износа ).
Если не затруднит, приложите системные журналы, может там, что можно будет увидеть.