|
|||||||
| Windows XP & Linux NVIDIA Display Drivers If you have a problem with the NVIDIA ForceWare Drivers on XP or Linux then this is the place to get help! |
![]() |
|
|
Thread Tools |
|
|
#1 |
|
DriverHeaven Newbie
Join Date: Jan 2006
Posts: 7
Rep Power: 0 ![]() |
Crashes/Voltage?
Puh. Seems i finally figured out how to make my geforce 4 ti (creative) totally worthless.
From the beginning: Had problems booting the Pc (no signal at all to monitor when hitting power switch; reset-button didnt work either). Managed to get this working by changing the clk-ratio-switch on the mainboard (via kt266; amd 1600). when clk-ratio is set to 100 (1100 mhz) it`s working, sometimes it works with 133 as well, but I always have to change the ratio to get the Pc to start. Okay, so it was ok for me running the pc on only 1100 mhz; but there was one more problem: I had crashes (reboots) when playing games. nv4_disp.dll seemed to be responsible for that - so i decided to try the latest omega releases. I deinstalled the detonator (via "software"), rebooted and installed the omega drivers. again reboot - windows won`t load anymore! wtf!? There`s the windows loading screen (sometimes the blue chkdsk window appears and checks a partition; no problems here) then suddenly the screen turns black and the monitor switches to standbye. so - no signal!? tried to reload bios defaults - same problem. same problem in windows safe mode. before i reinstall my system (i`m actually too lazy for that now haha) maybe anyone can help figure out where the problem really lies... i wonder how the first problem might have anything to do with that new one which appeared through omega-drivers. maybe my card is simply screwed? if so - how do i find out? maybe it`s a problem with the via kt266 chipset, which always has been known to cause trouble. i do have the latest chipset-drivers (latest LOL; oct. 2001); don`t know about the bios version though. thanks in advance for helping me on this weird topic. Last edited by illumin8er; Mar 3, 2006 at 09:07 PM. |
|
|
|
|
|
#2 |
|
Cthulhu/Dagon 2012
|
Could be that the system starts up fine but the monitor recieves a signal for a graphics mode it cannot handle, like a too high vertical refresh rate or resolution.
|
|
|
|
|
|
|
|
DriverHeaven Newbie
Join Date: Jan 2006
Posts: 7
Rep Power: 0 ![]() |
just reinstalled win xp. working.
so i guess i should have removed the previous driver more carefully. anyway i still have same old problems, including crashes on the fly... i guess it's my via kt266 mainboard ... will get me a new mainboard ... except anyone here claims it should be a problem with the geforce 4? guess not...
|
|
|
|
|
|
|
|
DriverHeaven Newbie
Join Date: Jan 2006
Posts: 7
Rep Power: 0 ![]() |
grml.
installed another mainboard with VIA KT400 (an asus board which worked in my main pc with no problems). still i get crashes, the blue screens outputs: portcls.sys smwdm.sys nv4_disp.dll (to be continued ... ? )crashes come after 30 - 60 (sometimes even more) minutes; (LOL it's my girlfriends PC - she's playing world of warcraft and it just crashed again after less than 20 mins ... muahaha :P ... saying again portcls.sys) is it my geforce 4? i'm willing to buy some new part if i know WHICH part ![]() thx 'n greetz EDIT: Problems concerning CLKRatio etc. are now gone with the new board. everything (including winxp) seems to work fine... except gaming. |
|
|
|
|
|
#5 |
|
Cthulhu/Dagon 2012
|
Have a look at the fan so that it's not clogged with dust and/or rotating slowly.
|
|
|
|
|
|
|
|
DriverHeaven Newbie
Join Date: Jan 2006
Posts: 7
Rep Power: 0 ![]() |
i cleaned all fans when i changed the motherboard.
so you think it's a heat-thingy? |
|
|
|
|
|
|
|
DriverHeaven Newbie
Join Date: Jan 2006
Posts: 7
Rep Power: 0 ![]() |
tried different chipset drivers for mainboard - no effect.
also just tested another card (radeon 9800 pro) and it's running perfectly nonstop. i guess it's somekind of voltage problem. is this info correct: If AGP 1.0 or 2.0 card is running in 2x, 1x mode it will use 3.3v If AGP 2.0 or 3.0 card is running in 4x mode it will use 1.5v If AGP 3.0 card is running in 8x mode it will use 0.8v AGP 1.0 slot supports 1x and 2x at 3.3v AGP 2.0 slot supports 1x and 2x at 3.3v AGP 2.0 slot supports 4x at 1.5v AGP 3.0 slot supports 4x at 1.5v AGP 3.0 slot supports 8x at 0.8v AGP 2.0 and 3.0 cards and slots overlap nicely. Hardly anyone has sold an AGP 1.0 anything for a couple of years now. found it here. i'll try something and tell you
|
|
|
|
|
|
|
|
DriverHeaven Newbie
Join Date: Jan 2006
Posts: 7
Rep Power: 0 ![]() |
sorry for massive replying to myself. but maybe i can help someone who has a similar problem in the future...
after hours of testing i think i finally i figured out the problem: seems the pc is running fine with onboard sound disabled. so doesnt seem to be any graphicscard issue. though i wonder why this can be due to the sound, but - well, i'll try a soundblaster card... |
|
|
|
|
|
#9 |
|
Cthulhu/Dagon 2012
|
Sometimes the drivers for onboard sound are just not good, but whatever the cause I hope it keeps working.
|
|
|
|
|
|
|
|
DriverHeaven Newbie
Join Date: Jan 2006
Posts: 7
Rep Power: 0 ![]() |
another day - another crash - i'm getting used to it :P
well it's not the onboard sound. it crashes with it disabled as well. now i'm testing my ram with memtest86. well i guess at this point this thread doesnt belong in this section anymore... maybe some mod can move it... concerning memtesting: i have 3 modules: 2 x 256 mb / 1 x 128 mb i did the test with all 3 modules: errors! lots! then i removed the 128 mb (3rd bank): 0 errors for 2 passes! today i tested the pc playing WoW: Crash!!! F*** i am just testing the 2 256mb again: errors! crazy!? yesterday: 0 errors. today: errors. normal!? greetz EDIT: man! so easy! ![]() it's simply one 256mb module that's screwed! f*** ebay! ![]() i'll try one more smiley for the fix i did: ![]() btw: can i do anything with the screwed module except faking it's A-okay and selling it via ebay (hehe) or throwing it out the f***ing window?! Last edited by illumin8er; Mar 6, 2006 at 07:56 AM. |
|
|
|
![]() |
| Thread Tools | |
|
|