Windows 10: Periodic re-boots

I have a problem that is driving me nuts.

Every so often the PC decides to re-boot. There is no BSOD to give a clue as to what causes it. The only clue I have is that I have never seen it happen. I would leave the PC for a time, maybe for a meal etc., and on returning would find that that the PC was awaiting a log-in.

I have a Nvidia GeForce 8800 GTX video card and have seen that some people have had issues with this card. I have tried the latest drivers (341.81) with no improvement, indeed the problem seemed worse so I have downgraded to 341.74 I have checked the system log file for warnings and/or errors but they give very little clue other than to tell me the system re-booted and that it may be due to a power failure.

When the system re-starts the ROM-BIOS is much slower in recognising my RAID configuration. This may or may not be significant as that is also Nvidia.

This afternoon I was at the PC when it did it again. There was a 3 tone notification sound followed by a black screen and a re-boot.

Any ideas?

Here's the WinDbg from the MEMORY.DMP.

Code: Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\\Desktop\MEMORY.DMP] Kernel Bitmap Dump File: Only kernel address space is available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Windows 8 Kernel Version 10240 MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 10240.16463.amd64fre.th1.150819-1946 Machine Name: Kernel base = 0xfffff803`18202000 PsLoadedModuleList = 0xfffff803`18527030 Debug session time: Tue Sep 8 17:27:51.681 2015 (UTC + 1:00) System Uptime: 0 days 1:45:08.524 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe - Loading Kernel Symbols ............................................................... ................................................................ .............................................................. Loading User Symbols ************* Symbol Loading Error Summary ************** Module name Error ntkrnlmp The system cannot find the file specified You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded. You should also verify that your symbol search path (.sympath) is correct. *** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgkrnl.sys - ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 116, {ffffe001018674c0, fffff8002b024608, 0, d} *** ERROR: Symbol file could not be found. Defaulted to export symbols for dxgmms1.sys - ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Either you specified an unqualified symbol, or your debugger *** *** doesn't have full symbol information. Unqualified symbol *** *** resolution is turned off by default. Please either specify a *** *** fully qualified symbol module!symbolname, or enable resolution *** *** of unqualified symbols by typing ".symopt- 100". Note that *** *** enabling unqualified symbol resolution with network symbol *** *** server shares in the symbol path may cause the debugger to *** *** appear to hang for long periods of time when an incorrect *** *** symbol name is typed or the network symbol server is down. *** *** *** *** For some commands to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* Probably caused by : nvlddmkm.sys ( nvlddmkm+154608 ) Followup: MachineOwner ---------[/quote]

:)

 

Process_initialization_failed

For win 10 builds that expired on October first they will stop booting period. You need to re-install the previous OS and then upgrade to the current version of win 10.

 

Spinning blue wheel icon.

Hey, It seems the issue has been resolved. I believe It happened because I forgot to re-boot after installing a driver. when I re-booted the icon stopped doing it.

During this period, sfc /scannow and Dism.exe /Online /Cleanup-image /Restorehealth would not work. They seem to be working now. Thanks, Pat.

 

Please use the tool and attach the zip.

 

Apologies, here's the zip file.

 

Problem device: Norman's S3 USB\VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_ANDROID\9&3899D6E&0&0000 This device cannot start.
Your GPU drivers are at fault. Please remove them with DDU and install another version.
Code: PxHlpa64.sys Wed Oct 17 20:25:02 2007 (4716537E) Sonic CD/DVD driver (used by many different CD/DVD programs)}pxHelp20.sys programs lists some of the programs that it's used in. http://www.carrona.org/drivers/driver.php?id=PxHlpa64.sys ctac32k.sys Wed Jul 2 10:38:22 2008 (486B3E7E) Creative Audio Driver}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=ctac32k.sys emupia2k.sys Wed May 5 19:55:01 2010 (4BE1B0F5) Creative E-mu Plug-in Architecture Driver}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=emupia2k.sys ctsfm2k.sys Wed May 5 19:55:08 2010 (4BE1B0FC) Creative SoundFont Management Device Driver}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=ctsfm2k.sys ctoss2k.sys Wed May 5 19:55:23 2010 (4BE1B10B) Creative OS Services Driver}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=ctoss2k.sys ha20x2k.sys Wed May 5 19:57:42 2010 (4BE1B196) Creative 20X HAL (WDM)}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=ha20x2k.sys ctaud2k.sys Wed May 5 19:58:54 2010 (4BE1B1DE) Creative Audio Driver (WDM)}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=ctaud2k.sys ctprxy2k.sys Wed May 5 19:58:57 2010 (4BE1B1E1) Creative Audio Driver (WDM)}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=ctprxy2k.sys CTEXFIFX.SYS Wed May 5 20:00:43 2010 (4BE1B24B) Creative sound card driver}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=CTEXFIFX.SYS CT20XUT.SYS Wed May 5 20:00:51 2010 (4BE1B253) Creative sound card driver}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=CT20XUT.SYS CTHWIUT.SYS Wed May 5 20:00:56 2010 (4BE1B258) Creative sound card driver}Creative Worldwide Support http://www.carrona.org/drivers/driver.php?id=CTHWIUT.SYS Mpfp.sys Thu Jul 15 21:40:11 2010 (4C3F641B) McAfee Personal Firewall Plus Driver}Antivirus Software and Internet Security For Your PC or Mac | McAfee http://www.carrona.org/drivers/driver.php?id=Mpfp.sys dccmtr.sys Thu Jun 2 22:56:51 2011 (4DE7F913) dccmtr.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. LEqdUsb.Sys Fri Sep 2 08:22:56 2011 (4E607640) Logitech SetPoint Unifying KMDF USB Filter}Logitech Support + Downloads http://www.carrona.org/drivers/driver.php?id=LEqdUsb.Sys LHidEqd.Sys Fri Sep 2 08:22:59 2011 (4E607643) Logitech SetPoint Unifying KMDF HID Filter}Logitech Support + Downloads http://www.carrona.org/drivers/driver.php?id=LHidEqd.Sys LHidFilt.Sys Fri Sep 2 08:23:09 2011 (4E60764D) Logitech SetPoint HID Filter Driver}Logitech Support + Downloads http://www.carrona.org/drivers/driver.php?id=LHidFilt.Sys LMouFilt.Sys Fri Sep 2 08:23:15 2011 (4E607653) Logitech SetPoint HID Filter Driver}Logitech Support + Downloads http://www.carrona.org/drivers/driver.php?id=LMouFilt.Sys wacomrouterfilter.sys Thu Nov 15 18:39:44 2012 (50A528E0) Wacom Router Filter}http://www.wacom.com/en/customercare/drivers.aspx http://www.carrona.org/drivers/driver.php?id=wacomrouterfilter.sys wachidrouter.sys Tue Dec 4 01:31:47 2012 (50BD4473) Wacom HID Router Driver}http://www.wacom.com/en/customercare/drivers.aspx http://www.carrona.org/drivers/driver.php?id=wachidrouter.sys dump_nvraid.sys Mon Apr 21 20:28:42 2014 (5355635A) dump_nvraid.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. nvraid.sys Mon Apr 21 20:28:42 2014 (5355635A) nVidia nForce RAID Driver}Download Drivers | NVIDIA http://www.carrona.org/drivers/driver.php?id=nvraid.sys nvstor.sys Mon Apr 21 20:34:03 2014 (5355649B) nVidia Storage Drivers}Download Drivers | NVIDIA http://www.carrona.org/drivers/driver.php?id=nvstor.sys ssudbus.sys Tue Jun 10 03:53:45 2014 (53966529) SAMSUNG USB Composite Device Driver. Likely a part of Samsung Kies.}Support: Where can I get support for Kies 2.6? [br] Download: Where can I get support for Kies 2.6? http://www.carrona.org/drivers/driver.php?id=ssudbus.sys ssudmdm.sys Tue Jun 10 03:53:49 2014 (5396652D) SAMSUNG CDMA Modem WDM. Likely a part of Samsung Kies.}Support: Where can I get support for Kies 2.6?[br]Download: Where can I get support for Kies 2.6? http://www.carrona.org/drivers/driver.php?id=ssudmdm.sys b57nd60a.sys Fri Sep 26 07:48:19 2014 (5424FE23) Broadcom NetXtreme Gigabit Ethernet}Downloads | Broadcom http://www.carrona.org/drivers/driver.php?id=b57nd60a.sys nvvad64v.sys Thu Nov 20 16:33:54 2014 (546E09E2) NVIDIA Virtual Audio Driver }Download Drivers | NVIDIA http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys NvStreamKms.sys Mon Jan 12 18:56:42 2015 (54B40ADA) nVidia Streaming Kernel service - may cause BSOD in Win8.1 systems (found in May 2014). Date/TimeStamp: Tue Apr 29 20:59:44 2014 (53604B00) MAY NOT BE A PROBLEM, this is a tenative posting - Appears that April 29 driver is a problem, July 2014 drivers seem OK}From: Solved BSOD at startup and lid closed DPC Watchdog ) [br] Possible fix: https://forums.geforce.com/default/t...ezing-your-pc/ [br] Or uninstall the nVidia drivers and then install a fresh copy without the Streaming Kernel Service (uncertain if this is possible) http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys psmounterex.sys Mon Feb 23 14:41:20 2015 (54EB2E00) psmounterex.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed. nvlddmkm.sys Mon Jun 29 21:13:29 2015 (559198D9) nVidia Video drivers}Download Drivers | NVIDIA[br]Get from OEM for laptops http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys intelppm.sys Fri Jul 10 05:12:59 2015 (559F383B) Intel Processor driver}Intel Download Center also at http://www.carrona.org/drivers/driver.php?id=intelppm.sys Code: Debug session time: Tue Sep 8 18:27:51.681 2015 (UTC + 2:00) Loading Dump File [D:\SysnativeBSODApps\090815-45765-01.dmp] Built by: 10240.16463.amd64fre.th1.150819-1946 System Uptime: 0 days 1:45:08.524 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+154608 ) BugCheck 116, {ffffe001018674c0, fffff8002b024608, 0, d} BugCheck Info: VIDEO_TDR_FAILURE (116) Bugcheck code 00000116 Arguments: Arg1: ffffe001018674c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8002b024608, 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. BUGCHECK_STR: 0x116 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys MaxSpeed: 2400 CurrentSpeed: 2400 BiosVersion = A06 BiosReleaseDate = 04/01/2008 SystemManufacturer = Dell Inc. BaseBoardManufacturer = Dell Inc. SystemProductName = Dell XPS720 BaseBoardProduct = 0P611C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Debug session time: Tue Sep 8 16:41:23.211 2015 (UTC + 2:00) Loading Dump File [D:\SysnativeBSODApps\090815-37875-01.dmp] Built by: 10240.16463.amd64fre.th1.150819-1946 System Uptime: 0 days 3:54:59.053 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+154608 ) BugCheck 116, {ffffe001c74ce4c0, fffff80047af4608, 0, d} BugCheck Info: VIDEO_TDR_FAILURE (116) Bugcheck code 00000116 Arguments: Arg1: ffffe001c74ce4c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff80047af4608, 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. BUGCHECK_STR: 0x116 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys MaxSpeed: 2400 CurrentSpeed: 2400 BiosVersion = A06 BiosReleaseDate = 04/01/2008 SystemManufacturer = Dell Inc. BaseBoardManufacturer = Dell Inc. SystemProductName = Dell XPS720 BaseBoardProduct = 0P611C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Debug session time: Mon Sep 7 16:17:51.636 2015 (UTC + 2:00) Loading Dump File [D:\SysnativeBSODApps\090715-77609-01.dmp] Built by: 10240.16463.amd64fre.th1.150819-1946 System Uptime: 0 days 1:23:40.479 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) BugCheck 116, {ffffe00127e674c0, fffff801fd6b4608, 0, d} BugCheck Info: VIDEO_TDR_FAILURE (116) Bugcheck code 00000116 Arguments: Arg1: ffffe00127e674c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff801fd6b4608, 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. BUGCHECK_STR: 0x116 DEFAULT_BUCKET_ID: PAGE_NOT_ZERO_0x116 PROCESS_NAME: System FAILURE_BUCKET_ID: PAGE_NOT_ZERO_0x116 MaxSpeed: 2400 CurrentSpeed: 2400 BiosVersion = A06 BiosReleaseDate = 04/01/2008 SystemManufacturer = Dell Inc. BaseBoardManufacturer = Dell Inc. SystemProductName = Dell XPS720 BaseBoardProduct = 0P611C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Debug session time: Mon Aug 31 19:04:57.225 2015 (UTC + 2:00) Loading Dump File [D:\SysnativeBSODApps\083115-44531-01.dmp] Built by: 10240.16463.amd64fre.th1.150819-1946 System Uptime: 0 days 6:02:33.067 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) BugCheck 116, {ffffe0016bc7e4c0, fffff80080794608, 0, d} BugCheck Info: VIDEO_TDR_FAILURE (116) Bugcheck code 00000116 Arguments: Arg1: ffffe0016bc7e4c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff80080794608, 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. BUGCHECK_STR: 0x116 DEFAULT_BUCKET_ID: PAGE_NOT_ZERO_0x116 PROCESS_NAME: System FAILURE_BUCKET_ID: PAGE_NOT_ZERO_0x116 MaxSpeed: 2400 CurrentSpeed: 2400 BiosVersion = A06 BiosReleaseDate = 04/01/2008 SystemManufacturer = Dell Inc. BaseBoardManufacturer = Dell Inc. SystemProductName = Dell XPS720 BaseBoardProduct = 0P611C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Debug session time: Wed Aug 26 10:06:18.347 2015 (UTC + 2:00) Loading Dump File [D:\SysnativeBSODApps\082615-53546-01.dmp] Built by: 10240.16431.amd64fre.th1.150810-2333 System Uptime: 1 days 21:35:14.500 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) BugCheck 116, {ffffe0018643e4c0, fffff800b7664608, 0, d} BugCheck Info: VIDEO_TDR_FAILURE (116) Bugcheck code 00000116 Arguments: Arg1: ffffe0018643e4c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff800b7664608, 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. BUGCHECK_STR: 0x116 DEFAULT_BUCKET_ID: PAGE_NOT_ZERO_0x116 PROCESS_NAME: System FAILURE_BUCKET_ID: PAGE_NOT_ZERO_0x116 MaxSpeed: 2400 CurrentSpeed: 2400 BiosVersion = A06 BiosReleaseDate = 04/01/2008 SystemManufacturer = Dell Inc. BaseBoardManufacturer = Dell Inc. SystemProductName = Dell XPS720 BaseBoardProduct = 0P611C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Debug session time: Mon Aug 24 12:29:32.622 2015 (UTC + 2:00) Loading Dump File [D:\SysnativeBSODApps\082415-57468-01.dmp] Built by: 10240.16431.amd64fre.th1.150810-2333 System Uptime: 2 days 23:28:47.464 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+154608 ) BugCheck 116, {ffffe001833184c0, fffff80156864608, 0, d} BugCheck Info: VIDEO_TDR_FAILURE (116) Bugcheck code 00000116 Arguments: Arg1: ffffe001833184c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff80156864608, 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. BUGCHECK_STR: 0x116 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys MaxSpeed: 2400 CurrentSpeed: 2400 BiosVersion = A06 BiosReleaseDate = 04/01/2008 SystemManufacturer = Dell Inc. BaseBoardManufacturer = Dell Inc. SystemProductName = Dell XPS720 BaseBoardProduct = 0P611C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Debug session time: Mon Aug 17 18:34:31.246 2015 (UTC + 2:00) Loading Dump File [D:\SysnativeBSODApps\081715-38218-01.dmp] Built by: 10240.16430.amd64fre.th1.150807-2049 System Uptime: 0 days 7:13:56.089 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : Unknown_Image ( PAGE_NOT_ZERO ) BugCheck 116, {ffffe0002fbce300, fffff800b32e4608, 0, d} BugCheck Info: VIDEO_TDR_FAILURE (116) Bugcheck code 00000116 Arguments: Arg1: ffffe0002fbce300, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff800b32e4608, 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. BUGCHECK_STR: 0x116 DEFAULT_BUCKET_ID: PAGE_NOT_ZERO_0x116 PROCESS_NAME: System FAILURE_BUCKET_ID: PAGE_NOT_ZERO_0x116 MaxSpeed: 2400 CurrentSpeed: 2400 BiosVersion = A06 BiosReleaseDate = 04/01/2008 SystemManufacturer = Dell Inc. BaseBoardManufacturer = Dell Inc. SystemProductName = Dell XPS720 BaseBoardProduct = 0P611C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Debug session time: Mon Aug 17 11:14:15.635 2015 (UTC + 2:00) Loading Dump File [D:\SysnativeBSODApps\081715-48531-01.dmp] Built by: 10240.16430.amd64fre.th1.150807-2049 System Uptime: 0 days 22:58:11.478 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+154608 ) BugCheck 116, {ffffe0007ff19010, fffff800fce84608, 0, d} BugCheck Info: VIDEO_TDR_FAILURE (116) Bugcheck code 00000116 Arguments: Arg1: ffffe0007ff19010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff800fce84608, 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. BUGCHECK_STR: 0x116 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys MaxSpeed: 2400 CurrentSpeed: 2400 BiosVersion = A06 BiosReleaseDate = 04/01/2008 SystemManufacturer = Dell Inc. BaseBoardManufacturer = Dell Inc. SystemProductName = Dell XPS720 BaseBoardProduct = 0P611C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` Debug session time: Tue Aug 11 14:30:31.673 2015 (UTC + 2:00) Loading Dump File [D:\SysnativeBSODApps\081115-45125-01.dmp] Built by: 10240.16412.amd64fre.th1.150729-1800 System Uptime: 0 days 1:53:49.765 *** WARNING: Unable to verify timestamp for nvlddmkm.sys *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys Probably caused by : nvlddmkm.sys ( nvlddmkm+154608 ) BugCheck 116, {ffffe00052c624c0, fffff8017d644608, 0, d} BugCheck Info: VIDEO_TDR_FAILURE (116) Bugcheck code 00000116 Arguments: Arg1: ffffe00052c624c0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8017d644608, 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. BUGCHECK_STR: 0x116 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT PROCESS_NAME: System FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys MaxSpeed: 2400 CurrentSpeed: 2400 BiosVersion = A06 BiosReleaseDate = 04/01/2008 SystemManufacturer = Dell Inc. BaseBoardManufacturer = Dell Inc. SystemProductName = Dell XPS720 BaseBoardProduct = 0P611C ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨`` --- E O J --- 2015 Sep 08 19:34:30 PM _88-dbug Copyright 2012 Sysnative Forums --- E O J --- 2015 Sep 08 19:34:30 PM _88-dbug Copyright 2012 Sysnative Forums --- E O J --- 2015 Sep 08 19:34:30 PM _88-dbug Copyright 2012 Sysnative Forums[/quote]

 

So, from the links you kindly supplied it seems likely, as I suspected, that the problem is with the display card, possibly overheating. I'll take the side panel off and clean the card's fans and get rid of any accumulated dust. If that cures the problem all well and good but I need to prepare myself for replacing the card.

Any recommendations? I'm not a gamer but do need a card with a reasonable amount of memory as my main computing is photo and video editing. I'm considering this one. Trying to avoid GeForce in case of similar problems with it's drivers.

 

Hi norman,

Currently there are a lot of problems caused by the drivers of Nvidia and AMD.
So if you have bad luck you won't avoid similar problems with AMD GPU's for the moment.

 

Got any recommendations?

 

OK, the dustbusting and cleaning seems to have had no effect at all. I decided to re-install the latest drivers as there seems no difference in either. I left the PC running and came back to it later to find it had re-booted. On logging in the PC informed me it needed a restart to perform this weeks upgrade. When the upgrade had completed I found that it had "downgraded" my display card drivers to the older ones (341.74). I have now done a "clean install" of all the Nvidia programs and drivers (341.81) and will leave the PC running once again.