XP Pro fresh install generated plenty blue screens

[Guest]

Please help. After enduring 2 years of very unsatisfactory XP machine with
frequent BSOD's I've decided to start fresh on new HDD and reinstall XP Pro
version 2002, then applied express updates took opportunity to update to sp2.
Got drivers for Video, USB, etc from MS. Soundcard drivers not installed
yet. The software ive installed are NAV and ZoneAlarm and Adobe reader, no
other application software.

I've tried moving and changing RAM, the RAM is OK'ed by the Mobo
Manufacturer. The first (most recent) stop error was while I was trying to
post this thread.

Going from most recent:
05/02/05 08:44am Error code 10000050, parameter1 ce242cde, parameter2
00000001, parameter3 bf801633, parameter4 00000000.

05/02/05 08:43am The computer has rebooted from a bugcheck. The bugcheck
was: 0x10000050 (0xce242cde, 0x00000001, 0xbf801633, 0x00000000). A dump was
saved in: C:\WINDOWS\Minidump\Mini020505-01.dmp.

04/02/05 09:24am Error code 10000050, parameter1 cdcdcde9, parameter2
00000000, parameter3 bf808d58, parameter4 00000000.

04/02/05 09:23am The computer has rebooted from a bugcheck. The bugcheck
was: 0x10000050 (0xcdcdcde9, 0x00000000, 0xbf808d58, 0x00000000). A dump was
saved in: C:\WINDOWS\Minidump\Mini020405-01.dmp.

31/01/05 08:34pm Error code 1000008e, parameter1 c0000005, parameter2
81352b4f, parameter3 f4a85c08, parameter4 00000000.

31/01/05 08:31pm Error code 10000050, parameter1 f4337f64, parameter2
00000001, parameter3 80577c65, parameter4 00000000.

31/01/05 08:30pm The computer has rebooted from a bugcheck. The bugcheck
was: 0x1000008e (0xc0000005, 0x81352b4f, 0xf4a85c08, 0x00000000). A dump was
saved in: C:\WINDOWS\Minidump\Mini013105-03.dmp.

31/01/05 07:33pm Error code 1000008e, parameter1 c0000005, parameter2
81552b4c, parameter3 f4a85c04, parameter4 00000000.

31/01/05 07:32pm The computer has rebooted from a bugcheck. The bugcheck
was: 0x10000050 (0xf4337f64, 0x00000001, 0x80577c65, 0x00000000). A dump was
saved in: C:\WINDOWS\Minidump\Mini013105-02.dmp.

31/01/05 07:26pm Error code 1000008e, parameter1 c0000005, parameter2
81552b4c, parameter3 f4a85c04, parameter4 00000000.

31/01/05 07:26pm The computer has rebooted from a bugcheck. The bugcheck
was: 0x1000008e (0xc0000005, 0x81552b4c, 0xf4a85c04, 0x00000000). A dump was
saved in: C:\WINDOWS\Minidump\Mini013105-01.dmp.

30/01/05 12:37pm Error code 1000000a, parameter1 8e676fd4, parameter2
000000ff, parameter3 00000000, parameter4 804e3b58.

29/01/05 11:58pm The computer has rebooted from a bugcheck. The bugcheck
was: 0x1000000a (0x8e676fd4, 0x000000ff, 0x00000000, 0x804e3b58). A dump was
saved in: C:\WINDOWS\Minidump\Mini012905-03.dmp.

29/01/05 11:32pm Error code 00000024, parameter1 001902fe, parameter2
f6419328, parameter3 f6419024, parameter4 8054b534.

 

[Rick \Nutcase\ Rogers]

Was it giving the same errors before? If so, then you have a hardware issue.
It could be a faulty power supply, or a misconfiguration on the motherboard,
bad jumper, etc - numerous possibilities.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Guest]

I got this PC from a dealer 2 yrs ago its an ASUS P4S8X and its "jumper less"
I think. Anyway I would hope they know what they are doing. I was not about
to spend more countless hours going through each part of the mobo to figure
it out so I bought another HDD and installed Ubuntu GNU/Linux. Installation
was an absolute breeze. Very easy. Had a good look around and ran it
overnight, did some testing, downloading a file from C-Media which was very
slow (XP got the blues trying to download this 4MB file.... twice) Ubuntu did
it in about 15 minutes no problems. I can feel the tension slowly vanish when
i am on this O/S, with my XP configuration though, every moment is tense
because it can simply zap into blue screen. I got a 0x0000008e just as i
tried to get on here and read your thread.

I'm no techie so I cant say this prove or not that the hardware is OK.
In reply to your question, prior to my reinstall, previous stop errors were:
0x00000050, 0x000000D1, 0x0000001A, 0x000000C5, 0x0000000A, 0x0000007F and
plenty of 0x0000008E's

Power supply was replaced to a 300W by the vendor (the ratbags replaced it
to fix this problem at my cost and it didn't solve the problem). Yeah...
numberous possibilities... just like finding XP stability.

 

[Rick \Nutcase\ Rogers]

Hi,

WinXP is far less fault tolerant than is Linux. Eventually, the hardware
will degrade to the point where Linux becomes unstable as well, but it may
be quite some time, so if you're happy with that then that's the way to go.
You'd probably find that a Win9x installation will run fine as well. If it's
two years old and you've never messed with the hardware, then something has
begun to fail. Which component is hard to say, but I would check that the
cpu fan is clean and running at full speed. Check the temp as well (it'll be
in the BIOS), should be in the mid 60's (C).

... just like finding XP stability.

The system I am using to type this went through the entire XP beta process -
with each release installed over the previous one, through the XP "Gold"
release, and both subsequent service packs and has never required a format
and reinstall. It gets rebooted about once a month or so during an imaging
backup process, but otherwise is never shut down.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Guest]

Rick, thanks for your post, I have too much invested in Windows application
software to go linux, and I dont want to go through the process of using wine
or other emulators to find out problems later on.

I have already installed Asus PC Probe and recorded MB and CPU temps and got
an incident while that was running, looking at the history, both showed
steady and no sudden increases although I think my tests were done at 5 or
10 second intervals. All I was doing at the time was browsing the web. I
will double check the temps later when I get back to that machine, but I had
in mind more like mid 40C not 60... but I'll have to confirm that.

I cannot believe what you are telling me with your stability experience! My
machine could never have managed to stay alive more than 48 hours, reboots
are done at least twice per day. Please tell me your hardware specs.... I am
just so frustrated trying to find stability I don't believe it exists, please
tell me your specs!

 

[Rick \Nutcase\ Rogers]

Hi,

That particular system uses:

Asus A7A266 board w/Ali chipset
AMD Athlon 1.4Ghz cpu (not the XP series, the original Athlons)
768MB of Crucial PC133 ram (DDR was too expensive back then, though the
board supports it)
Nvidia MX100/200 (not high end, but works well enough)
3 Maxtor drives of varying sizes, all ATA133, one is on a promise raid
controller board
Creative PCI512 (old but reliable, still has crappy drivers though)
Antec full case with lots of fans to keep the heat down and 350W power
supply

Love Asus boards, use them almost exclusively. Their support is a bit
lacking, but I've rarely had occasion to actually use it.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Guest]

Hehe, looks like I wont be able to replicate those specs today. My specs are
similar even with the Promise chip SATA RAID capabilities. Except the CPU
(Intel). Maybe I simply got a bad motherboard with intermittent problems, if
your opinion about linux being able to be more fault tollerant than XP is
correct. I think I will have to see if I can get a replacement mobo from
Asus. I've got an old PCI video card which maybe the only other component I
can think of that causes those errors. Is there a way to figure out what the
errors actually mean or do you think its not worth the effort having
described the series of events that has transpired?

 

[Rick \Nutcase\ Rogers]

You can always try debugging if you want to dig into the meat of it:

How to Use Dumpchk.exe to Check a Memory Dump File
http://support.microsoft.com/?kbid=315271

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Guest]

I have installed it but how do I decipher the numbers?

 

[Kui Tang]

And I didn't even know there were blue screens on XP! Maybe I just manage
computers better.

Possible Solutions:
1) Most likely your processor is generating errors. This is caused by a
variety of reasons, but could be as simple as overheating. In any case,
test your processor using a CPU testing/clocking utility. Just google some
up.
2) It could be a disk error. Run chkdsk. Make sure to also scan for
physical errors.
3) Try reinstalling windows AFTER YOU FORMAT YOUR DISK. It may be because
some system files are corrupt. Run chkdsk on the CDs that you install XP on
too.
4) Get rid of XP and dig up 98, and fire it up!
5) Ditch Windows altogether and hop onto the Linux bandwagon. We have many
flavors, Fedora, Mandrake, and much more!

=======================================

 

[Rick \Nutcase\ Rogers]

Hi,

Concentrate on the text portions, learning the debugger takes time.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[Guest]

And I didn't even know there were blue screens on XP! Maybe I just manage
computers better.

Actually there is a special configuration area and you can select the option
if you want this feature XP will default to blue screen, I chose "random" for
mine so its never boring.

I don't think you are managing your computers better than anyone else in
general, I recon you are just one of the lucky ones, just google for BSOD or
blue screen and bingo you'll see plenty..... in case you never heard of it.

Possible Solutions:
1) Most likely your processor is generating errors. This is caused by a
variety of reasons, but could be as simple as overheating. In any case,
test your processor using a CPU testing/clocking utility. Just google some
up.

I did a couple of runs about 3 or 4 hours worth each with ASUS PC Probe and
recorded Temps for MB (40C) and CPU (45C), on the second run I got a blue
screen while it was recording/monitoring and looking back there were no
sudden spikes or anything... very flat. As mentioned earlier I also got a
new HDD and installed Ubuntu... for a couple of days without any hangs or
reboots. That would suggest to me that the CPU is OK.

2) It could be a disk error. Run chkdsk. Make sure to also scan for
physical errors.

Could be, but chkdsk was done at every blue screen in original HDD. I took
that one out and installed a brand new same brand and model HDD and
reinstalled XP... which also blue screens soon after.... a few times as
already documented.

3) Try reinstalling windows AFTER YOU FORMAT YOUR DISK. It may be because
some system files are corrupt. Run chkdsk on the CDs that you install XP on
too.

I installed on a brand new HDD. I am not sure I can run chkdsk on a RAW
file format of the CD, will try later.

4) Get rid of XP and dig up 98, and fire it up!

I don't have licence for 98... I dont use anything I dont have licence for.
I got 95 licence but forget that option.

5) Ditch Windows altogether and hop onto the Linux bandwagon. We have many
flavors, Fedora, Mandrake, and much more!

I probably will eventually, at the moment there is a learning curve which I
dont have time for and having to consider Wine or other emulators to run my
windows apps for which I have paid dearly for.

For most blue screen and later XP asks for the problem to be reported and it
tells me the same frustrating useless information... Its a Driver issue, but
it could be this and that and everything else... its not much use.