 Consant Bsod |
Welcome Guest ( Log In | Click here to Register a free account now! )
Register a free account to unlock additional features at BleepingComputer.com
Welcome to Bleeping Computer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.  |
 Dec 18 2007, 10:18 PM
Post
#1
|
|
|
New Member  Group: Members Posts: 1 Joined: 28-November 07 Member No.: 173,276  |
P.S. 0x00000050 (0x8F1E4492, 0x00000001, 080D6F6A9, 0x00000000) Anyone know what this means? I think its the error code or something. one of hose Page_Fault_In_Non-Paged_Area Errors. |
 |
 
|
|
Dec 20 2007, 07:13 AM
Post
#2
|
|
 Still visually handicapped, new avatar :0) Group: Global Moderator Posts: 15,531 Joined: 2-October 05 From: Southeastern CT, USA Member No.: 35,824 |
There's lot's of things that can cause a STOP 0x50 error ( http://aumha.org/a/stop.php#0x50 ). Have you tried the Startup Repair? What was the result (and any error codes that you may have received)?
Since you can't get into Safe Mode, I'd tend to think that the software conflicts aren't very likely here (although a Windows corruption could cause the same thing). With this in mind, I'd first suggest testing your memory with a bootable memory tester such as the free one here: http://www.memtest86.com/ If that doesn't reveal a problem, I'd suggest a careful review of what was done to the system just prior to this problem (to see if it'll give any hints as to what caused it). Such as adding software or hardware - or changing or removing it. It could also have been caused by moving the system or hooking up new or existing hardware, power surges, etc, etc, etc. After that, I'd try stripping the system down to the bare minimum to get into Windows to see if any of the hardware that you've removed caused it. Then it's a matter of testing the remaining hardware (usually by replacement of parts) to see if the problem is there. On a hunch, I'd test the video card first (since it's hardware and it has the Video RAM on it). This post has been edited by usasma: Dec 20 2007, 07:18 AM -------------------- - John
**If you need a more detailed explanation, please ask for it. I have the Knack. ** BTW - the avatar pic is a camel as it looks back at me while I'm in the saddle (and he wasn't happy!) |
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
| Lo-Fi Version | Time is now: 9th January 2009 - 02:54 AM |
© 2003-2008 All Rights Reserved Bleeping Computer LLC.