Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

Computer shutting down - I need interpretation of message.

by Margeor Apr 20, 2005 8:14PM PDT

Latest message:Numerous reports have been created and forwarded to Microsoft - this a.m. shut down and following appeared on screen:
A problem has been detected and windows has been shut down to prevent damage to your computer.
If this is the first time you?ve seen this stop error screen, restart your computer. If this screen appears
again, follow these steps:
Check to be sure you have adequate disk space (I do). If a driver is identified in the stop message,
disable the driver or check with the manufacturer for driver updates. Try changing video adapters.
Check with your hardware vendor for any bios updates. Disable BIOS memory options such as
caching or shadowing. If you need to use safe mode to remove or disable components, restart your
computer, press F8 to select Advanced Startup options, and then select safe mode.

Technical info: Stop:0x000008E (0xc000005,0x01A00023, 0xF1CE1AB4,0x0000000)
Beginning dump of physical memory.
Physical memory dump complete
Contact your system administrator or technical support group for further assistance.


Serial No. is 0000-0D35 ? check File System on C ? FAT32

Discussion is locked

7 Posts
- Collapse + Expand Details
- Collapse -
STOP error codes
by MarkFlax Former Forum moderator Apr 20, 2005 8:40PM PDT

Margeor,

There's a list of STOP error codes here;

http://aumha.org/win5/kbestop.php . Scroll down to 0x000008E, (note it is 5 zeros not 6), and find the Microsoft link for this STOP error.

If you can't, the microsoft link is here

It says pretty much what you have been told, and it gives some options further down the page for you to consider.

In particular it suggests checking the Event Viewer log (Right click My Computer, select "Manage", then under System Tools > Event Viewer > System, view the log and highlight, right click and select properties of any errors). that may pinpoint which device or driver may be causing the problem.

Good luck. Perhaps others here with better technical knowledge can give you more advice.

Mark

- Collapse -
had the same problem only other error code
by vera kofler Apr 20, 2005 9:21PM PDT

Did everything possible, from reformating to review all drivers well everything and finnaly had to replace the motherboard, processor video card and since than almost a year ago my comp does not present any more problems, by the way thats why I dicovered this forum, hope you are more lucky than I was, it was expensive but worth

- Collapse -
Mystery problem solution, ... maybe.
by dromel May 20, 2005 3:27PM PDT

Similar problem several years ago with Win 98SE. To skip the 6 month long odyssey, the culprit turned out to be a bad RAM chip, but it drove everyone crazy along the way. (i.e. 256 in only 255 out, seeminly random error codes )

Before replacing mother boards, video cards, drivers, try having your RAM tested, or switch out with a working PC. Cheap and easy, but will either solve the problem, or eliminate one more component.

Good luck

- Collapse -
to test memory
by fkfrankie3 May 20, 2005 11:59PM PDT
www.memtest.org is a good site to look at to find a great software memory tester, you create a bootable CD or floppy and it reports any memory errors. that or search around microsoft.com for their version.
- Collapse -
Blue Error Screen Nightmare
by micromuerto May 20, 2005 2:45PM PDT

I too have a blue screen, stoping me. I cant even log into my win XP accounts. My safe mode still works, but i cant seem to figure out how to fix it.

Some of the technical info says....

stop: 0x0000008e (0x000005, more numbers here......)

I tried checking disk... reinstalling....need some help!!! I see that you went threw the same situation, how did you fix it?

Alfredo
California

- Collapse -
Some Thoughts.
by phantazy May 20, 2005 3:25PM PDT

I'm only going on my experiences of what you have described, so I don't propose the immediate solution. If you can find out more about the Error Code, as oulined by Mark, do so, but that may not help. There are four common causes for what you describe.

1) Incompatable programmes
2) Driver problems
3) Insufficient memory
4) Corrupted Windows files.

The first is dealt with by using the msconfig command and disabling services at startup, one by one until a culprit is found.
The second is by employing Device Manager, and checking drivers, and troubleshoot them. (roll back, update, etc.)
The third depends on individual systems, but bear in mind that 512Mb ram is minimum for XP and if you have powerful video graphics and sound installations, IMO you need more.
The fourth can sometimes be resolved by running Chkdsk at the Run, or Command Prompt, with parameter /r.
Also sfc /scannow, via the same, which checks all Windows intalled files.
Unfortunately, you need to be able to boot at least into safe mode to investigate the above initial exploration. Those lucky enough to still be able to get this far, and have an earlier System Restore point still available, might resolve their error code problem without having to discover the cause.
This is only a rough ouline of the most common causes, which I personally have discovered.

- Collapse -
'u have two things working against you.
by Cursorcowboy May 20, 2005 11:47PM PDT

1. Error Reporting which is enabled by default displays an error dialog box prompting the user to indicate whether or not they want to report the problem. When choosing to report the problem, technical information about the problem is collected and then sent to Microsoft over the Internet. If a report is rendered and if a similar problem has been reported by other people and more information is available, a link to that information will be provided the user. Turning it ON or turning it OFF is the user's call. For assistance and resolution, we would need to know WHAT cause(s) is/are reported.

a. Were there no links or anything else provided should you submit the report?

b. Please. For your benefit, always report the error information this report contains when wanting our analyses.

2. When a system error occurs, the computer displays a blue screen containing error codes and all computer operations stop. When an illegal operation or other error occurs in a program, that program stops working. System and program errors may be transmitted to Microsoft which allows them to track and address operating system, Windows component, and program errors. Error Reporting configuration is outlined in, [Q310414]:

a. Enable or disable
b. Enable for the operating system
c. Specify the program for which a report is generated
d. Remove programs from the list
e. Send an error report to Microsoft

3. Supplemental reading:

a. "Description and Availability of Internet Explorer Error Reporting Tool (Q276550)."

b. "No Date or Time Information Available When Program Stops Responding in Windows 98 or Windows Me (Q280660)."

c. "How to Disable or Redirect Internet Explorer Error Reporting (Q310116)."

d. "How to Perform a Clean Boot in Windows XP (Q310353)."

e. "HOW TO: Configure and Use Error Reporting in Windows XP (Q310414)."

f. "Preparation Before You Contact Microsoft After Receiving a STOP Message on a Blue Screen (Q314103)."

g. "You Receive a "System Has Recovered from a Serious Error" Message After Every Restart (Q317277)."

4. Many users question what the file "Appcompat.txt" is, besides assuming that IT is the error itself, which is a file generated by the WinXP compatibilit

Back to Windows Legacy OS forum

CNET Forums

Operating Systems
Software
Electronics & Gadgets
Hardware
Tablets & Mobile Devices
General Help
Brand Forums
Roadshow Autos
Off Topic

Other Forums

Forum Info