Homebuilt PC occasionally BSODs, how to diagnose

B

Bob Fry

I recently built a PC, my first one:

- AMD Athlon 64 X2 Dual-Core 4200+; stock heatsink and fan
- ABIT NF-M2 nView mobo
- No video card, using onboard video
- NZXT LEXA-NP case (Three 120mm fans, two blowing in, one blowing
out)
- 2GB DDR2 800MHz Super Talent T800UX2GC4 memory (no ECC, running at
default BIOS voltage and settings which are underclocked for the
memory)
- Corsair HX Series CMPSU-520HX PSU
- Three Western Digital WD1600YS drives in RAID5 config (supported by
mobo)
- Two DVD combo drives
- Microsoft Wireless Laser Desktop 6000 69A-00001 Keyboard and Mouse
Windows XP Pro x64

Nothing overclocked and typical temperatures are CPU 40degC & SYS 30.

The problem: occasionally, every two to four days, the machine will
BSOD and reboot itself without warning. I haven't noticed a pattern
(like everytime I start application X it BSODS). It certainly doesn't
make the computer unusable but I think the system should be more
stable than this. I leave the machnine on 24/7 but only actively use
it a few hours a day.

I'd like to debug this problem and hopefully fix it but don't really
know where to start. Hardware? Software? How to begin?
 
R

Rod Speed

Bob Fry said:
I recently built a PC, my first one:
Click to expand...
- AMD Athlon 64 X2 Dual-Core 4200+; stock heatsink and fan
- ABIT NF-M2 nView mobo
- No video card, using onboard video
- NZXT LEXA-NP case (Three 120mm fans, two blowing in, one blowing
out)
- 2GB DDR2 800MHz Super Talent T800UX2GC4 memory (no ECC, running at
default BIOS voltage and settings which are underclocked for the
memory)
- Corsair HX Series CMPSU-520HX PSU
- Three Western Digital WD1600YS drives in RAID5 config (supported by
mobo)
- Two DVD combo drives
- Microsoft Wireless Laser Desktop 6000 69A-00001 Keyboard and Mouse
Windows XP Pro x64
Click to expand...
Nothing overclocked and typical temperatures are CPU 40degC & SYS 30.
Click to expand...
The problem: occasionally, every two to four days, the machine will
BSOD and reboot itself without warning. I haven't noticed a pattern
(like everytime I start application X it BSODS). It certainly doesn't
make the computer unusable but I think the system should be more
stable than this. I leave the machnine on 24/7 but only actively use
it a few hours a day.
Click to expand...
I'd like to debug this problem and hopefully fix it but don't really
know where to start. Hardware? Software? How to begin?
Click to expand...

Check the event log, that may provide some useful info on what's causing it.
If it doesnt, it may be something as basic as a flakey power supply.

Try an overnight run of memtest86+, the motherboard manufacturers
are still excising warts from their bios memory setups etc.
 
K

kony

I recently built a PC, my first one:

- AMD Athlon 64 X2 Dual-Core 4200+; stock heatsink and fan
- ABIT NF-M2 nView mobo
- No video card, using onboard video
- NZXT LEXA-NP case (Three 120mm fans, two blowing in, one blowing
out)
- 2GB DDR2 800MHz Super Talent T800UX2GC4 memory (no ECC, running at
default BIOS voltage and settings which are underclocked for the
memory)
- Corsair HX Series CMPSU-520HX PSU
- Three Western Digital WD1600YS drives in RAID5 config (supported by
mobo)
- Two DVD combo drives
- Microsoft Wireless Laser Desktop 6000 69A-00001 Keyboard and Mouse
Windows XP Pro x64

Nothing overclocked and typical temperatures are CPU 40degC & SYS 30.

The problem: occasionally, every two to four days, the machine will
BSOD and reboot itself without warning. I haven't noticed a pattern
(like everytime I start application X it BSODS). It certainly doesn't
make the computer unusable but I think the system should be more
stable than this. I leave the machnine on 24/7 but only actively use
it a few hours a day.

I'd like to debug this problem and hopefully fix it but don't really
know where to start. Hardware? Software? How to begin?
Click to expand...

Check Event Viewer, any generated system logs, and most
importantly, disable Windows restart-on-error setting, then
write down any seemingly relevant info on the bluescreen,
especially the stop code. Search the web and MS' site for
that stop code and post it (and any links to info found on
it).

Bluescreens are often driver related, but we aren't at a
point that it's reasonable to conclude it yet.
 
T

Thomas Wendell

Inline

Bob said:
I recently built a PC, my first one:

- AMD Athlon 64 X2 Dual-Core 4200+; stock heatsink and fan
- ABIT NF-M2 nView mobo
- No video card, using onboard video
- NZXT LEXA-NP case (Three 120mm fans, two blowing in, one blowing
out)
Click to expand...

Change one of the in-blowing fans to blow out, to keep a slight
underpressure in the case
At least in these groups I've read that's better..



- 2GB DDR2 800MHz Super Talent T800UX2GC4 memory (no ECC, running at
default BIOS voltage and settings which are underclocked for the
memory)
- Corsair HX Series CMPSU-520HX PSU
- Three Western Digital WD1600YS drives in RAID5 config (supported by
mobo)
- Two DVD combo drives
- Microsoft Wireless Laser Desktop 6000 69A-00001 Keyboard and Mouse
Windows XP Pro x64

Nothing overclocked and typical temperatures are CPU 40degC & SYS 30.

The problem: occasionally, every two to four days, the machine will
BSOD and reboot itself without warning. I haven't noticed a pattern
(like everytime I start application X it BSODS). It certainly doesn't
make the computer unusable but I think the system should be more
stable than this. I leave the machnine on 24/7 but only actively use
it a few hours a day.

I'd like to debug this problem and hopefully fix it but don't really
know where to start. Hardware? Software? How to begin?
Click to expand...

