Solved System Randomly Shuts Off - Since Yesterday [Problem Details Within]

[Holiday7]

Hello there! this is my first post, I come here often as an 'outsider' for support on troubleshooting but this time I can't genuinely work out what's causing my issue after some research!

Since yesterday my Windows 7 Professional x64 system has been shutting itself off mid-use and whilst away, left idling. I've seen it shut down when:

• Midway through a SUPERAntiSpyware scan [Nothing else running]
• Typing in a form submission text box in Firefox [Latest version & Add-ons]
• Typing in a generated Notepad document

...just normal day-to-day use for me!

Here are the problem details under Windows Reliability Monitor [Same for all the occurrences]

• I'm using all the latest Windows Updates
• I managed to run and complete another scan, also with Avira Internet Security 2012 [Squeaky Clean as always]
• The integrity of my Windows System Files is OK
• My CPU & GPU temperatures are fine - it's slightly warmer than usual where I am as well
• My CPU & RAM seem to be stable
• My PSU of high quality construction and has an LED indicator which displays everything as functioning normally
• On a quick inspection all cables seem to be connected fine internally
• No other external USB devices were attached during any of the witnessed shut downs other than my Logitech G110 Keyboard and G9x mouse [Only ever plug in an external HDD from time to time]

Also, looking through my Windows Reliability History Log, apparently the only software change recently is the installation of Microsoft Visual C++ 2005 Redistributable and Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17. I've installed and uninstalled a few games via the Steam interface over the last week as well which aren't shown here (likely linked to the redistributable installs). FlashPlayerPlugin_11_3_300_265.exe is shown crashing daily as I use Firefox lately - though this is an issue with recent updates.

Is there something similar to a crash dump that I can locate and post to assist? It's not blue screening or freezing or necessarily crashing or even making any odd noises - it literally just shuts off... :shock:

I would be grateful for any assistance in getting things back to normal operation! Thank you in advance and don't be hesitant in asking/requiring any more information

EDIT:
Included system data/logs - View attachment 222942

FINAL EDIT:
My issues were due to a faulty motherboard. [See last posts]

 

[karlsnooks]

Holiday,
Welcome to SevenForums.

http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

That procedure will provide us with the needed info.
thanks,
karl

 

[Holiday7]

Thanks Karl, I've amended my original post with the requested information.

 

[karlsnooks]

there are no dmp files in there.

Please go thru each and every step of this procedure.

[FONT=&quot]MEMORY DUMPS - REQUIREMENTS[/FONT]


Enable automatic management of the Paging file
WIN + PAUSE/BREAK key combo |
Advanced system settings (left-hand side) |
Advanced tab, Performance section, Settings |
Advanced tab, Virtual Memory section, Change |
checkmark Automatically manage paging file size for all drives |
OK | OK | OK



STARTUP AND RECOVERY SETTINGS
WIN + PAUSE/BREAK key combo |
Advanced system settings (left-hand side) |
Advanced tab, Startup and Recovery section, Settings |
System Failure section | checkmark Write an Event to the system log
| uncheck Automatically restart |


Under Write debugging information, select Small memory dump |
in the Small dump directory: box, enter %SystemRoot%\Minidump| OK

If Overwrite any existing file is checked, then:
Ø Under Write debugging information, select Kernel memory dump
Ø Uncheck Overwrite any existing file
Ø Under Write debugging information, select Small memory dump
Ø OK button
If you get a crazy message from Win 7 about your paging file being too small, then just ignore the message since we have already made sure that the paging file is set to be managed by Win 7.

ENABLE THE WINDOWS ERROR REPORTING SERVICE
WIN key | type SERVICES.MSC | ENTER |
Scroll down to Windows Error Reporting Service |
Rt-clk on Windows Error Reporting Service | Properties |
General tab | for Startup type, choose Automatic |
In Service status, Start button (unless grayed out) | OK


ASSURE THAT CCLEANER IS NOT DELETING DUMPS
CCLEANER | Cleaner icon | Windows tab | System category |
Uncheck Memory Dumps
· WINDOWS ERROR REPORTING SERVICE must NOT be disabled!
· WIN | Services.msc | Enter
· Under Name, locate Windows Error Reporting Service
· If Status is not Started, then
Right-click on Windows Error Reporting Service |choose START
· If Startup Type is not Automatic, then
Right-click on Windows Error Reporting Service |
choose Properties | General tab |
set Startup type to Automatic
· Close Services.msc (I like to use ALT + F4)

After a crash, the minidump file will be in %SystemRoot%\Minidump
%SystemRoot% is generally C:\Windows

 

