Computer crashing/shutting down while playing fallout 4.

In the last 24 hours my system has started consistently locking up and shutting down about 60 seconds into playing fallout 4. I have never had quite a significant crash while playing any other game. The game had been working fine up until this point. I have installed new graphics drivers, I uninstalled virtu MVP, and I cleaned the inside of the tower and checked the wiring. None of these have resolved the issue. If anyone could help me I would be very grateful.

Heres my speccy link: http://speccy.piriform.com/results/2ZxBJzfg3yk0VM2sDAuFGh8

And this is the whocrashed report for the entire computers history.

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 11/15/2015 10:23:44 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111515-28470-01.dmp
This was probably caused by the following module: virtuwddm.sys (VirtuWDDM+0x867C)
Bugcheck code: 0x116 (0xFFFFFA800FA194E0, 0xFFFFF88000E7B67C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: virtuwddm.sys .
Google query: virtuwddm.sys VIDEO_TDR_ERROR



On Sun 11/15/2015 10:23:44 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: virtuwddm.sys (0xFFFFF88000E7B67C)
Bugcheck code: 0x116 (0xFFFFFA800FA194E0, 0xFFFFF88000E7B67C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: virtuwddm.sys .
Google query: virtuwddm.sys VIDEO_TDR_ERROR



On Sun 11/15/2015 7:04:53 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111515-28002-01.dmp
This was probably caused by the following module: virtuwddm.sys (VirtuWDDM+0x867C)
Bugcheck code: 0x116 (0xFFFFFA80106774E0, 0xFFFFF880047D067C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: virtuwddm.sys .
Google query: virtuwddm.sys VIDEO_TDR_ERROR



On Wed 11/11/2015 9:58:53 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111115-36254-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003292FE6, 0xFFFFF8800A93F7E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 11/10/2015 9:51:12 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\111015-32354-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x74200)
Bugcheck code: 0xA (0x140792E3FC, 0x2, 0x1, 0xFFFFF8000308BF7C)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 12/13/2014 2:34:24 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\121214-27534-01.dmp
This was probably caused by the following module: virtuwddm.sys (VirtuWDDM+0x867C)
Bugcheck code: 0x116 (0xFFFFFA80072FE1F0, 0xFFFFF880047A867C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: virtuwddm.sys .
Google query: virtuwddm.sys VIDEO_TDR_ERROR



On Tue 8/26/2014 4:33:29 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\082614-32417-01.dmp
This was probably caused by the following module: virtuwddm.sys (VirtuWDDM+0x867C)
Bugcheck code: 0x116 (0xFFFFFA800987C2D0, 0xFFFFF8800425D67C, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: virtuwddm.sys .
Google query: virtuwddm.sys VIDEO_TDR_ERROR

Edited by YoureReadingMyName, 15 November 2015 - 09:29 PM.

I hope these load correctly. Sorry for not including them in the original message.

Edited by YoureReadingMyName, 15 November 2015 - 09:08 PM.

Start with this:

Please follow these troubleshooting suggestions:  http://www.sysnative.com/forums/bsod-kernel-dump-analysis-debugging-information/35-video-tdr-timeout-0x116-0x117.html#post29532
Also, please monitor your temps with this free utility:  http://www.cpuid.com/softwares/hwmonitor.html

I'll be posting more in a short while (10-30 minutes).

Sorry for the delay in responding - I've been awfully busy with the home, family, and work over the past few weeks.
 

You have a Belkin USB Wireless Adaptor (driver dates from 6/20/2015):

I do not recommend using wireless USB network devices.
These wireless USB devices have many issues with Win7 and later systems - using older drivers with them is almost certain to cause a BSOD.
Should you want to keep using these devices, be sure to have the latest W7/8/8.1/10 drivers - DO NOT use older drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

Please uninstall the XFastLAN and XFastUSB utilities as they are known to cause BSOD's in some Windows systems

The STOP 0x116's point at VirtuWDDM.sys - a driver for your VIRTU LucidInterop WDDM Driver by LucidLogix

I think this is related to the switching software or touchscreen - I'm uncertain which it is.  But it does need to be uninstalled and a fresh copy installed.

Additionally, your Wireless USB XBox controller is outdated and is known to cause BSOD's on some Windows systems.

Unfortunately there is no update for this driver (xusb21.sys), so the test is to uninstall the software and physically remove the device from your system.

If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

Analysis:
The following is for informational purposes only.
**************************Sun Nov 15 17:23:44.880 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111515-28470-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
System Uptime:0 days 1:05:51.113
*** WARNING: Unable to verify timestamp for VirtuWDDM.sys
*** ERROR: Module load completed but symbols could not be loaded for VirtuWDDM.sys
Probably caused by :VirtuWDDM.sys ( VirtuWDDM+867c )
BugCheck 116, {fffffa800fa194e0, fffff88000e7b67c, ffffffffc000009a, 4}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Arguments:
Arg1: fffffa800fa194e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88000e7b67c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x116_IMAGE_VirtuWDDM.sys
CPUID:        "Intel® Core™ i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.90
  BIOS Release Date             07/11/2013
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z77 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 15 02:04:53.706 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111515-28002-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.19045.amd64fre.win7sp1_gdr.151019-1254
System Uptime:0 days 4:39:06.565
*** WARNING: Unable to verify timestamp for VirtuWDDM.sys
*** ERROR: Module load completed but symbols could not be loaded for VirtuWDDM.sys
Probably caused by :VirtuWDDM.sys ( VirtuWDDM+867c )
BugCheck 116, {fffffa80106774e0, fffff880047d067c, ffffffffc000009a, 4}
BugCheck Info: VIDEO_TDR_FAILURE (116)
Arguments:
Arg1: fffffa80106774e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880047d067c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
BUGCHECK_STR:  0x116
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: X64_0x116_IMAGE_VirtuWDDM.sys
CPUID:        "Intel® Core™ i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.90
  BIOS Release Date             07/11/2013
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z77 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed Nov 11 16:58:53.692 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111115-36254-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.19018.amd64fre.win7sp1_gdr.150928-1507
System Uptime:1 days 0:06:50.551
Probably caused by :ntkrnlmp.exe ( nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26 )
BugCheck 3B, {c0000005, fffff80003292fe6, fffff8800a93f7e0, 0}
BugCheck Info: SYSTEM_SERVICE_EXCEPTION (3b)
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003292fe6, Address of the instruction which caused the bugcheck
Arg3: fffff8800a93f7e0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Fallout4.exe
FAILURE_BUCKET_ID: X64_0x3B_nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+26
CPUID:        "Intel® Core™ i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.90
  BIOS Release Date             07/11/2013
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z77 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Nov 10 16:51:12.052 2015 (UTC - 5:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\111015-32354-01.dmp]
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Built by: 7601.19018.amd64fre.win7sp1_gdr.150928-1507
System Uptime:10 days 16:03:56.731
Probably caused by :win32k.sys ( win32k!SURFACE::Map+a1 )
BugCheck A, {140792e3fc, 2, 1, fffff8000308bf7c}
BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
Arguments:
Arg1: 000000140792e3fc, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8000308bf7c, address which referenced memory
BUGCHECK_STR:  0xA
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  Fallout4.exe
FAILURE_BUCKET_ID: X64_0xA_win32k!SURFACE::Map+a1
CPUID:        "Intel® Core™ i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.90
  BIOS Release Date             07/11/2013
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z77 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
**************************Sun Nov 15 17:23:44.880 2015 (UTC - 5:00)**************************
intelppm.sys                Mon Jul 13 19:19:25 2009 (4A5BC0FD)
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
xusb21.sys                  Thu Aug 13 18:10:17 2009 (4A848F49)
amdxata.sys                 Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asmtxhci.sys                Fri Mar  4 02:54:59 2011 (4D709AD3)
asmthub3.sys                Fri Mar  4 02:55:10 2011 (4D709ADE)
k57nd60a.sys                Tue May 10 00:42:30 2011 (4DC8C236)
AsrAppCharger.sys           Tue May 10 04:28:46 2011 (4DC8F73E)
cfosspeed6.sys              Mon Jul  4 09:18:51 2011 (4E11BDBB)
RTL8192su.sys               Wed Aug 10 22:36:33 2011 (4E434031)
ISCTD64.sys                 Tue Aug 23 13:32:39 2011 (4E53E437)
asahci64.sys                Wed Sep 21 05:42:57 2011 (4E79B1A1)
WPRO_41_2001.sys            Mon Nov  7 16:04:48 2011 (4EB847F0)
ikbevent.sys                Tue Jan  3 19:35:09 2012 (4F039EBD)
imsevent.sys                Tue Jan  3 19:35:31 2012 (4F039ED3)
AsrRamDisk.sys              Thu Jan 12 23:52:38 2012 (4F0FB896)
RTKVHD64.sys                Tue Jan 31 05:55:06 2012 (4F27C88A)
iusb3hub.sys                Mon Feb 27 05:56:50 2012 (4F4B6172)
iusb3xhc.sys                Mon Feb 27 05:56:53 2012 (4F4B6175)
iusb3hcs.sys                Mon Feb 27 05:58:49 2012 (4F4B61E9)
VirtuWDDM.sys               Mon Mar 12 04:55:57 2012 (4F5DBA1D)
GEARAspiWDM.sys             Thu May  3 15:56:17 2012 (4FA2E2E1)
FNETURPX.SYS                Wed May 30 23:00:47 2012 (4FC6DEDF)
IntcDAud.sys                Tue Jun 19 10:40:51 2012 (4FE08F73)
HECIx64.sys                 Mon Jul  2 18:14:58 2012 (4FF21D62)
iaStorA.sys                 Sat Sep  1 21:01:24 2012 (5042AFE4)
iaStorF.sys                 Sat Sep  1 21:01:27 2012 (5042AFE7)
igdkmd64.sys                Thu Sep 13 23:30:58 2012 (5052A4F2)
mbam.sys                    Wed Sep  3 13:50:25 2014 (540754E1)
nvvad64v.sys                Mon Aug 10 03:51:42 2015 (55C8580E)
NvStreamKms.sys             Fri Sep 18 01:02:24 2015 (55FB9AE0)
nvhda64v.sys                Mon Sep 21 05:44:17 2015 (55FFD171)
nvlddmkm.sys                Thu Nov  5 10:11:59 2015 (563B71BF)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sun Nov 15 02:04:53.706 2015 (UTC - 5:00)**************************
nvhda64v.sys                Thu Apr 16 15:03:16 2015 (55300774)
NvStreamKms.sys             Sat Jul 25 05:22:15 2015 (55B35547)
nvlddmkm.sys                Fri Oct  2 21:54:49 2015 (560F3569)
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=xusb21.sys
http://www.carrona.org/drivers/driver.php?id=amdxata.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=k57nd60a.sys
http://www.carrona.org/drivers/driver.php?id=AsrAppCharger.sys
http://www.carrona.org/drivers/driver.php?id=cfosspeed6.sys
http://www.carrona.org/drivers/driver.php?id=RTL8192su.sys
http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys
http://www.carrona.org/drivers/driver.php?id=asahci64.sys
http://www.carrona.org/drivers/driver.php?id=WPRO_41_2001.sys
http://www.carrona.org/drivers/driver.php?id=ikbevent.sys
http://www.carrona.org/drivers/driver.php?id=imsevent.sys
http://www.carrona.org/drivers/driver.php?id=AsrRamDisk.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hub.sys
http://www.carrona.org/drivers/driver.php?id=iusb3xhc.sys
http://www.carrona.org/drivers/driver.php?id=iusb3hcs.sys
http://www.carrona.org/drivers/driver.php?id=VirtuWDDM.sys
http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
http://www.carrona.org/drivers/driver.php?id=FNETURPX.SYS
http://www.carrona.org/drivers/driver.php?id=IntcDAud.sys
http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=iaStorF.sys
http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
 

Edited by usasma, 17 November 2015 - 07:34 AM.

Hey, thank you so much for responding. My computer actually ended up having a bad stick of memory and it got to the point where it refused to boot. I've just recently taken the time to identify and remove the bad stick. Once i get everything up and running properly again I'll take care of everything you listed. Thanks again, and sorry for taking so ridiculously long to respond. this is the only computer I spend any real time on and it was offline.

No problem with the delay, we all have lives outside of computers.

Thanks for letting us know!