Sign in to follow this  
Ray Proudfoot

BSODs driving me mad!

Recommended Posts

Hi Jim,

 

In recent weeks I've started getting BSODs when running FSX. They're completely random which doesn't help identify the cause.

 

This is what I've done...

 

1) Run sfc /scannow. This reports no problems.

 

2) Run verifier.exe in accordance with the instructions on this site. http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

When I bootup I get a BSOD with code c9 and points to gfvknt64.sys as being responsible. BlueScreenView is below.

 

BSOD.jpg

 

Right-clicking on this file in windows\system32\drivers states it's been signed by GoFlight. I have recently installed the latest version of their software having scrupulously removed all references and files from its earlier install.

 

My BSODs only occur when I either run verifier.exe at startup or when I'm running FSX. But in fairness I rarely use the PC for anything else.

 

I have the following GoFlight modules all bought over 10 years ago except for the MCP-Pro and EICAS. All except the MCP-Pro & EICAS are plugged into a D-Link USB powered hub. The others are plugged directly into the motherboard.

 

1xGF-LGT

2xT8

1xP8

2xGF166

1xMCP-Pro

1xMCP_EICAS

 

I'd appreciate your opinion and advice.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Ron,
BSODs are terrible and the causes hard to find.

About 2 years ago I was plagued by a series of random BSODs running FSX (not at bootup). BluescreenViewer showed a variety of DLLs/EXEs being the suspects. I did all checks I could think of but nothing was found. As a last step I installed an old joystick sitting in the basement and the problem was gone. So it turned out it was a malfunctioning Saitek module.

Since your GoFlight modules are over 10 years old it might be useful to check if they are all healthy.

Share this post


Link to post
Share on other sites

Ive been battling a stupid BSOD for over a year, and I tell you I dont like to lose to computer problems after being a technician for 25 odd years. Stupid Microcrap couldve put a little more useful info than the garbage it spits out when giving a BSOD. Bluescreen viewer does give some clues but still vague. Its most likely a driver. Hardware seems unlikely these days although a good hardware diagnostic is not a bad idea just to rule it out. Im sure youve done it already.  

 

Someone mentioned this to me and its worth a try. Sometimes MB manufactuers are not the best in keeping the chipset drivers up to date, so you can try this intel utility if you have an intel chipset. 

http://www.intel.com/p/en_US/support/detect

 

I agree with the GoFlight modules. Make sure its all up to date.  

 

What is MB manufacturer?  I just killed the AsusSuite that was running resident as a monitor for the mb temps and so forth and also its own usb utilities, and so far no BSOD, but havnt run p3d/fsx yet which is a fantastic test for it. 

 

Also sleep wake states can screw things up. Check up on those guys. 

Share this post


Link to post
Share on other sites

Andreas,

 

Who's Ron? :wink:  It's Ray.

 

All the GoFlight modules seem to work okay. I did install their latest software yesterday but may revert to the earlier version. I have posted on the GoFlight forum and await their response. I've given them full driver details of the offending file.

 

Dave, it's a Gigabyte M5.Snyper. I did have an Asus but suffered with the frozen clock problem and had the board swapped by the people who built it for me. I may try that Intel utility but want to hear from GoFlight first.

 

Previously to this PC I ran FS9 on a home-built PC that never gave me any problems like this. So damned frustrating when FSX runs like a dream.

 

Thank you both for your input. I'll come back once I've heard from GoFlight.

Share this post


Link to post
Share on other sites

Hi Ray,

 

I agree with the comments above. It is a problem with your GoFlight product. You should make sure you have the latest update installed - http://www.goflightinc.com/pages/support. You can also try uninstalling the product(s), cleaning your system registry with a registery cleaner like CCleaner and then reinstalling the drivers as the Administrator.

 

It could be a defect in the GoFlight hardware too (trying to pull up! to many time! LOL!).

 

