I'm running XP Pro SP2 fully updated

I received the following info on a BSOD:

Problem seems to be caused by file win32k.sys

Page fault in non-paged area

Technical Information:

Stop 0x00000050 ( 0xBC0D64A0, 0x00000000, 0xBF8363E5, 0x00000001

Win32k.sys address BF8363E5 base at BF800000, Date Stamp 43446a58


Please advise what may have caused the problem and what steps to take to correct the problem

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Some links here for particular situations:

http://www.aumha.org/win5/kbestop.php


Also for more detail:

Check your Event Viewer via Administrative Tools.

Open the System as well as Application tabs and look for red X errors that coincide with your problem. Details here:

http://support.microsoft.com/kb/308427




Also if your blue screen is showing a memory dump do the following:



Go to start | search (type in) .dmp
Note the location of your .dmp files.
If no .dmp files check for minidump.
Remember this location and the path that leads to it.

Then:

1) Download and install the

Debugging Tools from Microsoft

All you need do is download and install this. Make no attempt to start or run it.

2) Download and install this

debugwiz

This is a DOS based batch file that will command the above Microsoft Tools.

3) Open the Wiz & Browse to, or paste in the path to, your .dmp file.

4) After the Wiz creates a Text document attach it back to this thread.


If you are looking for links on how to interpret this data for yourself try here first:

http://www.wd-3.com/archive/registercontext.htm

was at aumha earlier today ,didn't find anything directly relating--they want $24.for a subscription for a yea; debug to show answers to a specific issue

event viewer shows error 1003 perhaps once/twice a day.

Have debugging tools & debug wiz installed for a long time, never could really understand the results.

Text file attached.

Writing this from my backup system--running Memtest 86 on rig which generated the info.

Thank you so much for responding--hope you can help me through this

Did you check out this link:

You receive a Stop 0x00000050 error on a Blue Screen {KB 894278} Win 2000, Win XP, Server 2003 (with concurrent 1003/System entry in Event Viewer: possible Rootkit spyware infestation)

http://support.microsoft.com/?kbid=894278&sd=RMVP

Had seen article today when I started trying to figure out the issue, but didn't look for:
This error message is caused by a kernel driver that is installed by the following known rootkit spyware programs:
• Msupd5.exe
• Reloadmedude.exe

because I run Rootkit Revealer, F-Secure Blacklight,and Rootkit Buster weekly---my problem has been recurring for several months at random intervals of between 12 and 72 hrs. I also nightly run Webroot SpySweeper which is set to sweep for rootkits, and run V-Com System Suite 7 Pro antivirus (Trend Micro),along w/ several otheranti-spyware progs. Also am behind a Linksys BEFSR41 router

Am running Memtest on the problem rig right now; after 4hrs will stop and advise results (930PM PST).

As soon as thats done, will check Windows for presence of
Msupd5.exe
Reloadmedude.exe
and advise if found or not.

Please advise any other steps to take?

At this point I think you are doing the best you can.

If MemTest comes clean and • Msupd5.exe and • Reloadmedude.exe are not found then we can go from there.

If you have multiple dumps it might also be informative to compare them.

I will advise you as soon as MemTest completes 1 full pass ---when thats done I'll check for everything in http://support.microsoft.com/?kbid=894278&sd=RMVP
and advise you of Memtest results along with all details of findings from following instructions for all procedures in MS support article.
Memtest now 47% complete of 1 pass at 6:21 PM PST

MemTest ran 3hrs 45min w/ no errors.

Msupd5.exe and Reloadmedude.exe were not present in the System32/drivers folder, or anywhere in the Windows folder.

I sent you the 1 dump file I had, will send you any others if/when I get them.
Per the advice of an MS MVP on another help site, I'm boosting my VDimm core voltage (referred to as DDR reference voltage in the bios) from 2.6 to 2.7 ----he feels that 2.6 is too low for the Mushkin Black High Performance level II PC3200 ram (1024 MB 2 x 512 DDR-SDRAM) that I'm running. He feels it needs closer to 3.0 to run w/o it being unstable. The max my bios will set it to is 2.9

Please advise your thoughts re the voltage boost, and the next step(s) you want me to take

It sounds like you are getting good advise. I am not too familiar with voltage issues. This page refers to your error although it was written for Windows 2000:
Stop 0x00000050

Faulty hardware. Stop 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM). If hardware has been added to the system recently, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. You need to run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owners manual for your computer.

Buggy system service. Often, the installation of a buggy system service is a culprit. Disable the service and confirm that this resolves the error. If so, contact the manufacturer of the system service about a possible update. If the error occurs during system startup, restart your computer, and press F8 at the character-mode screen that displays the prompt For troubleshooting and advanced startup options for Windows 2000, press F8. On the resulting Windows 2000 Advanced Options menu, choose the Last Known Good Configuration option. This option is most effective when only one driver or service is added at a time.

Antivirus software. Antivirus software can also trigger this error. Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update.

Corrupted NTFS volume. A corrupted NTFS volume can also generate this error. Run Chkdsk /f /r to detect and repair disk errors. You must restart the system before the disk scan begins on a system partition. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r . For more information about the Recovery Console, see Troubleshooting Tools and Strategies in this book. If the hard disk is a SCSI disk, check for problems between the SCSI controller and the disk.

http://www.microsoft.com/technet/pro....mspx?mfr=true

Per the article.....

Have not installed any hardware for at least a year.

my spontaneous reboot happens intermittently anywhere between 12 and 72 hrs or more, usually happens when I'm away from the computer.

Doubt anti-virus has anything to do with it, but can't disable it for as long as it would take to see if that stops the reboot---I'd be a sitting duck?! Also, have been running System Suite anti-virus for years previous w/ never a problem.

Don't think I have a buggy service---how to check that?--please advise.

Have run chkdsk /f frequently--no issues noted.

It will take up to 4 days to see if the voltage boost solves the problem--will advise results and send you any .dmp files if there is/are crash events.

Please advise re how to check for a buggy service, how to run safely w/o antivirus to see if its the problem (I'm HEAVILY on the internet and even my router is not enough to make me feel safe) and any other things you want me to do.

Thanks again for all the time/help!