Windows 7: Ntfs.sys

Chrome · 09 Jan 2010

Hello!
For Christmas I've got a new Computer (a good one too!), never had problems till yesterday.
I booted the pc, everything normal and when he was done with loading stuff, this popped up (http://i46.tinypic.com/9hrgpk.jpg
Then I saw that one partition (yes - only one) on my external hard disk didn't work anymore. In other words, I can't access it anymore (everything on it is gone too) and an error pops up.
I've got bluescreens saying that ntfs.sys is missing or corrupted.
So I started searching the internet and ended up finding always the same resolutions ("Missing or corrupt Ntfs.sys" error message when you restart Windows XP after you convert your hard disk to the NTFS file system) but it won't work.
I tried similar things in safe mode too, but it didn't work either.

Didn't find any resolutions for Windows 7 yet, so maybe you can help me? D:

**Pauly** · 09 Jan 2010

I would try running a system file check, you can do this by
Start>search>cmd.exe>right click run as admin>type sfc /scannow

May need to run more than once if errors are found

Hope this helps

Chrome · 09 Jan 2010

At 12% he stops and says that he found corrupt data but he can't 'repair' them all.

**Pauly** · 09 Jan 2010

Does it tell you whats corrupted? if not check the log/report and post back

Chrome · 09 Jan 2010

There's like 4 errors but I have no idea what the text behind it means.
Maybe you should take a look at the log log

usasma · 09 Jan 2010

The error message refers to NVCPL.DLL - most likely a component of your nVidia video drivers

Go to Welcome to NVIDIA - World Leader in Visual Computing Technologies and download the latest drivers for your computer
Uninstall the current nVidia drivers using Control Panel...Programs...Uninstall a program
Install the freshly downloaded drivers

usasma · 09 Jan 2010

As for the NTFS stuff:

1 - Upload Dump Files:
Please go to C:\Windows\Minidump and zip up the contents of the folder. Then upload/attach the .zip file with your next post.
{Left click on the first minidump file.
Hold down the "Shift" key and left click on the last minidump file.
Right click on the blue highlighted area and select "Send to"
Select "Compressed (zipped) folder" and note where the folder is saved.
Upload that .zip file with your next post.

If you have issues with "Access Denied" errors, try copying the files to your desktop and zipping them up from there. If it still won't let you zip them up, post back for further advice.

If you don't have anything in that folder, please check in C:\Windows for a file named MEMORY.DMP. If you find it, zip it up and upload it to a free file hosting service - then post the link to it.
Then, follow the directions here to set your system for Minidumps (much smaller than the MEMORY.DMP file): Set MiniDump

2 - H/W Diagnostics:
Please start by running these 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)

3 - CHKDSK /R:
Run CHKDSK /R from an elevated (Run as adminstrator) Command Prompt.
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 (Wininit for Windows 7; Winlogon for XP) entry.
Copy/paste the results into your next post.

Chrome · 10 Jan 2010

The NVIDIA message doesn't pop up anymore, so I think it worked. Thanks!

And I did everything you said:
1. Dump Files Zip is in the attachment.
2. Diagnostics
- Memory: no errors
- HD: passed
- Malware scan: 8 Tracking Cookies (apmebf, serving-sys, mediaplex, serving-sys, atlas dmt, doubleclick, metriweb, bluestreak)
3. chkdsk
Tried this 987654676 times before your post with a blue screen (ntfs.sys - stop...) as result. Got the same blue screen this time. But when I boot the pc, he controls C: so I think it's kinda the same. The log file says everything is okay, but I'll put it in the attachments just in case.

usasma · 10 Jan 2010

Quote:

Het bestandssysteem is gecontroleerd. Er zijn geen problemen vastgesteld.

So far, so good!

Running the dump files next....

usasma · 10 Jan 2010

The dump files all point to NTFS.SYS - a component of the Windows operating system that controls the file system on your hard drive.

Please update or remove 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 current drivers:

Quote:

How To Find Updated 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.

Here's the older drivers:

Code:

pssnap.sys   Tue May 20 04:32:36 2008 - Paramount Software Macrium Backup
RimSerial.sys Mon Nov 24 12:02:13 2008 - RIM Virtual Driver (probably associated with a Blackberry)
nvm62x32.sys Fri Oct 17 17:00:39 2008 - nVidia nForce driver (networking component)

Let's give Driver Verifier a try:

Quote:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Summary of the dump files:

Code:

Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Fri Jan  8 11:54:09.339 2010 (GMT-5)
System Uptime: 0 days 0:40:14.993
PROCESS_NAME:  chkdsk.exe
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Fri Jan  8 10:38:51.947 2010 (GMT-5)
System Uptime: 0 days 0:07:16.586
PROCESS_NAME:  explorer.exe
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Fri Jan  8 10:43:31.968 2010 (GMT-5)
System Uptime: 0 days 0:01:21.607
PROCESS_NAME:  chkdsk.exe
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan  9 08:48:25.361 2010 (GMT-5)
System Uptime: 0 days 0:15:08.015
PROCESS_NAME:  chkdsk.exe
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sat Jan  9 10:51:59.543 2010 (GMT-5)
System Uptime: 0 days 2:02:59.198
PROCESS_NAME:  explorer.exe
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Debug session time: Sun Jan 10 09:44:25.219 2010 (GMT-5)
System Uptime: 0 days 1:42:28.873
PROCESS_NAME:  chkdsk.exe
DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

Windows 7: Ntfs.sys

Ntfs.sys problems?