BSOD - MULTIPLE_IRP_COMPLETE_REQUESTS (0x44)

[martinlest]

Hi. I have had this BSOD twice, today and yesterday, while running Microsoft Flight Simulator 2004 (on my 'gaming' PC, dedicated to MSFS). I have never had a BSOD on this machine before yesterday... I did not install new hardware (or software, as far as I know!).

I have read the instructions on posting here, but can I ask first whether I have to use the DM Log Collector software, or can I just upload the minidump and xml files that I saved?

I have looked at the dmp files with Bluescreenview, which tells me:

MULTIPLE_IRP_COMPLETE_REQUESTS
Caused by driver: (1) rdbss.sys (2) srv2.sys
Caused by address: (1) rdbss.sys+858bf3c (2) srv2.sys+11f3c
Crash Address: (1) ntoskrnl.exe+748c0 (2) ntoskrnl.exe+748c0

.. (1) & (2) being the two BSOD dmp files from today and yesterday (not the same info!). I need to figure out how to use that information...

Many thanks for the help!

Martin

 

[martinlest]

Ok, some more info might tempt a reply!

I have been testing things using Windows 7 verifier.exe.

There are two drivers which seem to cause the BSOD on startup - both from Saitek (my USB X52 'joystick'). When I run verifier.exe with all but these two drivers checked, no BSOD at boot. With either one of these checked, and no others, 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 though??

I downloaded the latest drivers for the X52, deleted the old ones and installed the new - but still I get BSOD when I check them in verifier.

Otherwise, when I open these dmp files (the ones 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!!

I can upload whatever files needed of course...

Thanks again for any help.

 

[axe0]

Just follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html to provide the necessary data

 

[martinlest]

OK, done.

The minidumps I got when running verifier.exe gave very different results from those that just occurred as the PC was running MS Flight Simulator. The minidumps uploaded are the latter - the ones that occurred after an 'unprovoked' BSOD.

Last night I installed KB2552033. I ran the PC & MS FS for 5 hours with no problem, but that could be coincidental of course.

I have enabled full crash dumps on the PC now... is that needed for any future problems?? I gather 0x44 errors are hard to pin down..

Many thanks for your generous help here!

Martin

 

[axe0]

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.

Or configure Ccleaner to not remove dump files:

Diagnostic Test

 DRIVER VERIFIER

   Warning

Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.

Please follow this tutorial to run driver verifier.

Some windows drivers are blamed in a few crashes, but that usually means that a 3rd party driver is actually the cause.
Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.

   Note

Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

[martinlest]

As I say, I have been using driver verifier - I get a BSOD at startup, but with a different error message from those that occur during normal use of the PC.

Shall I just upload the dump files here (zipped) created after a BSOD 'forced' by verifier.exe? Full, or just minidump needed?

Thanks.

 

[axe0]

The dumps in the zip are not caused by verifier.
Have you used Ccleaner, disk cleanup or something that cleans up your system?

 

[martinlest]

No, that is what I was saying. I copied all the dump files from the windows/dumpfile folder to another location: I have so far only sent you the ones created when I got a BSOD while running Flight Simulator. I can either upload the zipped dumpfiles created by verifier, or make some fresh ones.

Do you need only minidumps or full dump files.. the PC is currently set to the latter.

I didn't use CCleaner after the dump files were created I think.

Not sure if having added the hotfix will have changed anything...

Thanks again.

 

[axe0]

Minidumps are enough.

I can't exactly read anywhere else that you are saying you have moved the dumps.

Please upload the dumps you have moved as a zip.

 

[martinlest]

OK, will do. I have one more question though first. As far as I can see, using verifier.exe there are two Microsoft drivers and two 3rd. party drivers which provoke a BSOD at boot. If I check all of those, you will only get information about the first driver to crash the system (no?). Should I not run verifier with just one ticked at each run so that you get four minidumps, one for each suspect driver, or is that not necessary?

Are these repeated BSODs possibly harmful to my hardware BTW?

Thank you.

 

[axe0]

The answer for how we suggest to run driver verifier is in the tutorial: http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html

 

[martinlest]

I have followed the instructions and attach the new zip file.

I asked my question as the tutorial is not 100% explicit - it says ".. select all drivers not provided by Microsoft Corporation", but the screenshot which goes with the instruction (no.6) shows non-Microsoft drivers which have not been ticked. Well, I checked everything that was not labelled as Microsoft for this anyway...

 

[axe0]

The tutorial is 100% explicit, the screenshots just show how you can do it, their function is nothing more then just showing a little bit clearer how to do it.

As sometimes happens with the verifier dumps, no driver is flagged, the reason why driver verifier sometimes needs to run a few times.

 

[martinlest]

No, the pictures follow the words exactly up to there and at that point, one contradicts the other. No big deal of course, but why be so defensive and tell me the tutorial is 100% explicit? I am not complaining, needless to say, I just commented as to why I asked you the question before about what to include!! I am grateful for the help and time you give so freely.

So no drivers flagged.. Hmmm. Should I try again? I haven't had any problems since I installed the hotfix, but it's tempting fate to say so of course!

Martin

 

[axe0]

I wasn't defensive, but explaining, depending on how one interprets it it might be taken in the wrong way.

I wouldn't try verifier again yet, I would test the system first to see if the problem is gone.

 

[martinlest]

OK, I have been running Flight Simulator for hours at a time, but no BSOD.. Not sure why it would have stopped, unless the MS Hotfix worked. Possible I suppose. I'll post back here if there is another. I just wish I knew for certain which drivers were t fault...

Thanks again.

 

[axe0]

The hotfix likely has changed a few things how Windows works what helped with the problem driver(s) working normal

 

[martinlest]

If I have read the data correctly, the hotfix installs a newer version of srv2.sys, which was one of the files cited in the dumpfile as causing the BSOD...

 

[axe0]

srv2.sys: Driver Reference Table - srv2.sys
I'm not sure how big the workaround would have to be to get rid of the bluescreens when a Windows driver was in the middle of it.

I'm very glad you installed that hotfix