• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

A64 3500+ @ 2.6Ghz = Data Corruption?

T

Twist

n00b
Joined
Jan 30, 2004
Messages
29
I've had to format my drive a few times because the hdd can't find the bootup files or programs will just stop running. If I try to install windowas at 2.6 I get IRQ Errors, I've cleared the CMOS and all that before overclocking.. I was running 237x11 and HT at 4x ( won't boot at 5x ) .. I'm new to A64 overclocking but I'm pretty good with P4's. I've never really had a problem like this before =( Also the voltages were.. 1.6v on the CPU and 2.8v on the memory.

3500+ NC -- Zalman CNPS 7000Cu
MSI Neo2 Plat
2x512mb XMS PC4000
9800 Pro 128mb
80gb Seagate 80gb.


Any help is appreciated. Thanks
 
i bet you are using sata. you should try installing windows on ata drive
 
Twist said:
Would it really matter that much? Yeah I'm using SATA..
Click to expand...

More importantly, what channel do you have that sata drive on? Try 3 or 4, not 1 or 2.
 
SATA = PCI bus (I believe, if not it's own bus that is affected by the HTT)...when you overclock your HTT's frequency, everything else goes up too....PCI and AGP both, and SATA's as well (EIDE'd do not tho). The PCI/AGP have locks now on most board, but on your board, the 3rd and 4th SATA's are the only 2 that are locked (the ones rightbelow your CPU).

Switch over to those, problem fixed.
 
Definatly switch to SATA 3/4 (over vid card) as those are the ones that lock. ALSO, in your cell menu, set the AGP Frequance to 67mhz. For some reason this board locks at 67 instead of 66mhz, so if you leave it at 66, your AGP/PCI bus does NOT lock!
 
That's the thing I'm using sata channel 3 for the only hard drive that's in the system.. Also if I set the AGP/PCI Frequence to 67 would that hurt the video card/etc?
 
Twist said:
That's the thing I'm using sata channel 3 for the only hard drive that's in the system.. Also if I set the AGP/PCI Frequence to 67 would that hurt the video card/etc?
Click to expand...
i think that was a typo he ment 66
 
No actually, I've read that you have to put it on 67mhz to enable the lock..
 
Yes, on the Neo2 the AGP lock isnt enabled unless you set it to 67mhz. Thats why your getting data corruption. Your AGP Freq. may say 66mhz, buts its not. Your sata drives are fllipping out because they really hate being over spec. Set it to 67mhz and you should able able to OC like a dream .
 
what kind of memory do you have? something very similar happened to me and it was caused by my memory timings being too tight. try run memtest with your curent settings overnight and see if you have errors. or just loosen the timings and see if your problems go away
 
Viper87227 said:
Yes, on the Neo2 the AGP lock isnt enabled unless you set it to 67mhz. Thats why your getting data corruption. Your AGP Freq. may say 66mhz, buts its not. Your sata drives are fllipping out because they really hate being over spec. Set it to 67mhz and you should able able to OC like a dream .
Click to expand...


Here's the thing, when I set it to 67mhz on the AGP, it will boot into windows, but, it won't be stable, and I think part of the Data corruption was SP2's Fault, last night I didn't have SP2 installed, and I was playing all my games just fine, cs1.6/css/hl2/ut2k4/farcry .. and then after I installed SP2, Explorer.exe would lock, and also the game's .exe's would just close ( yeah, even steam would do this ) WITHOUT ANY overclock..
 
Twist said:
Here's the thing, when I set it to 67mhz on the AGP, it will boot into windows, but, it won't be stable, and I think part of the Data corruption was SP2's Fault, last night I didn't have SP2 installed, and I was playing all my games just fine, cs1.6/css/hl2/ut2k4/farcry .. and then after I installed SP2, Explorer.exe would lock, and also the game's .exe's would just close ( yeah, even steam would do this ) WITHOUT ANY overclock..
Click to expand...

Well, running out of spec could have caused permanent data corruption. I would do a full format to make sure your system is clean, and then try your OCing again making sure your AGP speed = 67mhz. Also, if you dont already, I suggest you do this. Make a windows partition that is about 10gb, then leave teh rest of your drives space for games and storage. That way, if you experiance corruption like this again, you can format and only loose windows, not all your games and stuff.
 
I think it was a conflict with SP2 and my games ( I have no idea it worked just fine with my k8ns ultra ).. Anyways everyting is up and going good right now without SP2 ( also with no overclock ) -- when I try to put any OC at all on the CPU it will get into windows then fault, but before, even with the data corruption I was able to get into windows and operate fine ( did a few super pi runs to 1m) @ 2.53Ghz... and I booted into windows a few times at 2.6Ghz too
 
Twist said:
I think it was a conflict with SP2 and my games ( I have no idea it worked just fine with my k8ns ultra ).. Anyways everyting is up and going good right now without SP2 ( also with no overclock ) -- when I try to put any OC at all on the CPU it will get into windows then fault, but before, even with the data corruption I was able to get into windows and operate fine ( did a few super pi runs to 1m) @ 2.53Ghz... and I booted into windows a few times at 2.6Ghz too
Click to expand...


So, you formatted, and now your running SP1, and you can't overclock at all? Did you reset your bios? Make sure you set all your voltages properly.
 
Yup, cleared the cmos to make sure everything was cleared before I started OCing again.
 
Twist said:
Yup, cleared the cmos to make sure everything was cleared before I started OCing again.
Click to expand...


And all your voltages were checked? I have never heard of an issue like this, it just makes no sence. Even with a 5mhz fsb bump, no go? Can you post and just not boot windows? Voltages stock or changed?
 
I'm not so sure about that "lock" at 67 MHz. I had a 90nm A64 up to 325MHz fsb and no problems at all.....(w/ 66) i did have a great PSU and my SATA drive on #3
 
Yeah it's really weird...

I put my settings at what I had them to before formatting:

FSB - 230mhz ( to be safe )
AGP - 67mhz
Vcore - 1.6v
Vdimm - 2.8v
I even tried my HTT at 3x to make sure.. ( usually at 4x )
 
I've helped a buddy once with a 3500+ 130nm and thats about were we got his chip too. They just don't go that high in my opinion.
 
But the weird thing is that it WAS overclocking just fine, but now it will get to windows, to a desktop, and then crash. I just tried it at 66mhz on AGP, and it still didn't help it..

Also just tried it at 215mhz FSB
 
gclg2000 said:
I'm not so sure about that "lock" at 67 MHz. I had a 90nm A64 up to 325MHz fsb and no problems at all.....(w/ 66) i did have a great PSU and my SATA drive on #3
Click to expand...


I heard it from other members, and its also stated in the [H]ardOCP review. Maybe later revisions don't have an issue or something, because obviosuly your PCI bus would be a goner at 325mhz fsb. Just relaying what I was told.Never had a problem at 67mhz up to 260fsb
 
A user at Anandtech told me to try my memory timings a little differently so I did.. now running 250x10 and memory timings at 3-4-4-10 2T, so far so good.
 
Twist said:
A user at Anandtech told me to try my memory timings a little differently so I did.. now running 250x10 and memory timings at 3-4-4-10 2T, so far so good.
Click to expand...

Ewe, those arent very good timings. What memory do you have?
 
Corsair XMS PC4000

I know they're not very good timings, but atleast I found out that I can OC again..
 
Twist said:
Corsair XMS PC4000

I know they're not very good timings, but atleast I found out that I can OC again..
Click to expand...


Ah yes, thats why. 3-4-4-10 is the native timings. I had the same problem with my KHX4000. I could overclock up to the rated mhz, but even at DDR400, I coulnt change the timings.
 
You must log in or register to reply here.
Back
Top