BSOD ntoskrnl.exe - Random crashes

[mrblonde321]

For the longest time now I've been getting BSODs and I've never really looked into how to try and fix them. Recently I upgraded my graphics card and PSU which makes me worry that I messed something up while installing the PSU.

I've ran hard drive diagnostics and everything is fine.

I had two Mushkin 991770 RAM sticks but after testing them with MemTest I found one stick gives me errors. I've taken that stick out and am debating on buy new RAM.

I've attached my most recent BSODs, 3 from today and 2 from the past couple of days. If anyone could analyze them and help me try to narrow my systems problems down I would be grateful.

If there's anymore information I should provide let me know.

 

[YoYo155]

Welcome to SF .

Can you please upload the MSINFO32 file?

Start> RUN> "MSINFO32" without the quotes then hit [Enter].
In "MSINFO32" go to, File> Save> name it your user-name and upload.
​

Also I have to ask, did you stop using the bad RAM module?

 

[mrblonde321]

Sorry I thought it put that file in the zip. Yes I removed the faulty RAM and I just have one stick in at the moment.

 

[YoYo155]

Thanks, I only took this month's dumps into consideration,
because you said you had bad RAM and I assumed it was prior to that.

Start by testing the HDD.
Testing the HDD:

1. Perform a Disk Check | http://www.sevenforums.com/tutorials/433-disk-check.html
2. Then Post the results following | THIS METHOD
3. Download SeaTools for Windows if you don't want to use a CD to test the HDD you can use YUMI – Multiboot USB Creator to create a bootable USB (instructions are found at the bottom of both pages).
4. If SeaTools for Windows is unable to recognize your HDD visit HDDdiag and follow the instructions.

If the HDD is passing all the tests follow the tutorial below on how to run the SFC/ Scannow
utility, then upload the results as detailed in OPTION 3.

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Once that is done enable Driver Verifier:

Your crash dumps are not showing any finite probable cause.

Enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

 

[mrblonde321]

I'm having a lot of trouble with pretty much everything you suggested.

1. Disk Check
I enabled a disk check and restarted my computer. The disk check went fine and when everything was finished it logged me back into my computer. However, once I tried to find the file for the disk check it just wasn't there. I tried both methods you gave me but there wasn't a disk check file anywhere.

2. My HDD passed SeaTools. I tried the short and long tests and S.M.A.R.T.

3. SFC /SCANNOW
When I tried to execute that command in CMD it says "Windows Resource Protection could not perform the requested operation."

 

[YoYo155]

OK let's narrow it down.
Perform the disk check following OPTION 2 of the tutorial.
For SFC /Scannow also follow OPTION 2 and make sure you're using an elevated command prompt.
After that post the results and enable Driver Verifier as detailed above .