Soldato
- Joined
- 7 Jul 2009
- Posts
- 16,234
- Location
- Newcastle/Aberdeen
Well my PC is ageing a bit, but i recently bought a Gigabyte P35 board to keep it going a bit longer. That's an E2140, 2GB 667 DDR2, an 8400GS (with self modded cooler 
) and a WD 160GB HDD. Cooler's a Nexus XiR-3500 i bought for £5 from somebody who won it in a competition, so the CPU seems to sit at a cosy 25-30C most of the time.
Anyway, i've had problems recently whereby it just hangs on the Gigabyte POST splash screen, and i can't do anything apart from turn it off and on again. This fixed the problem, up until this morning, when no amount of restarting seemed to make it work. So i opened it up, cleaned some dust, tried (and failed) to install an old speaker that plugs into the mobo - start it again, it hangs. Restart, it works
So... any ideas? There's no beep codes, i was running an overclock to 2.6GHz (i think, whether or not it just reverted to default on it's own after the first boot is anybodies guess), which just gave up, i think when this problem started to arise. Not much to go on, i know - sorry about that. I just can't help but think that this might be a symptom of a larger problem that's about to strike...
) and a WD 160GB HDD. Cooler's a Nexus XiR-3500 i bought for £5 from somebody who won it in a competition, so the CPU seems to sit at a cosy 25-30C most of the time.Anyway, i've had problems recently whereby it just hangs on the Gigabyte POST splash screen, and i can't do anything apart from turn it off and on again. This fixed the problem, up until this morning, when no amount of restarting seemed to make it work. So i opened it up, cleaned some dust, tried (and failed) to install an old speaker that plugs into the mobo - start it again, it hangs. Restart, it works
So... any ideas? There's no beep codes, i was running an overclock to 2.6GHz (i think, whether or not it just reverted to default on it's own after the first boot is anybodies guess), which just gave up, i think when this problem started to arise. Not much to go on, i know - sorry about that. I just can't help but think that this might be a symptom of a larger problem that's about to strike...