Hi guys

This error happens and restarts the pc. Could be running 2 min or 2 hrs...

Blue screen of death. Need help with STOP ERROR 0x0000007f 80042000 0000000 000000
Beginning dump of physical memory...

Pentium 3/933 Mhz
128 PC 133 SDRAM

XP has freshly been installed. New power supply. I have tested the memory using memtest and bios errors. Changed the RAM with working 256MB RAM from other PC. Still errors. What is it? CPU? Motherboard?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
melissa8781Author Commented:
Thanks leew...I want to add that I have changed the BIOs CPU settings to the defaults (normal not turbo). I'm just trying to find out what it is so I can replace the hardware (if it is the hardware?).
Lee W, MVPTechnology and Business Process AdvisorCommented:
The link suggests that it is good change memory related.  However, if you've put known good memory in the system, you can't eliminate the POSSIBILITY that the memory subsystem of the motherboard is somehow fried.  You can try swapping memory slots - see if that helps.  And there's always the chance it's not the motherboard or the memory.
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Take a look at the following web page,

which is presented using frames.  Click on the error code (7F) in the left pane of the page, which is a link to the following quotation:

(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1558.)
One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause (many dozen KB articles exist for this error referencing specific hardware failures) and, of these, memory hardware failures are the most common.
General Causes {KB 137539} Win NT, Win 2000, Win XP
Windows Stops Responding with Stop Error 0x7F Error Message {KB 814789} Win 2000, Win XP (when running Terminal Services)
Windows NT 4.0 Setup Troubleshooting Guide {KB 126690} NT 4 (Recommendations for the current error message are buried down inside this article, which isn’t necessarily limited to NT 4.)

You should go to the actual page in order to read the links given in the quotation above.
hey Melissa, are you confortable playing with your pc hardware???

If yes, look to see how many memory chips you have on your motherboard.

If you have to chips, take one at the time and see which one is causing that BLue screen to come up.

Try to move your memory around with the available slots you have on the motherboard.

Like leew mentionned, there is really not much to do except playing with the memory chipset.

Dont bother looking any where else for anything else to cause this problem...focus on the memory.

If changing the memory gives the same error message (as you appear to have said), then its not the memory. Intel processors almost never fail (given adequate cooling), so its probably the motherboard... :(

Last ditch try would be to remove everything non-essential from the computer and see if that helps, also try 'underclocking' the processor to 100MHz FSB instead of 133.

Good luck Melissa
melissa8781Author Commented:
Hate to say it but it was the CPU.. I replaced it with a working celeron I had laying around and the error message no longer showed its face. Thanks anyway for trying to help.
Lee W, MVPTechnology and Business Process AdvisorCommented:
Could be the other CPU was overheating...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.