I wish there was an easy solution but BSOD's occur mainly because of defective hardware or hardware drivers. Fortunately the BSOD shows the driver that was the cause of your crashes. It could also be the USB port that your hardware is plugged in. A driver update program (freeware) will tell you what hardware drivers are out of date on your computer. If a USB port shows up, then I would move the device to another USB port or Google the USB port device shown in the update program that needs updated and download and install the update yourself. Of course, you could also pay the small registration fee for the update program to do all of that for you.

 

Hope this helps.

 

Best regards,

Share this post


Link to post
Share on other sites

I had similar issues with BSODs with around 10 different messages concerning memory, drivers, USB, HDDs...  Finally after months, figured out that in the process of OCing my CPU, it also made my memory run 0.25V over what it was originally.  Turning it down to the default value made all problems disappear.

Share this post


Link to post
Share on other sites

Hi Jim,

 

I have installed the latest GoFlight software yesterday and after uninstalling the old version searched the C drive for all files with GoFlight in their name and deleted them. I also manually checked the registry and deleted all references to GoFlight. So I'm happy that prior to the latest install the PC was clean.

 

I have tried these driver updates programs and I've read pros and cons about them. I will try a free scan and see what it comes up with. It is frustrating because I've had this PC a year now and the BSODs have only started in recent weeks. FSX in comparison is very stable.

 

I'm going to try the previous GoFlight software but first I want to hear from GoFlight.

 

Max, it's a professionally built PC which has been bench-tested for 24 hours to ensure it's stable. I loaded an unclocked BIOS profile and it still failed at bootup with verifier.exe running. So I'm certain it's not an overclocking issue.

 

Thanks to both of you.

Share this post


Link to post
Share on other sites

I haven't heard back from GoFlight yet but I've decided to uninstall the GF software and unplug all GF modules. Then I'll fly the default 737-800 or Concorde.

 

I've never gone more than 3 flights without a BSOD so if I can fly for a few days without problem it does point to either GoFlight software or hardware.

 

Assuming the flights are problem free I will then reinstall the GoFlight software but only plug in one module. Then more flying to see if the stability remains. If it does then I'll add another module. And so on and so on until they're all plugged in.

 

The randomness of these crashes is what is so mystifying. If they happened as soon as FSX loaded it would be easier to solve. But I can go a couple of flights or just sat at the gate and then bang!

 

Of course if I still get them without GF installed then the error above was a red herring and I'll have to try a different approach. But this seems like the best way to go.

Share this post


Link to post
Share on other sites

Ray,

 

I'm going to chime in here.

 

I agree with the chipset update. If you have Gigabyte, then they do a good job with their installer. You could also run a third party freeware driver update scan for information purposs only (I strongly advise against using those for installing, or even using some of the drivers they call for).

 

Question:  Do you allow Windows to Update?

Share this post


Link to post
Share on other sites

Besides drivers, you maybe want to see if there are firmware updates either for your PC hardware or the GoFlight modules. The only BSOD I've had with Win7 was due to my SSD firmware.

Share this post


Link to post
Share on other sites

I strongly advise against using those for installing, or even using some of the drivers they call for

Not sure why you made that recommendation. This might have been a good recommendation several years ago as the programs were primitive but hardware update sites do a great job finding the latest drivers for your system today. It is now a very competitive business. I run mine (Driver Genius) at least once a month. All of the programs set a restore point before installing. Perhaps the fact I keep my hardware updated is the main reason I get few CTD's and, if it is a CTD, it is not driver/hardware related. Bugs are found in hardware and drivers are frequently updated to fix that bug. So I think it's a good option for those who want to keep their systems updated.

 

I don't think it is really required for someone who buys a new computer system, like a Dell or HP, as these companies usually will post an update for a particular system. After a year or so, my experience has shown that they quit updating their "old" systems and move on to their newer systems. So an driver update program might be appropriate for older systems.

 

Best regards,

Share this post


Link to post
Share on other sites

I found an awesome driver update program after suffering similar blue screens

 

