STOP: 0x00000050 error? What to do?

bilditup1

Junior Member
Nov 20, 2003
8
0
0
I'm sorta lost here. Everytime I try to install WinXP home on my comp(Biostar M71VQ, AthlonXP 2200) it fails and show the following error:

The problem seems to be cause d by the following file: partmgr.sys

PAGE_FAULT_IN_NONPAGED_AREA

STOP: 0X00000050 (OXFA1364AB, 0X00000000, OXFA1364AB, 0X00000000)

I've searched Microsoft KB, which said the RAM was the culprit, which turned out not to be the case. It also sugested taking out any new device- which would be my modem. That didn't do it either. I disabled CPU internal cache- all of this to no avail.

Anynoe with a similar problem?

Thanks, Eli B.
 

EeyoreX

Platinum Member
Oct 27, 2002
2,864
0
0
How do you know RAM is not the problem? Generally speaking, a large number of blue screen errors in Windows XP are realted to RAM. If the RAM is not the problem (I'd still like to know how you are sure it isn't) then perhaps the slot the RAM is in is the problem. Try changing slots and see if that helps.

\Dan
 

bilditup1

Junior Member
Nov 20, 2003
8
0
0
I'm doing that now, hope it works. Thanks for speedy reply. Won't be able to get see this thread till Monday, so I really appreciate it.

Eli B.
 

bilditup1

Junior Member
Nov 20, 2003
8
0
0
The RAM can't be the problem because I tried the RAM in my working PC- in fact I'm using it right now. I ran memtest on it a couple times in any case, with no problems. Works like a charm. I disabled all the onboard stuff(Ethernet, Audio, etc.) and took out the modem. I'm trying it right now. If it still doesn't work, could I safely assume it's the mb?

EDIT: Didn't work again, gonna try switching RAM slots...I'm not very optimistic about this...
 

Black88GTA

Diamond Member
Sep 9, 2003
3,430
0
0
Heh, that's really interesting that this was posted today. I was just fighting with my PC over the same errors, trying to install the same OS.

The problem was my own stupidity :eek:. I accidentally disconnected my CPU fan while rewiring some stuff inside the case :Q. When I went into the BIOS and chanced to look at the PC health section, the CPU was showing temps of 70 deg. C :Q. EEEEEK! I quickly turned everything off, reconnected the CPU fan, and aimed a high powered fan at the HS with the side of the case off. After 20 minutes of that, I restarted everything, and it installed perfectly, with no more errors.

Make sure your CPU is staying cool, and the fan is running properly. Good luck!
 

buleyb

Golden Member
Aug 12, 2002
1,301
0
0
Originally posted by: bilditup1
The RAM can't be the problem because I tried the RAM in my working PC- in fact I'm using it right now. I ran memtest on it a couple times in any case, with no problems. Works like a charm. I disabled all the onboard stuff(Ethernet, Audio, etc.) and took out the modem. I'm trying it right now. If it still doesn't work, could I safely assume it's the mb?

EDIT: Didn't work again, gonna try switching RAM slots...I'm not very optimistic about this...

The RAM doesn't have to be bad for it to be causing a problem. Have you tried using 1 known good stick with SPD timings?

 

bilditup1

Junior Member
Nov 20, 2003
8
0
0
I'm running with 2.5-3-3-6, which, I've read, is pretty standard. I've tried two sticks both 256MB PC2100. CPU fan is working like a charm. Is it possible for the hard drive to be at fault here? It's a Barracuda 7200.7, should I get a cooler for it? (Keep in mind that I am basically a noob)