BSOD's, WhoCrashed says ntoskrnl.exe

Hi guys, PC noob builder here. 3 weeks ago I built up a gaming pc for my son (specs are in my profile for those interested). The build went very well considering it was my first time ever (prior to this my most adventurous attempt inside a case was switching out a bad video card). I used the tutorials from Newegg, and like I said the build & os install went pretty well. Shortly after original install & lots of automatic updates we began getting seemingly random BSOD's which I really couldn't figure out, so I took it to Geek Squad. They had it for several days and tested the crap out of each piece of hardware, could find no problems. Did a new install of the OS there and things are MUCH better, however I am still getting 1-2 BSOD's a day, and almost always overnight as the pc idles. I used Whocrashed, and a long string of crashes are attributed to ntoskrnl.exe:

example: On Sun 4/21/2013 7:43:41 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042113-20202-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x34 (0x50853, 0xFFFFF8800C2AE588, 0xFFFFF8800C2ADDE0, 0xFFFFF80002C81B05)
Error: CACHE_MANAGER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a problem occurred in the file system's cache manager.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

I read the posts on the forum where others experienced similar problems pointing to ntoskrnl.exe, but before I jump in and start changing things I thought I would post my own thread and dump files to see what the experts think is the best way to solve this pesky issue. Thanks in advance, having read a big volume of posts I have to say this forum is completely awesome and the amount & quality of help offered is just fantastic.

If I need to provide any other info please let me know, Dave

[edit] by 'tested the crap out of', I mean memtest and stress tests as well as checking volatges and connections, they really went over it thoroughly and could find no issues.

Hello bunabayashi.

First make it sure that the firmware of SAMSUNG SSD 830 is up to date.
https://www.samsung.com/us/support/o.../MZ-7PC512N/AM

Then scan the system for possible virus infection with the following programs.

• Anti-rootkit utility TDSSKiller
• Windows Defender Offline

Let us know the results. Depending on those we will do the further troubleshooting, if needed.

Also enable Driver Verifier to monitor the drivers, as the crash dumps are not stating anything clearly.
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.

bunabayashi said:

May I ask why you say that the crash dumps are not stating anything clearly? I just would like to understand more

Coz they are not stating anything clearly.

It is expected that the hint about a probable reason is included in the memory dump. It is not present there all the times, and in those situation DV is to be applied.