BSOD [APC_INDEX_MISMATCH] after some changes on the pc

So far so good, maybe the nVidia config change I made did it? I'll keep you guys posted...

I'm going on a trip, so I'll keep testing when I get back. Thanks to all!

OK, so today it happen again. No inet visibility from outside, monitors off, but PC running. No BSOD crash on BlueScreenView, and yes, pagefile is on, automatically managed by windows for all drives. Here's a new dump of my PC. I think it may happen after I play around with nVidia 3D vision, but I'm not 100% sure about that.

Thanks.

Search for live kernal reports > post links into the thread
live-kernal-reports
WATCHDOG-20180207-2102.dmp

Where would those be?

File explorer > this PC > C: > right upper corner search

1) backup all files to another drive or to the cloud
2) make a backup image using Macrium:
Macrium Software | Macrium Reflect Free
3) save the backup image to another drive or to the cloud
4) make a brand new restore point

Windows driver verifier is a tool that tests drivers.
It will repetitively produce BSOD until misbehaving drivers are fixed or until the tool is turned off.

In order to turn off the tool there are 3 methods using the windows advanced troubleshooting menu:
Enable and Disable Driver Verifier in Windows 10 Performance Maintenance Tutorials

Use the settings in this link for the customized tests:
Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

During the use of windows driver verifier the computer may become sluggish. Sometimes there is difficulty booting. If you experience either of these problems the customized test settings can be modified.

The tool will be used for 48 hours. After the last BSOD it will be used for an additional 36 hours of typical computer use.

After each BSOD > turn off windows driver verifier > uninstall the misbehaving driver > post a new zip for troubleshooting:
log collector v2-beta08.zip

zbook said:

File explorer > this PC > C: > right upper corner search

Founded on C:\Windows\LiveKernelReports\WATCHDOG :)

The msinfo32 was corrupt.
Please find it manually and post it into the thread:
In the left lower corner type: msinfo32 > save as NFO > save to desktop > zip > post into the thread

There you go. I tried verified before, as I said in the thread, and my PC went on a BSOD loop, never again booting properly. MSInfo32 seems to freeze at the end of the proccess, is that data actually relevant for my failure?