I have to add some stuff soon - I have lots to tell, I know you're excited to know ;)

Bat Flattery

Oh, and I have managed to charge up 38 Batteries in the last 35 Days. One. By. One. Almost glad I lost 2 the other day.

Still be my beating heart

So - I just thought I'd drop in to say 'HI'

I mean it's not like THE DEGREE is proving to be difficult or anything.

PC Works pretty well now.

This 'blog - it's aims. V1.20

This blog is now also about poetry and jobhunting.

There - I said it.

PC testing via elimiation

Well, it's been several days since we last had a crash on the new PC so I am beginning to think that it may have been solved, huzzah!

There were two small things I did which may, or may not have helped here: adjusting the cables between the motherboard tray and the removable side door so they, and the Molex/fan connectors are not squashed. And finding a poor quality Molex with a pin pushed half out by inserting the other plug, which may well cause noise on the PSU rails and errors.

Seeing as the fault manifested itself as a nonspecific 'memory error' I am well inclined to believe that a fault in the QPI transmission would cause an error like this, and bumping the QPI voltage should help to fix it.

More as I get it! And bike stuff next time too.

Compy 386 Update

I was a bit freaked out when one of the guys on Tom's hardware forum said he'd heard of a lot of problems with the UD3R, but later he came back saying that it was mostly caused by RAID issues, which is not something I worry about at the moment!

More Computer Testing

Over 6 hours of memtest passed. Will now try prime95 - Large, in Safe Mode.

Prime seems fine for 40 mins or so, so I doubt the CPU has gone faulty. I have bumped a couple of voltages in the BIOS, as it seems to be a stability problem with the motherboard.

Vcore is/was 1.2625
QPI/Vtt is 1.275 was 1.175
IOH Core is 1.3 was 1.1
DRAM Voltage is/was 1.66 [reads 1.65 under load in SpeedFan]

If this doesn't help I will try some graphics card tests I guess.