A problem has been detected and Windows has shut down to prevent damage to your computer.
PAGE_FAULT_IN-NONPAGED_AREA
If this is the first time you've seen this Stop error screen, restart your computer. If this screen appears again, follow these steps:
Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.
If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use Safe Mode to remove or disable components, restart your computer, press F8 to select Advanced Setup Options, and then select Safe Mode.
Technical Information:
*** STOP: 0x00000050 (0xFF2950FC, 0x00000000, 0x80571694, 0x00000000)
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further assistance.
There is no new hardware or software on this machine. The crash came right after startup; I had just shut down excess startup programs and was about to get online. I don't recall if I clicked the browser icon before the crash occurred or if I was just about to.
The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.
Interpreting the Message
This Stop message has four parameters:
1. Memory address that caused the fault.
2. Type of access (0x00000000 = read operation, 0x00000001 = write operation).
3. If not zero, the instruction address that referenced the address in parameter 0x00000001.
4. This parameter is reserved (set aside for future use).
Resolving the Problem
The following suggestions are specific to Stop 0x50 errors. For additional troubleshooting suggestions that apply to all Stop errors, see "Stop Message Checklist" later in this appendix.
* If you added new hardware recently, remove and replace the hardware to determine if it is causing or contributing to the problem. Run diagnostics software supplied by the hardware manufacturer to determine if the component has failed.
* Stop 0x50 messages can also occur after installing faulty drivers or system services. If the file name is listed, you need to disable, remove, or roll back that driver. If not, disable the recently installed service or application to determine if this resolves the error. If this does not resolve the problem, contact the hardware manufacturer for updates. Using updated drivers and software is especially important for network interface cards, video adapters, backup programs, multimedia applications, antivirus scanners, and CD mastering tools. If an updated driver is not available, attempt to use a driver from a similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000 might temporarily resolve the problem.
THIS sort of thing is why I laugh at people who go 'OMG no teh bluescreen on XP!' Rogue, first thing I'd try is memory, that error can mean a RAM problem somewhere. Also, video card, if it's a problem with the onboard memory there. Beyond that...can also be a driver fruityness of some sort. Can you start in safe mode?
Chronological Incontinence: Time warps around the poster. The thread topic winks out of existence and reappears in 1d10 posts.
Out of Context Theatre, this week starring Darth Nostril.
-'If you really want to fuck with these idiots tell them that there is a vaccine for chemtrails.'
Seconded. Last time I've got the BS is when one of my memory chip (on my notebook) is damaged. That's the reason I'm browsing from pubic internet service now because running XP with 128 Mb sucks like hell!!!
White Haven wrote:THIS sort of thing is why I laugh at people who go 'OMG no teh bluescreen on XP!' Rogue, first thing I'd try is memory, that error can mean a RAM problem somewhere. Also, video card, if it's a problem with the onboard memory there. Beyond that...can also be a driver fruityness of some sort. Can you start in safe mode?
How the hell do you think I posted this? Safe mode was completely unnecessary. It worked fine the second time I started and hasn't screwed up since.
White Haven wrote:THIS sort of thing is why I laugh at people who go 'OMG no teh bluescreen on XP!' Rogue, first thing I'd try is memory, that error can mean a RAM problem somewhere. Also, video card, if it's a problem with the onboard memory there. Beyond that...can also be a driver fruityness of some sort. Can you start in safe mode?
How the hell do you think I posted this? Safe mode was completely unnecessary. It worked fine the second time I started and hasn't screwed up since.
Call me paranoid but I usually went that far following a blue screen, reformatting my hard drive, reinstalling the O/S fresh, and restoring everything from backup.
Kreshna Aryaguna Nurzaman wrote:Seconded. Last time I've got the BS is when one of my memory chip (on my notebook) is damaged. That's the reason I'm browsing from pubic internet service now because running XP with 128 Mb sucks like hell!!!
Thirded, I got BSODed over and over because Windows XP didn't like my graphics card.
The weird thing is that I took it out, put it in ANOTHER computer running Windows XP Pro, installed the SAME driver, and it worked perfectly.
I've had this problem before, sounds pretty similar to mine in that it's intermittent and random. Turns out my RAM was in the wrong order, just swapped the chips around and problem solved.
Agitated asshole | (Ex)40K Nut | Metalhead The vision never dies; life's a never-ending wheel
1337 posts as of 16:34 GMT-7 June 2nd, 2003
"'He or she' is an agenderphobic microaggression, Sharon. You are a bigot." ― Randy Marsh
I'd still run memtest86 overnight just to be sure. (Run all of the tests, not just the standard 8.)
"I once asked Rebecca to sing Happy Birthday to me during sex. That was funny, especially since I timed my thrusts to sync up with the words. And yes, it was my birthday." - Darth Wong
Leader of the SD.Net Gargoyle Clan | Spacebattles Firstone | Twitter
Safe mode was completely unnecessary. It worked fine the second time I started and hasn't screwed up since.
