Re: Help with BSOD... tried everything



Give mick a break.
I understand based on his post, you may feel he's "jumped the gun."

He has been fighting this problem for quite a while very systematically running a great deal of diagnostics, using vendor support, multiple installs, updating drivers and BIOS, running bare minimum or running only one component at a time trying to find this problem. With minimum components, the unit survived much longer before BSOD and then the next failure was within minutes. As he has said, it is random. This lead to either a broken component on the motherboard or the power supply. It appears he went with the mobo. Knowing the history, I would not consider him to be shot gunning.

The BSODs were previously supplied, as were the dump files. But, the specific error does not provide information other than it is an error (sudden shutdown.)

"westom" <westom1@xxxxxxxxx> wrote in message news:fa5b0dbf-b1ed-4e7a-af8f-60037d436a34@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Mar 1, 3:56 pm, mickmeyers88 <gu...@xxxxxxxxxxxxxxxxx> wrote:
I've been working on this problem for some time now... and can't seem to
resolve the issue... with much good advice from numerous persons. The
BSOD are many and have different error messages...

BSOD message contains essential software ID and numbers identifying
the primary suspect. Meanwhile, other information is necessary long
before trying to fix anything. For example, what do system (event)
logs report? Device manager? What are critical power supply voltages
(on any one orange, red, purple, and yellow wires) especially when
computer is under most load (when accessing all peripherals
simultaneously)? Those numbers may appear good to you but have
further meaning to others.

Swapping parts without first identifying the problem is called
shotgunning. Informed techs first get facts before swapping
anything. Shotgunning can even exponentially complicate a problem.

Better computer manufacturers provide comprehensive hardware
diagnostics just for your problem. Yours does not provide them. So
download diagnostics from individual component manufacturers or third
parties.

Memtst is an excellent test, but only when conducted properly.
First execute a few passes at room temperature. Then repeat with
memory and related components heated to temperatures that are
uncomfortable to touch but ideal to semiconductors. A hair dryer on
highest heat settings is an ideal testing temperature causing a
defective memory location to fail only at that perfectly normal and
warmer temperature.

Having provided power supply numbers and tested memory using heat as
a diagnostic, then move on to other suspects. Hardware devices that
can cause a BSOD are fewer - including video processor, sound card,
memory, CPU, a limited number of motherboard functions, and firstmost
- the power supply system. Only after these hardware components are
confirmed (especially with manufacturer diagnostics), then move on to
software suspects.

However, those BSOD text and numbers are important; a shortcut to
identifying the primary suspect. Again, good diagnostic procedure
dictates not fixing anything until the suspect is first identified.
Shotgunning usually means replacing half the computer and never really
knowing what the problem was or if it was fixed. Shotgunning (also
called wild speculation) may only cure symptoms. First get facts
before replacing anything. Numbers such as power supply system
voltages (to three significant digits) means the better informed
provide useful assistance.

.



Relevant Pages

  • Re: Help with BSOD... tried everything
    ... BSOD are many and have different error messages... ... diagnostics just for your problem. ... memory and related components heated to temperatures that are ... identifying the primary suspect. ...
    (microsoft.public.windows.vista.installation_setup)
  • Re: Help with BSOD... tried everything
    ... BSOD message contains essential software ID and numbers identifying ... Shotgunning can even exponentially complicate a problem. ... diagnostics just for your problem. ... identifying the primary suspect. ...
    (microsoft.public.windows.vista.installation_setup)
  • Re: Wont boot.
    ... If I did not mention it, download diagnostics for devices that can ... memory heated by a hairdryer on high heat - the ideal temperature to ... Then look for what in that suspect system is defective (ie ... Motherboard failure was really an excessively low battery. ...
    (microsoft.public.windows.vista.general)
  • RE: Computer restarts in the middle of loading XP
    ... Not the kind of BSOD I think you're thinking of. ... Faulty memory module. ... > may be OK and that you need to run hard disk diagnostics. ... >> I also forgot to mention that it said ntoskrnl.exe was corrupt. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Computer keeps restarting
    ... The problem seems to be the startup of Windows. ... Therefore the doors (memory) are still not exonerated ... Foundation is the power supply system. ... diagnostics, well, that memory diagnostic will not report accurately ...
    (microsoft.public.windowsxp.general)