BSOD while playing

Question

I was playing halo and I got a BSOD, here's the minidump https://drive.google.com/file/d/1WlM67NLtpGsv8sJCXoUL1TOuJvyWFD6t/view?usp=share_link
thanks in advance

Answer 1

1) After uninstalling the gaming software related to easyanticheat.sys make a new restore point.

https://www.tenforums.com/tutorials/4571-create-system-restore-point-windows-10-a.html

2) Post the HD Sentinel results (they are instantaneous)

3) Post the tuneup plus results

4) Read this link on Windows Driver Verifier (WDV):

https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands:

verifier /reset

verifier /bootmode resetonbootfail

Plan to run the tool for 48 hours.

For each BSOD post a new V2 share link into this thread.

Start the tool with these customized settings:

a) Test all non-Microsoft drivers
b) Test no Microsoft drivers
c) Start the tool with the 3 customized tests displayed in the Ten Forums link

If there is no immediate BSOD then open administrative command prompt and type or copy and paste:

verifier /querysettings

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

.
.
.
.
.

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

First scannow:

Windows Resource Protection found corrupt files and successfully repaired them.

Second scannow:

Windows Resource Protection did not find any integrity violations.

The left side of each post displays 0 with an up arrow.

If you find the posts useful please click to upvote.

Answer 3

Detach the joystick and uninstall: vmulti.sys

vmulti HUION HID c:\windows\system32\drivers\vmulti.sys

https://sourceforge.net/projects/vjoystick/

Do not reinstall any of the misbehaving drivers at this time.

Restart WDV using the prior settings.

If there is no immediate BSOD then open administrative command prompt and type or copy and paste:

verifier /querysettings

Post a share link into this thread.

Please post share links for only the specific file instead of all the collected files so that everything can be quickly downloaded and troubleshooted.

If the thread posts are useful please click the upvote on the left side of each post.

Answer 4

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

Answer 5

The link did not have the results of the V2 log collector and only had the mini dump file.

It is not necessary to post the mini dump file as the V2 log collector will collect the mini dump file.

If any of the above posts were / are useful please click the arrow on the left side of each post.

This is an upvote.