NTOSKRNL.EXE - Repeated BSODs - Could use some assistance

Using WhoCrashed.

Determined BSODs coming from ntoskrnl.exe.

Crashing about once a week, generally at night.

Have run extensive memory tests (MemTest and Windows) with no errors.

Have updated all possible drivers.

Uploading files here in hopes someone can help identify.

Any assistance is greatly appreciated as I can not afford any additional hair loss.

I am a big fan of Nir Sofer's work, BUT blueScreenView more often than not, doesn't point out the correct causes. Similarly Who crashed is even worse.

I prefer to use WinDbg (the Windows Debugging Tools) to read the memory dumps. It is the Gold standard for those of us that do this and often will give us the answer by itself. (we don't need the full jcgriff2 report each time).

Your 3 crashes were caused by memory corruption. Probably because of your 2005 asacpi.sys file. It is a huge cause of crashes. In any case we cant investigate the underlying cause until it is updated.

Asacpi.sys

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (not before).

Installed the updated file as you mentioned, but no dice.

Just crashed on me while typing into IE.

Any additional thoughts I should try?

psills said:

Installed the updated file as you mentioned, but no dice.

Just crashed on me while typing into IE.

Any additional thoughts I should try?

AS always we need the new dmp files. As I said we needed to fix asacpi.sys before we could even begin to look at the underlying cause

Got it. Here are the new files...

Thanks for the assist!

psills said:

Got it. Here are the new files...

Thanks for the assist!

The only verified DMP was the most recent and pointed to an OS driver which you currently are not verifying

I would run a SFC if you havent already.

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

First thing I did. No issues.

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption.

Something is corrupting memory, possibly off the desktop or part of the desktop interface. Or incompatible drivers, even malware. There's a whole slue of old drivers on your system. Knowing your hardware configuration ("My System Specs") would go a long way in helping. Do you have a Microsoft wireless mouse or a web-cam? Multi-function Brother Printer? Adaptech hardware? These and others have drivers as old as 2006. Certainly not Windows 7 drivers.

Running a malware scan wouldn't hurt. Most here agree that MalwareBytes is the best. You can get the free version here. Run the program as administrator, be sure it's updated, then do a full scan.

What was the last piece of hardware or software added to you system? (Before BSODs began.) About the only way to find the culprit with its drivers is to start removing them one by one in reverse order of your installation. That or you can start updating all your drivers for your hardware. Apparently, you have a lot.

psills said:

First thing I did. No issues.

If you are still crashing you need to upload the new DMPs

Crashed this morning. Ran a MalWare scan - nothing...

Here are latest Dumps and files...

Nothing new hardware or software wise I can think of before crashes began. It's been a while since they started - just getting more frequent...