BSOD, even after new install, error 0x0000050. NTFS.sys problem

Hi all

First of all, thank you! This has been causing a huge amount of stress...

A couple of months ago I experienced a BSOD after installing AVG. I had been having problems with it previously so went down other antivirus roots, but decided to switch back. The problem was consistently shutting down my PC shortly after getting into windows.

I tried a fresh install of Windows 7 and every time it would get to the final stages and then crash. It would then not be able to boot into Windows fully when I re-booted. The error message it was giving was supposedly caused by NTFS.sys with the error code 0x0000050 and that there was a "PAGE_FAULT_IN_NONPAGED_AREA". Online people were suggesting hard-drive and/or memory related problems.

I eventually gave up trying and put it on the back burner for a while as work was picking up. In the meantime I used my fiance's Mac (shudders).

I managed to get hold of a friend's PC to use as a test machine. I installed Windows 7 on my SSD using his system and it worked succesfully (pointing towards it not being a problem with the hard drive). I put it back in mine, activated it and all seemed well for maybe 30 minutes. Then the problem kicked back in again, and it crashed and BSOD'd. Thinking that it might be a memory problem, I swapped a 4GB stick of his over to mine and it still had the same problem. It would BSOD within 5 minutes of getting into Windows. Everything else seemed to be running perfectly and I can run in Safe Mode without any crash.

So yeah, I don't know what is wrong. I am fairly proficient in computer related matters, I built this machine myself and can sort out most problems, but this has me stumped.

Attached is the zip file with all the data in.


If you could help that would be hugely appreciated!
Thanks
Jonny

Hello, jonnycavaciuti and welcome to the forums. I will try to help you with this. I looked at your last 5 or 6 dump files. They did not give any specific indications, but did give us a place to start. They were all the same. Also, thanks for filling out your system specs, not many new members think that is important. Here are the results of your dump files.

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff981149826e8, 0, fffff88001258460, 5}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!memcpy+250 )

Followup: MachineOwner

NTFS is the file system Windows uses. What is going to be the most difficult is checking it. You have an SSD. Most of the tests we have are not made for SSDs. I know, I have 5 in my system. So, please make sure you have the latest Firmware installed on your SSD. I would like you to run Seatools for DOS on your Mechanical Hard drive and check Disk too. If your SSD comes with a Tool Box, please use it and run whatever tests they provide. SeaTools for DOS and Windows - How to Use and Check Disk Disk Check Also, please be sure all of your Windows Updates are current.

It has been said several place that check disk is not good for SSDs, so I never advise people to run it on an SSD. I do run it on mine and have had no bad effects.

Once you have run that, if everything passes, I would like you to run memtest86+. Please download it from the link I give below. It has to be run for a minimum of 8 consecutive passes at a minimum. I suspect with your 12 GB of ram, it will take 12-14 hours. So just start the test one afternoon and let it run overnight. If you receive even 1 error, stop the test, the ram has failed.

Please Run Memtest86+

   Information

Please download from this site only http://www.memtest.org/ in the middle of the page are the Download links, you can download the ISO.zip or the Auto USB Flash Drive installer.zip

Extract the Zip file. If you chose the ISO image, burn it to a CD using Windows Disk Image Burner or any Image burner you may have. If you downloaded the Auto USB installer, extract it, insert your USB 2.0 Flash Drive and take note of the drive letter. Run the installer, select the Flash Drive Letter, check the format box and press next. It will install memtest86+ to a flash drive. You can use either V4.20 or V5.01. Boot from your selected media. If you use V5.01 it will tell you to press certain buttons at the start, please press no buttons. The test will begin on it's own and continue to run until you stop it. It needs to run for 8 complete passes or until you receive an error. If you receive an error, stop the test. Even 1 error is a fail. Each pass tests a different part of the ram and each of the 10 tests in each pass tests something different. It takes a minimum of 8 passes to completely test the ram, more passes are better. It is quite a long test and will take several hours depending on how much ram you have. Due to the time length it is best to run overnight. If you have any questions, please do not hesitate to ask

Also please open an elevated command prompt ( click start, type cmd in the search box, right click on the cmd entry and select run as administrator) in the black box that opens, copy/paste sfc /scannow. If you decide to type it, notice the space between the sfc and the /. It is a system file checker which will scan your system files and attempt to correct any missing or corrupt files. What we want are the results to say windows found no integrity violations. If it says files were found but could not be repaired, close the box, reboot and run it again, after opening the administrative command prompt. You may have to reboot and run it three times for it to repair all system files. If it can't repair them after 3 reboots, let us know.

You can do this in any order you like. The sfc scan will take very little time. If you have any questions, please feel free to ask. I don't mind answering anything. This does not seem to be a typical memory problem. The reason I am asking for the test after testing the hard drive is because of this from the above dump file results.

Code:

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff981149826e8, 0, fffff88001258460, 5}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!memcpy+250 )

Followup: MachineOwner

The NTFS is the file system, but I believe the memcpy is a memory copy operation where it failed. Because all of the files list an NTFS error, I am inclined to think more in lines of a hard drive or file system error. But that memory copy element it could very well be the memory too.