Author Topic: a filesystem causing a bsod (paged fault in a non-paged area)  (Read 8075 times)

0 Members and 1 Guest are viewing this topic.

Offline garegin

  • Jr. Member
  • **
  • Join Date: Nov 2014
  • Posts: 85
  • Karma: 1
    • View Profile
Hi

A volume on the HDD pulled from a computer causes the computers to crash when you connect it to them. the error is

"paged fault in a non-paged area ntfs.sys "
I can't fix the filesystem, because connecting it causes a BSOD to the host's OS. have any idea how I can get around this?

P.S. The HDD doesn't do this in Linux or Mac. Obviously I can just copy the files in Linux/Mac and then redo the OS. But I want to preserve the OS, if possible

Offline jraju

  • Hero Member
  • *****
  • Join Date: Feb 2013
  • Posts: 2323
  • Location: india
  • Karma: 17
    • View Profile
Re: a filesystem causing a bsod (paged fault in a non-paged area)
« Reply #1 on: May 17, 2015, 10:38:34 pm »
Hi, How many ram sticks you have. Please try to boot with one and check if the problem persists.
                 If it is not fixed, try memtest and if it fails , there may be a need to change the ram. Mostly ram problem.
The Bottom line is "Check your hardware first if it supports the task you try".

Offline garegin

  • Jr. Member
  • **
  • Join Date: Nov 2014
  • Posts: 85
  • Karma: 1
    • View Profile
Re: a filesystem causing a bsod (paged fault in a non-paged area)
« Reply #2 on: May 18, 2015, 07:10:23 am »
the problem is from the filesystem. It does the same when you pull the HDD and connect it to another machine.

Offline garegin

  • Jr. Member
  • **
  • Join Date: Nov 2014
  • Posts: 85
  • Karma: 1
    • View Profile
Re: a filesystem causing a bsod (paged fault in a non-paged area)
« Reply #3 on: May 18, 2015, 08:29:13 am »
ok I found the solution. You have to force the OS to check the volume before it mounts it.

http://www.retosphere.de/tipsandtricks/ntfserror.php

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: a filesystem causing a bsod (paged fault in a non-paged area)
« Reply #4 on: May 18, 2015, 02:41:11 pm »
ok I found the solution. You have to force the OS to check the volume before it mounts it.

http://www.retosphere.de/tipsandtricks/ntfserror.php

Glad you found the fix, basically the file system is so shot on that drive that when the Windows driver goes to access it, it kills the system. So checking the drive before Windows loads is the way to go :wink:

Shane

Offline jraju

  • Hero Member
  • *****
  • Join Date: Feb 2013
  • Posts: 2323
  • Location: india
  • Karma: 17
    • View Profile
Re: a filesystem causing a bsod (paged fault in a non-paged area)
« Reply #5 on: May 19, 2015, 05:43:27 am »
Hi, garegin,
                     Wonderful solution you found and rectified your system. But the knoppex link is not in english. Would you point the english link of  the program. What could not be accomplished with some of the best tools could be solved easily by simple and that too free tool. I have not heard about this solution. Thanks. I experienced bsod couple of times, the solution is only reinstall. I will try this tool. it corrects the ntfs in non bootable mode. wow. The link is not in english and the subsequent link reads number of files or folders, which is the file to be downloaded for the fix for windows
                                       
« Last Edit: May 19, 2015, 05:54:06 am by jraju »
The Bottom line is "Check your hardware first if it supports the task you try".

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: a filesystem causing a bsod (paged fault in a non-paged area)
« Reply #6 on: May 19, 2015, 06:51:09 am »
The link displayed for me in English.

You could try changing your location from the Control Panel settings but right click in the text area and see if Translate with Bing does anything for you, JR.