hey kids. Over the last couple of days ive been getting some weirdness with my q6700. Its not overclocked, its all at stock settings (although ive a tuniq tower fitted for future overclocking). The rig is six months old and has been fine mostly in that time.
A couple of days ago I rebooted and the machine hung at POST screen. i left it sat there to see if it sorted itself, but five minutes later still nothing so i reset. it did it again. then i noticed it was reporting a processor speed of 1.59mhz!!!! wtf??
Its a striker extreme (i have 1504 bios) which has a helpful CMOS wipe button on the mobo, so i shut off and wiped it. it rebooted fine and picked up the speed correctly. Strangely tho, ive been sat here with CPUZ running for a half an hour and it keeps flitting from 1.59mhz to the correct 2.6mhz. it stays at 1.59 for seeral minutes, changes to 2.6 for a few seconds then goes back to 1.59 for minutes.
Ive had varios blips and glitches with the striker extreme and im the verge of changing it tbh. does anyone know wots going on here? i havent fiddled at all in the bios so it cant be a borked overclock - in anycase, i reset the cmos to factory setup so something weird is definatly goin on.
A couple of days ago I rebooted and the machine hung at POST screen. i left it sat there to see if it sorted itself, but five minutes later still nothing so i reset. it did it again. then i noticed it was reporting a processor speed of 1.59mhz!!!! wtf??
Its a striker extreme (i have 1504 bios) which has a helpful CMOS wipe button on the mobo, so i shut off and wiped it. it rebooted fine and picked up the speed correctly. Strangely tho, ive been sat here with CPUZ running for a half an hour and it keeps flitting from 1.59mhz to the correct 2.6mhz. it stays at 1.59 for seeral minutes, changes to 2.6 for a few seconds then goes back to 1.59 for minutes.
Ive had varios blips and glitches with the striker extreme and im the verge of changing it tbh. does anyone know wots going on here? i havent fiddled at all in the bios so it cant be a borked overclock - in anycase, i reset the cmos to factory setup so something weird is definatly goin on.