win32k.sys BSOD page_fault_in_nonpaged_area? 0x00050 stop

[cdietschrun]

I have been having this problem recently, and I pretty much have no idea how to fix it.

I have

ASUS P5ND2-SLI w/ 0601
PD 805, frequencies at 180/100 (CPU/Memory)
GeForcce 7900GT 256MB w/ 84.43

I can give any other information needed, woudl really love if we could fix this. Thanks.

[mdcomp]

Welcome to the forums my friend! Though I don't specifically know about your problem, I was sure that someone else did, I looked around and found something for you:

Bugchecks Explained: PAGE_FAULT_IN_NONPAGED_AREA (http://www.osronline.com/article.cfm?id=335)

My first step when troubleshooting a problem is always searching viaOC Forums search (http://www.ocforums.com/search.php), Google search (http://www.google.com) and if the problem relates to windows a Microsoft Knowledge Base (KB) search (http://support.microsoft.com/search/?adv=1). That is always the best way to start, if all else fails, then come here and post as much information as you can and you will receive plenty of assistance.

Hope that helps. Best of luck! And a speedy recovery to that pc of yours.
:)

Matt

[redduc900]

Assuming you're running either XP or W2K, open Event Viewer (Start | Run | Type eventvwr.msc, and click OK) in order to access the error logs, and check for STOP: 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA errors | Right click the latest crtical error you've received related to the above fault (critical errors are in Red), and select "Properties" | Copy and paste (use the "Copy to Clipboard" button under the arrow butons in the Event Properties" window) the latest critical error message as it appears under the "Description" field, and post it in this thread.

The next time you receive the error, you may instead want to click the "click here" link at the bottom of the message box, and make note of the error signature information. Either way, it would be more helpful to us if you could provide the STOP error message in it's entirety. In the meantime return your OC to default settings, and test your RAM by running Memtest86 3.2 which you can download from Majorgeeks here...

Memtest86 3.2
http://www.majorgeeks.com/download1247.html

Run a virus scan, making sure you have the latest DAT files loaded for your scanner, then run Spybot S&D to check for spyware / malware...

SpyBot-Search & Destroy 1.4
http://www.majorgeeks.com/SpyBot-Search_&_Destroy_d2471.html

[mdcomp]

Thanks for showing me up, redduc900. You da' Man!
:p

On second thought, this really belongs in Microsoft Operating Systems. Moved.
:)

Matt

[cdietschrun]

Well I looked through the event viewer and I dont see anything specific that talks about anything remotely related to my problem. I spent about an hour looking and don't see anything.

I'm going to run the Memtest, adaware and S+D now.

Next time I get the BSOD ill write down most of the information and post it, but its pretty similar to what I posted.

[cdietschrun]

update- I can't run memtest because I don't have a floppy drive. Or a floppy disk.

[Flamed_Chip]

You can get memtest on the Ultime Boot CD (http://www.ultimatebootcd.com/)

[cdietschrun]

Dont have a CDRW... grr

[cdietschrun]

OK I just had another BSOD that had something to do with IRQL_IS_NOT_EQUAL or something like that-- I think it may have something to do with the heat.

I think this is the specific event for that crash

Error code 1000000a, parameter1 00000054, parameter2 0000001c, parameter3 00000001, parameter4 80501ff4.

[Captain Newbie]

Dont have a CDRW... grr
Wow, you're having a bad day. Welcome to the forums.

OK I just had another BSOD that had something to do with IRQL_IS_NOT_EQUAL or something like that-- I think it may have something to do with the heat.

I think this is the specific event for that crash

Error code 1000000a, parameter1 00000054, parameter2 0000001c, parameter3 00000001, parameter4 80501ff4.
Hardware problems? Reduce to stock volts/freqs, check cooling setup.

[redduc900]

It really makes no sense to keep posting STOP errors if you don't follow our advice, and then post the results...

1. You need to figure out a way to run Memtest, and then post the results.
2. What were the results of the virus scan?
3. What were the results of running Spybot S&D?
4. Did you return your OC to the default clock settings, including your VC clocks?
5. What were the results of mdcomp's suggestions afa checking the MSKB, and performing a forum's search? The faults you're receiving are all explained in Captain Newbie's sticky (Windows32: The Whys and Hows of Stop Errors) at the top of this forum, and have been discussed many times in the past in previous threads in this forum.
6. What were the results of following his link to the article describing the PAGE_FAULT_IN_NONPAGED_AREA bugchecks?

... and you still haven't even made mention of which OS you're running (including any SP installed). And when posting the contents of a BSOD, we need to know the EXACT error message as it appears on the blue screen, NOT...
OK I just had another BSOD that had something to do with IRQL_IS_NOT_EQUAL or something like that
... and also what you've done afa troubleshooting since the time when you received the first BSOD.

[Captain Newbie]

5. What were the results of mdcomp's suggestions afa checking the MSKB, and performing a forum's search? The faults you're receiving are all explained in Captain Newbie's sticky (Windows32: The Whys and Hows of Stop Errors) at the top of this forum, and have been discussed many times in the past in previous threads in this forum.
A handy link to that thread is conveniently located in my sig, to reduce member workload. :)

[DragonTattooz]

It's your RAM that is causing the problem.

[cdietschrun]

I have absolutely no idea how to run memtest. I have no floppy drive and no cdRW drive.

The error I got earlier today is:

"This problem was caused by :"win32k.sys"
PAGE_FAULT_IN_NONPAGED_AREA
STOP: 0x00000050 (0xf000E81A, 0x0000000, 0xBF8A1CB3, 0x00000000)

Techincal specifications:

win32k.sys - address BF8a1CB3 based at BF800000 DateStamp 43446a58.

This is copied and pasted from eventvwr.msc:

"Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 5/18/2006
Time: 5:33:37 PM
User: N/A
Computer: CHRIS-SSUG1I61R
Description:
Error code 10000050, parameter1 f000e81a, parameter2 00000000, parameter3 bf8a1cb3, parameter4 00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 31 30 30 30 30 30 35 1000005
0020: 30 20 20 50 61 72 61 6d 0 Param
0028: 65 74 65 72 73 20 66 30 eters f0
0030: 30 30 65 38 31 61 2c 20 00e81a,
0038: 30 30 30 30 30 30 30 30 00000000
0040: 2c 20 62 66 38 61 31 63 , bf8a1c
0048: 62 33 2c 20 30 30 30 30 b3, 0000
0050: 30 30 30 30 0000 "

I am running Windows XP Home SP2.
I ran adaware with the latest updates and found errors, had the stop error a few minutes later.
I ran spybot search and destroy, found errors also, had the stop error afterwards ( ran this right after Ad-aware).
I did not return any of my OC settings back to stock.

I am now runnig WinDBG and also have read over CaptainNewbie's page.

[cdietschrun]

BTw, this is the RAM I bought am currently am using.

http://www.newegg.com/Product/Product.asp?Item=N82E16820211012

[cdietschrun]

OK

-- I could not figure out how to use WinDbg for the life of me if it was the only thing I had to do to save my life I'd be buying my headstone.

In reading Captain's post, one person talks about the PAGE_FAULT error being solely a RAM issue. With not a clue how to run memtest, im going to see if the RAM Is possible unlodged in the case, but in all likelyhood this is not it. It gives an idea to lower the VDIMM?

What is that? How to change that?

I have the frequency of the memory at 100mhz right now, my multiplier in my BIOS ranges from 400-1600 and I have it set at 400.

Im looking at my CPU-Z and it also says that my RAM is in single-channel mode... I heard from someone I need to have my RAM in slots 1 and 3 or 2 and 4 to make most of it?

Also about the timings of a RAM module-- no idea how to check that or change that, someone said that might be part of the problem.

That is most of the information I can provide-- sorry for being so vague at the start, I had posted this somewhere else and I thought I had included the same information...

Any help to get rid of this at baby steps would be appreciated.

[Captain Newbie]

If you are at stock volts/freqs already, don't worry about screwing with 'em. Save the stuff you care about, and then format the drive and reinstall Windows.

[DragonTattooz]

You can run MemTest from Windows, but I'm pretty sure the preferred method is to run it from the BIOS, if your mobo is so equipped, or from a floppy.

I think one of these will work, but I'm not 100% sure. Memtest86 (http://www.memtest86.com/#download0)
I know there is a version that can be run from Windows because I did it that way before I found out that it was pre-loaded in my BIOS.:bang head

[cdietschrun]

All of that I posted and you say to reinstall Windows? I don't see how it could possibly be my OS. Plus, I said I am not at stock volts or anything like that. I still have everything in my OC settings. What about the VDIMM, what about the timings?

I don't see how that link lets me run memtest from windows. It wants a floppy or CD rom. Which I have neither. I might have to buy a friggin external floppy drive just to find out that my RAM is busted? this sucks...

Does anyone else have any input? I don't see how it's my OS.

[Captain Newbie]

I *said*, drop to stock volts and freqs and SEE if the problem recurs.

Here's usually the order and precedence of foulups that cause STOP errors.
1) Running too fast/with too high voltages—can be resolved by reducing your OC.
2) Driver problems or miscellaneous Windows crap including viruses and actual bugs in the OS—occasionally resolvable through clean install.
3) Hardware problems—rub money on the system and see what happens. If it still doesn't work, rub more money on it.

