Jump to content

Weird hardware/USB problem!


Recommended Posts

Hi there,

I recently ran into a weird problem with my FSX rig.

I will try to be as precise as possible so please bear with me.

After I am done flying in FSX I close the programs used (FSX & REX) and try to shut down my computer.

It proceeds through to the shutting down screen and gets stuck. After a while Windows restarts with this:

Problem signature:

Problem Event Name: BlueScreen

OS Version: 6.1.7601.2.1.0.768.3

Locale ID: 1031

Additional information about the problem:

BCCode: 9f

BCP1: 0000000000000004

BCP2: 0000000000000258

BCP3: 0000000000000000

BCP4: FFFFF80000B9C510

OS Version: 6_1_7601

Service Pack: 1_0

Product: 768_1

After that happened a few times I started investigating a little. After I shut down FSX I cannot start any other programs.

I tried to start Firefox just to test it and in the task manager it shows under processes but not under applications.

Some information about my setup:

CPU i7 980

Nvidia GTX 570

Windows 7 SP1

FSX Gold

Numerous addons (too many to list just now)

I have quite a few USB devices attached.

Saitek yoke, 2 Saitek throttles, all Saitek panels, Saitek rudder pedals.

Alternatively the X-65F but not connected at the same time.

The throttles are connected through the yoke's USB hub (powered).

The panels are connected through a third party USB hub (also powered).

All else is plugged in directly.

Between the start of the problem and now I did replace the original Saitek drivers with SPAD.

SPAD is set up so it quits when I quit FSX.

That cured my sometimes unresponsive panels but not the main problem.

The problem existed before the driver swap anyway.

I am suspecting a USB/driver problem but just do not know what to do since I cannot identify anything in particular.

Please help!

Regards

A.

Link to comment
Share on other sites

Have you checked your event logs? Have you googled details on the bluescreen you are getting? Blue screens are most often memory related, though not always. Im not familiar with yours, you will needto search for that on google and the MS knowledge base. Is windows fully upto date with te latest windows updates, do you have all the latest drivers installed?

You dont state how much RAM you have in your PC, so I could just assume you have run out of memory after running FSX, hence the blue screen. But then again with all those usb devices you could be running too close ot the limit of your power supply, whats the wattage?

My personal opinion, ditch the SPAD drivers or what ever the **** they are. Get the latest saitek drivers through windows update, suprisingly enough they work. After that, well, give us more information to help you fix the problem.

Link to comment
Share on other sites

Hi Matt,

thanks for your fast reply!

Sorry, just forgot the rest of the specs:

Cooler Master HAF 932 Big Tower Sort

Fan: 1x 230mm Front, 1x 230mm Top, 1x 230mm Side

Corsair TX 850W PSU

ATX 12V V2.2, 80 Plus, Standard, 4x 6+2-pin PCIe,

Intel Core i7 Extreme i7-980

3.33Ghz, Socket 1366, 12MB, 130W, Boxed w/fan

Gigabyte GA-X58A-UD3R

ATX, Socket-1366, DDR3, 4xPCI-Ex(2.0)x16, SATA 6Gb

Corsair XMS3 DDR3 1600MHz 6GB CL9

Kit w/3x 2GB XMS3 modules, CL9-9-9-24, for Core i7

Gainward GeForce GTX 570 1280MB PhysX

PCI-Express 2.0, GDDR5, 2xDVI, HDMI, DisplayPort,

Corsair SSD Force Series 2,5" 60GB

SATA2, 285MB/275MB/s read/write, incl 2,5" to 3,5"

Western Digital VelociRaptor® 600GB

10000RPM, 32MB, 3,5", SATA 6GB/s (SATA 3.0)

Windows is updated completely.

The same goes for all drivers apart from the NVidia one.

Just was not sure about the latest driver there (still running on the 275 family).

The rest should all be updated ok.

Cheers

A.

Link to comment
Share on other sites

Shut FSX down by going to end flight, then back to the menu screen, THEN closing the sim. Does it still fault?

If not, then it's nothng to do with USB or hardware, it's to do with the shutting down of the associated programs to FSX and a delay in their return of the allocated RAM to the buffer.

Also check you are running the highmem fix in FSX,cfg.

I am assuming 64-bit Win 7..?

Link to comment
Share on other sites

Hi Snave,

what you suggested is how I always close down FSX. Fault persists regardless.

Highmem fix is active.

Win 7 64 is correct.

Still at a loss...

Link to comment
Share on other sites

  • 2 weeks later...
  • Aerosoft

It's a bug that is rather common for many high end add-ons. Our Airbus suffers from it as well and it does so even if we ONLY use commands that are given by MS in the SDK. It has to be a memory issue but MS has never been able (or willing) to assist us in solving it. I have never seen it in Prepar3D so I assume Lockheed Marting solved it.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

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. Privacy Policy & Terms of Use