Windows 10: Blue Screen of Death (Crash) When Playing Games

Were you able to find the memory dump file? Post #4 step #7.
Please post it into the thread using a one drive or drop box share link.


If you have read the links for Windows driver verifier and performed the following steps you can troubleshoot BSOD when you have the time:
1) made a brand new restore point
2) backed up files to another drive or to the cloud
3) made a backup image with Macrium
4) placed the backup image onto another drive or into the cloud
5) are comfortable with the 3 methods to turn off windows driver verifier.

The computer may be sluggish while using windows driver verifier.
Plan to use Windows driver verifier for 48 hours.
Once there are no longer any more BSOD plan to use Windows drive verifier for an additional 36 hours.

After each BSOD please post a new zip and we will guide you through the troubleshooting.
BSOD - Posting Instructions - Windows 10 Forums

 

Ok I got a number of crashes today. I saved all the dump files and have posted the links from my one drive. I hope I did it correctly as I have never used one drive before.


Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

 

All you need to do is re-run dm_l0g_collector and upload the resulting zip file here, in this thread. No need to use OneDrive.

As zbook said:

After each BSOD please post a new zip and we will guide you through the troubleshooting.
BSOD - Posting Instructions - Windows 10 Forums

 

There were 2 misbehaving drivers identified with windbg:
MbamChameleon.sys
AnviFPFltd.sys

The first driver was in the bsod database.
The second driver was not in this database and did not appear on the drivers list.

The windbg reports indicated that the misbehaving may have been displayed on the BSOD window. The automatic restart was turned off to provide as much time as needed to view the BSOD windows. If there are any new BSOD please view the BSOD windows for misbehaving drivers in the form *.sys. Consider using a camera or smart phone camera to take pictures and post images into the thread.


1) Open file explorer > this PC > local C: > in the right upper corner type or copy and paste: AnviFPFltd.sys
2) Post the search results into the thread.
3) If it is not found please search:
anvi
fpf
ltd

4) Uninstall Malwarebytes
5) Post a new zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums

Once Malwarebytes has been uninstalled turn on Windows driver verifier and post zips into the thread for any new BSOD:
BSOD - Posting Instructions - Windows 10 Forums

Malwarebytes can be installed once there are no BSOD for 2 weeks.
After 2 weeks of a stable computer environment you can reinstall Malwarebytes.
If there are no BSOD then continue to use Malwarebytes.
If there are new BSOD after 2 weeks of no BSOD then uninstall Malwarebytes and look for other AV products.

 

DESKTOP-UJ3E6U6-Sat_11_11_2017__91552_71.zip

 

The anvi driver I believe belongs to a folder locker I had. I deleted the folder locker. The driver is no longer present after uninstall.

 

Just had a few crashes upon restart.DESKTOP-UJ3E6U6-Sat_11_11_2017__94351_65.zip

 

Both Malwarebytes and Avira were faulting applications.
So far Malwarebytes was identified as the source of misbehaving drivers.

Please uninstall Avira during the troubleshooting process:
How do I uninstall my Avira Antivirus product?
Turn on Windows defender.

Continue using Windows driver verifier.

 

I'm hoping I've fixed the issue. After uninstalling avira, the computer crashed upon restart. This time it told me the problem was iomap64.sys. After a little research i found out this driver belongs to the Asus suite 3. Software for the mobo to monitor and overclock. Sounds like many people have had issues with that exact driver and its conflict with nvidias drivers. When this problem first started a few months ago I had just updated nvidias drivers. I have uninstalled the Asus suite and deleted all traces of that driver in safe mode. It was in 4 locations. No crashed since. I will keep my fingers crossed.

 

I am reviving this thread because I have run into a new issue and I got such great help last time. Today I randomly got a bsod. The stop code was 0xc000021a. Upon restart I am stuck in a bsod loop. When Windows tries to go into the automatic repair I still get a bsod. Further more if I try to boot to the Windows disc or usb I still get a bsod.

Sometimes I don't get even that far and the comp freezes after the bios screen and before it tries to load Windows. When I do get a bsod I get different stop codes. Other than the one listed above I have gotten: driver_irql_not_less_or_equal
kmode_exception_not_handled
critical process died

I have tried swapping the memory around. I have removed one stick and then tried the other stick to see if one was bad. No change. If I put the sticks into slots B1 and B2 instead of A1 and A2 the computer won't boot at all. I have disconnected the HD to see if it was a problem booting to disc. No change.

I can't get to safe mode of even reinstall Windows.

Do I have a bad mobo maybe?

 

1) Does the computer post?
What is POST?
2) Are there beep codes?
3) Do your hear the drives?
4) Do you hear the fans?
5) Run though these links:
POST troubleshooting steps
Computer POST and beep codes
6) Find some flash drives that your can format.
7) Create a bootable windows 10 iso:
Download Windows 10
8) Create a bootable Memtest86+ version 5.01 flash drive
9) Create a Kyhi boot drive:
Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums
10) Report the post steps and the progress with the flash drives

 

Ok. There are no beeps during post, but there never were i don't think. All fans start fine. The HDDs are SSDs so i can't hear them. I am able to navigate the bios fine.

Memtest loaded fine and found no errors.

I made a kyhi boot usb. I get a Windows logo upon boot and then a bsod. The exact same thing as when I try to boot to the Windows disc. I tried to boot several times from the usb and got different stop codes listed above.

 

For memtest86+ version 5.01
Please test for 8 or more passes.
Memtest86+ version 5.01 is not run by time but by passes.
The more the passes the better the test.
There are multiple software products to test RAM. Please make sure that you use this link: Memtest86+ - Advanced Memory Diagnostic Tool
When testing has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
A substantial poertion of the testing can be done overnight.
Just 1 error is a fail and you can abort testing.
Then remove all RAM except 1 module and test 1 RAM module at a time in the same DIMM for 8 or more passes.

If you are able to boot to windows or safe mode run the DM log collector and post a zip into the thread for troubleshooting:
BSOD - Posting Instructions - Windows 10 Forums

 

I have run Memtest with all combinations of my 2 sticks of ram. Found no errors.

I took the memory sticks out of slots a1 and b1. I moved them to a2 and b2 where they should have been to begin with. The computer would not boot at all. Not even to the bios.

I read somewhere that 2 touching cpu pins could cause this. I took the cpu off and checked the line with a magnifying glass. Couldn't find anything so I reinstalled the cpu.

For some reason the computer now boots with sticks in a2 and b2, but still crashed. If I let the computer sit a while off and then boot i can sometimes get into Windows for a few seconds before the bsod. After that it won't make it that far.

I bought the same exact memory to swap out for shits and giggles thinking if it fixed my issue great and if it didn't i would just have 32gb instead of 16. No loss either way. No change with new sticks unfortunately.

I tried to reinstall Windows from the disc, but always crashed before it loaded. I did finally get the recovery to work from a usb and reformatted and reinstalled Windows. Once Windows went to load for the first time i get the bsod. No change with clean install.

Any more help of ideas would be greatly appreciated. Thanks.