Different memory. It works!!!!!!!

[Jim T]

Ok, I am the one with the FIC AZ11E MB.
I took out the PC133 memory and replaced it with PC100 and it seems to be working ok!!!!!!!
Thanks alot, everybody!!!!!!!!

[Jim T]

Well, after screwing around in the BIOS, I put the PC133 memory back in and it fired up, no problem. I have my FSB jumper on the Motherboard set to 100 (like Reid said).
In the BIOS I have "DRAM Timing By SPD" which says This item allows you to use supports of Serial Presence Detect (SPD), the system BIOS can recognize its specificity, then do automatic timer setting SPD data"
I set this to enabled, which precludes me from selecting DRAM Clock, SDRAM Cycle Length, and Bank Interweave.
My question is "is the MB detecting the pc133 memory?" and is there a way to verify this???

Thanks again everyone!!!!!!

[andreadebiase]

good question! I have no idea, i am wondering the same thing here. I think with a jumper at 100 and the SPD on enabled probably the system runs at 133. Did you check this configuration: disable the SPD and select the 133 option for sdram timing (FSB jumper at 100 ofcourse).

[Jim T]

We are running the same conversation on two posts, so lets just use this one.
Your right, the MB jumper has to be on 100MHZ. Period.
When I get home, I will change the bios "timing by SPD" to disable, which will allow me to set the DRAM clock to 133 and see what happens.
Let ya know.

[andreadebiase]

ok! i`ll wait to know what happens. Probably you will not be able to notice the difference, assuming something will really change. Maybe there are software programs that allow to see the real SDRAM timing in a system. Anyway, in the FIC site, under FAQS for AZ11, there is a question related to the 100/133 FSB jumper and the answer says that the FSB jumper is NOT for memory issues but only for CPU and is recommended to be left at 100! (i guess is necesseray for overcloking!). So the FSB jumper issue is solved finally and the mobos are not malfunctioning!

[Jim T]

Yeah, I read that 100/133 FSB info also.
I did change the timing to 133 and it is working OK.
I also went to the FIC website and downloaded these drivers and it seems to running good.
IRQ to PCI driver
INF driver
4in1 4.28
And because my job was a MB/CPU replacement, I cleaned my Windows using the clean tweaks at www.tweak3d.net/tweak/cleanup (http://www.tweak3d.net/tweak/cleanup)
Great site-check it out.
And your system-everything allright?

[andreadebiase]

hi, so you changed the SDRAM timing in the BIOS only right? the jumper is still at 100 i presume. For which CPUs is that FSB jumper anyway?
My system is doing great, I am getting a bit of bad "elecric static" noises from the integrated sound chip when playing quicktime videos but i think is a matter of drivers. I will download the new driver version and if this does not fix it i`ll buy a good sound card. For the rest is all ok, AZ11E seem to be a good motherboard. What kind of video card you have? I have a Gainward TNT2 M64 32MB...it`s a $70 video card, nothing "special" but is doing a good job.

[Jim T]

Thats right-Jumper on MB is at 100, Dram in bios at 133.
I don't know about any AMD Processors that run 133 FSB.
I know Intel has them.
I have a Voodoo3 Video Card running on the PCI. It is all right, doesn't really "make my socks spin". Paid $99 for it 4 mo ago, before 3dfx went out of business.
I also have a Athlon 600MHz/Epox MB with a Geforce 256 card which I built and it really has a nice display.
I'd like to replace the Voodoo3 card with a Geforce2 card as soon as the prices go down (probably when the Geforce3 cards are out.

[andreadebiase]

did you notice any increase in performance when you changed the SDRAM timing from 100 to 133?

[andreadebiase]

Jim, in order to change the SDRAM clock from 100 to 133 is necessary to disable the "Dram Timing by SPD" option and so I did, now shall I leave it disabled or should I re-enable it?
thanks

[Jim T]

I left my "timing by Spd" disabled.
"clock" at 133
"latency at 2
I am unable to access the system till sunday, so I am wondering if after setting the clock to 133 will the timing by SPD set it at 133 or what?
Which brings me back to my other question---
Is there somewhere that tells you what your sdram timing is currently running at???? I will start another post asking this question specifically!

[andreadebiase]

Jim, unfortunately i don`t know! i did set the clock at 133 for SDRaM but i re-enabled the SPD option and doing so now it shows a clock at 133MHz "shadowed"............thus is it disabled? or just protected?
I think SPD knows if the SDRAM is 133 or 100 and sets parameters automatiocally at 133 (if u have 133). I kinda had the impression that with SPD enabled the PC is booting faster but i am not sure and i don`t know of any program telling you the actual timing.

[Jim T]

Ok, andrea, heres the latest.
I changed the bios to spd detect enabled and it boots up faster. With it disabled it would hang periodically during bootup and I would have to restart. But now with the spd enabled it boots perfectly. I still don't know if my pc133 memory is running at 133 or 100. See other post.

[andreadebiase]

cool, i downloaded the program suggested in the other posting and endeed the timing is at 133. By enabling SPD, even if the timing is set manually at 100, the real timing is set at 133. So SPD does everything for you and you have to do no settings. Bytheway, the frequent crashing you experienced when setting were input "manually" could be due to the CAS set at 2. If your DIMMs don`t support CAS2 the system crashes. With SPD enabled the proper CAS is selected automatically and that is 3 if you have one of those DIMMs in the price range $40-80 for 128Mb (i think CAS 2 SDRAM is very expensive!).
cheers