Blue Screen of Death now Falcon BMS won't run
-
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!
-
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.Thanks so much!! Unfortunately, my computer is already at the dealer (me! I bought the components from Newegg based upon reviews for reliability and past experience with hardware), but hopefully it will be a software problem. I am comfortable building the computer from a hardware standpoint and selecting stable reliable components to help along those lines, but the software side is not my cup of tea. I’ve built my last 4 computers since I just can’t seem to find what I want in a complete package. So far, it’s been worthwhile as they have been stable and reliable, the last one going 8 years before this one.
I did disable my onboard sound via the BIOS, but a good check for sure!
LOL!! Yep, room temperature is 65-68F! I like the heat, but >150F would be a bit tough on me! Thanks for that….I needed a good chuckle.
All my best,
Rob -
Thanks so much!! Unfortunately, my computer is already at the dealer (me! I bought the components from Newegg based upon reviews for reliability and past experience with hardware), but hopefully it will be a software problem. I am comfortable building the computer from a hardware standpoint and selecting stable reliable components to help along those lines, but the software side is not my cup of tea. I’ve built my last 4 computers since I just can’t seem to find what I want in a complete package. So far, it’s been worthwhile as they have been stable and reliable, the last one going 8 years before this one.
I did disable my onboard sound via the BIOS, but a good check for sure!
LOL!! Yep, room temperature is 65-68F! I like the heat, but >150F would be a bit tough on me! Thanks for that….I needed a good chuckle.
All my best,
RobHi Rob, if you are the “dealer” that’s even better. It is good to know that you are comfortable opening the computer’s case.
And you still have warranty from newegg in case (I hope not) you have to RMA anything.
In my last post I forgot to mention that I would put the eVGA last in the list. THese are very good cards and eVGA a very good quality assembler. If the card is factory OCed, the card is fine at these settings.
So, as Dr. Arty said, start with the audio card checks. BTW, one easy test is to remove the sound card and see what happens. And remember, only 1 step at a time.
Good luck and report any doubt.
-
Captain obvious here, if your DSP overheats, what about the rest of components???
That is, mobo chips, SATA controller, USB controller, CPU, GPU. They can and WILL burn down and not just remind with BSODs.
-
Captain obvious here, if your DSP overheats, what about the rest of components???
That is, mobo chips, SATA controller, USB controller, CPU, GPU. They can and WILL burn down and not just remind with BSODs.
Good evening, sthalik,
I’m not sure what DSP is, but if that refers to the graphics card I had overheat that prompted my new computer, the fan failed on the card and I didn’t notice. Of course it was 8 yrs old with many thousands of hours on it (CAD, GAMES, etc.). But, just in case, I’ve got plenty of cooling capacity now. I have found a couple driver problems thanks to the help from this forum and kind folks like yourself, so I’m confident it’s closer to being solved. Watching football tonight, though, so I’ll finish this weekend!
Thanks again!
All my best, Rob
-
Hi there Rob:
I see you are taking the things with patience and this is a very good recipe for a final success.
I am very confident that you will solve the problem once you check the sound card. The good thing of your BSOD is 1) that is clearly pointing at the soundcard and 2) that the BSOD can be reproduced very easily. (In your detailed reports you have said that it happens when comitting to a furball). That is a good sign that it may be software related.
I have one new question for you:
on the screen to set up a 1v1 dogfight furball, when I clicked commit I got the BSOD
This has always been the case, or it worked before and started happening suddenly one day?
Best regards
-
DSP=digital signal processor commonly for sound cards.
-
Good morning, all,
Although not assured of success yet, I did find the following problem and corrected it:
The eVGA card is plugged into my monitor with an HDMI cable. I kept my monitor when I upgraded since it was fairly new, but had originally had it connected with a DVI cable since my old graphics card didn’t have HDMI. The new graphics card can send sound over the HDMI to a device with speakers. My monitor has speakers…didn’t remember that since the speaker grills are in a location where they’re not visible! So, I disabled the HDMI sound and after an hour or so this morning it ran without crashing.
I’m not sure I’m home free yet since it would run before and crash after a couple hours, but I did go back and forth between the game and the furball screen several times and changing the adversary airplane and everything ran as it should. I’ll try saving the world a bit this weekend and test the stability over a period longer than a couple hours and report back.
I probably should have figured this out, but I’d forgotten that HDMI had the bandwidth for sound, too. Alas, the technology once again is outrunning my (limited) knowledge!!
I know absolutely nothing about it, but I suspect the sound card driver for my sound card shown on the BSOD was flagged as it was competing with the HDMI driver, and the HDMI driver must have had a higher priority. Once again, keep in mind that I’m going out on a limb and know nothing about it in reality…just a WAG.
Thank you again to all you gents for your time, assistance, and patience. I’ll be sure to report back and close the loop.
Warmest regards,
Rob -
If speakers by HDMI do something, it’s in your interest to analyze it.
Still, worst case it can turn out is breaking the jack or ADSP itself. In the former case, you got a spare jack in front of the PC.
-
Good afternoon, All,
Sorry for the delay. After a while, the BSOD returned, and still identified the driver for the Asus sound card. I finally removed the card and all it’s drivers and went into the bios and turned on the on board sound. Now, after 3 days and many hours, there are no more BSOD. It appears to be a problem only with Falcon and the card since every other use of the sound card (CD, DVD, iTunes, Strike Fighters 2, etc.) never had a problem. Only Falcon BMS.
On board sound is not nearly as good for the music and movies, but it’s OK for the game.
Thanks again to all for your help, input, and patience. I wouldn’t have got as far as I did without your assistance.
Warmest regards,
Rob -
Same story I had with a Creative Sound Blaster EX did the same thing looooong time ago.