What Is Page Fault in Nonpaged Area?
By 01i
Blue Screen Of Death (BSOD)
STOP 0x50 Page_Fault_in_Nonpaged_Area
"Page fault in nonpaged area" is the error message for the 0x50 stop error on a Windows PC. At it's most basic, the error means that your PC asked for a page of memory in order to continue, and the page was not available. Windows was unable to continue with the processes it was running, and crashed with what is commonly known as the Blue Screen of Death (BSOD).
 | Amazon Price: $99.99 List Price: $128.70 |
 | Amazon Price: $162.95 List Price: $199.99 |
 | Amazon Price: $21.56 List Price: $39.99 |
RAM and the Page File.
Random Access Memory (RAM) contains the information required for the computer to process it's current task. The page file, is a location on a local hard disk that the RAM uses to store pages of memory that are still required, but not actively in use. Pages of memory are swapped between the physical RAM and the page file as required.
The Non-Paged Area
The Non-Paged area is an area of memory that contains data that is critical for the running of the system. This data is always required, so instead of swapping the data back and forth between the RAM and the page file, the data is kept constantly active, in the non-paged area of RAM.
What Might Cause the Error
Because this area of memory is reserved for the windows core, it is unlikely to be caused by an error in the code. While it 'may' be the case that software (like Norton) may have stored some data in the nonpaged area, this error is usually more indicative of a hardware fault with the RAM, it may also suggest a hardware problem with the level 1 or level 2 cache, or corrupt sectors on the hard disk.
 | Amazon Price: $7.99 |
 | Amazon Price: $14.33 List Price: $27.99 |
