blue screen came on with the code stop;oxooooooc2, oxooooooo7, oxooooocd4, oxoooooooo, ox8oo1d1b8, beginning dump of physical memory do you have any ideas
2007-05-27 00:12:57 · 11 answers · asked by Anonymous in Computers & Internet ➔ Other - Computers
I would say, something updated and did not go right...I doubt the pc is on its last legs as another poster commented. If you are able to get the pc loaded up, try doing a system restore point to a previous day. If not, try loading in safe mode (usually tapping F8 key when loading).
2007-05-27 00:17:35 · answer #1 · answered by John K 6 · 0⤊ 1⤋
If they happen outside of games you may have a physical memory problem.
Those look like errors caused by another application intruding into windows memory space. If it happens just in one or two games you may want to uninstall as many applications as possible, trying the offending application after each uninstall. Also try reinstalling the offending app.
It could be. You may want to install the latest drivers and directx if they are dx games.
Have you checked your "Event Viewer" for any hanging applications & error messages yet?
Start > Control Panel > Administrative Tools > Event Viewer
Click on "Application" in the left panel & see what errors may be recorded in the right side panel. You can then click on the error & right click for "Properties" & it will display more info.
Do the same to "System" & "Security" (& "antivirus" if that entry is there - some do some don't).
Your computer is producing a memory dump. This can be used for later diagnostic purposes to determine the cause of the crash, and then configure the system to avoid a crash.
Open Control Panel -> System Control Panel -> Advanced tab -> Startup and Recovery settings button. On the dialogue determine what type of dump is being produced (minidump, kernel dump or full dump).
If it's a minidump, look in c:\windows\minidump (or whereever the system is configured to save dump files in the dialogue above). Grab the 3-4 most recent files and post them up on the web someplace where there can be downloaded fro analysis.
If you have a kernel or full dump, you probably need to look for c:\windows\memory.dmp (again, the path is configured in the dialogue above). If you have a full dump, change the config to kernel or memory dump (generally a BSOD occus in kernel mode, and we don't need a full dump).
2007-05-27 00:23:24 · answer #2 · answered by The Thinker 6 · 0⤊ 0⤋
It may only be a glitch in Windows caused by a program or driver that was running. If you have updated any drivers lately, that may be the cause. Of a more serious nature would be a device having a problem and crashing Windows, such as a video or sound card going bad.
2007-05-27 00:15:40 · answer #3 · answered by The::Mega 5 · 0⤊ 0⤋
W/ PC unplugged, try clearing CMOS through the jumper or removing the CMOS battery for about 30 seconds.
Plug PC, power ON, press F1 or Del to enter BIOS menu. Load fail safe defaults. Save and exit. You should be back in business.
A power glitch on the low voltage rail may have caused memory error and corrupted CMOS settings.
2007-05-27 00:23:56 · answer #4 · answered by Karz 7 · 0⤊ 0⤋
Emachines has been usual to apply defective hardware to diminish expenses. I had an emachines for 5 years however formerly my potential grant purely stoped working, in case you got the laptop a month in the past you're probably nevertheless under guarantee so which you will likely deliver it in to have some hardware replaced
2016-10-08 22:30:03 · answer #5 · answered by Anonymous · 0⤊ 0⤋
1. When booting just hit the F8 key and choose Safe Mode.
2. Save any files you may need.
3. If you are novice try reinstalling Windows with the laptop's instructions.
4. If not, install Linux. :-)
2007-05-27 00:21:44 · answer #6 · answered by idan_slack 2 · 0⤊ 1⤋
Usually there is more information given with BSODs. If this is happening at startup and keeps repeating, then its bad. In that situation, a RAM or motherboard RAM slot issue is a possbility.
If it just happened one time seemingly randomly while you were in windows it could have just been caused by a device driver.
2007-05-27 00:18:48 · answer #7 · answered by Kris 2 · 0⤊ 0⤋
When windows is not shut downed properly than this memory dump error comes, it's normal & what you should do is open in safe mode & from command prompt run scandisk your problem will vanish.
2007-05-27 00:18:38 · answer #8 · answered by Anonymous · 0⤊ 0⤋
Is there nothing more specific on the screen? Sounds like it might be driver or an update. Have you installed something new recently?
2007-05-27 00:17:08 · answer #9 · answered by ChibiKris 3 · 0⤊ 1⤋
TROUBLESHOOTING WINDOWS STOP MESSAGES
http://aumha.org/a/stop.htm
2007-05-27 00:18:53 · answer #10 · answered by Anonymous · 0⤊ 0⤋