Random crashes - complete power shutdown

[JonJon]

I've had my computer for years and years. It will randomly crash in an instant at any given time - be it while playing a game or just surfing the web. I can find no rhyme or reason why it crashes or how to cause it to crash.

Sometimes it will run fine without crashing for months at a time. Then it slowly starts crashing more and more. First once every few days, then work its way up to crashing numerous times in a day.

The only thing I've found, through experimentation, to sort of remedy the problem is to turn off the PC, physically remove the graphics card, boot on the pc, wait ~2 mins, turn off PC, re-install GPU, turn on PC.

This usually will stave off the crashing, putting me at least back to the one or less crashes a day phase.

The issue seems to be OS independent, as I get the same behavior when running Ubuntu.

 

[JonJon]

Here are my attached dump files

 

[essenbe]

Hello, JonJon and welcome to the forums. I will try to help you. Please add to your system specs at the bottom left corner of you last post your PSU Manufacturer and Model. You have one dump file for this month. The next dump file was in April, so not a whole lot to go on.

Please make sure your system is configured for small memory dumps http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html.

this is the results of your last 3 memory dumps.

Use !analyze -v to get detailed debugging information.
[COLOR=red]BugCheck 124[/COLOR], {0, fffffa80074d6028, fe000000, 800400}
***** [COLOR=red]Debugger could not find nt in module list, module list might be corrupt, error 0x80070057[/COLOR].
Probably caused by : Unknown_Image
Followup: MachineOwner

BugCheck 124 means a faulty piece of hardware or a bad driver causing a piece of hardware to act as if it had failed/is failing. It is generic and gives no clue of which component it is.

April gave this dump file

[COLOR=red]VIDEO_TDR_FAILURE (116)[/COLOR]
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80094fd010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fd3caa4, 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.

A TDR error (Time Delay and Response) basically means your drivers crashed and did not recover in time.

Please reinstall your Video drivers following this tutorial http://www.sevenforums.com/tutorials/327414-nvidia-drivers-avoid-problems.html

Also, please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

Let us know the results please.

 

[JonJon]

Thank you for taking a look at this and offering guidance.

I have updated my System Specs to list my PSU. It is a Corsair HX1000W. I've also set up minidumps and uninstalled old GPU drivers / installed current GPU drivers as recommended in the post you provided.

First round of SFC /scannow found problems. I have since rebooted and am running the second round of SFC /scannow.

I will report back once I've run scannow three times.

 

[essenbe]

OK, sounds Great

 

[JonJon]

Ran "sfc /scannow" three times, rebooted after each time it finished. Each time it finishes it states it encountered errors. I believe that was the language used.

Here is a snippet from the end of my CBS.log file when I ran the last SFC /scannow

2015-06-13 13:05:07, Info CSI 00000306 [SR] Verify complete
2015-06-13 13:05:08, Info CSI 00000307 [SR] Verifying 100 (0x0000000000000064) components
2015-06-13 13:05:08, Info CSI 00000308 [SR] Beginning Verify and Repair transaction
2015-06-13 13:05:10, Error CSI 00000309 (F) STATUS_OBJECT_NAME_NOT_FOUND #6907728# from Windows::Rtl::SystemImplementation:irectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0xc7ca20->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[106]"\??\C:\Windows\WinSxS\x86_microsoft-windows-taskkill_31bf3856ad364e35_6.1.7600.16385_none_25545528bd642170"; aOBJ_CASE_INSENSITIVE)}, iosb = @0xc7ca00, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2015-06-13 13:05:10, Error CSI 0000030a@2015/6/13:17:05:10.486 (F) d:\win7sp1_gdr\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation:irectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2015-06-13 13:05:13, Error CSI 0000030b (F) STATUS_OBJECT_NAME_NOT_FOUND #6907727# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
2015-06-13 13:05:13, Error CSI 0000030c (F) STATUS_OBJECT_NAME_NOT_FOUND #6907726# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0xc7d318->SIL_OBJECT_ATTRIBUTES {s:40; on:"x86_microsoft-windows-taskkill_31bf3856ad364e35_6.1.7600.16385_none_25545528bd642170"; aOBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
[gle=0xd0000034]

 

[essenbe]

Open an elevated command prompt ( click start, type cmd in the search box, right click the cmd entry and select run as Administrator) Copy/paste this into the window and press enter

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt

It will place a sfcdetails.txt on your desktop. Right click it, select send to > compressed zip folder and upload the ZIP folder with your next reply. If it is over 8 MB, you can't upload it here. Upload it to One Drive or Dropbox and I will get someone to take a look at it.