Hello Alex and welcome to Sevenforums.
BSOD Analyse
Your dumps does in fact point to video related events. Therefore, we're having a good perspective of what's going on, and the threads are not too wide. We'll be working on some troubleshooting steps I recommend, and hopefully we'll draw out some conclusions.
Graphic Driver
The Graphic driver usually points out when the 0x116 bugcheck code triggers, and by that we want to
get a clean install of a new driver, and avoid having left-over files. If you're having any questions on the tutorial below, just ask away.
i) Make your way to
ATI Drivers - Download NVIDIA Drivers
ii) Uninstall the one you currently have and all its extensions
iii) Download
Driver Sweeper
iv) Get to
safe mode (without network) and search for Driver Sweeper in your
rb:
v) Select all the ATI components and
analyse them
vi)
Clean them, head into Windows
without internet and download the driver
Direct-X
There's also some pointers to your Direct-X files. Option one is that it
could be the Direct-X files. Option two is that it could be a part of the Windows system files (jump to the third suggestion), as Direct-X is a part of that. To be one the safe side, update your Direct-X files.
Download: DirectX End-User Runtime - Microsoft Download Center - Download Details
Windows Corrupted
We usually ask people to do this command to check if Windows is corrupted. It's the most common one used to check if the Windows files are corrupted. If it'll find errors, it'll restore them.
Tip
If you're having a custom customization layer on your Aero, it's likely to get restored to default.
Press
Start | search
'cmd' |
Right-click it
| open as
Admin | type
SFC /SCANNOW
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Memory
Looking at your bugcheck it's likely that a memory corruption event also happened. Though a driver could be causing the memory to be borked, but we're usually suggesting a memory test before moving forward. Do a scan with Memtest86+. Memtest is a scanner that'll check your sticks for errors. To ensure that we'll know if it's the slots on the motherboard that's broken, or the sticks itself - we have a little procedure we'll recommend. Remove 1 stick, scan the other with Memtest in the current slot. After 7 passes, move the stick to another slot and scan, and so on and so forth until you've scanned all the sticks, and all the slots, one by one.
Memtest86+ - Advanced Memory Diagnostic Tool
Code:
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8007f729b0
Arg3: 000000000000ffff
Arg4: 0000000000000000
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800daee4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88002a1945c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Other tips and tricks
- Stop any type of overclocking.
- Blow the Graphic Card fans.
- Make sure that no hidden overclocking feature is on.
- Download Speccy and make sure that temperatures are stable.
- Make sure that the games you're playing has the latest updates and look for Q&A's, fixes and compatibilities.
Your 3rd party drivers seems
OK.
Devices
Click
Start | Search for
'devmgmt.msc' | Expand all the dropdowns
| Look for :warn:
Report if it has those.
Hope this helps,
Frederik.