.http://download.cnet.com/DriverToolkit/3000-18513_4-75910245.html

 

I can tell you I hate handing over $$ to these types of programs as its a lottery but this works like a charm. It scans and in my case there were 24 drivers (confirmed by other scanners as well). One click on each and it downloads the latest version and one more click installs them. No need to trawl all the manufactures websites looking for drivers, thats a nightmare.

 

There is a trick. Download the program and then uninstall it and just before you do it asks if you want a 1 month license for $9.95. I did that although I wished I got the full program be cause Im going to buy it again anyway

 

best of luck!

Share this post


Link to post
Share on other sites

 

 


Not sure why you made that recommendation.

 

Jim,

 

i hear you.  Just last week I ran the freeware version of Driver Genius, and though my system ran, FSX performance took an incredible hit and I also had some VERY strange driver and video behavior.  Surprised me.  Something was terribly amis, and I had to go back to a system image.

 

DIdn't see it coming, but it happened.

Share this post


Link to post
Share on other sites

Jim,

 

i hear you.  Just last week I ran the freeware version of Driver Genius, and though my system ran, FSX performance took an incredible hit and I also had some VERY strange driver and video behavior.  Surprised me.  Something was terribly amis, and I had to go back to a system image.

 

DIdn't see it coming, but it happened.

It's hard to understand what you are trying to say above. You ran the freeware version of Driver Genius but "FSX performance" took an "incredible hit" and you had some "very strange driver and video behavior."  Yikes!  The freeware version only provides you a list of drivers that need to be updated. In order for the program to update your drivers, you have to pay for a yearly license. Then, the program will download and install your drivers AFTER it runs system restore. So it is impossible for the freeware version to do anything to your system other than tell you what drivers are out of date. As you know, whenever you suffer problems with FSX performance after installing a program, you can try to restore your system to a date before the performance "took an incredible hit". 

 

You should have seen it happen as you were the only one who installed the Driver Genius software and ran the program.

 

Best regards,

Share this post


Link to post
Share on other sites

Here's what I've done this morning...

 

Booted with verifier.exe running which checks all non-Microsoft drivers. Got the same BSOD on the GoFlight Virtual Keyboard driver.

 

Uninstalled GoFlight and had to uninstall virtual keyboard seperately. Rebooted still with verifier.exe running and it booted cleanly.

 

Installed previous build of GoFlight software. Forgot I still had verifier.exe running and got BSOD during install. Pointed to dxgmms1.sys as culprit. DX file so I ran DXDiag and it reported no errors. By now I have switched off verifier.exe.

 

