View Full Version : Possible Irq Conflict U Tell Me
acideater
August 27th, 2003, 04:32 PM
My new computer is running like shit
amd2400
128 ddr ram
40 gig
128 ddr geforce fx
s3 savage onboard video
If Im not giving enogth info let me know
Before I even set up my computer for the first time I added a geforce fx with 128 ddr ram and installed the latest drivers for it and then disabled the s3 savage in the device manager ( Now disabling it in device manager would be the only thing I had to do correct ? ). I then tried to play warcraft 3 and it got choppy .Then I attempted to play sof2 it gots choppy and it recognized my card as a geforce1. ( I later checked in unreal to see if it recognized it as a geforce fx and it did. When I tried to play unreal2003 It worked fine not great .I then turned the graphics all the way up and it got choppy then said closed to desktop and it said virtual memory is too low.
Now Im thinking it is either:
1) Need more memory
2) IRQ conflict between the s3 and the geforcefx (If it is how would i go about checking it)
Im confident i dont have a virus cause I didnt download nothing got a firewall and did a scan
Now If any1 has any comment that may be helpful I would appreciate it so much that when I take over the world Ill give you albania.
The Hunter
August 27th, 2003, 04:38 PM
I am not Krell, but i think you need more memory, especially when rendering the kind needed in fast video games. my thoughts are add at least a stick of 256DDR to your pc. Hell I am just doing basic things, and I run 512 of pc 133. More ram is never a bad move.
Winphuk
August 27th, 2003, 04:54 PM
What OS are you using?
You can help by throwing in another stick of RAM, but there are ways of increasing your virtual memory. (the size of your page file)
I need to know what OS you are using
REDO
August 27th, 2003, 05:02 PM
I dont think it is an IRQ conflct. The new OS's use IRQ sharing, so IRQ conflicts are very rare. And to fix that, you have to reinstall the OS with acpi disabled in your bios. IRQ conflicts usually dont give bad performance either. They usually give some kind of BSOD, a flickering moniter. There would also be an exclamtion mark next to the device in the device manager.
I can almost gaurantee you it is the ram issue. You need at least 256 now days. Preferable 512. What kind of ddr is it? Dont buy cheapo ram, and make sure you get at least ddr 2700.
I also noticed that your running an s3 svage on board video. Thay may also be causing your problems. You need an ati radeon or a geforce 3. Disable that s3 savage, and install something else. If im not mistaken, those are kinda old.
One word of advice. Never go with onboard video it only causes problems. Onboard sound, or LAN, doesnt matter much. But onboard video is a pain in the but.
phalkon30
August 27th, 2003, 05:30 PM
Here's my stab.
Dissabling the video card in windows is NOT the way to do it. Go into your bios (tap F2, or tab, or sometimes F1, F8, or any other random key that your motherboard may use...check the manual, or it should tell you while booting up)
Once you're in your bios...well, I don't know what kind of bios you have, so I can't step you through very well, but it shouldn't be too difficult, just dig around a little, it shouldn't be hard to find.
You can also check around in your bios and look at the speed of your AGP bus (I'm assuming the card is 8x, being the FX), and the AGP apperature size. With only 128 meg of ram, that could affect the game greatly, but turn your AGP apperature size down to 32 meg.
Also check your processor. Sometimes the multiplyer is never turned up, do the math. 13 (Multiplyer) x 133mhz bus = 1729 mhz (I think thats a 2100, but you get the idea). Find your Bus speed (don't mess with it), then find out how fast your processor should run. Divide the processor speed by the bus speed, and you find what your multiplyer should be at. This greatly improved the performance on a friends (2100 running at 1.1ghz, not 1.7, HMM)
If you do change your processor, put it under a full load for a while, and check your temps. You might have to underclock if it gets too hot, or get a case fan. Most stock cooling fans/fins should be enough to run it at its normal speed.
acideater
August 27th, 2003, 08:08 PM
Well ill try new memory Ill keep u updated thanks for the input I put my virtual memory up then I had to work Ill let u know if it helps
Redo I had already disabled the s3 and put in a geforce4 but it didnt hlp
Ea$y_E
August 27th, 2003, 09:33 PM
first of all...
just becuase you installed a new card doesnt mean u should disable the older video source.
when installing a AGP card the mobo automatically is supposed to dump the onboard display and go straight to AGP
check in BIOS settings for something that looks like
first/startup/initial (whichever the case may be) display source
you can usually change between onboard/PCI/AGP
select AGP as first source if available.
disabling the onboard video probably did something else like disable a bridge for the chipsets im not to familiar with S brand, so im not 100% sure of how they incorporate thier chipsets in relation to everything else, just enable the onboard through windows device manager, go to nvidia.com and get the latest drivers for your card, it should work fine
BTW: the FX brand of geforce was designed for DX9 get the latest i believe its 9b or so, and just do a plain update of windows, chances are something else has been made available in the way of patches or fixes or even drivers for your machine
edit: reply with what model card u have, if u got a crappy card u might have to reduce the quality of video settings, such as AA, anisotropic, and the like to get better performance, nvidia detonators usually tend to try to choke the card for every ounce of eye candy it can muster, even at the expense of FPS
acideater
August 31st, 2003, 06:51 AM
everything works now I added memory
The Hunter
August 31st, 2003, 06:55 AM
Im glad everything worked out for you.
Winphuk
August 31st, 2003, 05:59 PM
Originally posted by acideater
everything works now I added memory
there ya go
vBulletin® v3.8.4, Copyright ©2000-2010, Jelsoft Enterprises Ltd.