--
Tumppi
=================================
A lot learned from these newsgroups
Helsinki, FINLAND
(translations from/to FI not always accurate
=================================
 
K

kony

Inline



Change one of the in-blowing fans to blow out, to keep a slight
underpressure in the case
At least in these groups I've read that's better..
Click to expand...

No it is not better necessarily, it depends on the airflow
per fan and where they are. In his case, a front mounted
fan should blow in, a rear mounted fan should blow out, and
the third fan shouldn't exist at all if one of the other
fans isn't on the bottom front blowing in.

If there is that front intake fan, which direction the 3rd
fan blows depends on where it is, what it's purpose is since
the parts don't really need a 3rd fan in an normal (temp)
operating environment unless the case were greatly impeding
the airflow from the other two fans. Generalizing instead
of considering specifics of his case, it's more likely the
3rd fan should be intake, blowing into the case so long as
it is a separate fan, not in the PSU instead which should
always exhaust out of the case.
 
B

Bob Fry

FYI, the three 120mm fans are:
- front intake with filter
- back exhaust
- left side intake

There's also the PSU fan (120mm) which is thermally controlled by the
PSU and doesn't run much; I don't have a demanding setup. The case
has a final 80mm fan on top which I disconnected; enough's enough!

Thanks for the suggestions, I'm working through them.
 
B

Bob Fry

I checked the memory overnight (about 7 hours) with memtest86+, and it
didn't find any problems.

I finally got some memory dumps and whatnot from one of the
BSODs...but don't know what to do with them.

Windows creates 3 files in a directory in the TEMP directory:
manifest.txt, Mini012207-01.dmp, and sysdata.xml. The first, in spite
of its extension, is in some binary form but only 2KB. The second is
also binary and 132KB. The last is readable, 160KB, and appears to
simply be a list of all devices and drivers with not a clue as to what
triggered the BSOD.

One of the error dialog boxes had these codes:
BCCode : be BCP1 : FFFFFADFC9E47D08 BCP2 : 8000000001E14121
BCP3 : FFFFFADFBAC3A820 BCP4 : 000000000000000B OSVer : 5_2_3790
SP : 1_0 Product : 256_1

I'll google for some clues and if anyone can offer a hint please let
me know.
 
J

JAD

Bob Fry said:
I checked the memory overnight (about 7 hours) with memtest86+, and it
didn't find any problems.

I finally got some memory dumps and whatnot from one of the
BSODs...but don't know what to do with them.

Windows creates 3 files in a directory in the TEMP directory:
manifest.txt, Mini012207-01.dmp, and sysdata.xml. The first, in spite
of its extension, is in some binary form but only 2KB. The second is
also binary and 132KB. The last is readable, 160KB, and appears to
simply be a list of all devices and drivers with not a clue as to what
triggered the BSOD.

One of the error dialog boxes had these codes:
BCCode : be BCP1 : FFFFFADFC9E47D08 BCP2 : 8000000001E14121
BCP3 : FFFFFADFBAC3A820 BCP4 : 000000000000000B OSVer : 5_2_3790
SP : 1_0 Product : 256_1

I'll google for some clues and if anyone can offer a hint please let
me know.
Click to expand...

again update your hardware drivers and it looks as though you have only SP1
on a XP install... if your hardware relies on framework updates your going
to have to get SP2. You getting the WGA warnings about legitimacy? Also
check your ASPI install. try and reset configuration data from the bios. Any
hardware drivers give the not signed warnings?
 
B

Bob Fry

JAD> again update your hardware drivers and it looks as though you
JAD> have only SP1 on a XP install...

I will check the drivers. This is Windows XP x64, based on Windows
Server 2003 SP1, so the Service Packs don't track Windows 32-bit.

JAD> You getting
JAD> the WGA warnings about legitimacy?

No.

JAD> Also check your ASPI
JAD> install.

Hmm, OK.

JAD> try and reset configuration data from the bios.

Almost everything is Safe default, certainly all the timings and
voltages are except the memory voltage, which likes a little higher
than default.


JAD> Any hardware drivers give the not signed warnings?

I don't think so. They would indicate so in the device manager?
During initial setup I sort of recall one or two items not having a
proper signed cert, can't remember what they were.
 
K

kony

again update your hardware drivers and it looks as though you have only SP1
on a XP install... if your hardware relies on framework updates your going
to have to get SP2. You getting the WGA warnings about legitimacy? Also
check your ASPI install. try and reset configuration data from the bios. Any
hardware drivers give the not signed warnings?
Click to expand...


It would be quite ill-advised to switch to SP2 at this
point. Hardware should not need SP2 regardless of what
you've been led to believe and changing the OS this
significantly is more likely to introduce multiple new
problems to resolve, blurring the lines between cause and
effect.

If he wants SP2, so be it- after the current installation is
working.

The typical method to approach BSOD is to write down the
stop code and go from there.
 
J

JAD

kony said:
It would be quite ill-advised to switch to SP2 at this
point. Hardware should not need SP2 regardless of what
you've been led to believe and changing the OS this
significantly is more likely to introduce multiple new
problems to resolve, blurring the lines between cause and
effect.

If he wants SP2, so be it- after the current installation is
working.

The typical method to approach BSOD is to write down the
stop code and go from there.
Click to expand...


he did.....and it points to drivers or conflicting resources And the sp2 is
moot as he is using 64b/2003 server
 
B

Bob Fry

BF> I recently built a PC, my first one....
BF> The problem: occasionally, every two to four days, the machine
BF> will BSOD and reboot itself without warning.

I posted this a few weeks ago, received some good responses, and was
starting to track down the problem. But one morning the PC wouldn't
recognize the RAID5 configuration so everything was hosed. I did a
complete reinstall but the 2nd time used Windows XP Pro (really XP
Home, but with this trick: http://mikedopp.com/hackxphome.html)
instead of the XP Pro x64 I had installed the 1st time.

Since the reinstall, no BSODs. I'm not ready to blame x64, I think
the problem was some immature drivers. I plan on making a dual-boot
machine and testing x64 some more, but it won't be the primary OS this
time.
 
Top