Blue Screen of Death now Falcon BMS won't run
-
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.
-
@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
Good evening Arty,
Well, I tried for a couple hours with the Windows Debugger and reading the minidumps, but I never could get it to read the symbols files that I downloaded, even when I pointed to the directory where I put them. I’m afraid Windows Debugger “buggered” me! I did, however, turn off the auto restart after a crash dump, so next time I can write down the error.
I’ll try deleting the file display.dsp since I’m afraid that’s the only thing within my capability. That debugger kicked my computer-illiterate butt.
Warmest regards,
Rob -
well that is ok. For sure if it happens again u will be able to see the stop error.
-
Good morning, Gents,
Alas, it worked after deleting the display file……for a while. Then, once again, on the screen to set up a 1v1 dogfight furball, when I clicked commit I got the BSOD. Fortunately, I had disabled the auto restart and the following error was noted:
System_Service_Exception
Technical Information:
STOP: 0X0000003B (0x00000000c0000005,0xFFFFF88005839DB6, 0xFFFFF8800CB9BC00, 0x0000000000000000
cmudaxp.sys - Address FFFFF88005839DB6 base at FFFFF8800567F000
DateStamp 4eefffab
I have no idea what it means, but I hope it is helpful. The link Arty was kind enough to include says it’s likely a driver issue, but I’m not sure what to do. I have the latest drivers (installed two weeks ago, and verified last night when I got home).
Also, it seems that deleting the display file again get things running. HOWEVER…both times it crashed, it appears to corrupt my controller because my mapped keys no longer work. I am using Kolbe’s spreadsheet to make the keystrokes files. As I’d set it up some time ago, I’m now having trouble getting my CH sticks to work properly, but I’m sure that’s just my ignorance and I don’t believe it has to do with the crash. It had worked flawlessly until the crash. I think it’s because I don’t have the correct .cms or .map file downloaded to my joysticks. Ugh…
Thanks for the continued support, folks. This is my favorite sim for air to air combat thrills, but the continual tweaking and difficulties sure makes it a challenge to enjoy. Seems I just get it running and then something else goes wrong. Of course, most of it is probably due to my computer illiteracy, but I wish it was easier for a computer layman to play since it’s got so much potential.
Once again, thank you!!
Warmest regards,
Rob -
Hi Rob:
As you are getting more BSOD, we are now certain that your computer has a problem, that we have to locate and fix.
Deleting .dsp is curing the symptoms, but not the disease, so sadly in this case this solution is not valid.The BSOD could be related to many, many causes, some are software related (drivers, trojan-virus…) and some are hardware related. Hardware ones does not necesarily mean a faulty hardware, could be a failure due to bad bios settings in the best case, up to a phisic hardware failure in the worst.
The BSOD troubleshooting is a relatively difficult process, and if you haven’t troubleshooted one before,you’d better by helped in that process that attempting to fix it on your own. On the other hand, you could learn a lot by trying to do it yourself, but it will cost time.
As every step has to be tested thoroughly, this takes a lot of time. Change something, wait for BSOD to appear, change again… etc
I am sure Arty will come up with a step by step guide (at he says, one step at a time). I will be glad to team up with him to help you out.
In the meantime, if you make for us a list of all the recent things that you remember you made… did you make any hardware changes? did you change bios settings? did you install software? what about your antivirus and windows updates?.. etc
Have you Overclocked your PC?
Tell us about the temperature in the room where the PC is… do you know how to check your CPU, GPU and Motherboard temps?
-
It seems this “ASUS Xonar DGX 5.1 Channel Audio Card” is your problem…
From a solution forum : http://www.techsupportforum.com/forums/f19/solved-asus-xonar-dg-bluescreening-and-quot-cmudaxp-sys-and-quot-when-accessing-recording-devices-695101.html
Fixed. Cheers for the replies though, lads. If anyone else has this issue dig out the original driver disc and do a complete reinstall (i.e delete every trace of the driver and reinstall it again from the cd). This worked perfectly for me, but only after I deleted the driver completely.
Cheers!
-
Good morning, Arty and Alas,
Everything but the hard drive was new a month ago. I am not manually overclocking, that is beyond my ability, plus, I’m paranoid about burning up my computer (however, see below on the video card). I do have hardware monitor installed and check the temps regularly since my last computer had a video card get toasted (Of course, it was 8 years old when it died!). I am running the eVGA 760GTX Superclocked with ACX coolers. My CPU has the Noctua NH-D14 cooler installed. I keep my computer room air conditioned at about 65-68 degrees. After a couple hours of either Strike Fighters 2 or after Falcon BMS (checked right after it crashes) the CPU cores are all at 26-28 C and the GPU is at a maximum of 30 C.
Only Falcon BMS is experiencing difficulties right now. Otherwise, smooth as silk.
It’s interesting that the audio driver is the apparent problem. On my old computer (2 months or so ago) it was also an audio driver that was the problem. That was easy to find, though, since it was working before I updated the audio driver, then it quit working after the update. So, I reverted back to the original and all was well. Perhaps BMS is sensitive to the audio system employed?
As frustrating as this is, it’s certainly interesting and has piqued my curiosity!
I’ll try the fix Arty found when I get home this evening and report back.
Once again, thank you folks! It wouldn’t be possible for me to fix this without your kindness and volunteering your time. I appreciate your efforts.
Warmest regards,
Rob -
Perhaps BMS is sensitive to the audio system employed?
Yes, it is. I once spent a week trying to trouble shoot a particleSystem issue, only to find out that the game won’t start up if it can’t detect a legitimate audio device to use. I found an old pair of headphones and plugged them in (the system in question was my dedicated gaming server) and never had a problem again. But it was a silly error for the fix that I had to employ.
Essentially it was Black Screening and CTDing everytime I started up Falcon.
The quirks of playing an older game, I suppose.
-
Always glad to try to help a fellow falconeer.
Rob one thing caught inmediately my attention. Your computer is one month old. Thats good news, becasue if we dont find an easy fix, you can always have your computer returned to your dealer for thoroughly checks.
Also dont be surprised that the audio is, for the 2nd time, a source of problems. They often are. And your MB *which is good BTW} has an onboard chip sound, Realtek ALC892 8 .
Can you check if you have the onboard sound disabled_Cheers!
PS:yout temps seems pretty good, (provided that the 65-68 degrees in your room are Farenheit (J/K) )
The fact that the BSOD only happens with BMS is not conclussive, bit it gives clues. Falcon is very demanding on resources. During the troubleshooting, we will test your system CPU, RAM, etc with dedicated tests for this purpose. -
Yes, it is. I once spent a week trying to trouble shoot a particleSystem issue, only to find out that the game won’t start up if it can’t detect a legitimate audio device to use. I found an old pair of headphones and plugged them in (the system in question was my dedicated gaming server) and never had a problem again. But it was a silly error for the fix that I had to employ.
Essentially it was Black Screening and CTDing everytime I started up Falcon.
The quirks of playing an older game, I suppose.
I confirm I also had this problem in a dedicated server, and got solved as you say, probably I read the fix from you. So thanks!