{{ OT }} Computerj (PC) Troubles with PCI Buss
#202
Guest
Posts: n/a
Re: {{ OT }} Computerj (PC) Troubles with PCI Buss
On Aug 7, 6:32 pm, "Jeff Strickland" <cr...@verizon.net> wrote:
> Aren't computers fun...GL
>
> It behaved the same way with two different wireless adaptors and two
> different installs of WinXP Pro, and the latest install of XP did a forced
> reformat of the hard drive. I'm confident the only wireless drivers I am
> dealing with now are for the D-Link adaptor. As an aside, the machine seems
> to not care about the USB 2.0 adaptor that also uses the PCI bus. Maybe my
> hints at a badpower supplyare not accurate ...
>
> Somebody suggested a interupt conflict, but there was no change in the
> interupts between the time the machine worked okay and when it began working
> poorly. ...
Using your reasoning, I could recommend maybe 300 other reasons -
and still we have accomplished nothing. Put on blinders, spin three
times, point a shotgun, and fire. That must have fixed the problem.
We call that procedure 'shotgunning'. It only makes problems
exponentially more complex. Reloading Windows on defective hardware -
I cringe at the number of new problems added to the mix.
In you first post, you suggested a power supply. Ok. We use that
as an example. You do nothing more until you have taken the power
supply 'system' (more than just a power supply) from the unknown state
to either a 'definitively good' or 'definitively bad' state. Notice
the world is ternary - not binary.
Two minutes with a multimeter (and make not even one wire
disconnect) will identify a suspect or confirm the entire 'system' as
'definitively good'. See "When your computer dies
without warning....." starting 6 Feb 2007 in the newsgroup
alt.windows-xp at:
http://tinyurl.com/yvf9vh
In two minutes, numbers tell define the supply 'system' as
'definitively xxxx'. AND because you post those numbers, then must
other useful information is provided.
A defective power supply can make anything and everything appear
defective. If you do not first confirm that 'system' integrity, then
nothing useful can be learned.
Having confirmed power supply system, now collect other useful
information. Well you reloaded Windows. Therefore you may have
destroyed system (event) logs that stored the details of your problem
as it got worse. See what is still within those system logs. IOW
stop trying to fix anything - and making the problem exponentially
more complex. We don't fix anything until the suspect is first
identified. IOW we do as they say in CSI - "follow the evidence".
That means stop shotgunning.
Also what does Device Manager report?
Now what can cause Windows to crash or lock? Hardware list
(including software drivers) is very short - memory, CPU, power
supply system, video controller, sound card. Notice the many things
that do not lock a system - mouse, keyboard, disk drive, CD-Rom, video
monitor, etc
Responsible computer manufacturers provide diagnostics exactly for
what you are going through. If your manufacturer is not responsible,
then download the diagnostic for each hardware item from the component
manufacturer or from third parties.
IOW do not even look at Windows. Execute hardware diagnostics
without Windows. Windows will only exponentially complicate the
problem. Once each diagnostics works in a 70 degree F room, then do
then all again in another room of normal computer temperature - 100
degree F.
Heat is a diagnostic. All computers must work just fine in a 100
degree F room. Any computer that works in 70 degrees but not 100
degrees is 100% defective. Unfortunately, the naive cure symptoms
with "More Fans". Any part that fails in 100 degrees is defective and
is corrected. Heat is an excellent tool for making an intermittent
temporarily into a hard error. If you don't have a 100 degree room,
then heat components selectively with hair dryer as hot as it goes -
and then execute that diagnostic.
Meanwhile, when computer was running, load Task Manager. Have that
always on screen until computer locks. What do the various parameters
say? For example, does one task consume near 100% computer time?
Again, long before we fix things, first we identify the fault. It
saves so much time as you have already learned.
Well that is so much to do for now. Report back - especially every
number and exact text of every error message. Remember, your replies
will only be as good as information you provide. For now, stop trying
to fix anything. Until we have a suspect, fix nothing.
> Aren't computers fun...GL
>
> It behaved the same way with two different wireless adaptors and two
> different installs of WinXP Pro, and the latest install of XP did a forced
> reformat of the hard drive. I'm confident the only wireless drivers I am
> dealing with now are for the D-Link adaptor. As an aside, the machine seems
> to not care about the USB 2.0 adaptor that also uses the PCI bus. Maybe my
> hints at a badpower supplyare not accurate ...
>
> Somebody suggested a interupt conflict, but there was no change in the
> interupts between the time the machine worked okay and when it began working
> poorly. ...
Using your reasoning, I could recommend maybe 300 other reasons -
and still we have accomplished nothing. Put on blinders, spin three
times, point a shotgun, and fire. That must have fixed the problem.
We call that procedure 'shotgunning'. It only makes problems
exponentially more complex. Reloading Windows on defective hardware -
I cringe at the number of new problems added to the mix.
In you first post, you suggested a power supply. Ok. We use that
as an example. You do nothing more until you have taken the power
supply 'system' (more than just a power supply) from the unknown state
to either a 'definitively good' or 'definitively bad' state. Notice
the world is ternary - not binary.
Two minutes with a multimeter (and make not even one wire
disconnect) will identify a suspect or confirm the entire 'system' as
'definitively good'. See "When your computer dies
without warning....." starting 6 Feb 2007 in the newsgroup
alt.windows-xp at:
http://tinyurl.com/yvf9vh
In two minutes, numbers tell define the supply 'system' as
'definitively xxxx'. AND because you post those numbers, then must
other useful information is provided.
A defective power supply can make anything and everything appear
defective. If you do not first confirm that 'system' integrity, then
nothing useful can be learned.
Having confirmed power supply system, now collect other useful
information. Well you reloaded Windows. Therefore you may have
destroyed system (event) logs that stored the details of your problem
as it got worse. See what is still within those system logs. IOW
stop trying to fix anything - and making the problem exponentially
more complex. We don't fix anything until the suspect is first
identified. IOW we do as they say in CSI - "follow the evidence".
That means stop shotgunning.
Also what does Device Manager report?
Now what can cause Windows to crash or lock? Hardware list
(including software drivers) is very short - memory, CPU, power
supply system, video controller, sound card. Notice the many things
that do not lock a system - mouse, keyboard, disk drive, CD-Rom, video
monitor, etc
Responsible computer manufacturers provide diagnostics exactly for
what you are going through. If your manufacturer is not responsible,
then download the diagnostic for each hardware item from the component
manufacturer or from third parties.
IOW do not even look at Windows. Execute hardware diagnostics
without Windows. Windows will only exponentially complicate the
problem. Once each diagnostics works in a 70 degree F room, then do
then all again in another room of normal computer temperature - 100
degree F.
Heat is a diagnostic. All computers must work just fine in a 100
degree F room. Any computer that works in 70 degrees but not 100
degrees is 100% defective. Unfortunately, the naive cure symptoms
with "More Fans". Any part that fails in 100 degrees is defective and
is corrected. Heat is an excellent tool for making an intermittent
temporarily into a hard error. If you don't have a 100 degree room,
then heat components selectively with hair dryer as hot as it goes -
and then execute that diagnostic.
Meanwhile, when computer was running, load Task Manager. Have that
always on screen until computer locks. What do the various parameters
say? For example, does one task consume near 100% computer time?
Again, long before we fix things, first we identify the fault. It
saves so much time as you have already learned.
Well that is so much to do for now. Report back - especially every
number and exact text of every error message. Remember, your replies
will only be as good as information you provide. For now, stop trying
to fix anything. Until we have a suspect, fix nothing.
#203
Guest
Posts: n/a
Re: {{ OT }} Computerj (PC) Troubles with PCI Buss
On Aug 7, 6:32 pm, "Jeff Strickland" <cr...@verizon.net> wrote:
> Aren't computers fun...GL
>
> It behaved the same way with two different wireless adaptors and two
> different installs of WinXP Pro, and the latest install of XP did a forced
> reformat of the hard drive. I'm confident the only wireless drivers I am
> dealing with now are for the D-Link adaptor. As an aside, the machine seems
> to not care about the USB 2.0 adaptor that also uses the PCI bus. Maybe my
> hints at a badpower supplyare not accurate ...
>
> Somebody suggested a interupt conflict, but there was no change in the
> interupts between the time the machine worked okay and when it began working
> poorly. ...
Using your reasoning, I could recommend maybe 300 other reasons -
and still we have accomplished nothing. Put on blinders, spin three
times, point a shotgun, and fire. That must have fixed the problem.
We call that procedure 'shotgunning'. It only makes problems
exponentially more complex. Reloading Windows on defective hardware -
I cringe at the number of new problems added to the mix.
In you first post, you suggested a power supply. Ok. We use that
as an example. You do nothing more until you have taken the power
supply 'system' (more than just a power supply) from the unknown state
to either a 'definitively good' or 'definitively bad' state. Notice
the world is ternary - not binary.
Two minutes with a multimeter (and make not even one wire
disconnect) will identify a suspect or confirm the entire 'system' as
'definitively good'. See "When your computer dies
without warning....." starting 6 Feb 2007 in the newsgroup
alt.windows-xp at:
http://tinyurl.com/yvf9vh
In two minutes, numbers tell define the supply 'system' as
'definitively xxxx'. AND because you post those numbers, then must
other useful information is provided.
A defective power supply can make anything and everything appear
defective. If you do not first confirm that 'system' integrity, then
nothing useful can be learned.
Having confirmed power supply system, now collect other useful
information. Well you reloaded Windows. Therefore you may have
destroyed system (event) logs that stored the details of your problem
as it got worse. See what is still within those system logs. IOW
stop trying to fix anything - and making the problem exponentially
more complex. We don't fix anything until the suspect is first
identified. IOW we do as they say in CSI - "follow the evidence".
That means stop shotgunning.
Also what does Device Manager report?
Now what can cause Windows to crash or lock? Hardware list
(including software drivers) is very short - memory, CPU, power
supply system, video controller, sound card. Notice the many things
that do not lock a system - mouse, keyboard, disk drive, CD-Rom, video
monitor, etc
Responsible computer manufacturers provide diagnostics exactly for
what you are going through. If your manufacturer is not responsible,
then download the diagnostic for each hardware item from the component
manufacturer or from third parties.
IOW do not even look at Windows. Execute hardware diagnostics
without Windows. Windows will only exponentially complicate the
problem. Once each diagnostics works in a 70 degree F room, then do
then all again in another room of normal computer temperature - 100
degree F.
Heat is a diagnostic. All computers must work just fine in a 100
degree F room. Any computer that works in 70 degrees but not 100
degrees is 100% defective. Unfortunately, the naive cure symptoms
with "More Fans". Any part that fails in 100 degrees is defective and
is corrected. Heat is an excellent tool for making an intermittent
temporarily into a hard error. If you don't have a 100 degree room,
then heat components selectively with hair dryer as hot as it goes -
and then execute that diagnostic.
Meanwhile, when computer was running, load Task Manager. Have that
always on screen until computer locks. What do the various parameters
say? For example, does one task consume near 100% computer time?
Again, long before we fix things, first we identify the fault. It
saves so much time as you have already learned.
Well that is so much to do for now. Report back - especially every
number and exact text of every error message. Remember, your replies
will only be as good as information you provide. For now, stop trying
to fix anything. Until we have a suspect, fix nothing.
> Aren't computers fun...GL
>
> It behaved the same way with two different wireless adaptors and two
> different installs of WinXP Pro, and the latest install of XP did a forced
> reformat of the hard drive. I'm confident the only wireless drivers I am
> dealing with now are for the D-Link adaptor. As an aside, the machine seems
> to not care about the USB 2.0 adaptor that also uses the PCI bus. Maybe my
> hints at a badpower supplyare not accurate ...
>
> Somebody suggested a interupt conflict, but there was no change in the
> interupts between the time the machine worked okay and when it began working
> poorly. ...
Using your reasoning, I could recommend maybe 300 other reasons -
and still we have accomplished nothing. Put on blinders, spin three
times, point a shotgun, and fire. That must have fixed the problem.
We call that procedure 'shotgunning'. It only makes problems
exponentially more complex. Reloading Windows on defective hardware -
I cringe at the number of new problems added to the mix.
In you first post, you suggested a power supply. Ok. We use that
as an example. You do nothing more until you have taken the power
supply 'system' (more than just a power supply) from the unknown state
to either a 'definitively good' or 'definitively bad' state. Notice
the world is ternary - not binary.
Two minutes with a multimeter (and make not even one wire
disconnect) will identify a suspect or confirm the entire 'system' as
'definitively good'. See "When your computer dies
without warning....." starting 6 Feb 2007 in the newsgroup
alt.windows-xp at:
http://tinyurl.com/yvf9vh
In two minutes, numbers tell define the supply 'system' as
'definitively xxxx'. AND because you post those numbers, then must
other useful information is provided.
A defective power supply can make anything and everything appear
defective. If you do not first confirm that 'system' integrity, then
nothing useful can be learned.
Having confirmed power supply system, now collect other useful
information. Well you reloaded Windows. Therefore you may have
destroyed system (event) logs that stored the details of your problem
as it got worse. See what is still within those system logs. IOW
stop trying to fix anything - and making the problem exponentially
more complex. We don't fix anything until the suspect is first
identified. IOW we do as they say in CSI - "follow the evidence".
That means stop shotgunning.
Also what does Device Manager report?
Now what can cause Windows to crash or lock? Hardware list
(including software drivers) is very short - memory, CPU, power
supply system, video controller, sound card. Notice the many things
that do not lock a system - mouse, keyboard, disk drive, CD-Rom, video
monitor, etc
Responsible computer manufacturers provide diagnostics exactly for
what you are going through. If your manufacturer is not responsible,
then download the diagnostic for each hardware item from the component
manufacturer or from third parties.
IOW do not even look at Windows. Execute hardware diagnostics
without Windows. Windows will only exponentially complicate the
problem. Once each diagnostics works in a 70 degree F room, then do
then all again in another room of normal computer temperature - 100
degree F.
Heat is a diagnostic. All computers must work just fine in a 100
degree F room. Any computer that works in 70 degrees but not 100
degrees is 100% defective. Unfortunately, the naive cure symptoms
with "More Fans". Any part that fails in 100 degrees is defective and
is corrected. Heat is an excellent tool for making an intermittent
temporarily into a hard error. If you don't have a 100 degree room,
then heat components selectively with hair dryer as hot as it goes -
and then execute that diagnostic.
Meanwhile, when computer was running, load Task Manager. Have that
always on screen until computer locks. What do the various parameters
say? For example, does one task consume near 100% computer time?
Again, long before we fix things, first we identify the fault. It
saves so much time as you have already learned.
Well that is so much to do for now. Report back - especially every
number and exact text of every error message. Remember, your replies
will only be as good as information you provide. For now, stop trying
to fix anything. Until we have a suspect, fix nothing.
#204
Guest
Posts: n/a
Re: {{ OT }} Computerj (PC) Troubles with PCI Buss
On Aug 7, 6:32 pm, "Jeff Strickland" <cr...@verizon.net> wrote:
> Aren't computers fun...GL
>
> It behaved the same way with two different wireless adaptors and two
> different installs of WinXP Pro, and the latest install of XP did a forced
> reformat of the hard drive. I'm confident the only wireless drivers I am
> dealing with now are for the D-Link adaptor. As an aside, the machine seems
> to not care about the USB 2.0 adaptor that also uses the PCI bus. Maybe my
> hints at a badpower supplyare not accurate ...
>
> Somebody suggested a interupt conflict, but there was no change in the
> interupts between the time the machine worked okay and when it began working
> poorly. ...
Using your reasoning, I could recommend maybe 300 other reasons -
and still we have accomplished nothing. Put on blinders, spin three
times, point a shotgun, and fire. That must have fixed the problem.
We call that procedure 'shotgunning'. It only makes problems
exponentially more complex. Reloading Windows on defective hardware -
I cringe at the number of new problems added to the mix.
In you first post, you suggested a power supply. Ok. We use that
as an example. You do nothing more until you have taken the power
supply 'system' (more than just a power supply) from the unknown state
to either a 'definitively good' or 'definitively bad' state. Notice
the world is ternary - not binary.
Two minutes with a multimeter (and make not even one wire
disconnect) will identify a suspect or confirm the entire 'system' as
'definitively good'. See "When your computer dies
without warning....." starting 6 Feb 2007 in the newsgroup
alt.windows-xp at:
http://tinyurl.com/yvf9vh
In two minutes, numbers tell define the supply 'system' as
'definitively xxxx'. AND because you post those numbers, then must
other useful information is provided.
A defective power supply can make anything and everything appear
defective. If you do not first confirm that 'system' integrity, then
nothing useful can be learned.
Having confirmed power supply system, now collect other useful
information. Well you reloaded Windows. Therefore you may have
destroyed system (event) logs that stored the details of your problem
as it got worse. See what is still within those system logs. IOW
stop trying to fix anything - and making the problem exponentially
more complex. We don't fix anything until the suspect is first
identified. IOW we do as they say in CSI - "follow the evidence".
That means stop shotgunning.
Also what does Device Manager report?
Now what can cause Windows to crash or lock? Hardware list
(including software drivers) is very short - memory, CPU, power
supply system, video controller, sound card. Notice the many things
that do not lock a system - mouse, keyboard, disk drive, CD-Rom, video
monitor, etc
Responsible computer manufacturers provide diagnostics exactly for
what you are going through. If your manufacturer is not responsible,
then download the diagnostic for each hardware item from the component
manufacturer or from third parties.
IOW do not even look at Windows. Execute hardware diagnostics
without Windows. Windows will only exponentially complicate the
problem. Once each diagnostics works in a 70 degree F room, then do
then all again in another room of normal computer temperature - 100
degree F.
Heat is a diagnostic. All computers must work just fine in a 100
degree F room. Any computer that works in 70 degrees but not 100
degrees is 100% defective. Unfortunately, the naive cure symptoms
with "More Fans". Any part that fails in 100 degrees is defective and
is corrected. Heat is an excellent tool for making an intermittent
temporarily into a hard error. If you don't have a 100 degree room,
then heat components selectively with hair dryer as hot as it goes -
and then execute that diagnostic.
Meanwhile, when computer was running, load Task Manager. Have that
always on screen until computer locks. What do the various parameters
say? For example, does one task consume near 100% computer time?
Again, long before we fix things, first we identify the fault. It
saves so much time as you have already learned.
Well that is so much to do for now. Report back - especially every
number and exact text of every error message. Remember, your replies
will only be as good as information you provide. For now, stop trying
to fix anything. Until we have a suspect, fix nothing.
> Aren't computers fun...GL
>
> It behaved the same way with two different wireless adaptors and two
> different installs of WinXP Pro, and the latest install of XP did a forced
> reformat of the hard drive. I'm confident the only wireless drivers I am
> dealing with now are for the D-Link adaptor. As an aside, the machine seems
> to not care about the USB 2.0 adaptor that also uses the PCI bus. Maybe my
> hints at a badpower supplyare not accurate ...
>
> Somebody suggested a interupt conflict, but there was no change in the
> interupts between the time the machine worked okay and when it began working
> poorly. ...
Using your reasoning, I could recommend maybe 300 other reasons -
and still we have accomplished nothing. Put on blinders, spin three
times, point a shotgun, and fire. That must have fixed the problem.
We call that procedure 'shotgunning'. It only makes problems
exponentially more complex. Reloading Windows on defective hardware -
I cringe at the number of new problems added to the mix.
In you first post, you suggested a power supply. Ok. We use that
as an example. You do nothing more until you have taken the power
supply 'system' (more than just a power supply) from the unknown state
to either a 'definitively good' or 'definitively bad' state. Notice
the world is ternary - not binary.
Two minutes with a multimeter (and make not even one wire
disconnect) will identify a suspect or confirm the entire 'system' as
'definitively good'. See "When your computer dies
without warning....." starting 6 Feb 2007 in the newsgroup
alt.windows-xp at:
http://tinyurl.com/yvf9vh
In two minutes, numbers tell define the supply 'system' as
'definitively xxxx'. AND because you post those numbers, then must
other useful information is provided.
A defective power supply can make anything and everything appear
defective. If you do not first confirm that 'system' integrity, then
nothing useful can be learned.
Having confirmed power supply system, now collect other useful
information. Well you reloaded Windows. Therefore you may have
destroyed system (event) logs that stored the details of your problem
as it got worse. See what is still within those system logs. IOW
stop trying to fix anything - and making the problem exponentially
more complex. We don't fix anything until the suspect is first
identified. IOW we do as they say in CSI - "follow the evidence".
That means stop shotgunning.
Also what does Device Manager report?
Now what can cause Windows to crash or lock? Hardware list
(including software drivers) is very short - memory, CPU, power
supply system, video controller, sound card. Notice the many things
that do not lock a system - mouse, keyboard, disk drive, CD-Rom, video
monitor, etc
Responsible computer manufacturers provide diagnostics exactly for
what you are going through. If your manufacturer is not responsible,
then download the diagnostic for each hardware item from the component
manufacturer or from third parties.
IOW do not even look at Windows. Execute hardware diagnostics
without Windows. Windows will only exponentially complicate the
problem. Once each diagnostics works in a 70 degree F room, then do
then all again in another room of normal computer temperature - 100
degree F.
Heat is a diagnostic. All computers must work just fine in a 100
degree F room. Any computer that works in 70 degrees but not 100
degrees is 100% defective. Unfortunately, the naive cure symptoms
with "More Fans". Any part that fails in 100 degrees is defective and
is corrected. Heat is an excellent tool for making an intermittent
temporarily into a hard error. If you don't have a 100 degree room,
then heat components selectively with hair dryer as hot as it goes -
and then execute that diagnostic.
Meanwhile, when computer was running, load Task Manager. Have that
always on screen until computer locks. What do the various parameters
say? For example, does one task consume near 100% computer time?
Again, long before we fix things, first we identify the fault. It
saves so much time as you have already learned.
Well that is so much to do for now. Report back - especially every
number and exact text of every error message. Remember, your replies
will only be as good as information you provide. For now, stop trying
to fix anything. Until we have a suspect, fix nothing.
#205
Guest
Posts: n/a
Re: {{ OT }} Computerj (PC) Troubles with PCI Buss
On Aug 7, 6:32 pm, "Jeff Strickland" <cr...@verizon.net> wrote:
> Aren't computers fun...GL
>
> It behaved the same way with two different wireless adaptors and two
> different installs of WinXP Pro, and the latest install of XP did a forced
> reformat of the hard drive. I'm confident the only wireless drivers I am
> dealing with now are for the D-Link adaptor. As an aside, the machine seems
> to not care about the USB 2.0 adaptor that also uses the PCI bus. Maybe my
> hints at a badpower supplyare not accurate ...
>
> Somebody suggested a interupt conflict, but there was no change in the
> interupts between the time the machine worked okay and when it began working
> poorly. ...
Using your reasoning, I could recommend maybe 300 other reasons -
and still we have accomplished nothing. Put on blinders, spin three
times, point a shotgun, and fire. That must have fixed the problem.
We call that procedure 'shotgunning'. It only makes problems
exponentially more complex. Reloading Windows on defective hardware -
I cringe at the number of new problems added to the mix.
In you first post, you suggested a power supply. Ok. We use that
as an example. You do nothing more until you have taken the power
supply 'system' (more than just a power supply) from the unknown state
to either a 'definitively good' or 'definitively bad' state. Notice
the world is ternary - not binary.
Two minutes with a multimeter (and make not even one wire
disconnect) will identify a suspect or confirm the entire 'system' as
'definitively good'. See "When your computer dies
without warning....." starting 6 Feb 2007 in the newsgroup
alt.windows-xp at:
http://tinyurl.com/yvf9vh
In two minutes, numbers tell define the supply 'system' as
'definitively xxxx'. AND because you post those numbers, then must
other useful information is provided.
A defective power supply can make anything and everything appear
defective. If you do not first confirm that 'system' integrity, then
nothing useful can be learned.
Having confirmed power supply system, now collect other useful
information. Well you reloaded Windows. Therefore you may have
destroyed system (event) logs that stored the details of your problem
as it got worse. See what is still within those system logs. IOW
stop trying to fix anything - and making the problem exponentially
more complex. We don't fix anything until the suspect is first
identified. IOW we do as they say in CSI - "follow the evidence".
That means stop shotgunning.
Also what does Device Manager report?
Now what can cause Windows to crash or lock? Hardware list
(including software drivers) is very short - memory, CPU, power
supply system, video controller, sound card. Notice the many things
that do not lock a system - mouse, keyboard, disk drive, CD-Rom, video
monitor, etc
Responsible computer manufacturers provide diagnostics exactly for
what you are going through. If your manufacturer is not responsible,
then download the diagnostic for each hardware item from the component
manufacturer or from third parties.
IOW do not even look at Windows. Execute hardware diagnostics
without Windows. Windows will only exponentially complicate the
problem. Once each diagnostics works in a 70 degree F room, then do
then all again in another room of normal computer temperature - 100
degree F.
Heat is a diagnostic. All computers must work just fine in a 100
degree F room. Any computer that works in 70 degrees but not 100
degrees is 100% defective. Unfortunately, the naive cure symptoms
with "More Fans". Any part that fails in 100 degrees is defective and
is corrected. Heat is an excellent tool for making an intermittent
temporarily into a hard error. If you don't have a 100 degree room,
then heat components selectively with hair dryer as hot as it goes -
and then execute that diagnostic.
Meanwhile, when computer was running, load Task Manager. Have that
always on screen until computer locks. What do the various parameters
say? For example, does one task consume near 100% computer time?
Again, long before we fix things, first we identify the fault. It
saves so much time as you have already learned.
Well that is so much to do for now. Report back - especially every
number and exact text of every error message. Remember, your replies
will only be as good as information you provide. For now, stop trying
to fix anything. Until we have a suspect, fix nothing.
> Aren't computers fun...GL
>
> It behaved the same way with two different wireless adaptors and two
> different installs of WinXP Pro, and the latest install of XP did a forced
> reformat of the hard drive. I'm confident the only wireless drivers I am
> dealing with now are for the D-Link adaptor. As an aside, the machine seems
> to not care about the USB 2.0 adaptor that also uses the PCI bus. Maybe my
> hints at a badpower supplyare not accurate ...
>
> Somebody suggested a interupt conflict, but there was no change in the
> interupts between the time the machine worked okay and when it began working
> poorly. ...
Using your reasoning, I could recommend maybe 300 other reasons -
and still we have accomplished nothing. Put on blinders, spin three
times, point a shotgun, and fire. That must have fixed the problem.
We call that procedure 'shotgunning'. It only makes problems
exponentially more complex. Reloading Windows on defective hardware -
I cringe at the number of new problems added to the mix.
In you first post, you suggested a power supply. Ok. We use that
as an example. You do nothing more until you have taken the power
supply 'system' (more than just a power supply) from the unknown state
to either a 'definitively good' or 'definitively bad' state. Notice
the world is ternary - not binary.
Two minutes with a multimeter (and make not even one wire
disconnect) will identify a suspect or confirm the entire 'system' as
'definitively good'. See "When your computer dies
without warning....." starting 6 Feb 2007 in the newsgroup
alt.windows-xp at:
http://tinyurl.com/yvf9vh
In two minutes, numbers tell define the supply 'system' as
'definitively xxxx'. AND because you post those numbers, then must
other useful information is provided.
A defective power supply can make anything and everything appear
defective. If you do not first confirm that 'system' integrity, then
nothing useful can be learned.
Having confirmed power supply system, now collect other useful
information. Well you reloaded Windows. Therefore you may have
destroyed system (event) logs that stored the details of your problem
as it got worse. See what is still within those system logs. IOW
stop trying to fix anything - and making the problem exponentially
more complex. We don't fix anything until the suspect is first
identified. IOW we do as they say in CSI - "follow the evidence".
That means stop shotgunning.
Also what does Device Manager report?
Now what can cause Windows to crash or lock? Hardware list
(including software drivers) is very short - memory, CPU, power
supply system, video controller, sound card. Notice the many things
that do not lock a system - mouse, keyboard, disk drive, CD-Rom, video
monitor, etc
Responsible computer manufacturers provide diagnostics exactly for
what you are going through. If your manufacturer is not responsible,
then download the diagnostic for each hardware item from the component
manufacturer or from third parties.
IOW do not even look at Windows. Execute hardware diagnostics
without Windows. Windows will only exponentially complicate the
problem. Once each diagnostics works in a 70 degree F room, then do
then all again in another room of normal computer temperature - 100
degree F.
Heat is a diagnostic. All computers must work just fine in a 100
degree F room. Any computer that works in 70 degrees but not 100
degrees is 100% defective. Unfortunately, the naive cure symptoms
with "More Fans". Any part that fails in 100 degrees is defective and
is corrected. Heat is an excellent tool for making an intermittent
temporarily into a hard error. If you don't have a 100 degree room,
then heat components selectively with hair dryer as hot as it goes -
and then execute that diagnostic.
Meanwhile, when computer was running, load Task Manager. Have that
always on screen until computer locks. What do the various parameters
say? For example, does one task consume near 100% computer time?
Again, long before we fix things, first we identify the fault. It
saves so much time as you have already learned.
Well that is so much to do for now. Report back - especially every
number and exact text of every error message. Remember, your replies
will only be as good as information you provide. For now, stop trying
to fix anything. Until we have a suspect, fix nothing.
#210
Guest
Posts: n/a
Re: {{ OT }} Computerj (PC) Troubles with PCI Buss
"Jeff DeWitt" <JeffDeWitt@nc.rr.com> wrote in message
news:46b90ffd$0$30667$4c368faf@roadrunner.com...
> Jeff Strickland wrote:
>>
>> "Earle Horton" <el_anglo_burgues@usa.com> wrote in message
>> news:f9atsc$so1$1@registered.motzarella.org...
>>> Jeff, power supplies are real cheap, I think you said that too. I have
>>> two
>>> or three lying around as spares, just in case. I don't think it will
>>> fix
>>> it, but you never know until you swap it out.
>>>
>>> I like a recent Windows upgrade as another possible culprit, or the
>>> software
>>> that comes with the wireless card.
>>>
>>
>> No Windows upgrade. I did a reinstall, but that was a response to the
>> problem, and the problem persists ONLY when the hardware is installed.
>>
>>
>>
>>> Are the CPU fan and the one in the power supply turning? I had one just
>>> stop once. I spotted it before anything else failed.
>>
>>
>> Yeah, the fans are running.
>>
>
>
> When you reinstalled Windows did you go to Widows Update and get all the
> latests patches?
>
How do I do that when the portal to Windows Update (the wireless adaptor)
crashes the system?
Remember, Windows will crash on the desktop, I can't initiate any program in
that condition. When I do initiate a program, the system crashes long before
any useful information can be extracted. And the crash seems to NOT present
any errors that are tracked. It (the system) simply stops responding ...
> If you did it might be that one of those cause the problem, you could try
> reloading it again and then trying the machine out before updating
> Windows.
>
> Have you checked the MB manufactures website to see if there were any
> updated drivers (especially PCI bus drivers)for the motherboard?
>
> SOMETHING happened to make a well behaved machine started doing this, and
> Windows updating itself is an obvious culprit.
>
>
I would agree, but the windows update was initiated by me in response to the
trouble-set that I am having. And, I'm still having the same trouble set.