Yet more proof that we need forced I.Q. screening of parents before they are allowed to have kids. Fury190 would never have been born.
<< There is a well known via+geforce+win98 bug. And to deny that, like you are tryin to do, is retarded, much like yourself. >>
So wait, is it VIA+Geforce+Win98 or GF2 of GF3 or WinXP or 2k or Me or 98 or do you know what the hell you are talking about??? Obviously not, you haven't said the same thing twice!
If it is such a "well known" bug, surely you could provide at least ONE link to a hardware site or vendor that says so. Otherwise you are a liar and a retard.
<< I currently work as a unix Admin. >>
That's scary. An admin should at least know something about hardware. I suspect you are lying.
Workin', thats because that statment was a mistake too...
<< I currently work as a unix Admin. >>
What he meant was...
I currently work FOR a unix Admin.
He is actually the janitor
<< I currently work as a unix Admin. >>
What he meant was...
I currently work FOR a unix Admin.
He is actually the janitor
I have 2 80 gigers. And yes, my schlong *is* bigger than yours.
LoL, I'm sure, and they probably have really tiny ball bearings with a moving head that is extremely silent...so silent that you would think its never been used
In any case, guys, just run a search on the following forums: mobos, vid cards, cpu/ocing, case cooling and type in Fury190 as the thread author. You'll quickly see such extremely complicated titles such as:
Help, Can't uninstall the 4in1 drivers properly
antec 80mm case fan burned up in 2 days
10.5 x 133 = 1400. is this proper ?
8kha+ ddr section in bios.. help!
Crucial Ecc or Non-parity pc2100 for an epox 8kha+
System burn in. Yes or no.
I'm not making any of these thread titles up, I didn't even bother to look at the content, but if my memory serves me correctly, we're talking Computers 101 stuff here. So Fury, did you say you were a Unix administrator of an administrator of eunichs?
Anyways, this has gone a bit OT, so I actually did find a link that will help you out:
Nice Article for people with various problems with their computers and need lotsa help
Check it out guys and LMK if you think it will solve his problems
Chiz
LoL, I'm sure, and they probably have really tiny ball bearings with a moving head that is extremely silent...so silent that you would think its never been used
In any case, guys, just run a search on the following forums: mobos, vid cards, cpu/ocing, case cooling and type in Fury190 as the thread author. You'll quickly see such extremely complicated titles such as:
Help, Can't uninstall the 4in1 drivers properly
antec 80mm case fan burned up in 2 days
10.5 x 133 = 1400. is this proper ?
8kha+ ddr section in bios.. help!
Crucial Ecc or Non-parity pc2100 for an epox 8kha+
System burn in. Yes or no.
I'm not making any of these thread titles up, I didn't even bother to look at the content, but if my memory serves me correctly, we're talking Computers 101 stuff here. So Fury, did you say you were a Unix administrator of an administrator of eunichs?
Anyways, this has gone a bit OT, so I actually did find a link that will help you out:
Nice Article for people with various problems with their computers and need lotsa help
Check it out guys and LMK if you think it will solve his problems
Chiz
Hmm am I a complete moron? I'm running an Epox 8KHA+ with an Athlon XP 1800+ and a Gainward Geforce 3 in Windows 2000 with no problems. There is a problem with some Kt266A mobos and Win9x. Bios updates are resolving the problem. The problem isnt crashing, rather terrible performance in 3d apps.
There does appear to be a problem, although I'm not sure to what extent it exhibits itself and under what circumstances. It appears that it may be prevalent in the P4x266 also. I can't comment much further (and i'm sure i'll get flamed) but I know a little bit about it and can assure you that Via, at least privately, have acknowledged the problem(though it 'may' be an MS problem). It seems that, like the 686b bug, some people are affected while many others are not
Assimilator1
Elite Member
- Nov 4, 1999
- 24,152
- 517
- 126
lnguyen
Whoops! ,sorry!
Fury190
WHERE IS A LINK BACKING UP YOUR STORY????
Also I had a quick look at the at 2 sections of the amd forums & saw no mention of the problem ,can you even tell us which forum?
damocles
I can't speak for the others but I certainly won't flame you if you can ,
1. Tell us what the problem is supposed to be (fury190 has NOT explained it other than saying it crashes)
2.Provide a link showing other users with the same problem or an article about it from a website
Fury190 has proved himself an idiot by repeatedly saying there is a bug with NO explanation & no links!
Whoops! ,sorry!
Fury190
WHERE IS A LINK BACKING UP YOUR STORY????
Also I had a quick look at the at 2 sections of the amd forums & saw no mention of the problem ,can you even tell us which forum?
damocles
I can't speak for the others but I certainly won't flame you if you can ,
1. Tell us what the problem is supposed to be (fury190 has NOT explained it other than saying it crashes)
2.Provide a link showing other users with the same problem or an article about it from a website
Fury190 has proved himself an idiot by repeatedly saying there is a bug with NO explanation & no links!
Zebo
Elite Member
- Jul 29, 2001
- 39,398
- 19
- 81
<< heres your link
via bug confirmed >>
LOL... That's a Link to this thread!?!?! Anyhow, I have three Shuttle AK31a in my office which uses the via chipset in question. One has a VisionTek gf3, one AIW radeon and the third a GF2 GTS. No problems here when playing HL, Wolf or Unreal during our serious LAN parties.
Fury 190 are you Hardware?
Fury 190 are you Hardware?
no. I am a software guy.
Well i have all my issues resolved, but it does seem like others are having performance issues with 3dgames.
no. I am a software guy.
Well i have all my issues resolved, but it does seem like others are having performance issues with 3dgames.
Assimilator1
Elite Member
- Nov 4, 1999
- 24,152
- 517
- 126
<< Well i have all my issues resolved >>
So then it would be fair to say that there is no bug, and you are just a dumbass who is full of sh!t and knows nothing about high performance computer hardware.
For more information about this problem go to the following threads in viaarena.com. I also have the problem and my Video card is a Ati All In Wonder Radeon PCI 32sdr and my motherboard is a Soyo SY-K7V Dragon Plus and I was using Windows XP. The problem seems to occur in Windows XP and with Ati and nVidia video cards. I changed my OS to Windows Millenium and the problem dissapeared.
This is the original thread
http://forums.viaarena.com/messageview.cfm?catid=13&threadid=3759
This is the continuation
http://forums.viaarena.com/messageview.cfm?catid=13&threadid=4123
Thanks,
Wilfredo
This is the original thread
http://forums.viaarena.com/messageview.cfm?catid=13&threadid=3759
This is the continuation
http://forums.viaarena.com/messageview.cfm?catid=13&threadid=4123
Thanks,
Wilfredo
Some of you guys need to lay off Fury190 a little bit, because as misguided as he may seem to be, he is speaking the truth.
There is a problem with the VIA + Windows XP + Detonator 23.11 combination as reported by the Inquirer and in Wilfredo's link. Just because someone doesn't understand what they're seeing doesn't mean they're not seeing it.
There is a problem with the VIA + Windows XP + Detonator 23.11 combination as reported by the Inquirer and in Wilfredo's link. Just because someone doesn't understand what they're seeing doesn't mean they're not seeing it.
Problems with the new Detonator Drivers?
When the new 23.11 Detonator drivers were released yesterday, a whole bunch of people started to notice problems with an "infinite loop error" when running Windows XP - some games also "exit" whenever they feel like you're starting to get the upper hand. In a nutshell the new drivers allow your NVidia card access to a larger portion of memory than all previous drivers did - this is also why we've been seeing some promising speed increases from the 23.11's. However, because of this larger memory access improvement, a timing issue has evolved around the RX55 memory register (MWQ) in the BIOS when it is left in a opened state.
The MWQ timer is a timing device included in the memory host controller that prevents write data from being held in the memory queue too long. After the data has been in the queue too long it times out. This timed out data is then given a higher write request priority. Now that might sound nice ? a bit of extra performance, BUT the procedure fails when overloaded because 3D games / Win XP put too much load on the memory queuing timer procedure.
There are several things you can do so solve the problem, such as loading optimized defaults in your BIOS and not modifying memory settings, set your memory settings in the BIOS less aggressively and test, make sure you have an adequate power supply, update your BIOS and test (some motherboard manufacturers have already released BIOS updates that have the register closed), and disable or enable AGP fast write and test. In some cases though, none of these solutions appear to fix the problem, and a patch must be applied that closes the RX55 memory register manually. Wanna get your hands on this patch? Here's a link to it, but remember it's labeled as a BETA patch, and the word BETA is in all capital letters for a reason.
UPDATE: George Breese, the resident VIA Chipset guru at VIA Hardware has this to say about the patch: This patch detects the 0305, 3099, 3102, and 3112 (KT133x, KT266x, VT8662, and KLE133) *only*. On these chipsets, it will patch register 55 in the Northbridge, which will supposedly switch off a Memory Write Queue timer.
In the KT133A datasheet, register 55 is "reserved". But - yikes! - in the KT266, the documented MWQ register is register 95, not 55. Register 55 contains unrelated DDR timing adjustments and could actually be dangerous to program. For this reason, I do not recommend installing this driver on the KT266x chipsets until VIA examines this issue. For now, use WPCREDIT and set bits 5, 6, and 7 to zero in register 95 instead
The Link
----------------------------------
VIA released a BETA driver patch today to help address some of the problems on AMD based VIA motherboards in WindowsXP. Though users are having mixed results with this patch, here is what our resident scripting guru, George Breese, has to say about the patch:
"This patch detects the 0305, 3099, 3102, and 3112 (KT133x, KT266x, VT8662, and KLE133) *only*. On these chipsets, it will patch register 55 in the Northbridge, which will supposedly switch off a Memory Write Queue timer.
In the KT133A datasheet, register 55 is "reserved". But - yikes! - in the KT266, the documented MWQ register is register 95, not 55. Register 55 contains unrelated DDR timing adjustments and could actually be dangerous to program. For this reason, I do not recommend installing this driver on the KT266x chipsets until VIA examines this issue. For now, use WPCREDIT and set bits 5, 6, and 7 to zero in register 95 instead."
Electric lets us know they have this driver for download here.
Discuss this patch in our forums.
Another Link
---------------------------------------
i have never like via products and this is my reason
any products that needs to be patched as much as thiers i wont buy
just my opion remember
When the new 23.11 Detonator drivers were released yesterday, a whole bunch of people started to notice problems with an "infinite loop error" when running Windows XP - some games also "exit" whenever they feel like you're starting to get the upper hand. In a nutshell the new drivers allow your NVidia card access to a larger portion of memory than all previous drivers did - this is also why we've been seeing some promising speed increases from the 23.11's. However, because of this larger memory access improvement, a timing issue has evolved around the RX55 memory register (MWQ) in the BIOS when it is left in a opened state.
The MWQ timer is a timing device included in the memory host controller that prevents write data from being held in the memory queue too long. After the data has been in the queue too long it times out. This timed out data is then given a higher write request priority. Now that might sound nice ? a bit of extra performance, BUT the procedure fails when overloaded because 3D games / Win XP put too much load on the memory queuing timer procedure.
There are several things you can do so solve the problem, such as loading optimized defaults in your BIOS and not modifying memory settings, set your memory settings in the BIOS less aggressively and test, make sure you have an adequate power supply, update your BIOS and test (some motherboard manufacturers have already released BIOS updates that have the register closed), and disable or enable AGP fast write and test. In some cases though, none of these solutions appear to fix the problem, and a patch must be applied that closes the RX55 memory register manually. Wanna get your hands on this patch? Here's a link to it, but remember it's labeled as a BETA patch, and the word BETA is in all capital letters for a reason.
UPDATE: George Breese, the resident VIA Chipset guru at VIA Hardware has this to say about the patch: This patch detects the 0305, 3099, 3102, and 3112 (KT133x, KT266x, VT8662, and KLE133) *only*. On these chipsets, it will patch register 55 in the Northbridge, which will supposedly switch off a Memory Write Queue timer.
In the KT133A datasheet, register 55 is "reserved". But - yikes! - in the KT266, the documented MWQ register is register 95, not 55. Register 55 contains unrelated DDR timing adjustments and could actually be dangerous to program. For this reason, I do not recommend installing this driver on the KT266x chipsets until VIA examines this issue. For now, use WPCREDIT and set bits 5, 6, and 7 to zero in register 95 instead
The Link
----------------------------------
VIA released a BETA driver patch today to help address some of the problems on AMD based VIA motherboards in WindowsXP. Though users are having mixed results with this patch, here is what our resident scripting guru, George Breese, has to say about the patch:
"This patch detects the 0305, 3099, 3102, and 3112 (KT133x, KT266x, VT8662, and KLE133) *only*. On these chipsets, it will patch register 55 in the Northbridge, which will supposedly switch off a Memory Write Queue timer.
In the KT133A datasheet, register 55 is "reserved". But - yikes! - in the KT266, the documented MWQ register is register 95, not 55. Register 55 contains unrelated DDR timing adjustments and could actually be dangerous to program. For this reason, I do not recommend installing this driver on the KT266x chipsets until VIA examines this issue. For now, use WPCREDIT and set bits 5, 6, and 7 to zero in register 95 instead."
Electric lets us know they have this driver for download here.
Discuss this patch in our forums.
Another Link
---------------------------------------
i have never like via products and this is my reason
any products that needs to be patched as much as thiers i wont buy
just my opion remember
>- 8khi1b20
>Date: 20 November 2001
>Fixes: Fix some issues on GeForce 3 Titanium 500 series
>Changes: AGP Aperture Size = 256 MB
>Notes: Some users have experience crash after crash when using Athlon XP. See this thread: >http://www.amdmb.com/vb/showthread.php?threadid=79023
that was a paste from this post
http://www.asusboards.com/forums/showthread.php?threadid=11030
Guys, if you step away from this thread, go back and read it, I hope you see that you could prolly say a few sorrys to Fury190. Thats only if ya can detach yourself from the situation. He may not have posted the info according to way you like info posted, but truth remains he was posting about a REAL problem. If ya didn't/don't have a problem, say "hmmm, I don't have a problem with XY and Z components", and leave it at that! The flames here serve no purpose. I always see threads about how this is the best place on the net to post about info, and receive info about puters. But to sit there and flame over and over, is at best a mistake in judgement. Show a little respect even for those that you don't agree with, show that you are indeed adults.
kylebisme
Diamond Member
- Mar 25, 2000
- 9,396
- 0
- 0
he may have been refering to a real problem but he was doing it by spreading false infromation. when i saw the thread i thought to myself "aww hell, i just ordered a via kt266a board and a geforce3 and now im going to have to send something back and come up with a replacemnt because it wont work stablity in 3d games." i am realy looking forward to this new system and i was dissapointed to hear the bad news but at the same time grateful to fury190 for informing me of my upcomeing problems. then i realise that he has absolutly no clue what he is talking about and simply suffering from a self indused problem of instablity caused by by the use of a beta bios. hence he caused myself, and probably quite a few others like me, undue stress and possably talked some people out of purchaseing perfictly good hardware because of his own arrogent attitude and for that he deserves a good flameing. personaly i think he should be baned from the forums for such action, though i understand that many would say that such a thing would be overly harsh and it probably will not happen.
<< Guys, if you step away from this thread, go back and read it, I hope you see that you could prolly say a few sorrys to Fury190. >>
Ummmm...... No! Lmao, this guy is an idiot, plain and simple. Maybe I'm a prick, but I don't suffer fools well and I certainly won't apologize to one. He makes a blanket statement with no facts or specifics to justify his claim. That would akin to me saying "All Arabs are terrorists, because they can't play nice on airplanes." Then when people flamed me and asked why I said that, I'd just say "Sept. 11" or post a picture of the WTC on 911. I don't feel that way, and his statement was not nearly as serious as that, but I hope you get the idea. He changes his conditions for this "universal" bug 4 or 5 times, and then when asked for specifics he links back to this thread!! I'm not sure what level of competency you guys are accustomed to, but details and specificity are things I expect from adults (which he claims to be, but I have my doubts
). He claims to be a Unix Administrator, I can just imagine him now if something goes wrong at work: "Umm yes Mr. CIO, we have a problem with the server. I think its because via chipset and gefore 3 BUG confirmed! ."On the other hand, FiveDoubleO's post is much more informative and gives the background info of the problem. From reading that, I see the issue lies with a *specific* OS, and *specific* drivers, both of which are new. Now, you can blame Via if you wish, but if you have reservations about having to upgrade or patch things, you probably haven't been around PCs long enough. Both WinXP and the 23.11 dets antecede the Via chipsets, and considering both those companies are infamous Intel bedfellows, this could easily be a QA short-coming on nVidia's or M$ behalf. Regardless, this problem is definitely not as widespread as Fury190 indicated. And thats the bottom line.
Chiz
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter