Printable View
Just installed Windows XP x64.
In XP 32bit version I had my system @ 3055Mhzs, mems @ 235Mhzs 2-2-2-5, rock stable, running Folding.
Now in x64 version even @ 3Ghzs it gives me a blue screen, MACHINE_CHECK_EXEPTION, and reboots. Second Windows install and still gives me the error.
Anyone with the same problem, or a solution?
EDIT: Tried 2900Mhzs (less 155Mhzs than in 32bit version) still no go, same blue screen =(
Silence
:( Sorry to hear this mate - but that's exactly the reason I stay with the 32 bit version.........Quote:
Originally Posted by [_Silence_]
:toast:
Well I was afraid of this also, but had to try it :PQuote:
Originally Posted by HARDCORECLOCKER
Anyway, if I can't find the solution till tomorow I'll go back to 32bit till someone gets a solution.
Really bad running my CPU @ default knowing it can do 3100Mhzs for daily use =( (I was running 3055Mhzs daily because of the high temperature here in Portugal, yesterday was 40ºc :D)
I ran into the same problem, I had to switch to 2T mem timings.
At 1T I wasn't able to run 275*10, but 250*11 seemed work just fine, in 32bit anyway.
64Bit would BSOD right after I tried to install Ati Cat's, and then bsod every subsequent reboot.
I tried changing every single Genie option, the closest I could get was getting 64 bit to boot and seem somewhat stable with DRIVE Strength=1 and Data Drive = 1 (on 510-1).
However, this made 32bit very unstable (SPI 32m mainly, didnt ever bother to prime since the other broke so fast).
Switching to 2T (sucked) but solved my problems, I can now leave drive strengths on auto and boot 32/64 bit fine at 275*10. Its possible that the ram speed going from 250 to 275 might make up for the 2T setting, but now at least I can use my computer in both worlds.
HTH
;) All I saw so far 64 bit version causes only trouble.Quote:
Originally Posted by [_Silence_]
PLZ, send some of Ya 40°C to Germany - much to cold here for June, not even the half of portuguese temps.......... :(
:toast:
I tried 2T too, but still no go, same blue screen =(Quote:
Originally Posted by bottone
No way :PQuote:
Originally Posted by HARDCORECLOCKER
40ºc is perfect to go to the beach and enjoy the hot water and hot girls :P
Did you try to put the memory/alpha timings on Auto?
I'm not so sure the bios defaults are the least aggressive...
I had no probs runing everything at the same overclock speeds as i do in 32 bit windows XP.
I had stability problems too but it seems that it was the beta audio / video drivers :banana::banana::banana::banana:ing with me.
For any of those who actually got it working in x64, did you experience anything to be faster? The general thing I hear about x64 is that almost everything is much more responsive, though I do not know if that actually corresponds to an overall better performance.
There is absolutely no difference.
xp64 suxor!! last week I'd only played around with it couple hours and unloaded that crap immediately, you probably have better luck with win2k or win2k3 if you want to try something new, win2k3 is more stable than xp and I can clock higher without BSOD as I normally would on XP.
It your like me, it will be to do with the ram not the CPU. Try playing with CPC, dram drive strength, and dram voltage options(I had to lower mine with TCCD).
What are the minimum system requirements for xp64? the higher the requirements the less performance it seems you can get with over clocking, just look at how high you can get your system to run at in Dos compared to the GUI...Quote:
Originally Posted by [_Silence_]
I have a funny feeling this is related to the whole execution prevention thing.
There is a thread about it in XP SP2 here:
http://www.dfi-street.com/forum/showthread.php?t=12303
Solution is here:
http://www.dfi-street.com/forum/show...8&postcount=50
Bascially, with SP2 installed (and hence DEP on by default), I could not overclock past about 2.5 - 2.6 Ghz.
With Win 2k and SP1, I could happily go to 2.9 Ghz.
When I disabled the noexecute 'feature' of SP2, I could clock the same! :banana:
HOWEVER,
The noexecute 'feature' doesn't appear to be disableable (hehe nice word there!) in Win XP 64:
http://www.amd.com/us-en/assets/cont...4_pubfinal.pdf
Look on Page 19 'How Noexecute protection is configured in boot.ini'
See what I mean? It's always enabled in the kernel and in 64bit user mode. You can ONLY disable it in 32bit WoW mode...
Anybody else have anything to add?
Quote:
Originally Posted by Jimbo Mahoney
Ok, through Recovery Console I was able to change the "noexecute" to AlwaysOff, but I still have same problems, no go with OC =( Btw I verified with "bootcfg" and yes it really was AlwaysOff.
Well I'm going back to my 32bit Windows till this problem is solved.