Hi. I don't usually fly long-haul but trying to fly from CYVR to PHNL yesterday (in a PSS b777) and from PHNL to RJAA today (PMDG 747) both resulted in a BSOD after about 4 hours. I don't know if anyone here will be able to help? I have never had a BSOD on this PC before (which I use only for FS9 & FSX). I guess it is connected with FS9 in some way, as the PC has been on for several hours dozens of times (if not hundreds) with no problem. On the other hand, this is the first time I have run FS9 or FSX for more than three hours non-stop...

 

I am getting error 0x00000044 - Multiple_IRP_Complete_Requests. I have read the 'blurb' about this, but am only vaguely wiser... I saved the mini-dump file (the PC wasn't able to save the full dump file as I suppose I have not allocated enough resources and the system xml file. I also have a programme called 'AppCrashView', which produced its own file.

 

Event Viewer (Windows Logs/System) just says "The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000044 (0xfffffa800f81f010, 0x0000000000001d8d, 0x0000000000000000, 0x0000000000000000)." and refers to the dmp file I have saved.

 

Any insights, gurus? What more info can I provide? (Oh, Windows 7 x64 !!)

 

I have not installed any new hardware or software recently....

 

Thanks,

 

Martin

A BSOD is caused by a system malfunction.  It is usually a system driver that is at fault.  Run sfc /scannow to look for corrupt or missing files - http://pcsupport.about.com/od/toolsofthetrade/ht/sfc-scannow.htm

 

Best regards,

Good idea - I ran the programme and just one file was repaired (according to the log file at the end) - a jpg file in the wallpaper folder!!

 

I have run Windows Update too, and had 130 fixes installed, so I will see how it goes...

 

Thanks

Definitely bad code in the drivers - not something you can detect in a scan and not easy to track down. Interesting to determine whether you get the same BSOD error code. Do you get it in FSX?

 

https://msdn.microsoft.com/en-us/library/windows/hardware/ff558982(v=vs.85).aspx

 

Of those 130 updates, were any of them drivers?

 

Cheers!
 

Luke

Not sure about FSX as I hardly ever fly it..

 

Yes, I saw that page before I posted here. May be hard to locate the source of the problem, but I'll upload my minidump and xml files (to the WindowsSeven BSOD forum) and see if anyone can advise. There's also the inbuilt verifier feature in Win7 that I could use to stress the drivers, if I have to...

 

I don't think there were any drivers in the updates, apart from a Realtek audio driver (some 120MBs) that always failed to install. I will try and update it manually tomorrow..

 

Will post back here with anything useful.

 

Thanks.

I have been testing things using (the Windows 7 tool) verifier.exe.

 

There are two drivers which seem to cause the BSOD on startup - both from Saitek (my X52). When I run verifier without these two checked (included in the test), no BSOD at boot. With either one of these checked, and no other, immediate BSOD at boot. They are:

 

saibus.sys

saimini.sys

 

Can I confidently conclude that these are the culprits? Maybe it's not so straight forward as that??

 

I downloaded the latest drivers for the X52 from Mad Catz, deleted the old ones and installed the new - but still I get BSOD with them.

 

Otherwise, when I open these dmp files (produced after verifier.exe runs) in BlueScreenView, a different BSOD label is shown from those I got when I was running FS9 - DRIVER_VERIFIER_IOMANAGER_VIOLATION. The faulting driver is always shown as HIDCLASS.SYS..

 

It's very hard to know how to square all this information!!

Are there any newer Saitek drivers available?

 

Cheers!

 

Luke

No, they are exactly the same.. the same as I already had installed too. I have submitted a support ticket...

 

Incidentally, the site..

 

http://www.saitek.com/uk/down/drivers.php'>http://www.saitek.com/uk/down/drivers.php

 

always causes my router to turn off and restart when I start downloading from there. Very odd. It takes several tries before I can get the whole file, waiting for my router (BT Hub3) to reload! Anyone else get a problem downloading from there?

Sounds like your firmware on your router needs to be updated.  The following link might be of assistance - http://lifehacker.com/5910788/why-do-i-have-to-keep-resetting-my-router-and-how-can-i-fix-it?trending_test_two_c&utm_expid=66866090-68.hhyw_lmCRuCTCg0I2RHHtw.3&utm_referrer=https%3A%2F%2Fwww.google.com

 

Best regards,

Thanks for the link! I can always ring BT, but I remember this from getting the drivers before from this site - it's only this website that causes my router to disconnect. I have no problems with any other as far as I remember.

Meanwhile, the BSODs continue... I don't recall having any problems before I ran Windows Update! I wonder if one of the many I allowed to install are causing the problems. My PC is only 3 months old, so the manufacturer is also looking at the problem from my minidump files: so far they have said that the issue seems to be 'linked to the graphics card changing power states'. Not sure where that comes from..

 

When I run verifier.exe, it is always the same Win7 system files that cause the BSOD, if I select them in the check box: Hidclass.sys and Srv2.sys, plus the two Saitek drivers above. But those files have always been there, so why the crashes now?

 

On the other hand, driver verifier can give very misleading results (according to my searches) so I am far better off relying on the PC manufacturer to analyse what is going wrong, I dare say.

 

I did make an image backup of my C drive a few days before the BSOD problem occurred (with Macrium Reflect). If I can't fix this over the next couple of days, I may try restoring the image (always a stressful process!!), which would also remove all the Windows updates... What do you think?