Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD's, WhoCrashed says ntoskrnl.exe

22 Apr 2013   #1
bunabayashi

Windows 7 Home Premium 64 bit
 
 
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.


My System SpecsSystem Spec
.
22 Apr 2013   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
Let us know the results. Depending on those we will do the further troubleshooting, if needed.
My System SpecsSystem Spec
22 Apr 2013   #3
bunabayashi

Windows 7 Home Premium 64 bit
 
 

Thanks for the quick reply, I'm on it
My System SpecsSystem Spec
.

22 Apr 2013   #4
bunabayashi

Windows 7 Home Premium 64 bit
 
 

SSD firmware is up to date, TDSSKiller didn't find anything, going to run the Windows Defender Offline later today.
My System SpecsSystem Spec
22 Apr 2013   #5
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
22 Apr 2013   #6
bunabayashi

Windows 7 Home Premium 64 bit
 
 

Thank you, I will do that also overnight.
My System SpecsSystem Spec
22 Apr 2013   #7
bunabayashi

Windows 7 Home Premium 64 bit
 
 

May I ask why you say that the crash dumps are not stating anything clearly? I just would like to understand more
My System SpecsSystem Spec
22 Apr 2013   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

Quote   Quote: Originally Posted by bunabayashi View Post
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.
My System SpecsSystem Spec
23 Apr 2013   #9
bunabayashi

Windows 7 Home Premium 64 bit
 
 

all right, no worries

running DV now, Windows Defender Offline found no problems in full scan
My System SpecsSystem Spec
23 Apr 2013   #10
MrDismal

Windows 7 Home Premium 64bit
 
 

Hi bunabayashi, just like to say I'm seeing a similar issue with my PC. I actually just posted up a post about 30 mins ago you'll see it in the list. I'll keep an eye on this thread.
My System SpecsSystem Spec
Reply

 BSOD's, WhoCrashed says ntoskrnl.exe




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD Regularly WhoCrashed says ntoskrnl.exe Driver Power State Failure
Hello All, I believe the problem is the result of ntoskrnl.exe because WhoCrashed crash dump analysis says... This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0) Bugcheck code: 0x9F (0x3, 0xFFFFFA800A35EA10, 0xFFFFF80000B9C518, 0xFFFFFA8010D8CCA0) Error:...
BSOD Help and Support
Multiple BSOD different reasons acording to WhoCrashed
Hello guys! New here so don't be harsh. I need some help with my laptop. I'm getting BSOD errors since I start using my 2nd screen. I think it over heats. That's just my theory. So who can help me understand my dump files and how can I upload them or something like that? :) I'll be...
BSOD Help and Support
BSOD problem + screenshots (bluescreenview, whocrashed) pls help!
Hey guys, Recently my (relatively new) PC, has been crashing multiple times a day, for no apparent reason, giving a blue screen of death. Usually the main error is IRQL_NO_LESS_OR_EQUAL, but this also varies sometimes to MEMORY_MANAGEMENT or NTFS_FILE_SYSTEM. Some research showed me that it...
BSOD Help and Support
BSOD - whocrashed points to cdd.dll and kernel
Hi. Thank you all for your help. My computer has been getting BSOD memory dump errors for a couple of weeks now and I have tried many tools to pin down the error but at this point I need some expert guidance. Steps I've taken so far: Booting to safe mode and restoring to an earlier...
BSOD Help and Support
BSoD while playing Saints Row IV. WhoCrashed claims ntoskrnl.exe
I am having issues with BSoD crashes while playing Saints Row IV, it happens randomly during play time, anywhere from as soon as I try to open up the first menu, to while I'm randomly running across the map, to the very end of a cut scene. I've tested both my OS SSD, and the HDD that the game is...
BSOD Help and Support
Randoms BSOD since ~1 week. WhoCrashed - ntoskrnl.exe and ntkrnlmp.exe
Hello there, After browing the Internet for about 5 full days and still getting my BSODs, I'm creating this thread because of how desperate this is making me. I've tried formating and reinstalling Windows three times, with two different boot ISOs. The second seemed to worked better than the...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 01:54.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App