Installed Driver Support. Reports only 4 drivers are out of date:-

 

  • Intel HD Graphics 4600 (m/b graphics which I don't use.
  • HP Laserjet driver. Hardly relevant
  • Intel Display Audio
  • NVidia High Definiton Audio.

Don't think any of those are system critical.

 

I do run Windows Update. That is up to date.

 

Everything still points to GoFlight but I haven't heard from them yet.

 

So what next?

Share this post


Link to post
Share on other sites

I installed and ran the Intel Driver utility. It recommended the mobo graphics be updated. That was the only thing it found.

Share this post


Link to post
Share on other sites

I've just had this reply from GoFlight support...

 

Thanks for finding this. It appears that particular driver has not been recompiled. I'll look into it today and come back to you.

I maintain the Goflight driver code for Goflight, so technically you are talking to Goflight.

Apologies for the inconvenience.

 

If it just needs recompiling it could be a huge weight off my shoulders. Keeping my fingers crossed a new version solves the problem.

Share this post


Link to post
Share on other sites

GoFlight also suggested that as a short-term fix I could uninstall the GoFlight Virtual Keyboard utility. This has the effect that buttons programmed to actions in FSX not being recognised.

 

I did that and had a short hop from EGKK-EGCC. Everything went fine. I'm quite optimistic about this especially as Steve at GoFlight said the problem file could well cause BSODs.

Share this post


Link to post
Share on other sites

Good to hear you might have a bearing on the issue.  Bloody annoying. MS couldve made this a whole lot easier by having more informative error logs and messages.  Not sure if windows 8 is any different or if the whole error process is handled differently. 

 

If anyone else comes across this thread for BSODs, this page might also prove useful.  Ray was using it and it outlines the verifier program and your drivers and also used in conjuction with windows debug to find the addresses its pointing to thus the drivers.  

 

 

http://gadgets.itwriting.com/748-fixing-a-windows-blue-screen-with-driver-verifier.html

Edited by HighTowers

Share this post


Link to post
Share on other sites

I'm afraid I spoke too soon. Had another BSOD this afternoon with a different message. Never had this one before.

 

BSOD2.jpg

 

In desperation I've posted on Microsoft's site. Steve at GoFlight thinks it's hardware related. I've run chkdsk on both SSDs and they're fine. Currently running MemTest86 which will take around 4 hours so will report back either tonight or tomorrow.

 

If memtest reports errors (which I'm praying it will) then it's an easy enough job to replace the sticks. These BSODs have only started in the last week. Apart from Windows updates hardly anything has changed.

 

If it's not the memory then I'll have to start unplugging GoFlight modules and adding them back one by one. can't see what else it could be. The crashes are so random and in 20+ years of having PCs devoted to FS I've never had things as bad as this.

 

Dave, I've just read that blog you linked to. I'll do the same and see if anything starting up from the Registry is causing the problem. Thanks for that.

Share this post


Link to post
Share on other sites

I've had an answer from Microsoft with a link to a hotfix. Once my mail server is back on line I'll apply it and return here with good or bad news.

Share this post


Link to post
Share on other sites

I only get BSODs when my system overheats. That happened about six weeks ago. I opened the casing and saw that

 

my cpu fan and cooler were totally covered in dust. Since then I got the dust out and have not had another BSOD.

 

I would agree that your problem looks like its hardware related.

 

Good Luck

 

James

Share this post


Link to post
Share on other sites

Just a thought that passed my mind - even though it´s probably not an overclock issue - have you checked your system temps (dust might clog the heat spreaders, radiators etc)? Tried running the computer with Prime etc, to ensure it´s in fact stable?

Btw - regarding your last BSOD: 

 

 

 

http://www.solvusoft.com/en/files/bsod-blue-screen-error/sys/windows/microsoft/windows-7-home-premium/discache-sys/

Share this post


Link to post
Share on other sites

James & Kristoffer,

 

Appreciate your comments. Pretty certain heat is not an issue as the room is only slightly heated and I live in NW England and it's November.

 

I've applied the patch from Microsoft. It relates to this KB article. If anyone has a clue what it means I'd love to know.

 

FSX is now running with the aircraft parked at Gatwick. I'll leave it for a couple of hours and then take it for a spin or two tomorrow. Fingers are very tightly crossed. :Praying:

 

This is what the Microsoft support staff posted on his reply. Does it mean anything to anyone?

 

STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  srv2!Smb2FreeResponseBufferForAsyncCall+1c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: srv2

IMAGE_NAME:  srv2.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dba2b0a

FAILURE_BUCKET_ID:  X64_0x44_srv2!Smb2FreeResponseBufferForAsyncCall+1c

BUCKET_ID:  X64_0x44_srv2!Smb2FreeResponseBufferForAsyncCall+1c

Followup: MachineOwner

Share this post


Link to post
Share on other sites

Good to hear you are slowly getting your problem fixed Ray. I'm surprised another BSOD with another Bugcheck code occurred. According to the techs at this link - http://msdn.microsoft.com/en-us/library/windows/hardware/ff558982(v=vs.85).aspx it is difficult to determine the exact cause of this issue. Hopefully the Hotfix will work. I have a feeling it has something to do with the communication process to your GoFlight hardware.

 

Best regards,

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this