STOP 0x0000000A BSOD

[LiLRiceBoi]

Ever since my last format, 2 weeks ago, I've been getting the following BSOD

STOP 0x0000000A (0xE2A77070, 0X00000002, 0X00000000,0X80471D63)
ADDRESS 80491d63 base at 80400000, datestamp 3d366b8b - ntoskrnl.exe

Before it would just restart my computer, but under system properties I unckeck automatic reboot. I've noticed the last two times it happened the "ADDRESS..." part is the same.

I'm guessing its because bad RAM. Funny thing is that before the last formatted I never got this error, however, before that, it would occur occasionally.

Any ideas??

TIA

Athon XP 1800
512 PC2100 (2x256)
GF2MX400 64mb
SB Live! 5.1
Win2k SP3

[JayMan]

Might be an idea to check your memory, try something like www.memtest86.com (i think thats the right address... i forget...)...

Could also just be a bad install & ya might need to try again...

JayMan

[Scott Tiger]

I've got to agree with JayMan here - memtest is the first thing I'd try. Just let it run for 24 hrs (or however much time you can spare the pc) to see if you get any errors. You can burn the utitly to a cd and then boot to it. It's pretty painless.

If that turns up nothing we'll try something else.

Regards..

[LiLRiceBoi]

It has happened 2 and 3 formats before but not the last one and now its happening again. I'll try the memtest.

[muno]

What is the stop message? It's the line typed in capitals below the second line.

Check out here->
http://216.239.51.100/search?q=cache...=en&lr=lang_en|lang_fi&ie=UTF-8

It's a cached page - referred to invalid page at ms technet.
-M

[LiLRiceBoi]

Originally posted by muno
What is the stop message? It's the line typed in capitals below the second line.

Check out here->
http://216.239.51.100/search?q=cache...lr=lang_en</a>|lang_fi&ie=UTF-8

It's a cached page - referred to invalid page at ms technet.
-M

I'm not sure what the stop message was. but i do know that there was nothing between the two lines which I have posted earlier. I ran memtest and it repoted errors. I am now testing the sticks individually.

[LiLRiceBoi]

Okay, I got errors on test 8 when I tested both sticks together. the failing address was differtn each time. They were all under .5mb for one stick however, the second stick had a 232.2 and 247.2mb. The error bits were 80000000. When I test them individually, I get errors on test 5 and 8 with error bits either 80000000 or 0. I read at the memtest86 site that it is a known issue for Athlon systems to sometimes report these errors.

I have tested each of them individually and in each slot.

Well I'm not really sure what to do. The computer (my mom's) is still under warentee from compaq (I know, I know, but she got it for free at a company raffle type thing). Should I call them up and try to have them replace both sticks of ram? Should I see if they'll replace the motherboard too?

[EDIT] BTW the warentee expires Jan 25, 2003, so I need to act fast [/EDIT]

[muno]

It's below the two lines, not between them.

My link seems to be too long, but have no desire to fix it

I've never ran memtest, even though bsod's happen regularly on someone. It's usually nothing serious - unless it happens at a specific point, and even then I think it's a rarity for a stick to be bad.
-M

[LiLRiceBoi]

I'm pretty sure there's nothing below. I'll make sure to check next time it happens though.

After spending a long time trying to convince the guy to send me new ram, he sent two sticks. We'll see if it fixes the problem

[LiLRiceBoi]

Nothing was below.

Changed the RAM and I just got the same error again. The ADDRESS 80491d63 base at 80400000, datestamp 3d366b8b - ntoskrnl.exe part was the same. If the address is the same but the RAM is good, could it be the motherboard?

What else should I look into? I can get a hold of another win2k cd if my cd is the problem.

[muno]

http://www.microsoft.com/technet/tre...d_stp_hwpg.asp

Unless you've lately installed some new drivers, return it.
If you've installed new drivers, try another set of them.
-M

[LiLRiceBoi]

havent installed anything lateley

[LiLRiceBoi]

^^Bump^^

I'm going to try formatting again tonight if I cant find the solution.

[LiLRiceBoi]

Not formating til next weekend. So... bump