Windows Vista forum

General discussion

Sudden series of "IN_NONPAGED_AREA" stops (0x50)

The problems have started about 3 weeks ago on my Server 2008 (x32) machine (please, don't kill me -- have no separate forum on its own, but very similar to Vista from what I hear.) The account of all things will be a short epic, stay with me.

Got a crash with "NONPAGED_AREA" bluescreen, error code 50. Before that, system was rather stable, no crashes in months, and even before that, only on poorly written/ancient programs. But then this started, apparently randomly. Errors are mostly this (paging fault in nonpaged area), with the occasional IRQ_LESS_THAN_OR_EQUAL. It might or might not have something to do with the CasinoSA app that I have installed around that time (removed since then, problems did not cease). I checked the internet, one place suggested it might be due to a memory error (as it sounds obvious anyhow.) Got down to it, ran 6 passes of MemTest86, then another six on MemTest86+, everything prim and proper. Gave it another round, now per module and per slot (one stick at a time), results perfect. Memory testing never gave a freezing or any other indication of problems, neither did the bootable Win on Hiren's BootDVD.

Another suggestion was that it might be due to (impending) HD failure of sort, so I tested the HDs with whatever I had, no failure was found, but noticed that one of the HDs had a very low transfer rate. I thought it might be the culprit, so got a new HD, moved the entire old one to it, turned old one into a windchime. Was a rather old one at any rate, so switching it out wasn't a bad thing, but the problem remained.

The problems have started about 3 weeks ago on my Server 2008 (x32) machine (please, don't kill me -- have no separate forum on its own, but very similar to Vista from what I hear.) The account of all things will be a short epic, stay with me.

Got a crash with "NONPAGED_AREA" bluescreen, error code 50. Before that, system was rather stable, no crashes in months, and even before that, only on poorly written/ancient programs. But then this started, apparently randomly. Errors are mostly this (paging fault in nonpaged area), with the occasional IRQ_LESS_THAN_OR_EQUAL. It might or might not have something to do with the CasinoSA app that I have installed around that time (removed since then, problems did not cease). I checked the internet, one place suggested it might be due to a memory error (as it sounds obvious anyhow.) Got down to it, ran 6 passes of MemTest86, then another six on MemTest86+, everything prim and proper. Gave it another round, now per module and per slot (one stick at a time), results perfect. Memory testing never gave a freezing or any other indication of problems, neither did the bootable Win on Hiren's BootDVD.

Another suggestion was that it might be due to (impending) HD failure of sort, so I tested the HDs with whatever I had, no failure was found, but noticed that one of the HDs had a very low transfer rate. I thought it might be the culprit, so got a new HD, moved the entire old one to it, turned old one into a windchime. Was a rather old one at any rate, so switching it out wasn't a bad thing, but the problem remained.

Next shot at it: graphics card. My original card was a Gainward 8800GTS (tuned to be a Quadro 4600, otherwise I would have had zero drivers under S2008,) this has never truly caused a problem, but lately I did notice some artifacts not present earlier, I thought the card was getting old, or else, a problem with the unified driver. Fooled around with all the various versions of the unified driver, none of them solved the issue. Swapped in a GTX760, which incidentally seemed to run fine afterwards (but then I got a bluescreen again just recently -- the frequency is lower, true dat.)

All the same, after the swap, new and even more annoying errors started to show instead. I got desktop icons disappearing (just generic icon in their place), refresh sometimes helping, sometimes not. Got error messages such as "Not enough storage available to process this command (ReadFromDisk)" or "Insufficient system resources exist to complete the requested service." These came from a variety of programs, and tended to be fine after some one minute on retry. I could not point to a specific program, these errors seem to be plaguing the entire system currently.

I went to safe mode, downloaded some four or five rootkit/malware scanners on another machine, then ran them. Found a few things, but nothing too extraordinary -- indeed, most of what they have found was in there with me knowing, and were utilities that were neither rootkit nor malware by my standards. The few things that were there were removed/disinfected (attachments to emails that I've never ran, but Live Mail saves them in its cache all the same). Also removed Demon Tools while I was at it.

Still, the problem is not solved. I am contemplating whether I should move to Server 2008 R2 (probably would be a huge burden since there is no x32 version anymore, meaning several days' worth of migration hassle) or indeed to Windows 7 (even less favourable, but seeing no more upgrade paths anyhow...) -- I have no idea as to what the root cause of the problem is, and I would like to fix this and avoid the upgrading/migration altogether. I therefore ask your help.

Thank you in advance

Discussion is locked
You are posting a reply to: Sudden series of "IN_NONPAGED_AREA" stops (0x50)
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: Sudden series of "IN_NONPAGED_AREA" stops (0x50)
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
While Demon Tools was not good to read.

In reply to: Sudden series of "IN_NONPAGED_AREA" stops (0x50)

I read this once and found no make and model.

I'm going with the generic advice since details are lacking.

-> Get out the canned air and clean all heatsinks, vents and fans.
-> Now pull off all heatsinks, wipe the compound off, apply fresh and button it up.

I can't count how many times this helps or how many times the client replies "It's not heat."
Bob

Collapse -
HW

In reply to: While Demon Tools was not good to read.

That was about the first thing I've done. Compressed air, vacuum cleaner, a new thermal on pretty much anything except the RAM modules (I wouldn't like to risk disassembling them, I might damage the heatpipe.)

HW-wise: the machine is a GA-X48-DQ6, with an intel core 2 9550 in it. RAM modules from GEIL. House is ThermalTake Tai-Chi, sans watercooling. Power supply is an Odin GT 800W. Keyboard is a Genius KWD-910. Mouse is a Logitech M570. Monitor is an Iiyama X2485WS.

Collapse -
Is this it? Links, comments to follow.

In reply to: Sudden series of "IN_NONPAGED_AREA" stops (0x50)

BOARD: http://www.gigabyte.com/products/product-page.aspx?pid=2763#ov

1. The age of the board would have me inspecting for BAD CAPS. ANY and I mean ANY visual defect and I'm changing motherboards. At the office we don't bother with the board when we see that.

2. While I see BIOS F8D you would want to find F7 at least.

CPU: Small world, similar CPU as in our HP d4999t and d5000.
http://ark.intel.com/products/33924

1. Odd to read about x32 (32 bit OS) in use on what looks to be a very 64 capable machine. I think you're unsupportable as this would lead to very strange issues as the system tries to map all the hardware, video and such in the 4GB space. Nothing would stop me from moving to a 64 bit OS.

2. AHA!!! BIOS SHALL BE F8D -> http://www.gigabyte.com/support-downloads/cpu-support-popup.aspx?pid=2763 calls it out and is non-negotiable.

SYSTEM: Details are incomplete but for now, with the x32 OS you would have 4GB or less RAM. For testing I'd use a single stick.

1. Still sounds like a heat issue but given the above your system designer should be scolded a little.
Bob

Collapse -
moving

In reply to: Is this it? Links, comments to follow.

Well, I don't know. This last one had quite some chaff in it but I'll try to answer all.

1. Examined the caps, as well as all the other common bits of the motherboard.
2. Got absolutely no idea now, from the top of my head, what version the BIOS is, but more than likely it is suitable for the CPU since it never had any issue with it in the past couple of years.
1. When I bought this machine, the desktop version of Windows did not handle more than 3Gb but I had most of my applications' install kits in x32. Server 2000 thus. Even back then, it was capable of addressing the entire 8Gb alright, although individual apps could of course not use more than 3Gb of it (hardly an actual problem). Then I just went along the upgrade path, since as you probably also know, Windows does not support a server OS -> desktop OS upgrade [downgrade?], just the other way round. So it got S2003, then S2008.
Up until now; since in my annoyance/desperation/w.ever now I'm having a Windows 7/x64 on the system, and a good week of hunting down the install kits and reinstalling them from all around. Oh well, that's life, I guess.
2. See above.
1. He's dead in the meantime, and he was one of the few whom I used to call a friend. I won't scold him.

Collapse -
. Got absolutely no idea now, from the top of my head, what

In reply to: moving

". Got absolutely no idea now, from the top of my head, what version the BIOS is, but more than likely it is suitable for the CPU since it never had any issue with it in the past couple of years."

Given what I read it does not matter. I would not proceed until this is known.

"8GB" = Trouble on x32. Sorry but I will nor repeat the prior conversations. Try one stick.
Bob

Collapse -
Did that...

In reply to: . Got absolutely no idea now, from the top of my head, what

Did not mention, but memory testing was done on individual sticks and individual slots. No issues there with either testing software. BIOS is F6. Found an F7 image, but two things delay me in its usage: a) haven't got a single floppy disk anymore in the whole house, and b) from what I recall, the drive is also dead (not sure, but it is for sure unplugged.) Should get a drive and a box of floppies for the purpose?

Collapse -
Again.

In reply to: Did that...

The area of more than 4GB on x32 is a done discussion. You have two areas you must know are trouble with the BIOS and this.

It appears you are not wanting it to be what has been found in the past and want to test ram and disregard prior experiences. I know this will sound cruel but I think you are going to have to take this to a shop counter and pay for repair.
Bob

Collapse -
Two areas of trouble?

In reply to: Again.

I'm sorry, Bob, but I could not understand your last post. What two areas are the ones which I must know are trouble with the BIOS and this? And what do you mean, what has been found in the past? I had no problems using the full 8gb of mem in the past, and even now, it does not quite seem to demonstrate a memory problem. Which bit is broken according to you? Since (I'm sorry to put it bluntly) you made relatively few suggestions so far, memory testing I have even mentioned "done" in the starter post, apart from that you seem to be at most figuring new ways of calling me stupid in a subtle language.
Bringing it to a shop is not an option. I am looking for stuff I can do myself.

Collapse -
Bluntly.

In reply to: Two areas of trouble?

The BIOS version does matter and only the new PC user would dismiss it "because it worked before."

It's a simple thing to check and if you can't do this you seek assistance from a local friend or shop.

The x32 Windows with more than 4GB RAM is an interesting area with troubles and it appears you are unwilling to work or try anything.

As it stands I think you either have to re-think your stance or just take it in for repair. Your choice. I don't mind helping folk but once in a while you encounter folk that are stuck.
Bob

Collapse -
Mkay mkay

In reply to: Bluntly.

Well, for a thing, moved to Server R2 (tried 7/x64 but was painfully slow. This one seems to be doing fine so far). As of the BIOS, shall try F7. Need to get a box of 3 1/2's first. In the meantime, probably going to make a few rounds of Sandra on a what-if basis... Sounds cool Y/N?

Collapse -
Why F7?

In reply to: Mkay mkay

I detailed links and more which showed F8D to be the right version unless they have changed their web site recently.

Sadly and I know this is all annoying minutia, I fear you will need to let a good shop sort this out.
Bob

Collapse -
But for the record...

In reply to: Bluntly.

Whoever said that I was hell-bent on staying x86? I mentioned quite the opposite above, in fact.

Collapse -
Then check that BIOS

In reply to: But for the record...

That's a trivial item that I would have completed to tick it off the list of what's been discovered so far.

It appears you need some local help as even small items appear to have no movement or resolution.

-> I see some old and new PC users that get stuck in a loop like this. Usually they move after time or just fade away or get other help.

I can't guess why we can't get the BIOS check and the single ram stick testing done. And I do not mean running MEMTEST. I mean trying out the OS that has been faulting.
Bob

Collapse -
Bios

In reply to: Then check that BIOS

Well, the board's got dual bios that are checked against each other at system boot. If they don't match, the backup bios is used to overwrite the active one. The only thing modifying the backup bios is the official update util (startup time). In this way, it is unlikely that the bios got corrupted, considering I saw no indication of the reflash procedure. Would also get notification on battery close to failing, which so far has never ever happened.
Trying the OS that's been faulting is not possible now, on account of the machine having been moved to x64/R2.
And while trivial, it never really occurred to me that I should update the BIOS for whatever reason, since seeing the changelog, there was nothing relevant specifically to my config. But fain, gonna get a box of floppys tomorrow and give it a shot - it probably cannot hurt.

Collapse -
This many posts

In reply to: Bios

And I can't tell what BIOS is currently in use.

I supplied links and why F8D so my thought here is you need your local support to chime in. I think I've given you some good information yet after this many posts you never revealed the current BIOS version.

Now you are looking at changelogs and I'm guessing ignoring the maker's own web page at (repeating link from above) -> http://www.gigabyte.com/support-downloads/cpu-support-popup.aspx?pid=2763

Collapse -
Sorry, did not mention in specs...

In reply to: This many posts

CPU is Q9550, stepping 7, revision C1. BIOS is F6. According to the table, it is supported in F6.

Collapse -
Hm. So the thing got too long...

In reply to: Sudden series of "IN_NONPAGED_AREA" stops (0x50)

never really used fora before -- did not know they would have a problem on it.

Collapse -
Again, I see it at link.

In reply to: Hm. So the thing got too long...

http://www.gigabyte.com/support-downloads/cpu-support-popup.aspx?pid=2763

"Core™ 2 Quad Q9550 2.83GHz 12MB Yorkfield 45nm E0 95W 1333 F8D"

Good to read you have another CPU but this many posts and only now we learn the stepping and that looks to indeed be an older BIOS.

-> Given all these posts and you are still having issues, it's clearly a blunder by the supplier. Let them fix it or take it up with your local support. It's OK that you don't see the problems but at this point you seem reticent or unable to share details that I would use to look into this further.

I'll share I would have no issue of bumping it to the latest BIOS as well as an OS re-load at this point since Daemon Tools was on the machine. It's been a hit or miss app in my experience and some machines never come back. Definitely not something we let into the office.
Bob
Collapse -
Carry on posting here.

In reply to: Sudden series of "IN_NONPAGED_AREA" stops (0x50)

Dafydd.

Collapse -
Supplier...

In reply to: Sudden series of "IN_NONPAGED_AREA" stops (0x50)

Well, there's none really. I used to live in another country, bought the bits and pieces from three different sources, and incidentally the company from which I've bought the motherboard has already gone down. There was an issue with the original motherboard (liquid cooling pump [integrated into the Thermaltake Tai-Chi house] broke and leaked, but apart from the board, everything else survived it well), through some enormous luck I managed to find a back shed unused motherboard in one of the shops, no-one wanted to buy it but they did not feel like sending back -- same edition of the board, so it was good to go... So that's how my machine survived.

Collapse -
And details...

In reply to: Sudden series of "IN_NONPAGED_AREA" stops (0x50)

Do not know which ones would have been needed, but as it is now, there's a Server 2008 _R2_ installed, slowly getting stuff back from the backup that I made for the purpose. No data loss visible currently, but I can tell many software support houses are not quite keen on swapping my existing licences to the x64 ones. Oh well, guess I will try my best.
At any rate, thanks for the assistance, but in all likelihood, this will be of no further use -- seeing that we're talking about a completely different system now, that (crossing fingers) manifests no apparent problems. My current bet is on a worm/virus that might have been on the system silently for a while, but suddenly was "fixed" by either the video card driver or some Windows update -- in which case the square one install of the system is actually a much better bet.

Popular Forums

icon
Computer Newbies 10,686 discussions
icon
Computer Help 54,365 discussions
icon
Laptops 21,181 discussions
icon
Networking & Wireless 16,313 discussions
icon
Phones 17,137 discussions
icon
Security 31,287 discussions
icon
TVs & Home Theaters 22,101 discussions
icon
Windows 7 8,164 discussions
icon
Windows 10 2,657 discussions

SMART HOME

This one tip will help you sleep better tonight

A few seconds are all you need to get a better night's rest.