[Holiday7]

Oh, sorry about that. Just gone through each step now.

The only alterations that needed to be changed in the process were:

STARTUP AND RECOVERY SETTINGS-
Ø Under Write debugging information, select Kernel memory dump
Ø Uncheck Overwrite any existing file
Ø Under Write debugging information, select Small memory dump
Ø OK button

Followed by:

ENABLE THE WINDOWS ERROR REPORTING SERVICE-
General tab | for Startup type, choose Automatic |
In Service status, Start button (unless grayed out) | OK


There were no minidump files there when I inspected the relevant folder just now. Hopefully now if it happens again, there should be useful dmp files generated in there?

Also, do these files always get generated if 'Windows was not properly shut down' with no sightings of blue screens or a sense that the computer is about to turn off/have issues?

 

[karlsnooks]

Also, do these files always get generated if 'Windows was not properly shut down' with no sightings of blue screens or a sense that the computer is about to turn off/have issues?

Sometime yes. Sometimes no.

Please run the PowerShell script and upload the resulting file that is placed on your desktop.

# **********************INSTRUCTIONS**************************
# STEP 1 ** RUN POWERSHELL AS ADMINISTRATOR ******************
# ************************************************************
#
# WIN key | type POWERSHELL | do NOT hit ENTER |
# in the PROGRAMS list, right-click on WINDOWS POWERSHELL |
# choose "Run as administrator" |
# Click on the YES button (if such appears)
#
# WIN key = key with Microsoft log on top
#
# for the guru:
# WIN | type POWERSHELL | CTRL+SHIFT+ENTER key combo | ALT+Y keycombo
# ************************************************************
# STEP 2 ** COPY AND PASTE ***********************************
# ************************************************************
#
# COPY the script using CTRL+C,
# COPY every line of script down thru both EXIT statements
#
# PASTE into Powershell
#----Right-Click at the PowerShell Prompt
#----(Ctrl+V does not work)
#
# Start copying with first script line without a # at start of the line
# Note: Actually, you can paste the entire file if you rather
#-------Lines starting with a # are ignored by PowerShell
# ************************************************************
# STEP 3 ** SCRIPT OUTPUT & SCRIPT PURPOSE *******************
# ************************************************************
# --The script output and purpose is given at the very front of the script
#
# --The script output and purpose is given at the very front of the script
#
# ************************************************************
# ***************** NOTE - POWERSHELL VERSION*****************
# if you receive this error msg:
#--The system can not find the path specified
# you may need to update your PowerShell
# you must be using Powershell 2.0 or later.
#
# To determine your Powershell version:
#---Run PowerShell
#---enter $host.version
#---you should see at least:
# Major Minor Build Revision
# ----- ----- ----- --------
# 2......0......-1.....-1
#
# If you do not see the above, update your Vista/Win 7.
# ************************************************************
# *************** NOTE - EXECUTION POLICY*********************
# If you haven't set the execution policy, you may need to:
#---Run PowerShell
#---enter SET-EXECUTIONPOLICY -EXECUTIONPOLICY REMOTESIGNED
# ************************************************************

wmic recoveros get /all  /format:list > $env:userprofile\desktop\dmpinfo.txt

EXIT
EXIT

 

[Holiday7]

Is this okay?

View attachment 223067

