Does anyone have suggestions for how to fix the "infinite loop" error with F@H on my computer?

[InlineFive]

For some odd reason F@H causes my video driver to have lots of "infinite loop" errors and BSOD quite frequently. The system configuration is as follows:

ATI Radeon 9600 Pro @ stock speeds
Catalyst 4.10s and now 5.1s, same problem
F@H GUI 5.03
WinXP Professional
Abit NF7-S (not S2)
512MB OCZ Performance Memory

Thanks!

-Por

 

[ICXRa]

That's odd I have never had any problems especially like the ones you are describing. Good luck!

 

[Wolfsraider]

Originally posted by: PorBleemo
For some odd reason F@H causes my video driver to have lots of "infinite loop" errors and BSOD quite frequently.

Good luck all!

-Por

what video card?

which drivers? which version of f@h?

let us try to help

mike

 

[InlineFive]

Originally posted by: Wolfsraider

Originally posted by: PorBleemo
For some odd reason F@H causes my video driver to have lots of "infinite loop" errors and BSOD quite frequently.

Good luck all!

-Por

what video card?

which drivers? which version of f@h?

let us try to help

mike

Alright.

ATI Radeon 9600 Pro @ stock speeds
Catalyst 4.10s and now 5.1s, same problem
F@H GUI 5.03
WinXP Professional
Abit NF7-S (not S2)
512MB OCZ Performance Memory

 

[ICXRa]

I'll try and dig around the F@H forums for ideas. The reason I may not have seen this is because I run the service installation and not the GUI one, at least not the latest release of the GUI. I do have the GUI of the release before the 5.03 running on a couple boxes and it has not caused any issues for me.

 

[InlineFive]

This may be an issue with rendering with the GUI version, even though it is minimized. Does the CLI do rendering?

 

[ICXRa]

Nope just runs in the background like other services. You won't know it's running unless you open up task manager and see the process running.

 

[Wolfsraider]

Sorry had to take the wife to work

I agree with trying the cli as well .



Mike

I always had good luck with the 3.8 drivers as well (Catalyst 4.10s were causing me a problem in an app but I reverted back to 3.8 (my favorite).

 

[Wolfsraider]

Did that fix it?

 

[GLeeM]

There have been quite a few problems with the OpenGL part of the GUI.

The CLI console version uses no graphics.

It can be run as a console window, which you can hide with Hide It. Or Tray It will put an icon in the systray.

It can also be easily run as a service.

You can just download the CLI, into the GUI folder and run it. DON'T accidently run both. You would have to re-configure to run as a service.

 

[BlackMountainCow]

I'd also say that the OpenGL is the prob here. Just change to the CLI for one WU and see if the prob still occurs.

 

[Thump553]

No real help here but I ran F@H with a Radeon 9700 for slightly over one year (the warranty period on the card, whose fan fell off one day) under Windows 2000 with absolutely no problems. I was using the graphical version.

 

[ProviaFan]

Though I have to ask: have you run memtest86? How much are you overclocking? At one point, I kept getting video card related BSODs, but in reality it was bad RAM (though in this case I had bought the extremely crappy Kingston ValueRAM because it was cheap). It's worth checking out if other stuff doesn't fix it.

 

[InlineFive]

It turns out that the card was defective so I ordered a GeForce 6800. Once that comes F@H will be back up and running. One question, can the CLI be started and stopped as easily as the GUI?

 

[BlackMountainCow]

Yip, just hit the "x" on the DOS-Box and it's gone! :beer:

 

[ProviaFan]

Originally posted by: BlackMountainCow
Yip, just hit the "x" on the DOS-Box and it's gone! :beer:

Unless it's a service, in which case you need to be admin and use the Services control panel.

But in that case, why would you need to stop it in the first place. Unless you changed the priority settings when you installed it, it shouldn't interfere with gaming or anything else like that.

 

[BlackMountainCow]

You got me there!

:beer::beer:

 

[GLeeM]

Originally posted by: BlackMountainCow
Yip, just hit the "x" on the DOS-Box and it's gone! :beer:

The Official correct way to close the CLI console is with a Control + c

 

[InlineFive]

Originally posted by: ProviaFan

Originally posted by: BlackMountainCow
Yip, just hit the "x" on the DOS-Box and it's gone! :beer:

Unless it's a service, in which case you need to be admin and use the Services control panel.

But in that case, why would you need to stop it in the first place. Unless you changed the priority settings when you installed it, it shouldn't interfere with gaming or anything else like that.

Out of curiosity, where is this services control panel?

 

[BlackMountainCow]

start --> setings --> control panel --> administrative tools --> services

:beer:

 

[InlineFive]

But that doesn't allow me to add a service.

 

[ProviaFan]

Originally posted by: PorBleemo
But that doesn't allow me to add a service.

That's why you shut down the CLI, go to the command prompt, run the CLI with -configonly, select advanced options, say yes to install as a service, and then before rebooting (or starting the service from the services panel) make sure that all startup group shortcuts to F@H are gone (so two copies of the client aren't run at once).

 

[ProviaFan]

BTW, totally coincidential, but I had an "irq not less than or equal" BSOD out of nowhere yesterday. Running almost all the way back at stock (couldn't give up a "slight" overclock), we'll see if it happens again.

Edit: and this is on my system that has been rock solid since I built it in it's latest reincarnation (with an Abit NF7-S v2). The only thing that changed was the addition of a second stick of RAM (Same specs as the first one) just over a month ago.

 

[GunDog]

The best fix I've found to correct this issue is to lower the AGP speed. There is not a great deal of performance difference between 2X-8X. If your AGP speed is 8X lower to 4X, you *might* notice a drop of 2-3 FPS in games.

Force
aka Gundog

 

[ProviaFan]

Originally posted by: GunDog
The best fix I've found to correct this issue is to lower the AGP speed. There is not a great deal of performance difference between 2X-8X. If your AGP speed is 8X lower to 4X, you *might* notice a drop of 2-3 FPS in games.

Force
aka Gundog

If you're talking to him, I'd say that's good advice (also Fast Writes being enabled can cause problems, I hear), but I have a PCI video card, so unfortunately I can't put that suggestion to use.