Ok, I've been running the following system together for about 3 weeks now... Abit NF7-S v2.0 1GB (2x512) TwinMOS PC3200 XP2500 AQXEA Alpha 8045 w/ Antec 80mm fan Along with this went the rest of my stuff which was carried over from one rig to the other, hdds (2x Raptors and 2x Maxtor +9s), sound card, case, 400w Sparkle PSU, RAID card etc). Anyway, this particular has to my disappointment always been something of a rubbish overclocker, needing 1.85v just to do 190x12....very poor really, but it was prime 95 stable at that speed. A few minutes ago I was using the computer, and it crashed with an error message relating to w32k.sys or something, anyway I thought little of it and restarted. The BIOS from then on started detecting the cpu as an XP3200, every time. Going into the BIOS allowed me to set the cpu to manual, which worked, or auto, which would always give me XP3200 despite the chip being an XP2500. Anyway, a reset of the cmos later and it was fine again, detecting the chip as an XP2500. But now it is no longer prime stable at 190x12, with identical BIOS settings . I find it slightly disconcerting that the BIOS, through no apparent reason, decides my cpu is something totally different after giving me an unexplained crash (first time I've seen that particular error message). Is it possible that there is something wrong with the motherboard or cpu? The cpus always been a *very* poor clocker by the standards of most AQXEAs, but there always are good cpus and bad ones. But only until now has it started doing something this strange.... Any suggestions?
as I mentioned to you on MSN, the d18 bios fixes the XP3200 problem, and also it's more stable on the SATA side of the fence
