Windows 7 will run for a while and then crashes (BSOD)

[karlsnooks]

mojocharborn,

There are many possible causes of your problem.

One of them is temperature. One way of keeping an eye on your temperatures is to install SPECCY, minimize SPECCY and occasionally glance at it to see if temps are reasonable. The temps when you first start will be in order.

One possible source is an out-of-date driver. To spot if any drivers are perhaps in need of an update, then the NirSoft Driver View program is excellent DriverView: Loaded Windows Drivers List
Near the bottom of that web page is the download link.
Run DriverView, in the header row click on Modified Date

At the top of the list now, in a different color will be your older drivers.

If you would like you can "select" those items and use File | Save to save as a txt file.

You may upload that file if you would like for me to look at the file.

=========================================================
=========================================================

I'm going to give you a script which your can run to put the last 100 critical and error events into a TXT file.

Not all error events are anything to worry about, but some are.

All Critical events are cause for concern.

I would like for to upload the TXT file that the script puts 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
# ************************************************************

# ************************************************************
# Places CRITICALandERROREVENTS.TXT on your DESKTOP
#
# Displays 100 most recent critical and error events in a Grid View
# Writes 100 most recent critical and error events to CriticalAndErrorEvents.txt
#
# Change the $MAX value for more or fewer events
# Change the $Lwidth value to 254 for example for longer lines
# **********************************************************

$MAX = 100
$LWidth = 132
$a = Get-WinEvent -FilterHashtable @{logname='*';  level=1,2} `
-max $MAX  -verbose:$false -erroraction:silentlycontinue |
sort-object -property `
@{expression="level";Descending=$false}, `
@{expression="timecreated";Descending=$true} |
select-object -property leveldisplayname, timecreated, ID,  Message 
# $a | out-gridview -Title "Critical and Error Events"
$a | format-table  @{Label = "Level"; Expression =  {$_.leveldisplayname} }, timecreated, ID, Message -wrap -auto |
out-file $env:userprofile\Desktop\CRITICALandERROREVENTS.TXT -width $Lwidth

EXIT
EXIT

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

========================

 

[Layback Bear]

When you remove those check marks from msconfig you should reboot and then check the setting (check marks)
again. Them should be as you left them if you have administrator privileges. Are you the administrator?
This might help. From the cmd/prompt/admin type sfc /scannow run this 3 times boot after each.
What this is. It's Windows 7 way of checking it's own System Files and repairing them if it can. Can't hurt but could help.

 

[Layback Bear]

Sorry karl, my pages for this trend are loading crazy and I missed your post until now.

 

[mojocharborn]

Criticalanderrorevennts log file

Here is the log file.

Note: I have not had a crash since July 25.

 

[karlsnooks]

mojocharborn,
I'd appreciate the list of old drivers as explained here:

One possible source is an out-of-date driver. To spot if any drivers are perhaps in need of an update, then the NirSoft Driver View program is excellent DriverView: Loaded Windows Drivers List
Near the bottom of that web page is the download link.
Run DriverView, in the header row click on Modified Date

At the top of the list now, in a different color will be your older drivers.

If you would like you can "select" those items and use File | Save to save as a txt file.

 

[mojocharborn]

Driver List

The older drivers did not sort at the top in a different colour when I clicked "Modified Date". I copied the entire output to a text file. There are rows that are pink. I could select those only and copy them to a file if you wish.

Thanks,

 

[karlsnooks]

mojoborn,
True, at the very top are some entries with no coloring. Those can be ignored. They are oK. The ones that I want follow immediately thereafter and in a pink color.

Guess in the future, I'll ask people to use the CSV format capabilities of the program, because then I can always sort to my heart's content.

Yes, post a file back with only the entries in pink.

 

[mojocharborn]

driver list

Here are all of the listed drivers that were in pink rows

 

[karlsnooks]

thanks.

 

[karlsnooks]

mojocharborn,
Well, this has been a learning experience for me.

Best is going to be that you carry out this procedure will save the results of DriverView as a CSV file.

Rename the file to have a .TXT extension since SevenForums doesn't handle CSV files.

Upload and when I download, I'll rename to a .CSV extension and view the view in Excel.

Here's the procedure:
SAVE THE OUTPUT OF DRIVER VIEW AS A CSV FILE
§ In Windows Explorer, Shift + right-click on your DriverView folder
§ Click on Open Command Window here
§ type DriverView /scomma %userprofile%\Desktop\Drivers.csv and hit Enter
§ Type EXIT and hit Enter

You now will have an icon on your desktop for Drivers.csv

 

[mojocharborn]

drivers csv file

here you go.

 

[karlsnooks]

What happened to the rest of the entries?

 

[karlsnooks]

Forget it. After looking at the event logs, then:

Run check disk over all of your drives.

Perform a clean install http://www.sevenforums.com/tutorials/219487-clean-reinstall-factory-oem-windows-7-a.html#post1839164

 

[mojocharborn]

clean reinstall...

Thanks for your help.

I assume that this will take a while. Correct?