First Flight = BSoD

[Snacko]

I just bought, installed and started the free flight quick mission. 2 minutes in I was flying over the mountains, pulled up to a stall. Pushed nose down, throttled up pulling level about 100 feet above the ground when Windows Crashes to the Blue Screen of Death. Arg... :doh:

[amigastar]

Do you have a Saitek stick?

Maybe it's not the games fault, just saying.

[Snacko]

Yes, and x52 & x55, but what's that got to do with it?

[zaelu]

When you have BSOD and you are the only one who has it or most often people does not have it like you do... always blame your own hardware first.

 

If I get a BSoD out of nowhere I always jump scared that something cracked inside my PC. Never ever sleep on the thought that maybe is the new program... immediately check your hardware for imminent failure. BSoD is not what it used to be... is very rare now.

[amigastar]

Yes, and x52 & x55, but what's that got to do with it?

Simple, Saitek x52 is known to be vulnerable to produce BSod, your not the first one to get a Blue Screen and having a Saitek.

 

I don't know if you want my help but if the Blue Screen continues to happen try to erase the SaiH075.sys file from the system32/drivers folder.

[Cobra847]

Navigate to Users/Saved Games/DCS/Logs and zip up the contents there and attach them to a post. They may be helpful in identifying any issue. :)

[Corrigan]

You could also get the stop code from the windows logs.

[Eldur]

Not only the stop code... it also tells the driver dll that caused the BSOD:

 

 

In this example it's ati3diag.dll, which is most probably part of ATi graphics card drivers. Therefore you'll get a nice hint where to look at.

[Devrim]

I used to get BSOD at first days of using X55 (3-4 years ago), but I got that the problem was on my motherboard. Luckily Gigabyte released a new flash version in those days, soon later Saitek released newer driver of X55. Then, all BSOD problems are gone!

 

By the way, Snacko, monitor your CPU or graphics card core temperature. Just saying. :)

[Snacko]

Navigate to Users/Saved Games/DCS/Logs and zip up the contents there and attach them to a post. They may be helpful in identifying any issue. :)

 

Sorry, I just flew one mission with no problems before I read these replies. The logs were overwritten.. but the dcs.log.old is from this morning when I got the error. Let me know if you want that or any other files?

 

I do remember the blue screen having an error related to IRQL which was our of range or something.

 

@ Devrim.. The X55 just came out this year, so I don't know how you had one for 3-4 years?

 

If this happens again I'll try and get more info.

[Devrim]

Sorry, it's a typo, it's X-52.

[silverofx441]

I had a saitek and it caused a large amount of BSOD. I ditched it and never a problem after that.