Multiple BSOD's. "ntoskrnl.exe" in each dump. Unsure.

Hi SevenForums,

I've had this computer for almost two years, with only one other glaring issue that was related to a faulty HD.
However, over the past few days there have been several issues with the computer, the most serious of which were a series of BSOD's.
Two days ago, my computer would constantly disconnect from the internet for seconds at a time; causing Skype to reload, Chrome to hang, and Dota2/Steam to disconnect. This happened quite often; once every fifteen to thirty minutes. Several minutes past midnight, while listening to music, the first BSOD occurred.
The next night, while the computer was idling with the monitor off, it automatically restarted. Upon turning the monitor on, I caught the last few seconds of a BSOD. This very day I've suffered two BSOD's, both of which happened while listening to music, which would stutter and repeat before the computer died. Interestingly enough, the last half second of the song continued to repeat all through the BSOD, before the computer restarted.
Each BSOD has happened closer and closer together. The initial two were around 24 hours apart, each happening several minutes after midnight. The two today happened at noon, and 3pm.

I've downloaded BlueScreenView, even though I've heard it's not the best software to use, I'm a novice at troubleshooting. Each dump I scanned mentioned "ntoskrnl.exe" as having an issue. I don't know what to make of this, and I don't have a backup computer to work with.
I'm currently in safe mode with networking, and haven't crashed yet.

The only change I've made to my computer recently was moving the room it's located in, and plugging in two new studio-monitor speakers, though the speakers were attached after the first BSOD two days ago, so I can't be sure.

Attached below are the .dmp files, and the SevenForums Diagnostic Dump.
Thank's for your help, and I hope it's a very obvious and easily-solvable issue.

I'm going to run SFC while I wait for the feedback that hopefully arrives.

EDIT #1 - 5:05 PM - SFC failed. Verified up to 94% then gave the error "Windows resource protection could not perform the requested operation." Attempting again.
EDIT #2 - 5:10 PM - SFC ends. Was unable to solve any problems. Dumped a CBS file, which I have just uploaded and attached.
EDIT #3 - 5:15 PM - Attempted to run SFC a third time. Caused a BSOD the instant SFC initiated. I've updated the attachment with the .dmp files. "020213-11169-01.dmp" is the most recent file. Once again, BlueScreenView highlighted "ntoskrnl.exe." I'm a little scared to do anything else.

Welcome to SevenForums.

Crashes seem to be all over the place.

Code:

"Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3502

If you are overclocking any hardware, STOP. Reset any changed values back to default.

What antivirus software do you use? I see none.

Make scans with the following:

-Kaspersky TDSSKiller

• Anti-rootkit utility TDSSKiller

-ESET online scanner

• Free Online Virus Scanner | ESET

Microsoft Security Essentials.

Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-

• Microsoft Security Essentials - Free Antivirus for Windows
  
  • Malwarebytes : Malwarebytes Anti-Malware removes malware including viruses, spyware, worms and trojans, plus it protects your computer
    
    • Good and Free system security combination.
    • How to Scan Your Computer With Multiple Antivirus Programs - How-To Geek
    
    
  
  

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Run a full scan with both (separately) once downloaded, installed and updated.

Upload a screenshot of your hard disk using CrystalDiskInfo:

• CrystalDiskInfo - Software - Crystal Dew World
• Screenshots and Files - Upload and Post in Seven Forums

Make a hard drive test from the hard drive manufacturers website:

• Hard Drive Diagnostic Procedure

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• Disk Check

Reduce items at start-up. Nothing except anti-virus is required plus improves the time for logging in windows.

• Startup Programs - Change
• Troubleshoot Application Conflicts by Performing a Clean Startup

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

If Memtest86+ does not find any errors with ram run Windows Memory Diagnostics for 7-8 passes following its tutorial: Memory Diagnostics Tool
Let us know the results.

Hi koolkat77,

Starting from the top:
I haven't overclocked my computer to my knowledge; I'm not even sure how to. However whenever I load up the BIOS configuration screen on boot, I see it's often running in "Enhanced Mode" which might change the clocking speed, it seems to default to this every now and then.
I've never noticed the speed getting so high as 3502, though.

I haven't been running any AV software since I uninstalled Avast several weeks ago. I'll be installing MSE after these scans complete.
I've run TDSSKiller with no results.
ESET is currently scanning.
Last time I attempted a Malware Bytes scan (I haven't accepted the Pro trial) I got a BSOD partway through.
I'll try again after ESET completes.

Crystal Disk Info:
Attachment 253474
"Good Health" it said.

I've got Memtest, and the Seatools diagnostics tools burnt to CD's. I'll run those after ESET finishes scanning.

Thanks again for your help. I'll keep everyone updated.
It's never anything simple, is it?

EDIT #1 - 12:03 PM - I am unable to modify startup files as I'm in safe mode; running too long in normal mode causes BSOD's.

EDIT #2 - 12:27 PM - ESET completed the scan. 3 files were found and deleted, though each of them seemed to be adware. One was CrystalDiskInfo, so that shouldn't have been responsible since I downloaded it an hour ago. Attempting MBAM now.

EDIT #3 - 3:22 PM - MBAM completed a scan, finding 3 other files. These had been on my system for a long time, however. Still deleted. Seatools diagnostics turned up no major issues either.
I've unplugged all peripherals except for mouse and keyboard, I'll run a checkdisk and memtest tonight overnight.
I can't be sure what caused the crashes before. I'll just wait until they happen, or don't, then I'll post another update.
Thanks again. Even if I didn't find an obvious issue, it's soothing taking steps to resolve an issue, and comforting to know people are willing to help.

Thanks for the update.

Look forward to the results.