Error when trying to run program

I receive this error when I try to run the 3.34 version.

"FAH GPU Tracker V2 has encountered a problem and needs to close. We are sorry for the inconvenience."

I did not receive that error when I installed the 3.33 version. The cryptic nature of the resultant message also has me scratching my head. I've tried several times to run the thing, turning off my firewall, turning off my AV, I always run with very few background processes running, etc.

Does this program require a version of .NET or something? If so, which version? Also, there seems to be only the latest version available for download, which really doesn't help this situation at all, as I cannot try the previous version if I cannot download it. I did a pretty foolish thing, and overwrote the previous version download with the new one. Might I suggest including the version number in the .zip name? That way the previous version will not be overwritten inadvertantly.

Also is there any way to get ahold of version 3.33 to check and see if that one will work?

Ask and you will receive, unzip to your fah gpu tracker v2 install folder, (i might suggest renaming current exe to 3_34.exe or something just in case

>DOWNLOAD FAH TRACKER V2 3.33<

(we really need file upload)

We could use some more information however, try posting the log.txt file which is inside the installation directory.

i'll inform jedi95 right away about this problem.

I had a look at the logfile, and the latest entry makes absolutely no mention of ver 3.34, but here is the dump as requested...

[04:48:21] --------------------------------------------------
[04:48:21] FAH GPU Tracker v3.33 Startup
[04:48:21] --------------------------------------------------
[04:48:21] Detected OS: Windows XP
[04:48:23] Detected CPU: Intel Pentium III Xeon processor
[04:48:23] 4 Cores, 8 Threads, 3,910 MHz
[04:48:27] Creating client folders...
[04:48:27] Downloading FAH clients...
[04:48:50] Extracting clients...
[04:48:50] Clients extracted successfully
[04:48:50] Setting up clients...
[04:48:55] Client setup completed successfully
[04:48:55] Setting up client configs...
[04:48:55] Setting up GPU0 client config
[04:48:59] Setting up GPU1 client config
[04:48:59] Setting up GPU2 client config
[04:49:00] Setting up GPU3 client config
[04:49:00] Setting up GPU4 client config
[04:49:00] Setting up GPU5 client config
[04:49:01] Setting up GPU6 client config
[04:49:01] Setting up GPU7 client config
[04:49:01] Setting up CPU client config
[04:49:02] Setting up SMP client config
[04:49:02] Client configs generated successfully
[04:49:02] Cleaning up client folders...
[04:49:02] Initial setup complete
[05:06:10] Applied new config settings
[05:06:48] Applied new config settings
[05:07:27] Starting SMP
[05:07:27] Updated SMP config, restarting client
[05:07:28] Starting SMP
[05:07:28] Started new WU on SMP
[05:07:48] Error stopping CPU safely, code=127
[05:07:48] Stopped SMP
[05:08:03] GPU detection completed successfully
[05:08:09] Applied new config settings
[05:08:18] Applied new config settings
[05:08:21] Starting GPU 0
[05:08:21] Updated GPU0 config, restarting client
[05:08:22] Starting GPU 0
[05:08:22] Started new WU on GPU0
[05:10:28] Error stopping GPU0 safely, code=127
[05:10:28] Stopped GPU 0
[05:10:40] Applied new config settings
[05:10:45] Starting SMP
[05:10:45] Resumed existing WU on SMP
[05:10:45] Starting GPU 0
[05:10:45] Resumed existing WU on GPU0
[00:09:53] --------------------------------------------------
[00:09:53] FAH GPU Tracker v3.33 Startup
[00:09:53] --------------------------------------------------
[00:09:53] Detected OS: Windows XP
[00:09:55] Detected CPU: Intel Pentium III Xeon processor
[00:09:55] 4 Cores, 8 Threads, 3,910 MHz
[00:10:02] Starting GPU 0
[00:10:02] Resumed existing WU on GPU0
[00:29:25] Error stopping GPU0 safely, code=127
[00:29:25] Stopped GPU 0
[17:49:39] --------------------------------------------------
[17:49:39] FAH GPU Tracker v3.33 Startup
[17:49:39] --------------------------------------------------
[17:49:39] Detected OS: Windows XP
[17:49:41] Detected CPU: Intel Pentium III Xeon processor
[17:49:41] 4 Cores, 8 Threads, 3,910 MHz
[17:49:45] Attempting to update FAH GPU Tracker V2
[17:49:48] Updating Tracker..
[17:50:06] --------------------------------------------------
[17:50:06] FAH GPU Tracker v3.33 Startup
[17:50:06] --------------------------------------------------
[17:50:06] Detected OS: Windows XP
[17:50:07] Detected CPU: Intel Pentium III Xeon processor
[17:50:07] 4 Cores, 8 Threads, 3,910 MHz

Note that is it normal for the program to ID my i7 950 as a P3 Xeon? It's probably no biggie and most likely just an asthetic thing, but just in case it's relavent. Also, here are some of my machine stats if it helps.

Intel i7 950 3.06 GHz (O.C. to 4.08GHz)
6Gb of Corsair XMS3 triple-channel 1600 RAM 7-8-7-20-2 (running at 6-8-6-20-1)
Corsair H50 cooler with 2 fans in push-pull exhaust and Indigo Xtreme eti
EVGA 465GTX set to 800/1600/1950 at 1.075 mV
Asus P6T Motherboard
Creative Soundblaster Audigy 2ZS Platinum Pro
x2 Seagate 1Tb Barricuda 7200 RPM SATA drives
x1 Seagate 500Gb Barricuda 7200 RPM SATA drive
OCZ GamerXStream 700W Power Supply
Windows XP Pro SP3
Windows7 64bit Pro

Essentially the xeon and the i7 are the same cpu's just the xeons are more hand selected as the chips they designate xeons are for servers, which tend to need something more durable as its expected to run in crampt conditions for long periods of uninterupted times. so its "cherry picked"
So i wouldnt be surprised if your i7 reads as an xeon, maybe they were low on i7 stock and reflashed the xeon and sent you the i7, or maybe the new 950's have the same id designation. im not sure on how jedi gets the cpu stat.. (btw i7= overglorified pentium pro)

But that is offtopic, since there is no mention of the 3.34 when you updated it essentially means that before the tracker even got to opening the log it crashed, did the 3.33 client work? and if it didint try renaming the log.txt to logbackup.txt maybe the tracker Freaks out when it tries to read log.txt (maybe antivirus issue, what antivirus do you use?)

Latharion wrote:I had a look at the logfile, and the latest entry makes absolutely no mention of ver 3.34, but here is the dump as requested...

[04:48:21] --------------------------------------------------
[04:48:21] FAH GPU Tracker v3.33 Startup
[04:48:21] --------------------------------------------------
[04:48:21] Detected OS: Windows XP
[04:48:23] Detected CPU: Intel Pentium III Xeon processor
[04:48:23] 4 Cores, 8 Threads, 3,910 MHz
[04:48:27] Creating client folders...
[04:48:27] Downloading FAH clients...
[04:48:50] Extracting clients...
[04:48:50] Clients extracted successfully
[04:48:50] Setting up clients...
[04:48:55] Client setup completed successfully
[04:48:55] Setting up client configs...
[04:48:55] Setting up GPU0 client config
[04:48:59] Setting up GPU1 client config
[04:48:59] Setting up GPU2 client config
[04:49:00] Setting up GPU3 client config
[04:49:00] Setting up GPU4 client config
[04:49:00] Setting up GPU5 client config
[04:49:01] Setting up GPU6 client config
[04:49:01] Setting up GPU7 client config
[04:49:01] Setting up CPU client config
[04:49:02] Setting up SMP client config
[04:49:02] Client configs generated successfully
[04:49:02] Cleaning up client folders...
[04:49:02] Initial setup complete
[05:06:10] Applied new config settings
[05:06:48] Applied new config settings
[05:07:27] Starting SMP
[05:07:27] Updated SMP config, restarting client
[05:07:28] Starting SMP
[05:07:28] Started new WU on SMP
[05:07:48] Error stopping CPU safely, code=127
[05:07:48] Stopped SMP
[05:08:03] GPU detection completed successfully
[05:08:09] Applied new config settings
[05:08:18] Applied new config settings
[05:08:21] Starting GPU 0
[05:08:21] Updated GPU0 config, restarting client
[05:08:22] Starting GPU 0
[05:08:22] Started new WU on GPU0
[05:10:28] Error stopping GPU0 safely, code=127
[05:10:28] Stopped GPU 0
[05:10:40] Applied new config settings
[05:10:45] Starting SMP
[05:10:45] Resumed existing WU on SMP
[05:10:45] Starting GPU 0
[05:10:45] Resumed existing WU on GPU0
[00:09:53] --------------------------------------------------
[00:09:53] FAH GPU Tracker v3.33 Startup
[00:09:53] --------------------------------------------------
[00:09:53] Detected OS: Windows XP
[00:09:55] Detected CPU: Intel Pentium III Xeon processor
[00:09:55] 4 Cores, 8 Threads, 3,910 MHz
[00:10:02] Starting GPU 0
[00:10:02] Resumed existing WU on GPU0
[00:29:25] Error stopping GPU0 safely, code=127
[00:29:25] Stopped GPU 0
[17:49:39] --------------------------------------------------
[17:49:39] FAH GPU Tracker v3.33 Startup
[17:49:39] --------------------------------------------------
[17:49:39] Detected OS: Windows XP
[17:49:41] Detected CPU: Intel Pentium III Xeon processor
[17:49:41] 4 Cores, 8 Threads, 3,910 MHz
[17:49:45] Attempting to update FAH GPU Tracker V2
[17:49:48] Updating Tracker..
[17:50:06] --------------------------------------------------
[17:50:06] FAH GPU Tracker v3.33 Startup
[17:50:06] --------------------------------------------------
[17:50:06] Detected OS: Windows XP
[17:50:07] Detected CPU: Intel Pentium III Xeon processor
[17:50:07] 4 Cores, 8 Threads, 3,910 MHz

Note that is it normal for the program to ID my i7 950 as a P3 Xeon? It's probably no biggie and most likely just an asthetic thing, but just in case it's relavent. Also, here are some of my machine stats if it helps.

Intel i7 950 3.06 GHz (O.C. to 4.08GHz)
6Gb of Corsair XMS3 triple-channel 1600 RAM 7-8-7-20-2 (running at 6-8-6-20-1)
Corsair H50 cooler with 2 fans in push-pull exhaust and Indigo Xtreme eti
EVGA 465GTX set to 800/1600/1950 at 1.075 mV
Asus P6T Motherboard
Creative Soundblaster Audigy 2ZS Platinum Pro
x2 Seagate 1Tb Barricuda 7200 RPM SATA drives
x1 Seagate 500Gb Barricuda 7200 RPM SATA drive
OCZ GamerXStream 700W Power Supply
Windows XP Pro SP3
Windows7 64bit Pro

CPU detection is buggy under Windows XP. This is the reason I added the -nocpudetect flag. The Tracker uses .NET 3.5, so make sure you have it. I don't know why 3.34 wouldn't work but 3.33 does, that makes no sense at all. Without more details I can't really do anything about the problem with it crashing.

No problem. I'll try running it with the -debug flag later today and post the results. I'll also rerun the .NET 3.5 redistributable just to make sure it's installed properly. Is there anything else I can do to help solve this?

Latharion wrote:No problem. I'll try running it with the -debug flag later today and post the results. I'll also rerun the .NET 3.5 redistributable just to make sure it's installed properly. Is there anything else I can do to help solve this?

Can you post a screenshot of the error you get when the Tracker crashes? That might help me figure out what is going on.

Hi,

i saw this thread and thought i should post. I am having the same issue since trying to upgrade to 3.34. v3.33 was running fine.

I did a fresh install as well with just the v3.34 file and have the same issue. It doesnt download any extra files it just crashes.

the PC is P4 running XP sp3.

I hope this helps.

the error message is below

scorpia wrote:Hi,

i saw this thread and thought i should post. I am having the same issue since trying to upgrade to 3.34. v3.33 was running fine.

I did a fresh install as well with just the v3.34 file and have the same issue. It doesnt download any extra files it just crashes.

the PC is P4 running XP sp3.

I hope this helps.

the error message is below

Would you mind trying the 3.36 beta to see if it fixes your problem?

Download here:
<link removed, please use the new stable release>

The beta seems to have fixed the problem for me. Whatever was changed, looks good on my end. Thankyou for offering the beta!

Latharion wrote:The beta seems to have fixed the problem for me. Whatever was changed, looks good on my end. Thankyou for offering the beta!

Yeah, I don't normally just release the betas, but in this case it made sense to do so. Since this problem has been confirmed as fixed I plan to release a stable version with this fix tomorrow.

Just wanted to add that that beta version works for me while the current stable one doesn't.

ShiftEvolve wrote:Just wanted to add that that beta version works for me while the current stable one doesn't.

3.37 stable has been released with this fix.

Cool, thanks.