Thanks for the suggestion Vince. I might do that. I take it external solutions wouldn't be affected by the usual problems of chipsets etc.
Interesting thread on extreme overclocking btw. Shows it can be done.
I did think about the SSD but they're not really big enough yet and to get the size I want I'd have to use raid which might be self defeating. I do love the idea of SSD though and can't wait until they are both bigger and cheaper.
In case anyone gets the wrong idea, my frustrations are not aimed at Vadim in any way who have always been very helpful throughout
Latest update on this (I had given up for a while).
I've tried the Vadim supplied raid controller. Still had problems. What I mean by this is the gradual corruption of files as before???!
Tried another model of controller. Same again.
Tried a new pair of disks. Same again although on one install it was alright for a bit but by 30 minutes later files were starting to get corrupted again.
Either I have a duff motherboard or raid will not work with my setup. A non raid system seems fine although I haven't stuck with one for more than a couple of days. Just to test it.
When I started out on this venture 2 years ago I thought this was going to be so easy
Edit: I spoke too soon about non raid. After reloading Vista 64 on a non raid, I'm getting corruptions again! Is this MB just rubbish?
I've been using 64k blocks which is what Vadim set it up with. I've also tried 32 and 128 but don't recall much difference in terms of stability. All had corruptions still.
I did originally think that this was only a raid issue but having tested a non raid setup a bit longer it seems not. The corruptions just seem to be as frequent or damaging.
All the drivers and windows settings are on default. Are there any specific settings I should check?
I haven't a clue about the power rails. How do you find that out about that without resorting to electrical tools?!
Since I've had this system I've had constant stability issues. I'm on my third MB, third cpu, second memory sticks, second set of disk drives. The only major component that hasn't been changed is the power supply. Is it possible that could be the cause of my problems?
I was thinking memory but I did some memory tests over 24 hours and it found nothing.
If it was a MB issue I'd expect to see lots of others with the same problem but it doesn't look like it, at least not this problem.
Update:
I've managed to get Vista 32 working with raid on the latest BIOS (1001)
I hadn't tried the 32 bit version on with latest BIOS. On the previous version of BIOS it didn't work though, raid or non raid. I'm very sure of that.
So far now (2 days) and after lots of updates, installs, defrags there aren't any signs of corruption
It would have been nice to get Vista 64 working (it still doesn't) but I'd settle for 32 bit as long as it's stable! I'm not too sure if SP1 allows me to access the full 4Gb of memory? It shows 4Gb.
ASUS did send me a new BIOS (1103) to try out with Vista 64 but having finally got it going I might leave it for a while. They didn't include any text file for changes, just the .bin file so I don't know if it addresses anything specific to my problems or it's just a stab in the dark!
I'm not too sure if SP1 allows me to access the full 4Gb of memory? It shows 4Gb.
I believe Vista SP1 causes the correct amount of physical memory to display, but the limitations of 32-bit operating systems remain, so it can still only use ~3.5GB (depending on your system).
I'm not too sure if SP1 allows me to access the full 4Gb of memory? It shows 4Gb.
I believe Vista SP1 causes the correct amount of physical memory to display, but the limitations of 32-bit operating systems remain, so it can still only use ~3.5GB (depending on your system).
I tried setting my overclock settings back to the Vadim supplied ones and then tried to install a game. Got a BSOD (STOP: 0x0000008E) during the install when it was just copying files. Nothing too complicated!
It dumps the whole of memory to a dump file but I don't know if it's worth trying to investigate that. The crashes seem pretty random, not at the same place or even at a point where something intensive is happening.
A later one was STOP: 0x1000007E with dxgkrnl.sys driver mentioned. Another one happened while I was just digesting the previous one and the PC was just idling. On the next load it had the code as "a". Not 0x0000000a but just "a"? Which seems to be something to do with interrupts.
Everything is updated to the very latest (no betas). Apart from updating windows and drivers, all I've put on the system is 3DMark 2006 and Crysis (after a few attempts).
Turning off the overclocking didn't get much further as it won't run at all now (Crysis that is). Just crashes when you start it.
I'm assuming this 1001 BIOS isn't as wonderful as I first assumed! The problem is if I go back to 0802, as came with the MB, I'm going to be back to a system that overclocks but corrupts the disk. I've already been there.
In 25 years of owning PCs I've never had a system that caused so much trouble! I chuck it out the window if it wasn't so heavy!
Sorry for the long delay to this response
Once you have updated your BIOS the settings may no longer work you will have to input the figures again as the profile may not work
the settings should be on your order form if they are not send us an ofritus and we will get you system back to how it was
