Fanaleds crashing - iRacing / CSR Elite / CSP Pedals

[Coasterreal]

Fanatec CSP V1 Pedals
Fanatec CSR - Elite

It was working about 2 weeks ago. Now, as soon as I jump into the car, it crashes. Ive verified with a 4th monitor, it just quits and then the system tray icon is gone.

Any ideas? Ive tried reinstalling, upgrading to the newest version and then backing up 2 versions. Nothing works.


Problem signature:
Problem Event Name: APPCRASH
Application Name: FanaLEDs.exe
Application Version: 0.0.0.0
Application Timestamp: 52979a68
Fault Module Name: FanaLEDs.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 52979a68
Exception Code: 40000015
Exception Offset: 00042136
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 73f1
Additional Information 2: 73f1defe6a7157f052e971e3a615d410
Additional Information 3: dfae
Additional Information 4: dfaeddc58dc21b8916b361b59be9c859

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

[Bose321]

Is there anything you have changed in the meantime? I don't think it's likely that Fanaleds is suddenly broken or something. Any updates/new hardware or software that you're using perhaps?

[Coasterreal]

Is there anything you have changed in the meantime? I don't think it's likely that Fanaleds is suddenly broken or something. Any updates/new hardware or software that you're using perhaps?

Thats the odd thing, no. If I knew there was something I could roll back I would.

[DirkT]

Are you still having these crashes regularly?

[Coasterreal]

Yes. I actually today and short of fully formatting my machine, have tried these things:

Swapped out my pedals and wheel from USB 3.0 to USB 2.0 slots (crashes when iRacing sim enters car)
Uninstalled and shut down all non-essential programs I wasnt using.
Includes even things I use in conjunction with iRacing like MU, Trading Paints...
Still crashes.

Im getting this crash detail:
Problem signature:
Problem Event Name: APPCRASH
Application Name: FanaLEDs.exe
Application Version: 0.0.0.0
Application Timestamp: 52f2a752
Fault Module Name: FanaLEDs.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 52f2a752
Exception Code: 40000015
Exception Offset: 000451c6
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 73f1
Additional Information 2: 73f1defe6a7157f052e971e3a615d410
Additional Information 3: eed1
Additional Information 4: eed13f620c96916f8cbdddf61d177b40

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt


CSR Elite - Firmware 757 and 177 software
CSP V1 pedals

It worked beautifully. One day, stopped. It sounds weird. I want you to know Im pretty knowledgable and went back looking for anything I could have changed, but I cant locate anything. I am about ready to format this thing. I got far too used to the vibration for up shift since I run such a narrow FOV - cant see my shift lights.

I can tell you that before I press "PRactice" or "Race" or "Test" to jump into the car, it recognizes and talks with my wheel and pedals with absolutely no issues. Once I get into the car, no dice.

Any other ideas?!

[DirkT]

Not that it should make any difference, but have you disabled the native iRacing Fanatec functions?

[Coasterreal]

No....but I will.

Computer has also been acting a little strange lately. Nothing is showing up on scans and such, but I may format and it and start clean. I would better be able to tell you if anything changes if I started clean. Will try this now.

[Coasterreal]

Crashed again with the Fanatec output unchecked.

I formatted my machine and reinstalled the minimal amount of drivers, etc in order to get iRacing up and going. Working like a charm.

I will keep an eye out on if and when this stops. I will ensure to test it each time after any sort of installs or driver changes.

[DirkT]

Good to know it was probably down to a faulty install, keep us posted if you ever find anything.