Soldato
- Joined
- 4 Nov 2006
- Posts
- 2,752
- Location
- Yorkshire
Since building the rig in my sig, i've had nothing but hassle (mainly with the whole system freezing whilst playing COD4 MP)
Anyway, last few days i've been coming home from work to find my PC with a blank screen and the CPU fan speed reset so it's fair going for it
I have to kill the power, switch it on, at which point ASUS EZ Flash comes up saying the BIOS is corrupt of some kind and re-flashes back to the original BIOS that came with the board ... When i eventually get in to Windows, in the event viewer i see this error, constantly every few mins, about 10 mins prior to the shut down:
but it doesnt say what HARDWARE, whether thats actually RAM, the mobo, or my graphics card
I have run MEMTEST and Vista RAM Diag a few times in the past due to the COD4 issue, and last few days i've been leaving it running overnight and no errors are found on either sticks/slots ...
What do you think it causing this? OS is Vista Enterprise x64 and rig is in my sig ... i've had the latest BIOS on, all latest drivers etc .. i work in IT myself so kinda done all the main troubleshooting steps ...
Anyway, last few days i've been coming home from work to find my PC with a blank screen and the CPU fan speed reset so it's fair going for it
I have to kill the power, switch it on, at which point ASUS EZ Flash comes up saying the BIOS is corrupt of some kind and re-flashes back to the original BIOS that came with the board ... When i eventually get in to Windows, in the event viewer i see this error, constantly every few mins, about 10 mins prior to the shut down:
Code:
The hardware has reported an uncorrectable memory error.I have run MEMTEST and Vista RAM Diag a few times in the past due to the COD4 issue, and last few days i've been leaving it running overnight and no errors are found on either sticks/slots ...
What do you think it causing this? OS is Vista Enterprise x64 and rig is in my sig ... i've had the latest BIOS on, all latest drivers etc .. i work in IT myself so kinda done all the main troubleshooting steps ...
