Jump to content
The simFlight Network Forums

BSOD when WideServer active in FS9 on W7 Pro x64


Recommended Posts

Hi Peter

I am getting BSOD crashes when I have WideServer.dll and Wideserver.ini (6.9.4.0) enabled (active) in FS2004 on my

Windows 7 Pro x64 pc (fully updated). The module identified as generating the BSOD is the TCP/IP module (identified via "WhoCrashed"). FS2004 is installed on a disk and subdirectory away from the Windows protected areas. FS2004 has its updates. FSUIPC is version 3.999z. The crash occurs approximately 30 seconds after starting FS9 fly now. No crashes occur when WideServer.dll and WideServer.ini are disabled (by changing the dot in their names to an underscore). The LAN module driver is the latest one from the ASUS site for the P6T Deluxe v2 m/b.

The pc has two operating systems installed as a dual boot configuration. The other operating system is Vista HP x64.

I have FS2004, FSUIPC and WideServer installed (the same versions) and fully working under the Vista O/S. So the same hardware runs both O/S. FS2004 is installed in this case in the sub-directory "Program Files (x86)/Microsoft Games/Flight Simulator 9/", ie within the protected area.

I am attaching a zip file containing FSUIPC.ini, FSUIPC.log, FSUIPC Install.log, WideServer.ini, WideServer.log and WideServer0.log from the W7 installation in case that helps you at all.

Please would you review this information and if possible offer any advice you can.

Best regards

Sparrowm7

WideFS_W7_FS9.zip

Link to comment
Share on other sites

I am getting BSOD crashes when I have WideServer.dll and Wideserver.ini (6.9.4.0) enabled (active) in FS2004 on my

Windows 7 Pro x64 pc (fully updated). The module identified as generating the BSOD is the TCP/IP module (identified via "WhoCrashed").

It seems you definitely have either a hardware fault or a corrupted or mismatched Network driver system. There's no way WideServer itself can cause a BSOD, those things always indicate low level problems, hardware or hardware drivers. I can only suggest you try uninstalling the network hardware and re-installing it so that Windows will reload fresh drivers.

Regards

Pete

Link to comment
Share on other sites

Thanks Pete, I appreciate your feedback. With so many people (and myself) successfully using your FSUIPC and WideFS tools I thought it unlikely that the problem was routed in them.

I do appreciate you having got back to me so promptly.

Best regards

Sparrowm7

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.