Re: Trouble Loadiing XP
From: R. C. White (RCWhite_at_msn.com)
Date: 07/20/04
- Next message: Alex Nichol: "Re: problems with Alerter"
- Previous message: Mary: "Ad-aware"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: Trouble Loadiing XP"
- Next in thread: jt3: "Re: Trouble Loadiing XP"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 20 Jul 2004 09:43:17 -0500
Hi, Ricky.
Hilary's post should give you a good place to start your research. As you
can see, the fix may be very simple (replace your RAM) or very difficult to
diagnose. :>(
My own experience might illustrate how far-out the problem may be sometimes.
My otherwise well-performing system (EPoX 8K3A+/AMD Athlon XP 2000+/single
512 MB DDR SDRAM DIMM) had been giving an occasional BSOD for a year or so.
The Stop codes varied with few repeats; 50 popped up occasionally (pointing
to various memory locations) as did 0E, 0A, 8E and others. This usually
indicates hardware problems, not software, which would typically produce the
same Stop code each time. Then, about a month ago, the BSODs became much
more frequent, almost daily. I opened the case, checked connections and
vacuumed the easy places. I noted that some of the flat ribbon cables to
the drives were severely folded and crimped to make them fit inside the
cramped space; this might have inhibited airflow, but the case and CPU temps
had been well within their limits. But the bending of the ribbon cables
might have resulted in broken wires inside them, out of sight. I popped out
the DIMM and reseated it. No apparent effect.
Then, 10 days ago, my computer refused to reboot! My screen said, in
effect, "This monitor is fine, but I'm getting no signal from the computer."
I decided to replace the DIMM, so I bought a new one from Best Buy. Before
plugging it in, though, I tried the old one just once more. The computer
still wouldn't boot. Worse, there was the smell of burning electronics, so
I quickly turned off the power. When I popped out the DIMM, it was too hot
to handle. Close inspection showed a tiny black spot on one of the gold
"teeth" connectors. When I tried to wipe that off, several other teeth came
off. Then I looked into the case and saw that the DIMM socket had a blister
at the location corresponding to those teeth. My theory is that a "dust
bunny" had somehow made its way to the spot where it could cause a short
circuit there. :>(
I could not plug my new DIMM into the first socket, and I didn't think the
computer would boot without the first socket filled, but I plugged the new
DIMM into the second socket and powered up. The computer booted just fine!
The mainboard has 3 DIMM sockets, so I moved the RAM to the 3rd one to get
it as far as possible from the burned socket, and the computer ran as
before: perfectly, except for the several BSODs each day. That's when I
decided it was time for a new mainboard.
The new 64-bit mainboard and CPU (EPoX 8KDA3+/AMD Athlon 64 3200+) arrived
last Thursday (7/15); I had them installed by Friday morning and haven't
seen a BSOD since! ;<) The mainboard came with several new cables,
including 2 ROUND IDE cables, replacing my old flat ribbon cables. These
improve air flow AND remove the worry about breaks in the old cables. And I
was able to thoroughly vacuum inside the case. It had more dust than normal
because I had been running with some empty backplane slots for months,
letting dust come in through the gaps; I've plugged all of those now. Since
my old and new mobos both boot from the same IBM SCSI HD on an Adaptec host
adapter, I didn't even have to do an in-place upgrade, but I probably will
do that as soon as I get a new WinXP CD-ROM with SP2 integrated (next
month?), just to be sure that my copy of WinXP is properly customized for my
new hardware environment.
Sorry to be long-winded (one of my several faults), but I want to point out
that the problem may be obscure and hard to track down. I'm still not sure
what caused my BSODs; possibilities include cables, connections, RAM, a mobo
gone bad - or just plain old dust bunnies. :>(
Post back after you've narrowed down the possibilities, Ricky, and we'll see
what else we might suggest. If you fix it, post back with the solution,
which might help the next reader with a similar puzzle.
RC
-- R. C. White, CPA San Marcos, TX rc@corridor.net Microsoft Windows MVP <anonymous@discussions.microsoft.com> wrote in message news:009f01c46dc5$f07c9d60$a601280a@phx.gbl... > Thanks for the reply. I am trying do do a clean istall of > XP from a cd-rom. There is no new hardware on this system > other than a dvd burner, but that was working in my > computer before I began this project. I have tried > unpluging it and running from a different cd rom but > still no success. I also do not have any scsi devices or > raid. The code looks like this 0x00000050 follewed by > these ,(0x00000000,0x8097D530,0x00000000,0x88911820). I'm > not sure what these mean and am not familiar with how to > translate them. This might beyond my current knowledge. I > am assuming that i caught a virus on my system even > though i have norton, because my computer started messing > up and just went down hill from there. This is the reason > for the clean install. > Thanks for any help you can offer. > Ricky > >>-----Original Message----- >>Hi, Ricky. >> >>Please define "load XP" in this case? Are you trying to > INSTALL WinXP? >>Retail CD-ROM, or OEM, or "recovery" CD? You said, "I > have had xp on this >>system before"; are you trying to do a clean install? > Or an in-place >>upgrade? By "this system", do you mean the exact same > hardware, or is there >>a different mainboard/chipset, hard drive/controller or > other significant >>change? When you originally installed WinXP on this > computer, did you have >>to use the F6 key to install drivers for SCSI, RAID or > other mass storage >>controller? >> >>As you probably know, Stop 0x00000050 is > PAGE_FAULT_IN_NONPAGED_AREA. But >>it is not clear from your post whether 0x50 is the > actual stop code or some >>of the data for the code. In recent weeks, my computer > was giving me >>several BSODs a day with varying Stop codes, including > 0x50 sometimes. To >>make a long story short, I solved it by replacing the > mainboard and CPU. >>(But I had been wanting to upgrade to Athlon 64, anyhow, > so this was a good >>excuse. ;<} No BSODs in the past four days.) >> >>RC >> >>"Ricky O" <anonymous@discussions.microsoft.com> wrote in > message >>news:2fc1601c46dae$1ed3f180$a401280a@phx.gbl... >>>I am trying to load XP on to my computewr and it is >>> giving me stop errors as it begins loading the first >>> files (0x00000050,0x00000000,0x8097D530,... This comes >>> with a messege that it stoped installation to prevent >>> damaging my computer. I have had xp on this system > before >>> and am not sure what the problem is. I have pulled > every >>> unneccesary drive, card, stick of extra ram or exteral >>> device out, and have tried two different versions of > xp. >>> I am running a P4 2.66 w/512 ddr 2700 and a 90 gig >>> hitachi drive on an elite group 648fx-a board. Any help >>> is greatly appreciated . >>> Thank You
- Next message: Alex Nichol: "Re: problems with Alerter"
- Previous message: Mary: "Ad-aware"
- In reply to: anonymous_at_discussions.microsoft.com: "Re: Trouble Loadiing XP"
- Next in thread: jt3: "Re: Trouble Loadiing XP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