As an update, I haven't had a shut-off since the last one, yesterday. Since then I've updated my video drivers from the last WHQL release to the latest (prior, mine were the most recent WHQL release without being the latest - so they weren't old)

Also did the same regarding the physX installer (though I used a more up-to date one than the version that comes bundled with the latest WHQL drivers).

 

[karlsnooks]

dmpinfo shows that all dump settings are correctly set.

Let's hope that system continues without shut-offs.

 

[Holiday7]

Cheers for the assistance Karl

Fingers crossed that the shut-off's have magically disappeared for good...

The only thing I've done that could remotely help was make sure every single piece of installed software is up-to date and my Video and PhysX drivers were out of date (only by a release) - though I can't see this having any effect on my system shutting off randomly!

If any one else reading has suffered to same issue and has a diagnosis/answer please don't hesiste in posting!

 

[Holiday7]

So... my system has shut it self off abruptly again...

Not altered any hardware lately (quick look inside and everything is as the norm) and software wise - just today I did some important Windows Updates, followed by software updates to Adobe Flash, Adobe Reader X, EA's Origin, Samsung Kies and the Ubisoft Uplay client.

Note: At the time I was mid-way through a long session on a computer game - Payday: The Heist (Never had any issues running it). After turning my system back on it quickly shut it self off shortly after loading the OS.

What shall I post in-order to get a diagnosis?

Thanks in advance!

 

[karlsnooks]

carry out following again. do not amend anything. Attach the zip file to your NEXT post. thanks, that helps us.

Blue Screen of Death (BSOD) Posting Instructions

 

[Holiday7]

Updated .zip file here:
View attachment 226648

What may be of significant info is once my system shut it self off last time and I turned it back on again - I noticed the back-light on my Logitech G110 keyboard and G9x mouse didn't light up during boot as normal. I unplugged both for a moment and reconnected - I haven't had another incident since yesterday...

I remember this occurring to my keyboard back-light during my first bout of random system shut offs and after updating my video drivers I did unplug my keyboard and re-connect (which I forgot to mention) - could a fault with my keyboard/mouse be forcefully shutting my system down?

 

[Holiday7]

So... after using a different keyboard, my system is still randomly shutting off! At least I can rule that out though

On the last couple of occasions some shut-off were mid-way through playing games, I've had HWiNFO64 combined with MSI afterburner to display GPU and CPU temps whilst gaming for around an hour and my temps were all well within safe limits!

I decided to run Windows 7's Error-checking tool on my HDD incase that was to blame? I set one up to run before boot to automatically fix file system errors and to scan for an attempt recovery of bad sectors. Strangely enough my system shut off shortly into stage 4 of the process. I have a Samsung HDD and downloaded and ran a Samsung Tool for scanning and diagnosing issues with the HDD before boot, oddly my system also shut off shortly into the scanning process.

I scheduled another Windows 7 disk check to run later on and it managed to complete - after looking at the log in windows there were no bad sectors mentioned or anything but it did still say at the end 'Windows has made corrections to the file system.' However my system is still randomly shutting off!

As it managed to shut off during disk checks before the OS loaded, am I right in saying its a hardware issue and not anything software related? I need your help diagnosing what's up with my system soon as I'm about to resume my University studies and need a stable system to work from! Any help at all is greatly appreciated!

Here are my most up to date logs to assist you guys!
View attachment 228695

 

[karlsnooks]

First, you can not rule out software You can not rule out hardware. I wish life was so simple.

Does the samsung disk check program run within windows or do you burn the program to CD and run the program from CD?

 

[Holiday7]

Haha, oh - I also now wish life was this simple!

It's something you download and burn to a CD which you then run at boot. It's something I'd had a while and used a long time ago. It doesn't seem to be prominently documented on Samsung's website no more - it looks to be the 'ES Tool' mentioned here.

When I ran it a long time ago it was on the very same drive to scan for any issues and everything was A-Okay.

 

[karlsnooks]

That the system hung while running a disk test is not a good sign, regardless of your chkdsk results.

On each and every "drive" on your hard disk, run:
chkdsk x: /R

where you substitute the correct letter for X:

Don't worry about capturing the results.

When you are finished, I'll give you a script to run which will give us the info from all chkdsk commands that you have run.

 

[Holiday7]

Cheers for the reply, I'll be in touch again once I'm done

 

[Holiday7]

chkdsk went accordingly, ready to run the script!

 

[karlsnooks]

# STEP 1 ** RUN POWERSHELL AS ADMINISTRATOR
WIN key | type POWERSHELL | do NOT hit ENTER |
in the PROGRAMS list, right-click on WINDOWS POWERSHELL |
choose "Run as administrator" |
Click on the YES button (if such appears)

# STEP 2 ** COPY AND PASTE
COPY the script using CTRL+C,
PASTE into Powershell
---Right-Click at the PowerShell Prompt
---(Ctrl+V does not work)

WIN key = key with Microsoft logo on top

# ************************************************************
# Places CHKDSKLOGS.txt on your DESKTOP
# Results of running chkdsk (check disk) are in ChkDskLogs.txt
# ************************************************************

$obj = new-object -typename psobject
$events = get-winevent -filterhashtable @{logname='application';id=1001,26212,26214} -verbose:$false -ea:silentlycontinue |
where {($_.providername -ne 'Microsoft-Windows-LoadPerf') -and ($_.providername -ne 'Windows Error Reporting')} |
sort-object -property timecreated -desc 
If ($events -eq $Null) {$events = "No check disk logs exist." } ELSE {
$obj = $events | SELECT timecreated, id, message }

$obj | ft -auto -wrap > $env:userprofile\desktop\CHKDSKLOGS.TXT

EXIT
EXIT

# ************************************************************

 

[Holiday7]

Here is the generated log from the script:
View attachment 228774