BSOD - NTFS.SYS Error - help please!

[kb1dqh]

Hi,

I get this error within 1 minute of turning on the computer each time. How can I fix? The computer is less than 5 months old!

Thanks,
jake

 

[zigzag3143]

Hi,

I get this error within 1 minute of turning on the computer each time. How can I fix? The computer is less than 5 months old!

Thanks,
jake

Jake the offending driver is not mentioned but I do see that the Avast drivers eng64.sys is loaded in each. If you are running avast remove it and replace with microsoft security essentials

http://files.avast.com/files/eng/aswclear5.exe

http://www.microsoft.com/security_essentials/

If not run driver verifier to find the offending driver

Beyond that, please run Verifier with these settings:

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/Win7 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"
NOTE: You can use Low Resource Simulation if you'd like. From my limited experimentation it makes the BSOD's come faster.
- 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. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

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:

Delete these registry keys (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

Using Driver Verifier to identify issues with Windows drivers for advanced users


Ken J

 

[kb1dqh]

Ok, I ran disk verifier, rebooted, then the computer crashed again. This time, only a 331 mb memory.dmp was created. Seems too big?

 

[kb1dqh]

Crashed again and got the DMP files. Does this help? Thanks, Jake

 

[kb1dqh]

Also, is there a phone number to reach or is this the only option? Hope to have a computer that works tonight!

 

[Jonathan_King]

Hello Jake,

It seems perhaps the hard drive is the problem. Could you try testing the drive with the DOS version of SeaTools?

| Seagate

I am suspicious of these drivers:

mwlPSDFilter.sys  Tue Jun 02 06:07:30 2009 (4A24F9E2)
mwlPSDNServ.sys   Tue Jun 02 06:07:39 2009 (4A24F9EB)
mwlPSDVDisk.sys   Tue Jun 02 06:15:29 2009 (4A24FBC1)

That belongs to your "Mylocker" encryption program. Could you boot into Safe Mode and uninstall that?

No phone number to call, unfortunately. We are just a volunteer forum; phone service isn't provided here.

...Summary of the dumps:

[FONT=lucida console]
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 26 21:31:17.107 2010 (UTC - 5:00)
System Uptime: 0 days 0:11:20.949
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_VRF_Ntfs!memmove+250
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Debug session time: Sun Dec 26 21:19:05.352 2010 (UTC - 5:00)
System Uptime: 0 days 0:05:03.209
Probably caused by : Ntfs.sys ( Ntfs!memmove+250 )
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x50_VRF_Ntfs!memmove+250
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
[/FONT]

 

[kb1dqh]

Ok, I will try that. Thank you! I didn't realize it was all volunteer until just now. I appreciate it quite a bit.

Jake