Windows 10: How do I fix BSOD?

At first my pc start was getting a lot of BSOD because Riot's anti-cheat, Vanguard, so I deleted the game and the anti-cheat and I stop getting BSOD for a while. Now I start getting BSOD a lot suddenly for some reason, it only happens when I'm playing games or right after I boot up from BSOD, i get it again. For fvevol.sys I don't use any encryption on any of my drive. Currently using the lasted windows version.


Here are my dump files analysis using WhoCrashed:


[COLOR=000000]On Thu 2020-06-11 3:45:16 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\061120-10515-01.dmp
This was probably caused by the following module: [COLOR=000000]fvevol.sys[/COLOR] 0xFFFFF8076605309D
Bugcheck code: 0x1E 0xFFFFFFFFC0000005, 0xFFFFF8076605309D, 0x0, 0xFFFFFFFFFFFFFFFF
Error: [COLOR=000000]KMODE_EXCEPTION_NOT_HANDLED[/COLOR]
file path: C:\WINDOWS\system32\drivers\fvevol.sys
product: [COLOR=000000]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=000000]Microsoft Corporation[/COLOR]
description: BitLocker Drive Encryption Driver
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating thermal issue or because of a buggy driver.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

[/COLOR]

[COLOR=000000]On Fri 2020-06-05 4:00:31 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060520-9812-01.dmp
This was probably caused by the following module: [COLOR=000000]ntfs.sys[/COLOR] Ntfs+0x145310
Bugcheck code: 0x1000007E 0xFFFFFFFFC0000005, 0xFFFFF80429312C49, 0xFFFFCB0E0255B2A8, 0xFFFFCB0E0255AAF0
Error: [COLOR=000000]SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M[/COLOR]
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: [COLOR=000000]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=000000]Microsoft Corporation[/COLOR]
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

[/COLOR]

[COLOR=000000]On Thu 2020-06-04 4:00:51 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060420-9359-01.dmp
This was probably caused by the following module: [COLOR=000000]netio.sys[/COLOR] 0xFFFFF8058098E3C0
Bugcheck code: 0xD1 0x20, 0x2, 0x0, 0xFFFFF8058098E3C0
Error: [COLOR=000000]DRIVER_IRQL_NOT_LESS_OR_EQUAL[/COLOR]
file path: C:\WINDOWS\system32\drivers\netio.sys
product: [COLOR=000000]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=000000]Microsoft Corporation[/COLOR]
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

[/COLOR]

[COLOR=000000]On Thu 2020-06-04 3:46:47 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\060420-9796-01.dmp
This was probably caused by the following module: [COLOR=000000]fvevol.sys[/COLOR] 0xFFFFF80425A53B25
Bugcheck code: 0x50 0xFFFFFFFFFFFFFF89, 0x2, 0xFFFFF80425A53B25, 0x2
Error: [COLOR=000000]PAGE_FAULT_IN_NONPAGED_AREA[/COLOR]
file path: C:\WINDOWS\system32\drivers\fvevol.sys
product: [COLOR=000000]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=000000]Microsoft Corporation[/COLOR]
description: BitLocker Drive Encryption Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

[/COLOR]

[COLOR=000000]On Tue 2020-05-26 8:54:08 PM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\052620-8859-01.dmp
This was probably caused by the following module: [COLOR=000000]ntoskrnl.exe[/COLOR] nt+0x1C2390
Bugcheck code: 0xA 0x1, 0x2, 0x1, 0xFFFFF8012F3C10D6
Error: [COLOR=000000]IRQL_NOT_LESS_OR_EQUAL[/COLOR]
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: [COLOR=000000]Microsoft® Windows® Operating System[/COLOR]
company: [COLOR=000000]Microsoft Corporation[/COLOR]
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.[/COLOR]

:)

 

BSOD issue after fixing another BSOD error

Hi Williams,

There are several reasons why BSOD occur, which has different resolution. To check for any corruption or the integrity of your computer's Windows, we suggest that you perform a
Check Disk by following these steps:

• Type cmd in the search bar.
• Right-click on the Command Prompt, then Run as administrator.
  
• Type chkdsk x: /r, the /r command will fix errors found on the disk.

Let us know if you need further assistance.

 

Programs not working

In post 26 there were steps listed to fix the operating system corruption.
Are you able to follow them?
In post 29 was the suggested dism repair command.

 

Bsod

Wow, I took too long to type, so I didn't see the other suggestions.
But for one thing, I just rememnber that there was a thread about 8800 BSODs and a fix.
IIRC thread by d44ve, I'll have a look.