Intermittant BSOD, always ntoskrnl.exe, checked ram, hdd, etc

What's your results of post #20?

Best Regards,
Frederik.

Sptd.sys is removed. That's the good news.

Have you been running SFC /scannow yet?

We usually ask people to do this command to check if Windows is corrupted. It's the most common used one to check if the Windows files are corrupted. If it'll find errors, it'll restore them.

   Tip

If you're having a custom customization layer on your Aero, it's likely to get restored to default.

Press Start | search 'cmd' | Right-click it
| open as Admin | type SFC /SCANNOW

SFC /SCANNOW Command - System File Checker

Best Regards,
Frederik.

computron5000 said:

Yeah I ran that back a few days and it reported no error, I think that was in post #8

I will have a closer look of your setup and system tomorrow. I have school unfortunately, stay tuned.

Best Regards,
Frederik.

computron,

Help us to help you by carrying out:

Update your SevenForums System Specs
User CP (located on the top menu bar) |
Your Profile | Edit System Spec (left-hand column)

To gather info, use Speccy (my favorite) or SIW or System Info

In the System Manufacturer Block, enter:
Ø Manufacturer and Model OR Custom build.
Ø ADD the word laptop, desktop, netbook or tablet.
For example:
Toshiba Satellite L305D notebook.

Provide full windows version info, for example:
MS Windows 7 Ultimate SP1 64-bit

Use the “Other Info” block for Optical Reader,
Mouse, touchpad, wifi adapter, speakers, monitor, etc

Scroll down and click on SAVE CHANGES.

With Speccy, you can select with your mouse/touchpad info from the display
and paste that info into your specs.

SIW is a marvelous program, but the free version does not offer
this capability.

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

After that is finished, since much water has flowed under the bridge, then attach to your next post:
Blue Screen of Death (BSOD) Posting Instructions

thanks,
karl

Oh yes,
If you can't find make & model of your computer, then this will put a file on your desktop with info about your system--file name, MySystem.TXT

# **********************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
# ************************************************************

Script:

$obj = new-object -typename PSobject
$bios = gwmi win32_bios
$cs   = gwmi Win32_ComputerSystem
$CSprod  = gwmi Win32_ComputerSystemProduct 
$os = gwmi win32_operatingsystem
$obj | add-member -membertype noteproperty -name "Operating System" -value ($os.caption + " " + $os.csdversion + " " + $os.osarchitecture) -passthru |
 add-member -membertype noteproperty -name "Computer" -value ($cs.manufacturer + " " + $cs.model + " || " + $csprod.version + " || " + $cs.systemtype) -passthru |
 add-member -membertype noteproperty -name "BIOS Version, date, name" -value ($bios.smbiosbiosversion + "--" + $bios.converttodatetime($bios.releasedate) + "--" + $bios.name) -passthru |
fl > $env:userprofile\desktop\MySystem.txt

EXIT
EXIT 


Keep the faith. I'll be looking at the upload soon.
karl