View Full Version : General Forceware Problem (event id 106)
09-30-04, 09:37 AM
I have an Prob with Forceware Drivers General.
i have testet the 61.77 - 66.70 always the same prob
source : nv
description: SIlent Running: Stress test transition: LO -> LO
I dont know what it is or mean ???
Please Help ..
Leadtek 5950 Ultra
WinXP Prof sp1 Directx 9.0c
sorry for my bad english i'm from Germany
09-30-04, 10:05 AM
your card is entering low power 3d mode.
Are you overclocking your card? If so then your card is complaining. (spit)
09-30-04, 02:05 PM
It's a bug. I'm running 6800 GT 400/1000 and I'm getting the same, even when I set to default clock speed 370/1000 (BFG 6800 GT OC)...
It's a bug with 66.51, 66.70...didn't have this with 61.77 and 65.76
return the card. it is defective.
09-30-04, 04:53 PM
No, it's not...
I tested it today. I run 3DMark05 5 times in a row, no problems. It's a bug in drivers. For every NVIDIA cards I own, this event message pop ups, and it's only in 66.51, and 66.70.
but you have a GeForce 6800. he has a FX 5950...
I have a 5900 and never get that message with the drivers. Even having it flashed and overclocked past 5950 speeds.
Dr Death. Check the fan on the card, make sure its not clogged up.
10-01-04, 02:50 AM
Thanks for all your answers.
But the same prob.
I have check the hardware it's okay.
i remember that the problem begins after installing Directx 9.0c
before i do this i have no problems with 61.77
I think the 61.77 is not full compatible with 9.0c
I testet the 66.51 and the 66.70 same Prob.
I don't get this error with any of the drivers you mentioned. I also have DX 9.0c.
Try looking on Leadtek site for a new video BIOS.
10-01-04, 03:47 AM
Hello and thanks for your answer.
I visit the Leadtek site (Taiwan) but there is no new bios available
for my A380 Ultra TDH
Do you have a Link to a new bios ??
There are two leadtek 5950 BIOS on Mavke's site.
10-01-04, 07:03 AM
I have a Gainward 5950ultra and I have got the same message after installing dx9.c, But it used to give a warning 'ID 107' before updating dx rather than the NV '106' error it gives now. I think its the same thing (fan speed change), just after installing dx9.c it says its an error rather than a warning.
Stress test transition: LO -> LO is a bit strange though coz usually it would be L2 - > L1 or L1 - > L0 dependant on how bad your hammering the card?
10-08-04, 04:01 AM
I used the new Nvidia set of Forceware Drivers from
and my Probs are still going on. I reduced the core speed of my card from 515 to 510 Mhz and the Ram speed is on 955 Mhz. And now the error message frequency is much lower.
But i think the Performance of these driver is great. It tooks my result in 3DM05 from 1215 to 1980 Points.
I also tested the complete range of Forcewares from the 53.04 - 66.81
every time the same prob. I took an Image from winxp pro early befor i installed directx 9.0c. And here comes !!!!
No Problem with any of the Forcewares from 53.04 - 66.81.
But when i installing Directx 9.0 c . After reboot my computer the errors begin
event ID 106 silent stress bla bla bla.
So i think its a prob with directx 9.0c and the forcewares.
greetings to everyone from cold rainy germany.
And thanks for your answers.
It could be that Directx 9.0c causes the card to do more work, in turn making temps higher, thus you get the error message. It seems highly unlikely that it is a driver/directx issue. Especially since every machine I use DX 9.0c and don't get this error (unless I overclock too high). Reduce core speed to default and see if the error persists. If it does, the card (or BIOS) is most likely faulty.
10-08-04, 07:25 AM
Even at unclocked speeds 475/950 I still get the same warning. As said before it only started giving a warning after updating DX to .C , it hasn't affected the card in any way I can see. Clocked at 525/1050 it does give more errors but that you would expect.
Perhaps you should try the 66.81 driver as this has lowered many people's card temps by a good few degrees overall.
I'm running 480/1026 on my BFG 5900NU w/ driver 66.81 and DX 9.0c. Haven't got that error. Perhaps modding the BIOS to get rid of throttling is your best bet. Works for me ;)
10-11-04, 09:29 AM
Could be a chipset thing, maybe only N-Force mobo's get this error?
vBulletin® v3.7.1, Copyright ©2000-2015, Jelsoft Enterprises Ltd.