[cdietschrun]

OK. Before I change my OC settings, I managed to get a floppy drive working and I'm still unsure what's going on when I boot with it. I just get a bunch of random lines of numbers and letters scrolling that does nothing until I restart... is that the test itself?

[redduc900]

You're obviously unfamiliar with overclocking, and as such I'd suggest returning your system to either it's Optimized Defaults or Failsafe Defaults settings by way of the BIOS (like Captain Newbie suggested, but you obviously refuse to do), and see if you still encounter problems. Regarding all of your OC'ing questions, my first suggestion to you is to start reading the various stickies at the top of the individual forums. Secondly, I'd suggest leaving your system at stock until you fully understand what the various BIOS settings are for and what changing them will affect.
Does anyone else have any input? I don't see how it's my OS.
Your OS install is more than likely fubared caused by your inexperience and lack of knowledge regarding overclocking. Take Captain Newbie's advice, and reinstall Windows at default BIOS settings, changing only those settings that are absolutely necessary for Windows to correctly install. Only after you fully understand what all of your different BIOS settings are for, and what each one does (including the effects of incorrect BIOS settings on the OS)... should you even begin to start OC'ing.
I managed to get a floppy drive working and I'm still unsure what's going on when I boot with it. I just get a bunch of random lines of numbers and letters scrolling that does nothing until I restart... is that the test itself?
If you're referring to what's going on when you boot to Memtest, then the "random lines of numbers and letters scrolling" are memory errors. Return your system to default settings, and re-run Memtest through all of the tests... you should have 0 errors (any errors that appear during the test is an indication of incorrect BIOS settings, faulty RAM, bad memory controller, etc.)

[cdietschrun]

OK I hear what you're saying.

It seems like MemTest isn't testing anything, though. I just boot with the disk in and all it does is display a list of "Ax0001" or "Cx8010" something like that. I even left the thing runnnig all night... It never gave me a prompt or anything. Is that the entire test? There was nothing that seemed like a test. If that was it, does that mean I need new RAM?

[Captain Newbie]

OK I hear what you're saying.

It seems like MemTest isn't testing anything, though. I just boot with the disk in and all it does is display a list of "Ax0001" or "Cx8010" something like that. I even left the thing runnnig all night... It never gave me a prompt or anything. Is that the entire test? There was nothing that seemed like a test. If that was it, does that mean I need new RAM?
You probably got a bad disk image; go download and burn the latest knoppix, and follow the included instructions on how to start memtest from there. (That's one way of running Memtest — it is included as part of the newer Knoppix builds, as I recall correctly, and because I always have a LiveCD lying around that's how I do it. The official Windows instructions for installation and operation of Memtest86 may be found here (http://www.memtest86.com/#install).)

It should give you a prompt.

And —
Known Problems

Sometimes when booting from a floppy disk the following messages scroll up on the screen:

X:8000
AX:0212
BX:8600
CX:0201
DX:0000
This the BIOS reporting floppy disk read errors. Try re-writing the disk. If that does not work replace the disk.