I never had this problem with the old drivers but I don't know which ones I had or how to revert to them.
Page fault in nonpaged area is to do with Windows Virtual Memory, nothing to do with the drivers. But to fix this Windows related problem....
Control Panel > System > Advanced system settings > Advanced tab > Performance - Settings... > Advanced tab > Virtual memory - Change...
Click on a drive with System Managed under Paging File Size, and change it to No paging file > set. exit all windows and reboot.
When your back, open the same again and tick System managed size > set. exit all windows and reboot.
Should solve the issue.
Thank you. Unfortunately, I forgot to hit Apply after setting it to No Paging File, but I got help from another source and they caught my mistake.
I set the minimum and maximum sizes to both be equal, usually to the recommended size; it might help to prevent page file fragmentation.
this isn't a problem with Window's page file. it is a problem with the atikmdag.sys file.
the only versions of the AMD package that cause this issue for me are the crimson versions. every CCC package works great with no errors, every Crimson package leads to this same page-fault crash & error.
tried with system managed on system drive, system managed on empty drive. set 4096MB min/max on system drive, on empty drive, and on empty partitions of system drive. nothing stops the eventual crash with page fault error while using Crimson.
Page File in Nonpaged Area is an OS issue relating to the Page File. The OS deals with the Page File at the drivers request. Are you having an issue like the OP?
shade74 Can you provide and update on your situation. If it's working now please mark your thread as answered.
and as I stated: it is the newer atikmdag.sys file that is causing the issue, not Windows itself. if it was a system-wide problem with Windows paging file then it would happen with or without Crimson installed.
have been through 2 versions of Crimson causing the same page fault. revert back to any of the previous Catalyst packages and the page fault does not happen. have found more than 20 threads across the internet with the same exact problem caused by Crimson.
Would you like to open a thread? Im a little confused you seemed to have jumpped into a thread unconfirmed if the situation is solved, not providing any support yourself.
Is this issue only on Windows 10? Again the OS is in control of the Page File, it controls who uses what. I dont have the issue myself, have you or any of the other 20 threads looked into the problem, checked your Event Viewers for a solution? Maybe rolled back to CCC? Reported to AMD? Matching the Page File to your RAM size?
Maybe you could address the opening post with your findings, "if your still having problems I have taken some time to look into the situation and have come to the conclusion X Y Z so would recommend Z" is a suggestion. The advice and information I provide is based on experience, and was 5 days ago. But will point out your findings to anyone else having a similar problem.
Crimson - Display driver 15.30.1025 causing "page fault in nonpaged area - atikmdag.sys" system crash...? It would seem seeing what you have tried, it is a small number of issues and your issue may not even be related. As it's not affecting everyone this could very well be an isolated issue. Particularly when you have had mild success with Crimson.
is english your native language?
posting an issue in a thread about that issue, responding that your solution is incorrect, and providing support that it is a problem with the Crimson package and confirming the OP's original problem is confusing to you?
this thread being specifically about Windows 10 x64 bit..."Page Fault in Nonpaged Area" should be a clue for you as to what OS it is happening in for me.
this thread being open and the fact that i have started a similar one plus the other sites with users posting the same issue is confirmation that it is a problem.
were you not able to comprehend my sentence stating that reverting back to Catalyst packages fixes the problem?
reported multiple times to AMD.
have tried zero page file, system managed page file, 4GB min/max on mutliptle drives, 16GB min/max on system drive(yesterday upon reinstalling), nothing fixes the issue. as I stated.
seems pretty easy to me by my initial post that i am confirming the issue and pretty clearly reporting facts about the issue. you may not like that you are wrong about the solution but you are.
a small # of issues? it is 1 large issue: any installation of the Crimson software packages leads to the atikmdag.sys file causing crash to blue screen with error "page fault in nonpaged area-atikmdag.sys".
if it was an isolated issue only suffered by me then I would of course take it as a personal system error. but seeing multiple threads here on AMD and many others around the internet confirming the same problem means that is not an isolated issue.
"The advice and information I provide is based on experience, and was 5 days ago. But will point out your findings to anyone else having a similar problem."
This is a user to user support forum, the user needing support hasn't responded. Im providing support to that user, not having an argument or a debate, if you don't find my response helpful use the Helpful No button. This is to stop threads being filled with 20 odd posts providing nothing constructive, like these.
I can see you have tried a few things, I can see that in some cases you have succeeded even just for a short while. The problem being sporadic would suggest there is more to look into with it. Rather than a simple crash.
updated to the new 16.1 hotfix on the 7th. have 12-15 hours of games over the passed week and the page_fault error has not reoccurred.
with 15.12 and the previous Crimson packages it happened within a very short time of install.
hopefully the problem has been corrected for all now...
Hmmm thanks! I'll maybe try that later on. For now, doing a system restore fixed it.
Retrieving data ...