Blue Screen of Death now Falcon BMS won't run
-
Good morning, all,
Last night I was playing Falcon BMS 4.32 after several training missions and furballs (approx 2 hrs), I received the “blue screen of death” when setting up my next furball match before committing to the game. Now, the game will no longer start. I get the start up menu and can access the configuration stuff, etc, but Falcon BMS will try to load, but then crashes back to the desktop.
My system is new as of a month ago and is as follows:
Windows 7 Home Premium Service Pack 1
i5-4590 processor
Asus Z97-A motherboard
8GB of memory
eVGA GTX760 video card with driver version 340.52
ASUS Xonar DGX 5.1 Channel Audio Card
CH Fighterstick & CH ProThrottle, using HOTAS setup as found in “USER” folder within BMSWhat I have tried after BSOD:
Turned off start up movie (as suggested)
Re-start computer (even though it did after BSOD)
Checked drivers for most up to date versionsNO other configuration, driver, or other changes were made between when it was working and when it stopped. When this happened on my old computer, it was due to an audio driver update. It worked before the update, and didn’t after so it was easy to diagnose. This problem is more difficult for me as I can’t find the problem. My other applications and games run fine, which is primarily MS Office and Strike Fighters 2 series.
Would anyone be able to shine some light on what to check for? I apologize if I’ve left any needed info out. If more is needed, please let me know what and I’ll post it when I get home this evening.
Thanks in advance to you all, and thank you for your patience if this is a silly problem.
Best regards,
Rob -
simple spot the stop error message in the BSOD and search what it is.
Like here: http://pcsupport.about.com/od/findbyerrormessage/tp/stop_error_list.htm
-
Try one thing Rob
In config folder, delete display.dsp, BMS will rebuild it.
See if that solves your problem. Then go to setup and configure again your screen.Good luck.
Note: this will not solve the BSOD. If it is only one instance of BSOD, ok. But if you get more BSOD you will have to find and solve the main problem.
-
ALAS this is not needed at all.
-
Why Arty? this has solve for me similar problems in the past.
I am wondering if his .dsp got corrupted when he had the BSOD… -
Good morning, Gents,
Wow…Thanks for the quick replies!
I will try both…much appreciated! I didn’t think to write down the error message from the BSOD…is there a log file somewhere that I can retrieve the error? Sorry again if it’s common knowledge…I’m a bit ignorant of such matters.
Once again, thanks so much for the quick reply! I’ll try both when I get home.
Best regards,
Rob -
@ALAS cause u haven’t yet found the source of problems. Starting to jump around this and that in luck might cause more troubles. This ain’t a virus so to act in multiple actions at the same time. One step at a time.
This might be simple like from drives to serious like hardware fault.
@RobfromME in case your system restarts and u don’t have time to spot the error do this: http://pcsupport.about.com/od/windows7/ht/automatic-restart-windows-7.htm
else info is located in the minidumps which is more tricky: http://www.ehow.com/how_5349981_read-screen-death-minidump-files.html
-
Thanks so much! I’ll try that tonight and report back.
Once again, thank you.
Best regards,
Rob -
Don’t mention it m8. Hope the problem is something simple like a driver or so.
-
Arty:
He has not requested help for solving the BSOD, but for solving BMS not starting.
A single BSOD is not enough to diagnose a hardware problem, but it should be taken into account, that what I put my final note on the post.In his post he states that his computer and other applications are operating normally, only BMS is showing problems
It is very obvious that if BMS is not starting, something was corrupted, during a file I/O operation. I bet for .dsp but I could be wrong, but as deleting the .dsp is very simple, and wont cause any harm, because it will be rebuilt in the next BMS start, I recommend to do that.
I agree with you that he has to find the source of the problems, but I disagree that you have to be worried for a single BSOD. Why? because as you know, correctly troubleshooting a BSOD is a long process. Its the repetition of the BSOD that would rise a warning in me to start that long process, specially with anyone’s computer that I don¡t have access to.
So in summary my approach is: try to repair Falcon, and if the BSOD does not repeat, do not worry about it.
-
BTW, when I first posted, we cross-posted, so I saw your reply after my post, was not my intention to step on you
-
I don’t have a problem with that. Also I understand that your intention is to help. This is good and I’m glad with it.
But some things need more special and focused care maybe from more experienced ppl. I’m not saying I’m a guru or the experienced guy then u.
Just saying that dx9display.dsp has nothing to do with BSOD from what I know till now.Also from what I learned till now the best solution to isolate a problem is to interfere with one thing at time, to narrow down the problem cause. If u change multiple things at the same time u will end up without knowing what caused the problem, if a solution is found, and if not u might cause more then one problem and then u will have to fight for 2 or more problems instead of one.
The last case drives many users to often format their systems and reinstall OS, cause of luck of knowledge and cause things are way fubared to solve.
My OS was installed only once… since the very beginning of win7.
For HW problems u leave on the very basic and remove the rest… then one step at a time u add one component and check, then the next and so on.
-
This post is deleted! -
But Arty you are explaining my the ABC…All fair, I dont think I have to demonstrate my experience in a forum. Again, IMO one single BSOD is not a reason to be worried, but who am I.
Rob in my country there is a saying: One medic will heal you, two will kill you. And is true so I quit.
Good luck
-
buhhh u might step on a bad doctor and die either way. This is why we have the forum. If u know the solution or if u think u know the solution share it. If it’s wrong someone will correct things up.
-
I am always hesitant to tell others to delete ANYTHING. Especially if its just a educated guess.
-
Hi guys,
I really appreciate the input of all you. Thanks so much! I hope I didn’t start trouble for you fellows… that wasn’t my intention. I really do thank you all for your kindness and willingness to help. Makes me glad to be part of the BMS user family!
All my best,
Rob -
No trouble m8. we just talk.
-
I am always hesitant to tell others to delete ANYTHING. Especially if its just a educated guess.
I had exactly the same problem, from a BSOD, and exactly the same solution fixed it for me, deleting the .dsp file.
Further, one of my flying buddies had the same problem and doing the same thing solved his problem as well.
In this case, the file in question is IN the Falcon directory, so if it’s REALLY a problem, you can just reinstall.
-
Hmmm see ALAS seems u r more correct then me.