Where did you get the reference to NTFS.sys? If it's valid, then try the following:
CHKDSK /R /F:
Run CHKDSK /R /F from an elevated (Run as adminstrator) Command Prompt. Please do this for each hard drive on your system.
When it tells you it can't do it right now - and asks you if you'd like to do it at the next reboot - answer Y (for Yes) and press Enter. Then reboot and let the test run. It may take a while for it to run, but keep an occasional eye on it to see if it generates any errors. See "CHKDSK LogFile" below in order to check the results of the test.
Elevated Command Prompt:
Go to Start and type in "cmd.exe" (without the quotes)
At the top of the Search Box, right click on Cmd.exe and select "Run as administrator"
CHKDSK LogFile:
Go to Start and type in "eventvwr.msc" (without the quotes) and press Enter
Expand the Windows logs heading, then select the Application log file entry.
Double click on the Source column header.
Scroll down the list until you find the Chkdsk entry (wininit for Win7) (winlogon for XP).
Copy/paste the results into your next post.
and
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)
The Microsoft Symbol Server doesn't recognize your OS kernel - this means that the Windows Debugging Tools aren't able to access symbols for your operating system files (in particular NTOSKRNL.EXE / NTKRNLMP.EXE / NTKRNLPA.EXE / NTKRPAMP.EXE) from the Microsoft Symbol Server - so that makes debugging them difficult if not impossible.
Please do the following:
- activate/validate the Windows installation at
Genuine Microsoft Software
- run sfc.exe /scannow to replace any problem files
- If that doesn't fix it, then wipe the hard drive and reinstall Windows
- don't use "leaked"/torrent builds
Also, please remove or update these older drivers that were loaded at the time of the crash.
Don't use Windows Update or the Update drivers function of Device Manager.
Please use the following instructions to locate the most currently available drivers to replace the one's that you uninstall
OR remove:
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 manufacturer links are on this page:
http://www.carrona.org/drvrdown.html
Here's the older drivers. Please pay particular attention to any dated
2007 or earlier:
Code:
adfs.SYS Mon Nov 03 11:48:14 2008 - Adobe File System - http://www.carrona.org/dvrref.html#adfs.SYS
pstrip64.sys Wed Apr 14 08:07:40 2004 - Power Strip - http://www.carrona.org/dvrref.html#pstrip64.sys
Rtnic64.sys Mon Mar 31 01:39:38 2008 - Realtek Ethernet NIC driver - http://www.carrona.org/dvrref.html#Rtnic64.sys
SscRdCls.sys Fri Nov 16 14:59:09 2007 - Ram Disk by SuperSpeed - http://www.carrona.org/dvrref.html#SscRdCls.sys
Summary of the BSOD:
Code:
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Debug session time: Fri Mar 12 02:13:32.441 2010 (GMT-5)
System Uptime: 0 days 0:16:58.408
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
BugCheck C2, {7, 1097, 509040f, fffff8a0129dcc60}
Probably caused by : ntoskrnl.exe ( nt+689c0 )
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
