Vista 64 issues

matt100 · 31 Jan 2008 at 01:11

Is it common for windows 64 to pretty much constantly be telling you one process or another has stopped working?

Its doing my head in! Either its the installer service, host process service etc etc etc.

Is this just my experience or is it just one of those things with being 64bit? my 32bit copy was flawless.

matt100 · 31 Jan 2008 at 08:59

deleted

matt100 · 31 Jan 2008 at 09:24

edited

I figure it could be a RAM issue too, I switched at the same time as upgrading so it could be that, I'll memtest it. Its bluescreening a lot too.

matt100 · 31 Jan 2008 at 20:16

NathanE said:
Check your memory voltages.

DDR2 is very sensitive about voltages.

hmm

I seem to be sort of getting somewhere by putting my pc back to stock which really I ought to have done from the off for installing windows.

Is it so sensitive to the point where 2.15v which is over the mfr 2.0-2.1v would upset it?

matt100 · 31 Jan 2008 at 21:56

I was yeah, it was a very safe 3.2 on a Q6600 G0, I'm reinstalling now which seems to be going ok apart from defender reckoning it had stopped working.

I seem to get a silly amount of "display driver has stopped responding" etc too, only since vista 64 though. I have xp64 I could give a whirl I guess, I've just got used to vista, I like it.

Mind you I'm on my xp laptop now that just works.. period.

matt100 · 31 Jan 2008 at 22:35

yeah its an 8800gtx.

attempting to install 60 updates now and the updater module has stopped working a couple of times.

Not terribly impressed but I'll soldier on!

matt100 · 1 Feb 2008 at 01:41

mattyrigby00 said:
if windows was installed when overclocked, file(s) mightve got corrupted during the install.

I've reinstalled tonight all at stock and it only seems slightly better...

still during updates it has some process or other stop working and keeps bluescreening due to the memory manager? Is that faulty sticks?

matt100 · 1 Feb 2008 at 13:38

I gave them a go with the vista memory tester thing and they seemed to be ok.. I'll try memtest.. its test 5 isn't it?

matt100 · 3 Feb 2008 at 23:43

I came back to it the other day to find my screen a garbled mess, inevitably it was a knackered gfx card. The break was caused by a leaky EK waterblock and the gpu core was washing about in feser.

There was a fair bit in the pci-e slot too which I've cleaned out and now it all seems fine, I also changed psu from a 600 to a 620w but I doubt that had much to do with it but its been on an hour now with no processes stopping so, maybe it was the gfx card dying?

matt100 · 4 Feb 2008 at 00:15

nope, dead as a dodo.

to be fair there was a fair bit of it in there and it wasn't shorting but I think over time it can become conductive.