Windows 10: BSOD (After Windows 10 Upgrade) Bugcheck 116

Recently updated to Windows 10 from a ancient build after I suffered serve issues with adware etc,
After literally nuking my system I installed the latest version of windows 10, all info below,

Card = Nvidia (GTX 980 EVGA) (Factory Overclock)

Attachment 134717

Then I started to receive extremely weird behavior. The game I would be playing (Arma 3, Cities Skyline) would semi freeze (UI still updates but rendering is stuck in place). If I alt-tabbed out, windows would become extremely odd also. UI elements would remain on screen after I clicked them (ie opening taskmanager via taskbar menu), all programs in taskmanager would be reported to have 0% usage. But in the performance tab, it would list the CPU as "99%". Search would stop working, windows would be barely alive at this point. Teamspeak 3, (VOIP client) would now suffer from garbage audio. Cmd would not load (ie window opens, blinking cursor) Shutting down via start menu would do nothing.

I only managed to get a memory dump out by doing the combo (windows key + right arrow x 2 + S) to get the system to shutdown.

Upon reboot, everything's fine. It only occurs when I play certain games.

I used the driver removal software from guru3d and all that, and installed cleanly from absolute scratch. Made sure XBOX dvr was off, including game mode, and waited.

In the bugcheck dump ,one nvidia driver and two direct x drivers are the issue.

I do stress that it is not my hardware that is at fault, it literally only starting occurring when I reinstalled windows. The computer has correct ventilation, fans controlled automatically to ensure temp = correct etc...

Necessary files are included below.

Attachment 134720

:)

 

Endless IRQL_NOT_LESS_OR_EQUAL and MEMEORY_MANAGEMENT

The 0xf7 bugcheck dump was interesting as it is quite different from the 0xa bugcheck dumps.

See if Driver Verifier flags any 3rd party drivers -
http://www.sysnative.com/forums/bsod-crashes-kernel-debugging/29-driver-verifier-bsod-related-windows-10-8-1-8-7-vista.html

 

APC Index Mismatch- Windows 10 Pro 64 bit

I started getting the error today after upgrading from Windows 10 1703 to Fall Update 1709. I noticed in the bugcheck it was referencing the Intel display driver. I downloaded a new build that came out last week and installed it. So far i did not get the
BSOD but only time will tell i suppose.

 

New behavior; After the above issue, my files almost seem to be reverted to a old version of themselves, eg in filezilla my config has been reset to a config I was using last week for example (ip user/pass reverted). System restore inst even enabled, nor shadow copies....

 

Not able to read your dumps, keep get wrong symbols.

I did notice quite a few of these in the event log:
Code: Event[4971]: Log Name: System Source: Display Date: 2017-05-12T20:30:27.183 Event ID: 4101 Task: N/A Level: Warning Opcode: Info Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-O8C9QTN Description: Display driver nvlddmkm stopped responding and has successfully recovered.[/quote] Code: Event[4999]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-05-12T20:33:06.100 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-O8C9QTN Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xffffc884ff91f3e0, 0xfffff80eec46e0a4, 0x0000000000000000, 0x000000000000000d). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 73cea9fb-bfb0-4ef4-90fd-12d3c145087d.[/quote] See if you have this file: C:\Windows\MEMORY.DMP. If you do, zip it and upload to a site like OneDrive then post a link to it here. It's too big to upload directly to this site.

Since you already have the latest Nvidia driver, do the following:

 

MEMORY.zip

Onecloud memory.dmp as requested!

 

That dump also indicates a video error:
Code: VIDEO_TDR_FAILURE (116) Attempt to reset the display driver and recover from timeout failed. Arguments: Arg1: ffffc884ff91f3e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff80eec46e0a4, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation. Arg4: 000000000000000d, Optional internal context dependent data.[/quote] SInce the latest driver for your Nvidia card is having problems, try rolling back to a previous driver via Device Manager.

 

SInce the latest driver for your Nvidia card is having problems, try rolling back to a previous driver via Device Manager.[/quote] Will do [Even thought its a basic microsoft driver I'm afraid], I'll see if the error persists. Could it be that the newest version of windows is to blame for the incompatibility? And should I just try reverting to an old build ?

 

You have the latest Nvidia driver installed, not the default Microsoft driver.
Code: Driver File Version: 22.21.0013.8205 (English) Driver Version: 22.21.13.8205 Driver Attributes: Final Retail Driver Date/Size: 01/05/2017 01:00:00, 885032 bytes[/quote]