• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win2k pro recovery of ntfs.sys ?

B

boran

Golden Member
lately I'm getting random bluescreens of
PAGE_FAULT_IN_NONPAGED_AREA

indicating a certain piece of memory could not be read (it sais 0x00000000 indicating a read operation)

alongside with the bluescreen it sais ntfs.sys

debugging sites tell me that this error is mostly a faulty dll or system file (which ntfs.sys is) that has to be reïnstalled, now, is there any way to replace ntfs.sys with it's original without a format C ?

The strange thing is my OS works fine 90% of teh time, it boots okay, it handles okay, just at really random moments, not under high stress even or so, it crashes...

I was thinking about the recovery console, but then I would need to know what commands to use.

thanks for any suggestions.

 
test the ram, sounds like it could be bad hardware


its not overclocked right? got a good power supply? (big enough and decent brand?)
 
abztrak, chances of it being hardware is nil, a reinstall I did on second harddisk (swapped 1st and second) prooves this, it is related to the current install, some faulty files or so :S
cant seem to find a way to fix it, will have to use the shotgun approach (formatC)
 
The chances are almost 100% that the problem is not ntfs.sys itself. NTFS is used by millions and millions of customers and the likelihood of you discovering a bug in ntfs is very, very low.

Far more likely is that another driver is passing bad data to NTFS and NTFS is blowing up as a victim of this bad data. Drivers such as antivirus drivers, quota management drivers, open file backup agents, realtime disk mirroring, etc, are all likely candidates. If you have any drivers such as these, ensure you're running the latest versions.

Set your machine up for a kernel or complete dump if you have not done so already (control panel, system, advanced, startup and recovery).

 
Short of reinstalling you could also try a repair install which will replace all system files on your disk with the versions on the cdrom. Keep in mind if you have applied a service pack this will effectively uninstall it. You could also boot into recovery console by booting off of the cd and choosing repair by recovery console. Once logged in you can extract the ntfs.sys file and copy it (after renaming your current ntfs.sys to ntfs.old or something) to the correct spot on your hard drive.

Keep in mind with the recovery console you can only copy to the system, not copy from it (security issues). At any rate, there is the information you wanted. Most of all of the problems with windows NT, 2000, XP, and 2003 are caused by faulty drivers.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top