NTOSKRNL.EXE is the kernel (core) of the Windows Operating System. If it was at fault, you'd have a lot more problems other than an occasional BSOD. Most likely there's a 3rd party driver passing bad stuff to NTOSKRNL.EXE - which causes it to crash.
There is one crash dated 23 Jan 10. Prior to that, the next most recent one is dated 21 Dec 09 - over a month prior.
Have there been any other BSOD's between those 2 dates?
The latest BSOD points to memory corruption, so I'd suggest running these tests first:
Quote:
H/W Diagnostics:
Please start by running these
bootable hardware diagnostics:
Memory Diagnostics (read the details at the link)
HD Diagnostic (read the details at the link)
Also, please run one of these free, independent online malware scans to ensure that your current protection hasn't been compromised:
Malware (read the details at the link)
Summary of the latest BSOD:
Code:
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Jan 23 07:47:03.585 2010 (GMT-5)
System Uptime: 0 days 0:46:55.664
BugCheck A, {cb004b2c078, 2, 1, fffff80002ee1b74}
Probably caused by : memory_corruption ( nt!MiUnlinkFreeOrZeroedPage+1ca )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: MsMpEng.exe