PAGE_FAULT_IN_NONPAGED_AREA with our windows server 2012 R2

We are facing some strange issue with past 3days, our production server getting stopped frequently and its creates some minidump files,

As we checked the minidump file’s and we found some error like below

kindly help us to sort out the issue.

Dump File: 050217-25828-01.dmp

Crash Time: 5/2/2017 3:09:26 PM

Bug Check String: PAGE_FAULT_IN_NONPAGED_AREA

Bug Check Code: 0x00000050
Parameter1:ffffe002`0803f000

Caused By Driver:ntoskrnl.exe

Caused By Address: ntoskrnl.exe+14e3a0

Caused By Address:ntoskrnl.exe+14e3a0

Was this discussion helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this discussion?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this discussion?

Thanks for your feedback.

Replies (3) 

Also windows server 2012 r2, same minidump errors.

i will try to look into update history,

also check disk, shows disk is ok, and sfc /scannow also says that it’s all ok.

If You solve this, please leave coment how?

53 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Also windows server 2012 r2, same minidump errors.

i will try to look into update history,

also check disk, shows disk is ok, and sfc /scannow also says that it’s all ok.

If You solve this, please leave coment how?

For the above error, we have been installed around the 90mb (.msi) file update patch to being stop unexpected server unreachable .

Kindly find the below URL to which we were installed,

we have been installed 2 days before as of now the server is running will let you update.

53 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I have the exact same problem. Here is what I know and what is the common thread with all my servers.

1. I have over 50 servers and only the ones on ESXi 5/6 (VM) have had this issue.

2. The issue started 10 days ago.

3. Only the servers that are Domain Controllers are effected.

4. The restarts are random amd all have the same error as above.

5. Some of these servers have not been restarted in over a year and have been in production with zero issues.

I did MS updates, then I reconfigured the page files for custom (I do not ise the old rule of 1.5 on todays OS and VM’s).

Page faults windows server

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

Question

I have a 2012 Server running Hyper-V for a few VM’s. It’s a good spec Dell Poweredge with 192GB RAM.

Typically it runs around 130GB RAM available. Pagefile is managed by system, currently allocated 25,600 MB.

I am currently testing Veeam One monitoring solution and one of the things it’s highlighted for this server is that the Page Faults/sec is high and above the warning threshold. I’m seeing alerts with values of 3,606.0 and 2,1560.0 Pages/sec.

I have since run perfmon on the server and tried to make sense of the data I’m seeing.

I just paused Perfmon and have the following values:-

1. Page Faults/sec — Last 285.452, Avg: 1,066.649, Min: 1.002, Max: 15,149.914

2. Page Input/sec — Last 0.00, Avg: 0.654, Min: 0.000, Max: 33.051 (I believe this is the number of reads from pagefile.sys)

3. Transition Faults/sec — Last 139.221, Avg: 528.399, Min: 0.000, Max: 8,423.310 (I believe this is the number of soft faults)

Strangely (to me anyway), I would have expected the number of Page Input/sec + Transition Faults/sec should = Page Faults/sec?

Do these figures look correct and normal to you all?

If not, where do I start with diagnosing the issue?

Thanks in advance for help and assistance given 🙂

Page faults windows server

Вопрос

Есть машина с двумя SSD в RAID и терабайтным HDD WD Red, 32 Гб оперативы. На машине стоит proxmox, на котором выделена виртуалка под сервер. Виртуалке выделены 20 Гб оперативы, 100 Гб HDD. Виртуалка на базе KVM. На виртуалке стоит Windows server 2012 r2. Есть еще одна виртуалка с 5 гб оперативки — по сути снапшот основной системы. Все ето больше года стабильно работало. В системе не устанавливался никакой софт. Обновления системы производятся вручную.

Гдето месяц назад система начала произвольно перезапускаться. Провел тесты памяти, HDD. Правда средствами системы, и поетому не уверен насколько коректны такие тесты, если сам сервер на виртуалке. Удалось определить что проблема перезагрузки BSOD PAGE_FAULT_IN_NONPAGED_AREA (50) вызван процесом ntoskrnl.exe

*** STOP: 0x00000050 (0xfffff90105fffffc, 0x0000000000000000, 0xfffff960002579ba,
0x0000000000000000)

*** ntoskrnl.exe — Address 0xfffff801f4223f20 base at 0xfffff801f407a000 DateStamp
0x5aa43238

Знает ли кто-то в чем может быть проблема?

Дамп ы https://fex.net/722535054373

Все ответы

Добро пожаловать на форум TechNet.

Могли бы предоставить ссылку на дамп (C:\Windows\Memory.dmp) и на мини-дампы (C:\Windows\Minidump\*.dmp).

Avis de non-responsabilité:
Mon opinion ne peut pas coïncider avec la position officielle de Microsoft.

Bien cordialement, Andrei .

MCP

Прошу прощения. Б ы л не на месте, когда писал. Сейчас загрузил дамп ы:

— Уточните пожалуйста кроме роли терминального сервера 1C какую роль еще играет сервер?

— Уточните пожалуйста вам знаком процесс et.exe?

— Предоставите лог сторонней диагностической утилиты FRST согласно следующей инструкции:
Важно: обратите внимание, что указанная утилита, может показать возможное использование средств обхода лицензионного соглашения.
— Скачайте Farbar Recovery Scan Toolи сохраните на Рабочем столе.

Примечание: необходимо выбрать версию, совместимую с Вашей операционной системой. Если Вы не уверены, какая версия подойдет для Вашей системы, скачайте обе и попробуйте запустить. Только одна из них запустится на Вашей системе.

• Запустите программу двойным щелчком. Когда программа запустится, нажмите Yes для соглашения с предупреждением.
• Убедитесь, что в окне Optional Scan отмечены «List BCD» и «Driver MD5«.



• Нажмите кнопку Scan.
• После окончания сканирования будет создан отчет (FRST.txt) в той же папке, откуда была запущена программа. Пожалуйста, прикрепите отчет в следующем сообщении в качестве ссылки на скачивания с файлового хранилища (например onedrive).
• Если программа была запущена в первый раз, будет создан отчет (Addition.txt). Пожалуйста, прикрепите его в следующем сообщении в качестве ссылки на скачивания с файлового хранилища (например onedrive).

  Avis de non-responsabilité:
  Mon opinion ne peut pas coïncider avec la position officielle de Microsoft.

  Bien cordialement, Andrei .
  
  MCP

  What is “a lot” of Page Faults?

  I am monitoring the memory object in Windows 2k8, and am tracking the Page Faults/sec counter. Is there any threshold to determining what is an excessive amount of page faults? Or should I be more concerned with a sustained, high, amount of page faults?

  Is there a better way to look at page faults?

  

  2 Answers 2

  This is a good question because getting a read on memory issues for performance monitoring is difficult.

  First off, when looking at Page Faults/sec keep in mind that this includes soft faults, hard faults and file cache faults. For the most part, you can ignore soft faults (i.e. paging between memory locations) and cache faults (reading files in to memory) as they have limited performance impact in most situations.

  The real counter for memory shortages will be hard faults which can be found under Memory: Page Reads/sec . Hard faults mean process execution is interrupted so memory can be read from disk (usually it means hitting the page file). I would consider any sustained number of hard faults to be indicative of a memory shortage.

  As you go further down the rabbit hole, you can also compare disk queue lengths to hard faults to see if the disk reads are further affecting disk performance. To get a picture here, look at Physical Disk: Avg. Disk Queue Length. If this number is greater than the number of spindles in your array, you have a problem. However, if this number only spikes during hard page faults, you have a problem with memory capacity and not disk performance.

  What causes page faults?

  A page fault is a trap to the software raised by the hardware when a program accesses a page that is mapped in the virtual address space, but not loaded in physical memory. (emphasis mine)

  Okay, that makes sense.

  But if that’s the case, why is it that whenever the process information in Process Hacker is refreshed, I see about 15 page faults?

  

  Or in other words, why is any memory getting paged out? (I have no idea if it’s user or kernel memory.) I have no page file, and the RAM usage is about 1.2 GB out of 4 GB, which is after a clean reboot. There’s no shortage of any resource; why would anything get paged out?

  7 Answers 7

  (I’m the author of Process Hacker.)

  A page fault is a trap to the software raised by the hardware when a program accesses a page that is mapped in the virtual address space, but not loaded in physical memory.

  That’s not entirely correct, as explained later in the same article (Minor page fault). There are soft page faults, where all the kernel needs to do is add a page to the working set of the process. Here’s a table from the Windows Internals book (I’ve excluded the ones that result in an access violation):

  • Reason for Fault — Result
  • Accessing a page that isn’t resident in memory but is on disk in a page file or a mapped file — Allocate a physical page, and read the desired page from disk and into the relevant working set
  • Accessing a page that is on the standby or modified list — Transition the page to the relevant process, session, or system working set
  • Accessing a demand-zero page — Add a zero-filled page to the relevant working set
  • Writing to a copy-on-write page — Make process-private (or session-private) copy of page, and replace original in process or system working set

  Page faults can occur for a variety of reasons, as you can see above. Only one of them has to do with reading from the disk. If you try to allocate a block from the heap and the heap manager allocates new pages, then accesses those pages, you’ll get a demand-zero page fault. If you try to hook a function in kernel32 by writing to kernel32’s pages, you’ll get a copy-on-write fault because those pages are silently being copied so your changes don’t affect other processes.

  Читайте также:  0х8007232в ошибка при активации windows