Mag Posted February 28, 2005 Share Posted February 28, 2005 Desktop recently crashed, or some sort, Had a blue screen displaying this message: A problem has been detected and windows has been shut down to prevent damage to your computer. PAGE_FAULT_IW_NONPAGED_AREA If this is the first time you 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 window updates you might need. If problem continue, disable or remove any newly installed hardware or software. Disable options such as caching or shadowing. If you need to use software to remove or disable components, restart your computer, Press F8 to select Advanced Startup options, and the selec state mode. Technical Information *** STOP: 0x00000050 COXBADOB138, 0x00000000, 0x805550FF, 0x00000000 Begining dumped physical memory. Physical memory dump complete. Contact your system administrator or technical support group for future assistance. Then I reboot and everything ran fine til the third startup. I got into desktop and recieve this: any idea ? it looks like a serious issue. Link to comment Share on other sites More sharing options...
Robert Posted February 28, 2005 Share Posted February 28, 2005 Your typo doesn't help matters. It seems that error can be caused by any number of things, the main culprits being something you recently installed (a hardware driver), OR bad ram. 0x00000050 PAGE_FAULT_IN_NONPAGED_AREAThis error indicates that invalid system memory has been accessed.Parameters On the blue screen, the following parameters are displayed: Memory address referenced. 0: Read operation1: Write operation Address that referenced the memory (if known) Reserved If the driver responsible for the error can be identified, its name is shown on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.Cause This error is usually caused by the installation of faulty hardware or by failure of installed hardware - usually defective RAM, Level 2 Cache or Video RAM. Another common cause is the installation of a faulty system service or the corruption of an existing system service. Antivirus software can occasionally trigger this error, as can a corrupt NTFS volume. Resolving the problem Resolving a faulty hardware problem: 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 should run hardware diagnostics supplied by the system manufacturer. For details on these procedures, see the owner's manual for your computer. Resolving a faulty system service problem: 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 menu that displays the operating system choices. At the resulting Windows 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. Resolving an antivirus software problem: Disable the program and confirm that this resolves the error. If it does, contact the manufacturer of the program about a possible update. Resolving a corrupted NTFS volume problem: 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 the hard disk is SCSI, check for problems between the SCSI controller and the disk. Finally, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Disabling memory caching of the BIOS might also resolve it. Link to comment Share on other sites More sharing options...
Gryph Posted February 28, 2005 Share Posted February 28, 2005 This is what happens to people who put their system specs in their sigs. Anyway, next time your system starts, try to delete that sysdata.xml file. Also, do the CHKDSK thing that robbbert mentioned in his post. Another thing I suggest doing is clearing your pagefile. A long time ago I got an error like that and that was the solution to it. I don't know if it will do the same for you. But yes, that is a serious problem. Back up all your important crap just in case. This is why I recommended making a Windows partition on your harddrive in case crap like this happened. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now