Blue Screen While Windows 10 booting up

Toggle sidebar Toggle sidebar
J

Justforcause

Member
May 12, 2014
107
5
81
Hey all,

I have a pretty new PC (last friday) and today when I turned on my computer. I got a message. Unfortunatelly I cannot exactly say what is was coz before I could read it all my computer restarted and booted up just fine.

The screen was blue with white text saying something that: Nonlanding_page... NTFS or something like that and that my computer is trying to fix the problem and loading was counting up to 100% adn then restart.

So i would appreciate your help telling me what it possibly was and what might be the problem?

Thank you very much all.
 
LTC8K6

LTC8K6

Lifer
Mar 10, 2004
28,520
1,576
126
"Page Fault in Nonpaged Area" perhaps?

If it fixed itself, I wouldn't worry about it.
 
J

Justforcause

Member
May 12, 2014
107
5
81
LTC8K6 said:
"Page Fault in Nonpaged Area" perhaps?

If it fixed itself, I wouldn't worry about it.
Click to expand...

Well what I really remember was the abbreviation ntfs mentioned in the text. But what u propose sounds like it was that. Not sure if it's fixed though. Althought I restarted and even turned off and turned on the pc again and nothing came up. So is the system really capable of fixing the issue itself?
 
LTC8K6

LTC8K6

Lifer
Mar 10, 2004
28,520
1,576
126
Justforcause said:
Well what I really remember was the abbreviation ntfs mentioned in the text. But what u propose sounds like it was that. Not sure if it's fixed though. Althought I restarted and even turned off and turned on the pc again and nothing came up. So is the system really capable of fixing the issue itself?
Click to expand...

Yes, it would be an NTFS.sys error, I believe.

Windows is capable of fixing lots of errors by itself.

Unless it happens again, I'd let it go.

If it's something like a RAM problem, it will happen again, and then you can diagnose it.
 
J

Justforcause

Member
May 12, 2014
107
5
81
here is my setup:

CPU Intel Core i5-6500
MB MSI B150M NIGHT ELF
Case SilentiumPC Gladius M45W
PSU CORSAIR RMx Series RM550x
HDD SSD Samsung 850 EVO, 2.5"
COOLER SilentiumPC Spartan 3 LT HE1012
RAM CRUCIAL 2x8GB DDR4 2133MHz
VGA nV GIGABYTE GV-N960WF2OC-4GD
 
J

Justforcause

Member
May 12, 2014
107
5
81
Actually I wasn't. Now I do. I just updated them. However, I was told by a friend that it is not always wise to go for the latest drivers as they might not be stable.
 
nerp

nerp

Diamond Member
Dec 31, 2005
9,867
105
106
Well, that advice is often true but video cards are one item I tend to recommend people update more often than not. If anything, always run the latest WHQL version. Avoid beta drivers, I suppose.
 
J

Justforcause

Member
May 12, 2014
107
5
81
Hey guys it did it again. But this time different error showed up. See the screenshot please. http://postimg.org/image/s7criy6pt/

It says: PAGE_FAULT_IN_NONPAGED_AREA

What it seems to me is that it only occurs when Windows is being updated. Not sure though! Is it possible? Or what may be the cause of this error?
 
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Unfortunately, I have no idea what those blue screens are saying. You really need to find out what it in those minidump files.

WhoCrashed is a great program for this, and their free program can be quite helpful. Paste the results here after you run it.
http://www.resplendence.com/downloads
 
J

Justforcause

Member
May 12, 2014
107
5
81
Thanks alot. Here is the analyses of all the dump files:

