melissa8781
asked on
STOP error BLUE SCREEN OF DEATH HELP
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 test...no errors. Changed the RAM with working 256MB RAM from other PC. Still errors. What is it? CPU? Motherboard?
NEED HELP NO CLUE!!
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 test...no errors. Changed the RAM with working 256MB RAM from other PC. Still errors. What is it? CPU? Motherboard?
NEED HELP NO CLUE!!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
Take a look at the following web page,
http://aumha.org/win5/kbestop.htm
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:
0x0000007F: UNEXPECTED_KERNEL_MODE_TRA
(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.
http://aumha.org/win5/kbestop.htm
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:
0x0000007F: UNEXPECTED_KERNEL_MODE_TRA
(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.
GL!
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.
GL!
Hi
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
CS
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
CS
ASKER
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.
Could be the other CPU was overheating...
ASKER