Hi, I'm really hoping someone can help me.

I'm getting random crashes using Windows Vista 32-bit. They seem to come at
any time - while installing an application, copying a file, running a game -
there doesn't seem to be a pattern. The crashes are the straight-to-reboot
sort of thing rather than blue screen of death. I otherwise really like
Vista but I'm now tearing my hair out. I've had it installed since yesterday
morning and I can't go on much longer.

Please could someone help direct me to some way I can start to diagnose this
(nothing appears logged in event views, etc.), or suggest a solution. I
originally thought it was my running Intel Matrix RAID, but I've disabled
that and am now running in IDE mode.

Other threads have suggested a hardware problem, but given the system info
I've shown below I'm not sure how this could affect me. I have run the
Windows Memory Diagnostic overnight (5 runs in extended cycle) and it showed
no memory errors.

My specs are:
Intel Quad-Core Q6600 @ 2.40 GHz (normal) with Zalman 9500 cooler
Asus P5K Premium Wi-fi mobo
2GB Corsair 1066 MHz RAM
NVidia GeForce 8800 GTX
Zalman 600-HC 600W PSU (84% efficiency)
3 x 250GB SATA-II HDDs
Optiarc DVD RW 18x SATA drive

And operating stats:
CPU 30C idle, 40C max under load
MB 30C idle, 35C under load
All voltages appear normal
Checking the exhaust fans from the case, all are running fairly cool (not
even warm).

I'll be externally grateful for any pointers to help solve this.

Many thanks, Dom.

Dom wrote:[color=blue]
> Hi, I'm really hoping someone can help me.
>
> I'm getting random crashes using Windows Vista 32-bit. They seem to come at
> any time - while installing an application, copying a file, running a game -
> there doesn't seem to be a pattern. The crashes are the straight-to-reboot
> sort of thing rather than blue screen of death. I otherwise really like
> Vista but I'm now tearing my hair out. I've had it installed since yesterday
> morning and I can't go on much longer.
>
> Please could someone help direct me to some way I can start to diagnose this
> (nothing appears logged in event views, etc.), or suggest a solution. I
> originally thought it was my running Intel Matrix RAID, but I've disabled
> that and am now running in IDE mode.
>
> Other threads have suggested a hardware problem, but given the system info
> I've shown below I'm not sure how this could affect me. I have run the
> Windows Memory Diagnostic overnight (5 runs in extended cycle) and it showed
> no memory errors.[/color]

(snip specs of very nice machine)

The specs of your machine have nothing to do with this (except that we
know the machine is not old). Your symptoms do indeed point to failing
hardware. It doesn't matter if your hardware is new; in fact if hardware
is going to fail it will usually do so pretty quickly or go for years.
Since you tested the RAM and it appears to be good, some other component
is failing - perhaps a bad processor, motherboard, power supply, etc. I
really don't think this is a software issue although you could test by
1) updating all your drivers one at a time and testing after each
change; 2) booting with a Linux live distro such as Knoppix (live
distros run from CD) and work with it. If the machine misbehaves
similarly under a different operating system, then you know for sure
hardware is at fault.

[url]http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot[/url]
[url]http://www.knoppix.net[/url]

If this is a new computer under warranty, don't mess about with it at
all and return it under warranty for replacement.


Malke
--
Elephant Boy Computers
[url]www.elephantboycomputers.com[/url]
"Don't Panic!"
MS-MVP Windows - Shell/User

"Malke" wrote:
[color=blue]
> The specs of your machine have nothing to do with this (except that we
> know the machine is not old). Your symptoms do indeed point to failing
> hardware. It doesn't matter if your hardware is new; in fact if hardware
> is going to fail it will usually do so pretty quickly or go for years.
> Since you tested the RAM and it appears to be good, some other component
> is failing - perhaps a bad processor, motherboard, power supply, etc. I
> really don't think this is a software issue although you could test by
> 1) updating all your drivers one at a time and testing after each
> change; 2) booting with a Linux live distro such as Knoppix (live
> distros run from CD) and work with it. If the machine misbehaves
> similarly under a different operating system, then you know for sure
> hardware is at fault.[/color]

Thank you Malke, I had a good look over the system and found that only one
of the two 4-pin connectors were connected to the CPU point. Although the
motherboard manual says this is ok, obviously something was going wrong so
I've connected both and it appears more stable.

Unfortunately I now get blue-screens but I have something to work on now. I
think it's graphics driver problems, but unfortunately the possible updates
can only be downloaded from Microsoft when I have validated Vista, which I
don't want to do until I have it stable and know I don't want to keep
reformatting (with XP this meant re-validation). I'll give MS a call
tomorrow and see what they say .

Thanks again.

Dom.

Dom wrote:
[color=blue]
> Thank you Malke, I had a good look over the system and found that only one
> of the two 4-pin connectors were connected to the CPU point. Although the
> motherboard manual says this is ok, obviously something was going wrong so
> I've connected both and it appears more stable.
>
> Unfortunately I now get blue-screens but I have something to work on now. I
> think it's graphics driver problems, but unfortunately the possible updates
> can only be downloaded from Microsoft when I have validated Vista, which I
> don't want to do until I have it stable and know I don't want to keep
> reformatting (with XP this meant re-validation). I'll give MS a call
> tomorrow and see what they say .[/color]

Hi, Dom - You don't want to use drivers from Microsoft anyway so you can
update the drivers without validating Vista. Here is information about
getting drivers:

Never get drivers from Windows Update. Get them from:

1. The device mftr.'s website; OR
2. The motherboard mftr.'s website if hardware is onboard; OR
3. The OEM's website for your specific machine if you have an OEM
computer (HP, Dell, Sony, etc.).

Read the installation instructions on the website where you get the drivers.

To find out what hardware is in your computer:

1. Read any documentation you got when you bought the computer.
2. If the computer is OEM, go to the OEM's website for your specific
model machine and look at the specs (you'll be there to get the drivers
anyway)
3. Download, install and run a free system inventory program like Belarc
Advisor or System Information for Windows.

[url]http://www.belarc.com/free_download.html[/url] - Belarc Advisor
[url]http://www.gtopala.com/[/url] - System Information for Windows

If you have installed drivers from Windows Update, you can roll them back:

How to Roll Back a Device Driver in Windows XP - [url]http://tinyurl.com/86yb6[/url]
Roll Back Troublesome Device Drivers in Windows Vista from the How-To
Geek - [url]http://tinyurl.com/346lox[/url]


Malke
--
Elephant Boy Computers
[url]www.elephantboycomputers.com[/url]
"Don't Panic!"
MS-MVP Windows - Shell/User

[color=blue]
> Hi, Dom - You don't want to use drivers from Microsoft anyway so you can
> update the drivers without validating Vista. Here is information about
> getting drivers:
>
> Never get drivers from Windows Update. Get them from:
>
> 1. The device mftr.'s website; OR
> 2. The motherboard mftr.'s website if hardware is onboard; OR
> 3. The OEM's website for your specific machine if you have an OEM
> computer (HP, Dell, Sony, etc.).
>[/color]

Thanks again! Lots of information that will prove useful. What I mean was
that there are Vista fixes designed specifically for Nvidia compatibility
which I can't get to (yet), I'd always get the drivers from Nvidia
themselves. :)

I have seen two different blue screens now though, so I may possibly have
other problems =/ I'll give it another day or two and then back to XP if I
can't fix it.

Dom.