| Amazon Price: $21.56 List Price: $39.99 |
What to do
As with any system crash, the first thing you ought to do is reboot and try logging in again. You may well find that everything works and the crash does not happen again. You may, however, find out that the blue screen occurs before you get the chance to finish logging in. If this is the case there are a few things you can check.
First, restart the PC, and during the first stages of booting your PC (while the background is black with white text) press the F8 key, this should bring up the boot menu. The boot menu will offer a selection of options, including starting windows normally, booting into the various safe modes, and starting using the last known good settings.
If you fail to log back in using the last known good settings, the next thing to try would be booting into safe mode, and restoring back to a previous save point using system restore. The System Restore utility can be found in the Start Menu, under Accessories -> System Tools.
The Command Prompt
System Restore Has Not Worked
If you still cannot log in after restoring to an earlier save point, log back into safe mode and run checkdisk. This program will scan through the sectors of your hard disk, looking for bad sectors and correcting them, or flagging them us corrupt to prevent them being used. To run check disk, go to the 'run' option in the Start menu, and type:
cmd
Pressing enter should open a black screen with white text called the command prompt. Type
chkdsk
and press enter. Windows will run through checking the status of the drive and will tell you if it finds any errors. It is probable that windows will want to restart prior to running chkdsk. This enables the program to scan files that are locked and in use by the operating system by running before windows loads.
If chkdsk finds an error, you will want to run the command again, this time adding the /F switch telling chkdsk to fix any errors it has found on the volume. Fixing issues on a disk can take some time so be patient. To tell chkdsk to fix errors type into the command prompt:
chkdsk /F
RAM Chips
![RAM [Special Edition]](http://ecx.images-amazon.com/images/I/61QxDYQTG-L._SL75_.jpg) | Amazon Price: $10.94 List Price: $19.98 |
| Amazon Price: $90.98 List Price: $124.98 |
Check Disk Has Not Worked
At this point, you have eliminated software and hard disk as the cause for the crash. That leaves the most likely suspect, your RAM. You could open up the event viewer and try to find errors that suggest another cause. You can do this by typing the command eventvwr into the start menu's 'run' option, and looking through the System and Application logs, but unless you know what to look for, this could easily send you off on a wild goose chase.
*** Before you touch anything inside your computer ***
Make sure that you earth yourself to discharge static electricity that may damage the PC. This can be done by touching something that is earthed, like a radiator or the metal case of your PC when it is plugged in (but not turned on). Make sure that you unplug your PC before making any changes to the hardware.
******************************************************
Turn off your PC and take off the side. Inside - once you push aside the mass of cables - you will find the RAM fixed onto the motherboard. The RAM chips generally sit next to each other in parallel slots on the motherboard. Little plastic clips often clip into small grooves on the side, keeping them fixed into place.
Hopefully you will find that you have more than one stick of RAM, if this is the case you may well find that the problem only exists with one of the sticks of RAM. To establish which chip is causing the problem, simply remove the clips to either side of one of the sticks, and then pull it out. Try loading up the computer again, if the problem still exists, put the chip back, and remove a different stick of RAM.
Comments
very informative
Didn't do me any good!
Bob, I assume you are getting this exact message, there are a whole host of blue screen crashes that each mean different things. If it is this specific message, and you have worked your way through everything I've suggested and it still happens, then your problem is likely to be with the level 1 or 2 cache. That means a motherboard replacement, which generally means you'll need to replace CPU and RAM too :(
I get the BSOD in every option, I get it even in safe mode.
Thanks to everyone.
I get this blue screen after checking all of that on my brand new system. It goes away when I underclock the CPU and memory.
01i, why do you think that motherboard, CPU, and RAM need to be replaced instead of just the motherboard or the CPU?
Thanks
CC, you do not need to generally replace the motherboard, CPU and RAM if you get this BSOD. You should run through the various suggested checks to see if they resolve the issue, it will usually related to recent installed or upgraded software or drivers, HDD or RAM.
I suggested Bob may need to replace Motherboard, CPU and RAM because he advised that he had already checked everything I suggested (including RAM) and that the issue was still apparent.
That leaves the cache on the motherboard as the most likely cause. Motherboard replacements usually mean that you also have to replace the CPU and RAM due to needing them to work with the new board.
If you can resolve your issue by underclocking the RAM, then you should probably upgrade to some better quality RAM. Unless you built it yourself, brand new systems often tend to come with the cheapest RAM available.
I just wanted to correct myself after recalling where level 1 and 2 cache are actually located. I should have advised that the cache is part of the CPU, rather than the motherboard. This does not effect the advise I have given though, as motherboard and CPU tend to need replacing at the same time.
CC, I am not sure whether the CPU caches are effected when you over or underclock a processor, I'd still assume cheap RAM rather than a requirment to replace the CPU.
01i, thank you for the quick reply.
This is a diy computer. I picked the fastest RAM and the brand that the motherboard manufacturer recommends. Both RAM modules passed memtest at the maximum speed individually, but not simultaneously. Even tried different sockets. They passed simulatneously at a slower speed.
CPU cache is a likely culprit, but I am puzzled to why both CPU and memory have to be underclocked. I would guess that slowing the CPU alone would have solved the problem. My other thought is that the DRAM controller on the motherboard is busted and can't keep up. This is a rev 1.0 motherboard. I don't have a lot of confidence.
I assume that when you tested the RAM individually, the CPU was at the normal clock speed?
Have you tried leaving the CPU at full speed and underclocking the RAM further to see if you can get them all at the same time without needing to underclock the CPU? Or even overclocking the CPU to see if the RAM works at full speed with a bit more power from the processor?
Although, I think you're right about it being the motherboard in this instance. I think it highly unlikly that you have bought yourself dodgy RAM and a dodgy CPU at the same time.
I also assume that your manual that came with the motherboard actually advises that it is suppsed to be able to run the quantity and speed of the RAM you have put in it?
Both CPU and memory have to be underclocked. I haven't tried overclocking yet. Been afraid of doing so. I need this computer to finish doing taxes (tax day is tomorrow in the US). I did find something interesting last night. I can run the CPU at full speed if I set the BIOS setting for CPU voltage from 1.35V to 1.425V. According to AMD, my CPU can run from 0.9V to 1.4V depending on clock speed. I noticed that the motherboard reports 1.35V CPU voltage when I set to full CPU speed. So I suspect that the motherboard is not giving enough juice to the CPU to run reliably at full speed. When I change the voltage to 1.4V, Windows startup got a lot further than ever before. No BSOD, but froze on Explorer. I then increased the voltage to 1.425V. Windows started up without issue and ran several hours with heavy processing load. Next, I will try running the memory at full speed to see if this solve my issue.
I am a bit concerned running the CPU voltage above spec. I may have to limit the voltage to 1.4V via Cool&Quiet feature.
I'm having this same problem however I can run checkdsk or view minidump or anything because I can't get the computer to start. If it doesn't blue screen as soon as windows loads, it reboots before windows loads.
XP Pro SP2
Can we I request a screenshots?
This is a real question here, why is it that Windows is the only one that has this problem? In linux you never see this screen. I have bought 2 windows xp pro. cd's, two windows xp home cd's, one windows millenium cd, one windows 2000 cd, I could go on here, but I feel foolish for having to keep redoing windows everytime this little "BSOD" occurs, the last time I just installed Ubuntu and that magic little screen went away and I can only say I just love Linux. I hate having to pay someone to torture me with an obnoxious blue screen. I do like the clean look windows has and would love to set it up to dual boot, but just cannot handle the blue screen, if they could write it out of the programming it would be great.
Thanks for the excellent post and information.
A quick note before I answer the last few sets of questions (where I can). This article in ONLY valid for the specific BSOD that contains the stop error text PAGE_FAULT_IN_NONPAGED_AREA. There are LOTs of different blue screen crash messages, that all mean different things.
mentalkayse,
I'd try swapping out RAM as suggested.
ronjersan,
There is a screenshot at the start of the article.
glorybeenow,
The Blue Screen of Death happens when a critical system error happens and windows shuts down to prevent irreversable damage from occuring. The dump of text contains information about what was going on at the time of the crash for diagnostic purposes.
The reason why the crash doesn't happen on Linux is simply because Linux doesn't display errors in the same way as windows.
good..but more better if you could explain with screen shoot.....
what if safe mode doesn't work, should i just try replacing the ram, also would changing the bios to boot from cd help to load it up with the windows disk?
Hi 01i,
Among the so many webpages discussing this kind of fault, yours here is the most structured, methodic, useful and making sense I've found !
I'm suffering from time to time from these page faults in non paged areas with my laptop (a 4 years old Acer 9301AWSMi), especially when it has been powered off at least a few hours (i.e. when it cooled off).
I didn't find any disk corruption problem, and I don't get these BSOD short after sw changes (the HW is unchanged since years now).
Rebooting in safe mode with cmd prompt then often works, standard safe mode sometimes.
I have two questions for you:
1) If I choose a 'reboot with logging enabled' in the F8 alt boot menu choices, what is the log file and where is it created exactly ?
2) can I use the page fault memory address or some 'fault code' to drill down the actual fault ? for instance in what task did it crash ? with what piece of software ? in cache memory or standard RAM or disk or other peripheral ?
When this phenomen happens, it crashed consistently at about the same time: Windows XP SP2 starts, logon screen prompts, then after a few secs the HD LED stops flashing, then starts over intensively after say 5 secs, like if something is then being loaded then *bang*. If I log in or not doesn't change anything -- the HD behaviour is the same, pointing at the fact that it might still be loading all the sw at start-up.
Thanks for your suggestions !
The boot log is stored in your windows directory (C:\Windows or C:\WINNT) and is called ntbootlog.txt
You can view the contents of a memory dump file using some of the microsoft debugging tools. Check out this support article from microsoft
Windows NT/2000
http://support.microsoft.com/kb/192463
Windows 2000/XP/Vista/Server 2003/Server 2008
Sorry to sound a bit lame I have sort of understood the excellent info above... but could a virus cause BSOD? As Im sure a virus was on my laptop just before this BSOD happened.
Yes, a virus could theoretically cause this BSOD. If you suspect a virus, then I'd update your anti-virus definitions asap and then run a scan
Wow thanks for such a speedy reply 01i the trouble is I cannot get it to even run in safe mode as no matter what I do the BSOD appears I think it may be caused by the virus that was there as everything was fine untill the virus popped up. I think it will require looking at. Thanks ever so much for your help
I have this BSOD which came up when updating a Sempron 64 3500+, HD 2850 512MB AGP, 2GB DDR2 533MHZ system with a new Athlon x2 6000+ processor. The error seems to be caused by ATI drivers.
I tried the ram check and nothing changed. When i tried the new CPU with a GeForce 6600GT everything went fine.
So the CPU should not be the cause.
Any suggestion?
Edit: HD3850
Nice hub,thanks for sharing.
Hello,is there a way i can be sure of the fault by using the code in front of the STOP in the BSOD? thanks
Bio, if the STOP error reads Page_Fault_in_Nonpaged_Area then it's the same problem. If it says something else eg 'irql_no_less_or_equal', 'unmountable_boot_volume', 'bad_pool_caller' etc etc etc, then you have a totally different cause.
The STOP 0x00000050 code associated with the pagefault BSOD wont show up on any other BSOD, it is the code specifically for the error this hub is about. If you have a different code, then googling might help. If you post it in here I'll try and point you in the right direction.
If you are refering to the large dump of information included with the BSOD, yes it can be used to troubleshoot the root cause. I linked to a couple of microsoft kb articles earlier, but reading dump files, tends to get left between a 3rd line support team and microsoft because they are not an easy read.
I just tried to run checkdsk on my laptop and all I get is "checkdsk" is not recognised as an internal or external command, operable program or batch file. What should I do? Pls help
Duraid, I suspect that a lot of people have skipped the check disk step, as you're the first to point out the typo that's been there since I wrote it. Open the command prompt and run "chkdsk" not "checkdsk"
Thanks for the tips. Finally removed my BSOD!
Some really good tips! However they didn't work for me. Although I got my computer booting when I removed a TV capture card from a PCI port.
I was having the same issue and after a few days of troubleshooting, it's down to the NB or CPU cache, and I'm leaning towards the CPU cache.
01i:
I'm intrigued. Some of your comments/ideas are spot on, while others are laughably wrong. How do you get to know so much about some of the finer points of troubleshooting while remaining ignorant of so many of the basics? L1/2/3 cache on the motherboard? Not sure whether OCing affects the cache (notice the 'a' in 'affect')? CPU+MB+RAM needing to be replaced together? Underclocking the RAM but not the CPU so the memory gets more power from the CPU? What? You seem confused.
Erik,
I wrote this hub in response to the question 'What is Page Fault in Non-Paged Area?' It was written as a definition of what the error means at its basic level. What is the non-paged area? and what might cause it to fault? At the time I did not expect to be asked for my opinion in troubleshooting the problem in a growing multitude of situation specific examples, if the cause turns out to be something other than the main causes of the error message.
To test beyond the HDD and RAM you really need spare components or an exceptional understanding of circuitry and a multimeter. I didn't write a hub on the ins and outs of processor cache, I've not once suggested overclocking or underclocking anything, that's been other people telling me what they've tried.
As for my statement about replacing the montherboard and cpu at the same time I stand by it. If this problem comes up on a new PC then it's probably under warrenty, I expect that most people looking to hubpages for this problem have probably not got a cutting edge PC. If your CPU dies, chances are your existing motherboard wont work with the replacement you buy and vica versa.
This is a hub aimed at people that dont know much about their PC, to help them test out a few things before paying a proffessional. Rather than at people that have the skillset to troubleshoot which specific area of cache might be at fault.
I dont know whats wrong with my comp, i get this error mostly when i power down the machine and leave it off for several hours, i've found that flipping the power switch off in the back and pressing the power button, then flipping the PSU back on and turning it back on makes the comp work fine, however i dont want to do this all the time, anyone know what might be the cause?
Brian, I'd suggest working your way through the artical above. The most likely cause will be HDD, RAM or recently installed software. After that it gets a little trickier to diagnose.
Oh I am very familiar with the blue screen of death...a terrifying site indeed. THanks for this hub
I found that it was one of the Ram sticks....... I didnt think it would be because I had ran the ram through several hours of diagnostic tests, sure enough though I tested one out at a time, and the computer kept crashing with just one and fine with the other. Thanks for the form!
Hi I am getting the same message 'page fault in non paged area'....I restart and press F8 to get into safe mode but it crashes again and starts again and it never takes me to safe mode....what to do....I tried booting from the OS disk I got with my laptop but it shows me the same BSOD....please help..it's a windows Vista....
Gaurav, if you cant log into windows, try the RAM suggestion at the end of the article
I originally had just the BSOD with page fault error, when tried to do a restore point it gave me an error message saying it couldnt find the right path to do it. I then went ahead and did the chkdsk and after doing that I cannot even enter safemode anymore. It trys to load it and ends up timing out and starts the reboot process. if anyone could help that would be a big help.
Install Linux/Ubuntu.
Honestly, i am running a 64 bit piece of shit acer that my gf bought about 13 months ago. It gave me bsod, and i was fucked. I tried everything, and even brought it to a shop. They told me, after taking my fifty bucks, that i had a hardware issue. More specifically, they told me "we've tested everything (ram, h/d, power/temp/etc.) and that I needed a new motherboard. I was about to give up until i downloaded the ultimate boot cd and got the partition manager to open. Since it's linux based and had no issues at all, i just installed ubuntu. s hit works awesome!
I just wanted to point out that switching to Linux will certainly resolve the problem. But only in the context that BSOD is a Windows error reporting mechanism that linux does not share. Unless the issue was software installed on top of windows, whatever was causing the crash is still there, you've just installed a different operating system that crashes in different ways.
Thanks for your hub.well I never faced any issue with page fault. but I will bookmark your hub and keep it handy.
why do i get the impression that Erik is just some pimply faced numb nutted turkey choker. For starters, if your having the problem and coming here to find a solution then like myself you are out of ideas on what the cause could be. however to turn around a critisize a technician for what i believe to be a very well written "how to" for those who do NOT have the years of computer trouble shooting experiance. personally people like you are what makes the computer industry so political and bitchy. correcting someones spelling on a word like affect "which i might ad is spelled different depending on the country that you are from" is just bad form.
crawl back under the rock and go back to sitting on your hand so it feels liks someone else
Prob--everytime i chkdsk or restore the computer also crashes with no title and not even a code as it was all 0x0 and ask admin for help.Huh?
In my non-expert opinion, I suggest either looking into power source options, I recently solved my problem, which was running 4 hd's and 8900gt sli with 2 caddys in the usb. Same issue with page filing, power hoarding from the CPU, hds, gfx to squeeze more juice into the RAM. Upgraded my psu from 240v to 360v or close to that. Never had another issue.
That's my say, just a fortunate guess in my mind of what should better my situation which also worked for that too.
To temp fix my prob I ran 3 hds and the sli. And caddy hopped the other hds on the single usb.
I didn't try your thread personally but i have referenced your posts to my mate with this prob to a resolution. Ended up being the RAM.
Thanks :D
01i, thanks for the info, much appreciated. I got to the point that I tried to run chkdsk/F, but I got this:
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts?
I selected Y, and proceeded to restart in safe mode. Just for kicks I tried to run it again, and ( no surprise) it did the same thing. I'm just wondering what this means. Thanks.
*edit* I restarted again (not in safe mode) and saw chkdsk/F working, but was cooking dinner, and had to get up and go to the other room. When I came back, chkdsk/F had finished and windows was asking for my login password, so I didn't get to see the results of F, if there were any. Doh. I'm gonna restart in safe mode so I can chkdsk again.
Thanks again for the hub.
Oldandintheway, chkdsk needed to scan files that are in constant use by windows. It cannot do that while windows is running, so instead launches after the next reboot. Maybe I should edit the hub to warn people that chkdsk may want to run after a reboot.
After I re-chkdsk'ed I got a list of issues: Master file bitmap attribute is incorrect, the volume bitmap is incorrect, windows found problems with the file system. It recommended I run chkdsk/f. Can I assume that the fix didn't work? Any idea why?
Many thanks!
When you run chkdsk without adding the /f switch, the system searches the disk for errors but does not do anything about them. Adding /f tells chkdsk to fix errors on the volume. If chkdsk suggested that you run with the /f switch specified, you probably didn't include it when you checked, and will need to in order to fix the problems that it found.
Sorry if I was unclear, I did run the Chkdsk/f function on startup (the second time). After that, I restarted again in safe mode and ran chkdsk again. The issues were not fixed. Should I move on, or try to figure out why chkdsk/f didn't work?
Are you running chkdsk/f or chkdsk /f ?? I am not 100% certain of this as I've not experimented running the command without a space, but it might not work, and as you've missed the space every time you've typed it here, maybe that's the problem?
Also, but less likely you may have typed chkdsk f without the forward slash. This would have run the read-only form of chkdsk on your F drive. Assuming you have one.
Crap, missed the space. Thanks for catching that. I'll try that when I get home. Thanks again for all your help!
thank you so much!!!
Hi, in your 'what to do' section, you say the first thing to do is to reboot and try logging in again.
You missed out a vital step. I think you should remember that when you see a BSOD, the very first thing to do is swear loudly, maybe scream a little in frustration and anger, then reboot and try logging in again.
:)
hello sir,
when i try to boot the window, it says hal.dll is missing, therefore i can't boot on any mood, such as safe mood or last good config, because i received same massage on all of them. So i tried to do fresh install, but I received same blue screen as above. I swapped the ram with new ones but still same problem. took out HDD and CD Drive out and put them back. still same thing. What do you think i should do? thanks
hal.dll is a vital component of windows. Without that file the operating system doesn't know how to communicate with your PC hardware. This hub is probably not your answer. Resolve the hal.dll issue first, and chances are your BSOD will stop. Reinstalling windows is your quickest fix, although obviously not so good for your data. If you need your data there are a few good guides when you google 'hal.dll is missing'
thanks for your reply. im trying to reinstall the window, but thats when the BSOD comes into the play. I tried both system recovery and fresh install of window, both tries BSOD shows up. so fixing hal.dll is kind of out of question. I dont care about the data that i will lose, they all backed up. i did alot of research on how to get hal.dll fixed but to no avail. thanks so much
mark, if you've checked software by formatting and reinstalling windows, and you've checked RAM by replacing it, then you've already covered the most obvious causes. Based on the reports in this thread so far, your most likely issue would seem to be with an area of cache on your CPU or motherboard. It's going to be really hard to disgnose further without replacement components.
However. Loss of a vital windows file, followed by issues reisntalling could theoretically mean that you have a corrupt HDD right in the places windows loves to install core functionality. Maybe the very start or end of the drive. It might well be worth either attempting to boot into Linux from a USB stick and running HDD checks, or perhaps simpler, trying to reinstall windows onto a new HDD.
ill try to install linux into it and hopefully it will install and from there i could have access to hard drive and repair my missing files. ill get back to you on that. thanks so much
so i did boot into linux with no problem, so i restarted the computer and i was able to do system recovery without BSOD appearing. so linux saved me without doing anything. how weird! anyways thanks so much your help.
Cheers dude. It was 1 of the RAM models in the laptop although this kept me from reinstalling win 7 but it allowed me to install windows vista and xp, any reason why?
Isn't it easier to google something rather than figure it out urself =P
SIR I M GETTING DIFFRENT BSOD ERROR EACH AND VERY TIME AND ONE MORE THING I HAVE REINSTALL WINDOWS MANY A TIME FROM DIFFRENT DISC BUT STILL THERE..WHAT YOU THINK IS MAIN PROBLEM BEHIND IT...MY MOZZILA FIREFOX IS ALSO GETTING CRASHED EVERY TIME EVEN ALL THE WEB BROWSER GETTING...WHAT DO YOU THINK ABOUT THIS PROBLEM..WHAT SHOULD I DO SHOULD I INSTALL UBUNTO OR LINUX IN PLACE OF WINDOW?
A friend of mine has recently received this error. Actually she's had it for about a year but I've been in Iraq, so now I'm finally working on her computer to see what could be the problem. So far I've run a chkdsk and it says there were 8kb of bad files, I figured 8kb isn't a problem but I've set it so that it will run the chkdsk/f when it boots up again. Till then however, I am running a memtest. I have had 3 good passes, and figured I would let it run all day just to be on the safe side. We are fairly positive it isn't the hard drive as we pulled the current one from a known working system and swapped them both. The old hard drive works fine in the other computer and this one still BSOD. I'm going to swap out the processor soon, but so far I'm thinking it might be the motherboard. Can I get your opinion on that?
I have such problem only while watching online video and last time it happened while i was watching film from my HDD.
Can u help me?
Wow, loads of recent updates
Mark, glad it's working, although PC problems that have been recurring regularly rarely just fix themself. Hopefuly it'll stay fixed.
Chris, I could only guess as to why windows 7 was crashing when vista and xp didn't. My guess would be that windows 7 introduced some new checks that were previously not in earlier versions. Glad it's sorted.
Vineet, installing a linux distribution wont resolve your problem if it's hardware related, it'll just prevent you getting a windows specific crash. Are you getting any BSOD more frequently than others? It might be worth noting down what crashes occur, maybe there is a connection between them.
Dave, if chksdk found bad files, I'd run with the /f flag first and make sure a processor upgrade is actually required. 8KB could be critical if they are the wrong files.
Nik, have you run through the suggestions in the hub?
HDD was checked. Memory - too.
Ihave this BSOD rarely but it's annoying.
Reinstalling of W7 haven't worked.
my RAM is 1600MHz, but manufacturer put 1333MHz as basic, so I've set it on 1600MHz manually.
Also my i5 2500K worls at 4500MHz.
And in journal the problem looks like Kernel problem.
I think that's because voltage, but i have this BSOD rarely and when PC isn't used hardly (watching films). So maybe it's Nvidia drivers problem?
Nik, if you've gone through the Hub you start getting to an issue that's pretty much impossible to troubleshoot remotley over the internet based on a short description in text, and an overclocked PC. You could well be right about Nvidia drivers, googling nvidia along with nonpaged area has a lot of hits. Although the fact you've significantly overclocked your CPU and RAM might also be the issue. I'd download the latest Nvidia drivers in the first instance, and if that doesn't help try undoing your overclocking and see if that makes a difference.
Thanks for the advice. A startup repair failed. Booted Win 7 Ultimate 64 into Safe Mode and ran the CHKDSK/F command. Now it's booting to a different BSOD (0x0000000A / IRQ_NOT_LESS_OR_EQUAL). Thought it worth mentioning in case others get the same — it's easy to assume the BSOD message is just the same one recurring if you don't pay attention!
I'll move on to track that one now!
Quick update, just for the record. Switched off and unplugged. Pressed power switch in or 20 secs. Re-booted and the second BSOD has gone. Did startup repair again. Worked, but Windows decided it was now unauthorised (after 2+ years of working fine!). So system restore just done and Windows recognises itself as legit again. Confusing, but at least it's working now.
I really appreciate this article - it's very clear and concise and gives a great explanation of the problem. I'd been getting this error off and on and had no idea what it meant, so I'm really glad I decided to look on hubpages. Thanks a lot for the info. :)
i have tried everything suggested but i cannot to do the chdiscs but all i get is the blue screen when i press f8 back to the blue screen i have checked the ram and it makes no difference please help
Glen, a BSOD is a windows crash, so if it's blue screening when you press F8 then you're pressing F8 to late in the boot process. To get to the boot menu you want to press it 'before' your PC starts the process booting windows. Turn the PC on and immediatly start pressing F8 over and over quickly until you see the boot menu. Easiest way to ensure you press it early enough and at the right time.
i am unable to load in safe mode also......what to do now...?.....can any one help!
Yeah!!finally fixed it.
Just had one defect ram stick, so I just booted up windows time after time with a single ram stick to test which one was defect, and by one of the ram sticks windows didn't boot so I knew that was the defect one.
Just sending it back to the store and I will receive a new pack of new ram sticks.
I have to admit that I did some overclocking where I adjusted the RAM voltage from 1.50 to 1.65 :$
Hope this will help some others fixing their boot problem.
Kind regards,
Hubert.
Hi, 1 more time)
I've understood that it's NVIDIA driver problem. Cause Sometimes there's BSOD, sometimes simply "driver had crashed and should restart". But also I'm afraid that it's problem of videoram, but in GAMES everything is OK!
People say that problem may be in voltage...
But once more. I have BSODS maybe once a week... and always in different situations, when PC doesn't even work hard!
Dear people. If you are having this error when booting normally and having the 0x74 error when going into safe mode, please try clearing the registry and then in the system restor menu, open the command prompt and type chkdsk /f c: That should work
For me I only have this error when first logging into an online video game. It never does it any other time. I was using an nvidia card and am now trying my old ATI again to see if that fixes it.
hi i'm just getting this error and a lot more.i've formatted c drive and when i try to reinstall xp the pc just completely freezes.and when i try a boot disk it shows a page fault.i cant do a chkdisk as i never reach the command prompt due to this problem.and i think my ram is ok.pls help me out
i had a problem with BSOD with this and a few other types of faults. It seemed to be a loose SATA cable at the hard drive end. Ive just had (for the first time in nearly a year) this page fault again. Hopefully it will as simple as a a loose sata connection again.
I am also a sufferer of the BSOD "Page Fault" problem and on the same screen it also says that it is the file MSIBIOS32_100507sys.
Im running XP and I can boot and get to Windows starting up but within minutes of logging in it all crashes and the BSOD starts dumping ram memory to the hard drive. Also I can get to the safe mode options but I am not able to go up and down on the menu, it just hangs and then I have to reboot. Its frustrating as I cant to a safe mode start or use any of those options and when I do get in to my login I cant do anything either because the inevitable crash happens. Any input would be appreciated!
hi sir, i have the same problem with my computer..bsods ocuring many times a day..i have an advice that you can recomend this software "whocrashed" that analyses dumb file and display the cause of bsod... Btw "whocrashed" analysed my diff dumb files and it shows diff drivers as the cause like some nvidia,and windows files,i tried replacing my hdd and dosent work(i reinstalled windows too)now i guess the problem is with ram or mb or cpu..what do you say? Btw how can i check my ram or mb is broken?
hi sir, i have the same problem with my computer..bsods ocuring many times a day..i have an advice that you can recomend this software "whocrashed" that analyses dumb file and display the cause of bsod... Btw "whocrashed" analysed my diff dumb files and it shows diff drivers as the cause like some nvidia,and windows files,i tried replacing my hdd and dosent work(i reinstalled windows too)now i guess the problem is with ram or mb or cpu..what do you say? Btw how can i check my ram or mb is broken?
Most likely the PAGE_FAULT_IN_NONPAGED_AREA BSOD is caused by a driver software bug, such as dereferencing a dangling pointer. A driver software bug is the most likely cause of any other memory access violation BSODs too, such as IRQL_NOT_LESS_OR_EQUAL or KMODE_EXCEPTION_NOT_HANDLED (with 0xc0000005, STATUS_ACCESS_VIOLATION as the first of the 4 parameters).
While the nonpaged memory cannot be swapped out, it can be unallocated, causing a page fault if accessed. Most likely, a dangling pointer just happens to point to an unallocated nonpageable page.
what if i was vista
I have gotten this same error ever since i bought my laptop. I put in new ram and still get the error. Tested it all with memtest. I popped out each stick as well and tested them and still no errors. I believe i have everything up to date software wise on my laptop so i am thinking it is from heat. Is heat something that will cause the BSOD from happening?
also i get 0x0000001E error from time to time
Can we I request a screenshots?
Bill k 2 years ago
some good points thank you.