Re: Won't boot.



On Mar 21, 11:50 am, "Marko" <dkv...@xxxxxxxxx> wrote:
I can't get past this blue screen and therefore SAFE mode is  not an option.
Starting the machine with a clean, NTFS formatted hard drive and the Vista
disk in the DVD drive I again get to where it loads the initial Vista files
but then goes to the -end of the road- blue screen.

Nothing says the video controller is functional.

If I did not mention it, download diagnostics for devices that can
cause a BSOD failure message. Since the manufacturer does not provide
the hardware diagnostic (that they have and could have provided for
free), then find third party diagnostics such as Memtst86. It boots
without loading any drivers or OS. Test is best also executed with
memory heated by a hairdryer on high heat - the ideal temperature to
all memory. Defective memory often passes tests until heated.

Same applies to a video processor diagnostic from that
manufacturer. Like any good diagnostic, it also loads without
Windows, etc.

Of course, the one system that can cause all other components to
appear defective is the power supply 'system'. A system where the
supply is only one component. In your case, most important DC numbers
measured with a 3.5 digit multimeter are any one purple, red, orange,
and yellow wires. Probed where those wires enter a nylon connector on
motherboard. Numbers must exceed 3.23, 4.87, and 11.7 volts. If not,
you have a suspect that typically makes other components appear
defective. Then look for what in that suspect system is defective (ie
bulging capacitors).

If CMOS was a problem, the meter will identify that problem by
measuring the CMOS battery without removing it. If a 3 volt lithium,
then 2.8 volts DC says to plan replacing that battery in the next six
months. A lower voltage may explain problems on some motherboards.
Motherboard failure was really an excessively low battery.

Of course, other power supply connections to video controller board
and to a connector near the CPU exist?

Meter is necessary to confirm power supply system is definitively
good. Passing video controller and memory diagnostics mean only the
motherboard (or sound card) remains suspect. Those are the few
devices that could cause failure (without the benefit of a
comprehensive hardware diagnostic). Easy is to remove those other
components from the suspect list.

I am troubled by a stop code that does not report additional text.
Also troubled that the stop code was only followed by three numbers.
Should be four.

And finally, why do we fix things? Learning. Based upon what you
report, additional insight may be learned. Appreciate why we don't
'try this and try that'. Without 'following the evidence', I could
have listed maybe 30 things to try; if only using speculation.
.



Relevant Pages

  • Re: Help with BSOD... tried everything
    ... 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. ... the unit survived much longer before BSOD and then the next failure was within minutes. ... 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 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: Vista stalls and reboots at expanding files prompt
    ... I ran diagnostics on both the hard drive and memory but both came back ... I tried a different Power supply so I'm suspecting the motherboard. ...
    (microsoft.public.windows.vista.installation_setup)
  • Re: Vista stalls and reboots at expanding files prompt
    ... I ran diagnostics on both the hard drive and memory but both came back ... I tried a different Power supply so I'm suspecting the motherboard. ...
    (microsoft.public.windows.vista.installation_setup)
  • Re: MCA messages in dmesg
    ... I've no idea what specific hardware is busted (memory or motherboard or ... but I suspect something is likely broken. ... I'm going to play around with BIOS voltages to ...
    (freebsd-stable)