overclocked
Veteran
I don´t know how too describe this problem but i´l give it a try.
The cpu a 2400+ would start in a system i build for my friend but then reboot itself after awhile, we/i didn´t notice it first because another friend took the job too install the OS(XP-HE).
After many hours of testing i find the cpu as damaged and after countless tries i put in my Duron 600Mhz and the computer worked fine.
After some time my friend (of course) wanted me to test it again, and i did mainly just because we had ruled out any other hardwareproblem.
Well after spending quite some time i couldn´t find the motherboard manual, apparently it had been cast away, so back to square one.
My pal really wanted me too give it another try so i decided to put the cpu in my rig/A7V8X to see if any miracle would happend.
Ok i boot up my rig and managed to get in too Windows, then the EXACT problem came up and windows rebooted.
Ok so now i have done some "extensive" tweaking (about 4 hours) in the BIOS and used diagnostic tools in windows too test stability etz.
OK, here is what i have find out=
1. The CPU is NOT stable at stockspeeds settings, even if i slighty increase the Vcore.
2. I find out the cpu to be "unlocked" soo i decresed it and booted up at 1,3~Ghz and find it stable.
Beginning too tweak from there on(as i now know the cpu "works") i find it stable at 166/33*12=1,93~ghz. this is as far as i can push it EVEN with increased Vcore and relaxed settings/no superfan/heatsink and no arctic silverpaste. Simply because i thought the cpu was done, damaged.
I really need some hint here at what´s going on here, and your suggestions and theories because this has been bugging me for month´s now.
Feel free too ask about the system´s and rig´s and i could use a good CPUID tool also(just formated c..
Thanks
The cpu a 2400+ would start in a system i build for my friend but then reboot itself after awhile, we/i didn´t notice it first because another friend took the job too install the OS(XP-HE).
After many hours of testing i find the cpu as damaged and after countless tries i put in my Duron 600Mhz and the computer worked fine.
After some time my friend (of course) wanted me to test it again, and i did mainly just because we had ruled out any other hardwareproblem.
Well after spending quite some time i couldn´t find the motherboard manual, apparently it had been cast away, so back to square one.
My pal really wanted me too give it another try so i decided to put the cpu in my rig/A7V8X to see if any miracle would happend.
Ok i boot up my rig and managed to get in too Windows, then the EXACT problem came up and windows rebooted.
Ok so now i have done some "extensive" tweaking (about 4 hours) in the BIOS and used diagnostic tools in windows too test stability etz.
OK, here is what i have find out=
1. The CPU is NOT stable at stockspeeds settings, even if i slighty increase the Vcore.
2. I find out the cpu to be "unlocked" soo i decresed it and booted up at 1,3~Ghz and find it stable.
Beginning too tweak from there on(as i now know the cpu "works") i find it stable at 166/33*12=1,93~ghz. this is as far as i can push it EVEN with increased Vcore and relaxed settings/no superfan/heatsink and no arctic silverpaste. Simply because i thought the cpu was done, damaged.
I really need some hint here at what´s going on here, and your suggestions and theories because this has been bugging me for month´s now.
Feel free too ask about the system´s and rig´s and i could use a good CPUID tool also(just formated c..
Thanks