jowl Posted July 8, 2013 Report Share Posted July 8, 2013 Hi. Having problems with WideFs carshing on startup - logs below. Regards Jonas Windows application log: Faulting application name: WideClient.exe, version: 6.9.9.8, time stamp: 0x51d1babc Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f Exception code: 0xc0000005 Fault offset: 0x0002e3be Faulting process id: 0xb08 Faulting application start time: 0x01ce7b62f06ce9c2 Faulting application path: C:\Program Files (x86)\WideClient\WideClient.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 2fa1d9f1-e756-11e2-b03c-60a44c314c13 WideClient.log: ********* WideClient Log [version 6.998a] Class=FS98MAIN ********* Date (dmy): 08/07/13, Time 00:40:11.247: Client name is 737PROSIM 46 LUA: "C:\Program Files (x86)\WideClient\Initial.LUA": not found 46 Attempting to connect now 46 Trying TCP/IP addr 192.168.2.50, port 8002 ... 46 Error on client pre-Connection Select() [Error=10065] No route to host 46 Ready to try connection again 296 New Client Application: "YokeControl" (Id=2844) 358 New Client Application: "SwesimAppStarter" (Id=2772) 1076 Attempting to connect now 2090 Connection made okay! Link to comment Share on other sites More sharing options...
Pete Dowson Posted July 8, 2013 Report Share Posted July 8, 2013 Having problems with WideFs carshing on startup - logs below. ... Faulting module path: C:\Windows\SysWOW64\ntdll.dll That's a network driver or hardware problem. Last time i had one of those I just uninstalled the Network connection and associated hardware (in device manager) and re-booted so that Windows would find it again and reinstall. Regards Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now