On Thu 12.05.2016 16:24:08 GMT your computer crashed
crash dump file: C: \Windows\Minidump\051216-3921-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFullDeleteLcb+0x47)
Bugcheck code: 0x50 (0xFFFFC00159832478, 0x0, 0xFFFFF8008B974E89, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C: \Windows\system32\drivers\ntfs.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Thu 12.05.2016 16:24:08 GMT your computer crashed
crash dump file: C: \Windows\memory.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsFullDeleteLcb+0x47)
Bugcheck code: 0x50 (0xFFFFC00159832478, 0x0, 0xFFFFF8008B974E89, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C: \Windows\system32\drivers\ntfs.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 11.05.2016 15:43:44 GMT your computer crashed
crash dump file: C: \Windows\Minidump\051116-3703-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!TxfDeleteTxfFo+0xF)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF800DE7D383F, 0xFFFFD0002584C5A8, 0xFFFFD0002584BDC0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C: \Windows\system32\drivers\ntfs.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 09.05.2016 16:12:35 GMT your computer crashed
crash dump file: C: \Windows\Minidump\050916-3484-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS!NtfsDeleteScb+0x34D)
Bugcheck code: 0x50 (0xFFFFC0005703BEDC, 0x0, 0xFFFFF800266AD36D, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C: \Windows\system32\drivers\ntfs.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: NT File System Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Sat 07.05.2016 5:09:17 GMT your computer crashed
crash dump file: C: \Windows\Minidump\050716-5828-01.dmp
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltReleaseFileNameInformation+0xAB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF803E3CB59BC, 0xFFFFD00023C270C8, 0xFFFFD00023C268E0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C: \Windows\system32\drivers\fltmgr.sys
product: Operační systém Microsoft® Windows®
company: Microsoft Corporation
description: Microsoft Filesystem Filter Manager
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
 
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Thanks for posting those. The weird part is that you are getting two different errors, neither one of which will point to a specific driver.

Makes things a little harder, but it is what it is.

Memtest: it's a mixed bag in my book. I have seen people find the problem anywhere between 10 minutes and 10 hours using this method. What I like to tell people: run each stick individually and see if you get the crash with both sticks.

If you do, it's on to drivers. Aside from the video card, which you mentioned, where did the drivers for your system come from.

I have also seen tune-up utilities and AVs with such "free" software also getting in the way. If you have anything like that, get rid of it.

Is it fair to say that the blue screens are getting more frequent than they were when you first posted? If so, I am almost tempted to lean towards it being a memory problem.

If you are still stuck, see if you can link the blue screen to anything specific you were doing on the PC at the time, and look to see if the dumps show any different information.
 
J

Justforcause

Member
May 12, 2014
107
5
81
Thanks for help. Ill try what u propose after i get back from work. Meanwhile, everytime i got the bsod was when my windows were being updated, cannot say with certainty but i have a feeling that it was always when an update took place. Also it happens when i boot up the pc first time in the day, not during my session of playing, browsing etc. Always the first boot. Regarding frequency, nope cannot say, i have the pc since last friday, since then these five errors.
The rig was build by a conpany with the drivers pre-installed so i have no idea about the drivers but i suppose are those which come with the CDs.
 
Last edited:
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
That is very helpful info.

First off, the Windows update. Windows 10 might be trying to install a new driver, and that may be the cause of (at least some of) your problems. To turn off this particular feature, type 'device installation settings' into Cortana and set it to 'no'.

Secondly, did the people who built it offer you any type of warranty? If they are installing things for you, they should have some type of warranty on their service. It would be silly for them to charge you money and give you a computer that doesn't work right out the door.
 
J

Justforcause

Member
May 12, 2014
107
5
81
Unfortunatelly, no warranty on the assembly itself. Its an offer by the company. If you purchase all the components from the store they will asseble and pre-instal for free. I have warranty for the PC and all its components of course but not for the assembly itself.
Even if I had it would be extremely hard for me to ship the whole rig to the store and then wait (14 days usually if you make a complaint) for the computer to come back. Also I would have to prove that it is doing such things and if it wouldnt show up to them they could just say that its all fine, that they didnt get the BSOD.

So now is all me (you) and the issue :(
 
Ketchup

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Well, if we still don't get anywhere, you can wipe the drive and re-install Windows yourself, and install drivers off the CD it came with. It's not rocket science. Then you will know exactly what was done.
 
J

Justforcause

Member
May 12, 2014
107
5
81
Yeah, well thought about it myself. But I guess I would have to find the drivers online as I don't have a CD/DVD ROM anymore :D

So is it safe to say its the drivers causing the issues? Or it can still be anything?
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom