General discussion

Locked

direct 3D not working

By clark-hans ·
As my grandchildren are now into high level games I decided to upgrade my AGP cards, but their games did not work, and in dxdiag the spinning cube looks like shattered glass, have tried updated drivers, and loaded direct X8, all the other tests wereOK. I have tried 3 different cards, ATI MAXX, Apollo32mb, and the present one S3 savage4, the mo'bo' is a FICAZ31. Hope you can help, thanks, Clark

This conversation is currently closed to new comments.

20 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

direct 3D not working

by TheChas In reply to direct 3D not working

The cards should be adaquete for 3D.
I personally think the Savage 4 is a bit slow.

Anyway, make sure that you have the latest AGP mini-port driver installed for the motherboard / chipset.

I would also check the BIOS settings.
Make sure thatAGP 4X mode is enabled.
The Graphics Aperature should be set to at least double the memory on the card, and up to 1/2 of system RAM.

Make sure that the monitor is detected correctly.

Chas

Collapse -

direct 3D not working

by clark-hans In reply to direct 3D not working

I found the AGP mini port driver for this board and installed it OK. Also the 4x mode was on, but instead of aperture size which I was expecting to find, there was a box which was set to auto, when set to manual the settings were unknown to me, the setting default was CB, and there were numerous settings rangin from AB through to 64, with various combinations like, ab, fc, b3, f6 etc. No amount of configuring has made any difference. The monitor was detected correctly.

Collapse -

direct 3D not working

by smmurphy In reply to direct 3D not working

You stated that you updated drivers, did this include the monitor? I had a similar issue after I had to replace the original monitor with an older monitor (The original burned out & I was waiting for HP to ship the replacement). The drivers needed to be updated to work with the upgraded video card.

Collapse -

direct 3D not working

by clark-hans In reply to direct 3D not working

The monitor is a Samsung digital 17"GLi and worked fine with another machine where the cards worked fine also. This is a case of finding the fault, no direct 3D working, but have found no solution as yet, having fun but losing my hair!!

Collapse -

direct 3D not working

by TimTheToolMan In reply to direct 3D not working

Hi,

I'm just answering for the moment to let you know I have the same problem with my partner's machine. She doesn't play too many games so I haven't really been worried about it.

But for the others who may read this, my setup is different again, A LeadTek GeForce2 MX 100/200 and the problem happens on both WinXP and Win98.

...so dont close this question for the moment, I'll be looking for a solution and will post it back here as a comment when I find it :-)

Cheers,
Tim.

Collapse -

direct 3D not working

by TimTheToolMan In reply to direct 3D not working

Hi,

Well, I'm glad TheChas is still looking at this one :-)

For Clark's and TheChas' benefit, I thought I might explain my problem a bit more fully...

I first noticed this problem some months ago when Monique's PC with WinXP blue screened with an infinite loop detected on the video driver. After that the MS Plus aquarium screen saver displayed corrupted fish. Much like the broken glass Clark mentioned.

At that time, I located a "fix" for that crash but was unable to find the actual patch for fixing it. Perhaps TheChas remembers my one and only question ever posted on TechRepublic on this? :-)

So it *was* working but then failed.

It came around again when I tried to run Dungeon Siege on the PC for some of Monique's kid cousins. I was in a hurry to get it working for them so I thought I'd put it up on Win98 (The dual boot on her machine)

But that didn't help. Since then Clark has shown it isn't Video card dependent and I've shown it isn't OS dependent. Consequently,I dont think it'll be driver dependent either.

I liked TheChas' thoughts that it may be memory speed dependent cause one 64Mb bank in Mon's machine is a very old one... but it doesn't have troubles with anything else and I'm running her FSB at 100Mhz which *should* be in spec for it...

I guess its possible its not, though, and I'll try removing that card to see if it makes a difference...

To finish up, here are the specs of the machine.

SocketA Athlon 700Mhz (100Mhz x 7)
abit kt7 motherboard.
384Mb memory in 2x64Mb + 1x256Mb
Leadtek GeForce2 MX 100

+ nic, awe64 sound, and the usual HD, floppy, and CD....

WinXP & Win98 Dual boot (both with the same problem)
Norton Antivirus.

I'll post back here after my test removing the memory.... she's using the PC right now for her Uni assignment right now, though...

Hope this helps,
Cheers,
Tim.

Collapse -

direct 3D not working

by TimTheToolMan In reply to direct 3D not working

Hi Clark,

FYI, Here's what I've tried so far to get my problem fixed. I'm 95% confident we have the same problem by the way - same results in dxdiag, same problem only with 3d games.

I've removed the older 64Mb boards, leaving 256Mb.
I've Upgraded the BIOS
I've Upgraded the drivers for the video card
I've performed an upgrade installation of WindowsXP (Haven't tried re-installing win98 yet, though)

None of this has helped.
Next I'll try putting the video card in another machine andsee if the problem "follows it".

Cheers,
Tim.

Collapse -

direct 3D not working

by clark-hans In reply to direct 3D not working

Hi Tim, I have given up and re-installed windows with the card istalled, same problem!! The motherboard has an updated bios and all the suggestions here have been implemented. I have been to the FIC website and am going to download A-Z until I find a solution, if I do not find one am going to try to see if the mobo can fly!! If I do find a solution bet your life this problem never comes up again, c'est la vie!!

Collapse -

direct 3D not working

by TheChas In reply to direct 3D not working

I'm looking over the AZ31 Manual right now.
There is an option to set the AGP Aperature under Advanced Chipset Features.
I believe what you were changing was the Driveing control. Leave this on Auto.

Since this is a Socket A motherboard using PC100/133 SDRAM, double check the CPU speed settings.
Per the manual, you need to use a utility that is on the motherboard CD.
The FSB should be set to 100MHZ, the multiplier must be set appropriately for the CPU. (10X for a 1GHz)
Set the memory clock accordingly in BIOS.
Make sure that the FSB jumper on the MB is set to 100MHz.

I have seen numerous "strange" problems with socket "A" motherboards, when the BIOS auto-detected the CPU frequency settings.
I now manually set the clock speeds on every socket A board I setup.
(many clock a 1GHz at 500MHz even though they detect the CPU as a 1GHz)
(I suspect that htis is a problem since PC100/133 SDRAM based MBs do not support the 200MHz FSB)

Chas

Collapse -

direct 3D not working

by clark-hans In reply to direct 3D not working

Hi, had sent a reply but notice it is not here!! So, here it is again in case. The mobo is not quite the same as the manual, no aperture size adjustment, the adjustment to the cpu clock not found, the cpu detected correctly, the jumper for the 100/133 set to 100 OK, as well as in bios. The only adjustment is the driving control which I had never heard of, I have checked for updated drivers and installed them but to no avail, I am about to check for motherboard drivers again, will let you know, meanwhile I am upgrading my other computer and will test the cards in there.

Back to Hardware Forum
20 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums