NTOSKRNL.EXE - Repeated BSODs - Could use some assistance

[psills]

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.

 

[zigzag3143]

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).

 

[psills]

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

Just crashed on me while typing into IE.

Any additional thoughts I should try?

 

[zigzag3143]

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

 

[psills]

Got it. Here are the new files...

Thanks for the assist!

 

[zigzag3143]

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.

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

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

 

[psills]

First thing I did. No issues.

 

[carwiz]

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. :shock:

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.

 

[zigzag3143]

First thing I did. No issues.

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

 

[psills]

Crahsed Again

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

 

[zigzag3143]

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

Still verified and related to memory corruption.

Any of these old drrivers may be at fault.

These drivers need updating

wacommousefilter.sys    2/16/2007 2:12:17 PM        fffff880`05f0c000    fffff880`05f14000    0x00008000    0x45d5f401                        
SiWinAcc.sys    6/14/2007 8:02:02 PM        fffff880`01414000    fffff880`0141d000    0x00009000    0x4671d6fa                        
SiRemFil.sys    6/20/2007 3:42:10 PM        fffff880`01f97000    fffff880`01f9f000    0x00008000    0x46798312                        
SI3132.sys    10/3/2007 2:39:29 PM        fffff880`0155c000    fffff880`01576000    0x0001a000    0x4703e1e1                        
DDCDrv.sys    4/8/2008 3:50:11 AM        fffff880`0416a000    fffff880`04173000    0x00009000    0x47fb23b3                        
wdcsam64.sys    4/16/2008 4:39:08 AM        fffff880`05e94000    fffff880`05e97880    0x00003880    0x4805bb2c                        
btusbflt.sys    8/27/2008 9:12:08 PM        fffff880`09a00000    fffff880`09a10000    0x00010000    0x48b5fb68                        
000.fcl    9/26/2008 9:11:22 AM        fffff880`04173000    fffff880`0419e000    0x0002b000    0x48dcdf7a                        
adfs.SYS    11/3/2008 12:48:14 PM        fffff880`02c72000    fffff880`02c8a000    0x00018000    0x490f2b4e                        
hardlock.sys    2/2/2009 11:34:08 AM        fffff880`04028000    fffff880`04075c00    0x0004dc00    0x49871270                        
ALSysIO64.sys    4/19/2009 3:41:04 PM        fffff880`09bf5000    fffff880`09bfd000    0x00008000    0x49eb7e50                                                  wacomvhid.sys    5/20/2009 3:53:55 PM        fffff880`049f8000    fffff880`049fa800    0x00002800    0x4a145fd3                        
ADIHdAud.sys    5/21/2009 4:21:06 AM        fffff880`05e00000    fffff880`05e79000    0x00079000    0x4a150ef2                        
iaStor.sys    6/4/2009 9:53:40 PM        fffff880`012d0000    fffff880`013ec000    0x0011c000    0x4a287aa4                        
LHidFilt.Sys    6/17/2009 12:49:39 PM        fffff880`05fcc000    fffff880`05fdf000    0x00013000    0x4a391ea3                        
LMouFilt.Sys    6/17/2009 12:49:43 PM        fffff880`04be4000    fffff880`04bf8000    0x00014000    0x4a391ea7                        
L8042Kbd.sys    6/17/2009 12:50:43 PM        fffff880`04e74000    fffff880`04e7f000    0x0000b000    0x4a391ee3                        
PxHlpa64.sys    6/23/2009 7:16:35 PM        fffff880`0141d000    fffff880`01428e00    0x0000be00    0x4a416253

How To Find Drivers:

- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference Driver Reference
Driver Reference Table (DRT)