Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

Crashes & Stop Codes - for a n00b


  • Please log in to reply

#1
n00bman

n00bman

    Member

  • Member
  • PipPip
  • 17 posts
My computer crashes on occasion for unknown reasons. It would be most appreciated if someone could help me interpret the stop codes. Hits from Google and the Microsoft Knowledge Base have unfortunately not been useful.

First - I'm a n00b. :tazz: I'm happy to learn anything about diagnosing a bad comp that you'd like to teach.

System - Windows XP Pro, all available Windows updates installed (minus MS .NET framework 1.0 SP 3 - fails to install on comp). No malware (using products from GeeksToGo/Malware, HJT log clean, etc.). No hardware recently installed. Hard drive has ~10 gigs left.

Crashes - Crashes are often spontaneous. These are sometimes caused by unplugging ethernet cable from card. Has also crashed after pressing "Restart," but does NOT crash during reboot. Random problems have occurred - Norton Antivirus and Ad-Aware had internal errors during the same session, both of which resolved after reboot.

Warning Message in Event Viewer (recurrent, edited for privacy):
Your computer has automatically configured the IP address for the Network Card with network address "xxxxxxxxxxxx". The IP address being used is "xxx.xxx.xx.xxx".

Stop Codes:
(In event viewer format - ex: 1000007e = 0x0000007E, c0000005 = 0xc0000005, 0000000a = 0000000a, etc.).

These errors have occurred on separate crashes or together. The errors often change from crash to crash.

Error code 1000007e, parameter1 c0000005, parameter2 804e280e, parameter3 f7a3ac24, parameter4 f7a3a924.

Error code 1000008e, parameter1 c0000005, parameter2 804e2801, parameter3 f778ebf8, parameter4 00000000.

Error code 0000000a, parameter1 8cae1b1c, parameter2 00000002, parameter3 00000001, parameter4 804ee2a0.

Error code 0000000a, parameter1 8cc4b084, parameter2 00000002, parameter3 00000001, parameter4 804e4eb0.

Error code 0000000a, parameter1 8800000c, parameter2 00000002, parameter3 00000000, parameter4 804df6ac.

Error code 000000c2, parameter1 00000043, parameter2 80000000, parameter3 00000000, parameter4 00000000.

Error code 00000050, parameter1 8c7e2300, parameter2 00000000, parameter3 80556d22, parameter4 00000000.


There are more errors I could dig up, but these should hopefully provide a starting point for a general diagnosis. I'm eager to find out what's wrong before the problem gets worse.

Thanks so much for your assistance!
  • 0

Advertisements


#2
austin_o

austin_o

    Retired Staff

  • Retired Staff
  • 2,089 posts
This is from the guide which is posted at the top of this forum:
http://www.geekstogo...des-t43519.html
  • 0

#3
SRX660

SRX660

    motto - Just get-er-done

  • Technician
  • 4,345 posts
Another good site is this one.

http://aumha.org/win5/kbestop.php

SRX660
  • 0

#4
n00bman

n00bman

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts

Another good site is this one.

http://aumha.org/win5/kbestop.php

SRX660



That site is incredibly useful, thanks a bunch! It led me to a library of the Windows error codes, which was very handy: Error Codes

I'm going to spend a few days de-n00bifying myself (if that's possible). The fast response was greatly appreciated.
  • 0

#5
n00bman

n00bman

    Member

  • Topic Starter
  • Member
  • PipPip
  • 17 posts
I'm happy to report that my problem (for 6 days and counting) seems to be resolved!

My error codes translated to a hardware or driver problem. A driver verifier was used to narrow down the possible bad drivers. After it fried my video card driver (I got an 8-color screen after the verifier), I updated that and several other unsigned drivers, just in case. I have not had a single crash or error appear in the Event Viewer since.

Although it is not my place, I think it would be handy to have the Windows stop code library and possibly this handy page in the forum guide.


Thank you GeeksToGo for helping my computer out of a jam!
:whistling:
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP