Windows Stop error

Promilf · January 19, 2017

Hey,so my computer suddenly got a blue screen. The computer was running fine, then I went and took a shower and came back to the computer not reacting to anything and the screen was completely black. I then restarted the computer and when windows was about to boot I get a blue screen.

The message says:

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

A problem has been detected and windows has been shut down to prevent damage to your computer.

Ntfs.sys

PAGE_FAULT_IN_NONPAGED_AREA

If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed if this is a new installation, ask your hardware or software manufacturer for any windows updates you might need.

If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing if you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select advanced startup options, and then select Safe Mode.

Technical information:

***STOP: 0x00000050 (0xFFFFF98001880000, 0x0000000000000000, 0xFFFFF88001c52355,0x0000000000000000)

*** Ntfs.sys - Address FFFFF88001c52355 base at FFFFF88001c47000, Datestamp 4a5bc14f

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Now I don't have much knowlage with computers so I have no idea what to do, I started with taking out the RAM, and put in some new ones that I borrowed from a friend to check if it was the RAM that was the problem, still nothing. I then figured I would try to install Windows on my HDD, so i started disconnecting my SSD and installing windows on my HDD, and everything worked well. It booted up as it should and I figured I might try to plug the SSD back in, so I turned off my computer, plugged the SSD back in. Then I went into the BIOS to make sure it booted from the HDD. And then I got the bluescreen again when trying to boot Window.

A little side note, the SSD and Graphics card was installed about a month ago and has worked perfectly untill last night, also I have turned off all auto updates on my software for motherboard, graphics card, etcetera.

My specs:

*HyperX Savage 240GB 2.5" SSD

*Seagate Barracuda 3TB 3.5'' HDD

*ASUS ROG Crosshair V Formula-Z, S-AM3+

*AMD FX-8300 Black Edition

*Crucial BallistiX Sport DDR3

*Cooler Master Nepton 240M CPU cooler

*ZOTAC GeForce GTX 1070 Founders Edition

*Windows 7 Ultimate edition

*Silent Pro M2 520W

Mira Yurizaki · January 19, 2017

That error is usually caused by one of these things:

RAM has had an issue. However it can also mean the CPU's cache hiccuped (which is very rare) or VRAM hiccuped (which also tends to be rare)
One of your drivers is bad. But since it said ntfs.sys was the problem, it's probably not a driver.
A corrupted system volume.

Since it flagged ntfs.sys as the problem program, it may mean the system volume had problems. So either reinstalling Windows (the nuclear option) or issuing an sfc /scannow command in a recovery environment should help.

If this is the first time you've seen this, then I wouldn't worry about it too much unless you start getting it more.

Promilf · January 19, 2017

6 minutes ago, M.Yurizaki said:

That error is usually caused by one of these things:

RAM has had an issue. However it can also mean the CPU's cache hiccuped (which is very rare) or VRAM hiccuped (which also tends to be rare)

One of your drivers is bad. But since it said ntfs.sys was the problem, it's probably not a driver.

A corrupted system volume.

Since it flagged ntfs.sys as the problem program, it may mean the system volume had problems. So either reinstalling Windows (the nuclear option) or issuing an sfc /scannow command in a recovery environment should help.

If this is the first time you've seen this, then I wouldn't worry about it too much unless you start getting it more.

Should the RAM be a problem when I have tested with my friends RAM, he got the same bricks as me, I put them in the same slots as mine used to be, should I try put it in the two other unused RAM slots. and I was trying to re-install windows on the SSD but when it boots up the download thing it goes straight to the bluescreen, same as when I try booting normaly. And also this happends everytime I turn on my computer, so no it's not the first time. And if I wanted to re-install windows how can I do it?

Mira Yurizaki · January 19, 2017

2 minutes ago, Promilf said:

Should the RAM be a problem when I have tested with my friends RAM, he got the same bricks as me, I put them in the same slots as mine used to be, should I try put it in the two other unused RAM slots. and I was trying to re-install windows on the SSD but when it boots up the download thing it goes straight to the bluescreen, same as when I try booting normaly. And also this happends everytime I turn on my computer, so no it's not the first time. And if I wanted to re-install windows how can I do it?

This sounds more like a hardware issue then, so I would start with RAM and run memtest86+ to check for errors