BSODs with different errors

Question

Hi there.

I get BSODs very often. I couldn't find the reason. Sometimes once a day, sometimes twice, and so on. Let me know what you need to provide so you can help me.

Answer 1

Indicate whether the current RAM modules came with the computer or had been changed over time.

Run Memtest86 for two tests of four passes each overnight while sleeping.
Take pictures and post images or share links into this thread.

After posting the Memtest86 results please open administrative command prompt and type or copy and paste:
chkdsk /b /v

Run these chkdsk switches on all drives using the syntax chkdsk /b /v C: or chkdsk /b /v D: or chkdsk /b /v E: etc.

Plan to run the chkdsk switches on the Windows drive overnight while sleeping.

C:\WINDOWS\system32>chkdsk /b /v
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y

Reboot as needed.

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 2

When the drive chkdsk runs have completed on all drives please run this bat script:

(bat scripts by design will prompt antivirus software and require manual overrides)

https://www.tenforums.com/attachments/bsod-crashes-debugging/317041d1612147952-batch-files-use-bsod-debugging-chkdskfromevent.bat

Post a share link into this thread using one drive, drop box, or google drive.

For any new BSOD post a new V2 share link into the newest post.

Event[2999]:
Log Name: System
Source: Ntfs
Date: 2022-09-16T21:17:28.3280000Z
Event ID: 55
Task: N/A
Level: Error
Opcode: Info
Keyword: N/A
User: S-1-5-18
User Name: NT AUTHORITY\╤╚╤╥┼╠└
Computer: DESKTOP-EH5UL17
Description:
A corruption was discovered in the file system structure on volume C:.

╥юўэр  яЁшЁюфр яютЁхцфхэш  эхшчтхёЄэр. ═хюсїюфшью яЁютхЁшЄ№ ш шёяЁртшЄ№ ёЄЁєъЄєЁ√ Їрщыютющ ёшёЄхь√ т ртЄюэюьэюь Ёхцшьх.

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 3

@Docs

I have runned "chkdsk /b /v D:" & "chkdsk /b /v C:" commands(I only have 2 disks). On the D disk, no problems were found, I also provide a screenshot. On disk C, in order to check, I had to restart the computer, a disk scan was performed, but the final result was not displayed on the screen, so I can’t say if there were problems or not.

Yesterday I had a new BSOD, here I provide a new V2 log - https://drive.google.com/file/d/1nUAzw07gyEiHs5aEKXnOEjnsezl4obIY/view?usp=sharing

Answer 4

@Docs

Right now, I again gets BSOD. Here is new V2 log(including 10/10/22 Minidump) - https://drive.google.com/file/d/1lqP9N5m2k3QYadgOCz3GLgcFZwytZh0l/view?usp=sharing

Answer 5

Chkdsk C: results were good.

The BSOD bugchecks seen in the log files were:

1E
D1
A
7E
139
50
3B
F7
4A
C4

Please place the laptop into safe mode (shift + restart) for several days.

This can be safe mode, safe mode with networking, or safe mode with command prompt.

The longer the uninterrupted or continuous testing period the better the testing environment.

For BSOD post a new V2 share link into the newest post.

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.