PDA

View Full Version : Crew Chief v 4.9.6.4 failing to start



Mr Kippers
02-10-2019, 05:06 PM
After updating Crew Chief a few weeks back I've been having some issues with crew chief failing to load up on occasions, even though it show it active on the task manager.

I've tried unistalling and re installing today and it now fails to load up at all. Any idea what could be causing the issue?

Brilliant app by the way. An absolute savior in races

mr_belowski
02-10-2019, 09:04 PM
heh, we've been working loads and loads on this issue. It's a badly behaved device driver and working around it is proving *hard*. My money is on a USB headset or some fancy gaming keyboard (like a Corsair). Might be worth trying with different deviced plugged in for the time being. We'll have something out in the next few days that should accommodate these crappy drivers a bit more elegantly

Mr Kippers
02-11-2019, 02:50 PM
Cheers, I'll give it a go with another keyboard or the headset unplugged.

mr_belowski
02-12-2019, 08:08 PM
new release is live, it should fix this problem (or rather, the app no longer attempts to scan devices on startup)

AlenC
02-15-2019, 01:31 PM
Hi,

After the last update (few days ago, must've been the update you mentioned in previous post) CrewChief starts and apparently runs (can see it in task manager), but the app window doesn't opet... So it seems this fix broke it for me.

aritanbm
02-15-2019, 05:05 PM
Hi,

After the last update (few days ago, must've been the update you mentioned in previous post) CrewChief starts and apparently runs (can see it in task manager), but the app window doesn't opet... So it seems this fix broke it for me.

This is happening with me too. It was working perfect before, and now its broken. Oh my. Gonna try unplugging some USBs here...

Sparten
02-15-2019, 05:30 PM
Make sure its not an "old" macro file that causing the issues see here: http://thecrewchief.org/showthread.php?1034-Unhandled-exception-has-occured-in-your-application

aritanbm
02-15-2019, 05:39 PM
Make sure its not an "old" macro file that causing the issues see here: http://thecrewchief.org/showthread.php?1034-Unhandled-exception-has-occured-in-your-application
Yeah, I don't think that's it, because I've never used custom macros and there are no json files in my crewchief documents folder... I tried uninstalling it, but it does not work. Important to say that it was working a few minutes before. I only closed it for a minute after a session in iRacing and it stopped working again. I've already had this behavior last week, before the last update.

EDIT:
Btw, rolling back to version 4.9.6.3 worked. I'll keep that version for a while then, since I can't generate error logs (the app shows in task manager, but doesn't start, not even in long periods).

AlenC
02-16-2019, 01:20 PM
I rolled back to an older version as well (from last year, it's the only installer I had), but if you need me to do some test, I can reinstall the latest one.

The Iron Wolf
02-16-2019, 03:03 PM
I rolled back to an older version as well (from last year, it's the only installer I had), but if you need me to do some test, I can reinstall the latest one.

Yes, if you'd like to help here are things that would be helpful:

* Using latest 4.9.6.7 version, pass NODEVICESCAN parameter to CrewChiefV4.exe and see if it makes difference with CC's startup.

* If you still get issue where CC does not show up, please follow this post on how to collect process dump: http://thecrewchief.org/showthread.php?1013-Update-4-9-6-4-Not-Working&p=4959&viewfull=1#post4959 Important: we need dump of the moment when CC does not show up and is only visible in the task manager.

Two more things:
- before you start CC, make sure it is not still running in the task manager. Do not start the new instance. If old CC does not close in 30 seconds, kill it before trying things.
- do you use trigger word recognition?

Thanks in advance.

AlenC
02-17-2019, 01:15 AM
I've updated to the last version and NODEVICESCAN parameter didn't do any difference.
Here's the link to the process dump: https://www.dropbox.com/s/aenvsoik8yw6kws/CrewChiefV4.DMP?dl=0
And I don't use word recognition.

Sparten
02-17-2019, 03:29 AM
Did you create any costum macros using older versions ? if so please rename the file.

AlenC
02-17-2019, 03:44 AM
Did you create any costum macros using older versions ? if so please rename the file.

No, nothing like that. I'm a very basic user. I just installed and played. And downloaded updates when it asked me to.

Sparten
02-17-2019, 04:08 AM
Thanks for the dump, i now had some time to check out what the issue is, and it looks like it fails to creat a device for playing audio, but my problem is that i do not know why its failing for you, so if you could you please check that you have 2 files located in "C:\Users\{USERNAME}\AppData\Local\CrewChiefV4\soun ds\background_sounds" also please go into windows sound settings, right click the speaker and click "Open sound settings" then click on "app volume and device preferences" in there the is an option to reset to Microsoft recommended settings, click that and try again.
Also remove possible corrupted app settings that might have gotten left over for previous install by deleting "C:\Users\{USERNAME}\AppData\Local\Britton_IT_Ltd"

AlenC
02-17-2019, 11:25 AM
Thanks for the dump, i now had some time to check out what the issue is, and it looks like it fails to creat a device for playing audio, but my problem is that i do not know why its failing for you, so if you could you please check that you have 2 files located in "C:\Users\{USERNAME}\AppData\Local\CrewChiefV4\soun ds\background_sounds" also please go into windows sound settings, right click the speaker and click "Open sound settings" then click on "app volume and device preferences" in there the is an option to reset to Microsoft recommended settings, click that and try again.
Also remove possible corrupted app settings that might have gotten left over for previous install by deleting "C:\Users\{USERNAME}\AppData\Local\Britton_IT_Ltd"


I have two files in background_sounds: dtm_pit_window_open.wav and dtm_pit_window_closed.wav. Also, I have deleted Britton_IT_Ltd without success. About sound settings, I can't find these options. Is this maybe win10 specific? I'm still using win7.

However, I should point out that I have a very old sound card installed along with onboard soud. It's a Terratec ews88mt and I use it to plug in musical instruments and route sounds. Windows default device should always be onboard sound (it must be, because otherwise a BSOD occurs). But if there is a problem with sound device, this is what could probably causing issues.

The Iron Wolf
02-17-2019, 06:14 PM
I have two files in background_sounds: dtm_pit_window_open.wav and dtm_pit_window_closed.wav. Also, I have deleted Britton_IT_Ltd without success. About sound settings, I can't find these options. Is this maybe win10 specific? I'm still using win7.

However, I should point out that I have a very old sound card installed along with onboard soud. It's a Terratec ews88mt and I use it to plug in musical instruments and route sounds. Windows default device should always be onboard sound (it must be, because otherwise a BSOD occurs). But if there is a problem with sound device, this is what could probably causing issues.

Alen, we have an idea what might be going on. I'll send you patched binary in a private message.

The Iron Wolf
02-21-2019, 09:07 PM
Version 4.9.6.8 should (hopefully, maybe, possibly) address issues mentioned above. Let us know how it goes, and huge thanks to AlenC for testing and data.

aritanbm
02-22-2019, 10:38 AM
Version 4.9.6.8 should (hopefully, maybe, possibly) address issues mentioned above. Let us know how it goes, and huge thanks to AlenC for testing and data.
I can confirm that the version 4.9.6.8 did the trick, at least for me. I haven't been able to start any of the recent versions and this last one is 100% here. Thanks a lot and sorry for not being able to help more with logs and such. Awesome work!

AlenC
02-22-2019, 04:00 PM
Working for me as well! Great job,thanks!

The Iron Wolf
02-22-2019, 06:22 PM
Thanks for confirming guys, that's a relief :)