Solved Dell Inspiron mini BSOD Multiple IRP

[tonynascar]

Wife is getting sporadic BSOD on this device but system reboots and her comments was "it just stopped".
I finally caught it and saw the Multiple IRP... error. Many searches later led me to this site where I see good results with what appears to be a conflicting resource issue that isn't always cut and dry...so I have uploaded my files into your capable hands! Thanks!
Tony

 

[Arc]

Your crash dumps are not showing any finite probable cause. In such a situation, it is better to enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
___________________________________________________________________________________________

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 44, {fffffa8001b7f5d0, eae, 0, 0}

Probably caused by : bowser.sys ( bowser!BowserCancelQueuedIoForFile+112 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

MULTIPLE_IRP_COMPLETE_REQUESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed.  This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened.  Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it.  The
first actually works, and the second fails.  Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second.  However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: fffffa8001b7f5d0, Address of the IRP
Arg2: 0000000000000eae
Arg3: 0000000000000000
Arg4: 0000000000000000

Debugging Details:
------------------


IRP_ADDRESS:  fffffa8001b7f5d0

FOLLOWUP_IP: 
bowser!BowserCancelQueuedIoForFile+112
fffff880`0303c732 488b4c2420      mov     rcx,qword ptr [rsp+20h]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x44

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80001a6a8c0 to fffff80001a81bc0

STACK_TEXT:  
fffff880`1409d858 fffff800`01a6a8c0 : 00000000`00000044 fffffa80`01b7f5d0 00000000`00000eae 00000000`00000000 : nt!KeBugCheckEx
fffff880`1409d860 fffff880`0303c732 : fffffa80`010de710 fffff8a0`00dbe6a0 fffffa80`023564b0 fffffa80`010deac8 : nt! ?? ::FNODOBFM::`string'+0x413f2
fffff880`1409d950 fffff880`030378e8 : fffffa80`010de710 fffffa80`0318ec50 fffff880`03037890 fffffa80`010de710 : bowser!BowserCancelQueuedIoForFile+0x112
fffff880`1409d990 fffff880`03031cd3 : fffff8a0`0a2ed610 fffff8a0`00dbe6a0 fffff8a0`0a2ed610 fffffa80`0318ec50 : bowser!BowserCancelRequestsOnTransport+0x58
fffff880`1409d9c0 fffff880`030260de : fffffa80`022c9010 fffffa80`02957aa0 fffffa80`0318ec50 00000000`00000000 : bowser!BowserForEachTransport+0x6f
fffff880`1409da00 fffff800`01d8a96f : fffffa80`022c9010 00000000`00000000 00000000`00000000 fffffa80`023564b0 : bowser!BowserFsdDispatch+0x56
fffff880`1409da30 fffff800`01d78964 : 00000000`00000000 fffffa80`02957aa0 00000000`00000c84 fffffa80`023564b0 : nt!IopCloseFile+0x11f
fffff880`1409dac0 fffff800`01d78721 : fffffa80`02957aa0 fffffa80`00000001 fffff8a0`00dbe6a0 00000000`00000000 : nt!ObpDecrementHandleCount+0xb4
fffff880`1409db40 fffff800`01d78ce4 : 00000000`00000c84 fffffa80`02957aa0 fffff8a0`00dbe6a0 00000000`00000c84 : nt!ObpCloseHandleTableEntry+0xb1
fffff880`1409dbd0 fffff800`01a80e53 : fffffa80`03303840 fffff880`1409dca0 00000000`00000090 fffffa80`0331ba80 : nt!ObpCloseHandle+0x94
fffff880`1409dc20 00000000`76e413aa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`025df4d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76e413aa


STACK_COMMAND:  kb

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  bowser!BowserCancelQueuedIoForFile+112

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: bowser

IMAGE_NAME:  bowser.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d649328

FAILURE_BUCKET_ID:  X64_0x44_bowser!BowserCancelQueuedIoForFile+112

BUCKET_ID:  X64_0x44_bowser!BowserCancelQueuedIoForFile+112

Followup: MachineOwner
---------

 

[tonynascar]

OK, when I booted up this morning I got to the Desktop and went straight to another BSOD (that I couldn't catch much of other than it was a "hard stop"). Re-boot prompted for System Repair which I ran and DID NOT attempt System Restore. FYI - I did not play around with the tool last night and start Driver Verifier as I know better than to play with other people's diagnostic tools.
Windows could not repair but I was able to restart normally and have attached those files. Looks like since the first dump files didn't bring anything up, we're starting over. Thanks again for the help and quick replies.
Tony

 

[Arc]

The latest BSOD is influenced by Realtek audio driver.

BugCheck 1000007E, {ffffffffc0000005, fffff80001bbfa9b, fffff88001fc2248, fffff88001fc1aa0}

*** WARNING: Unable to verify timestamp for [URL="http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys"]RTKVHD64.sys[/URL]
*** ERROR: Module load completed but symbols could not be loaded for [URL="http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys"]RTKVHD64.sys[/URL]
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+1df )

Followup: Pool_corruption
---------

And the driver is very old.

fffff880`0380b000 fffff880`039f9f00   RTKVHD64 T (no symbols)           
    Loaded symbol image file: RTKVHD64.sys
    Image path: \SystemRoot\system32\drivers\RTKVHD64.sys
[COLOR=Red]    Image name: RTKVHD64.sys
    Timestamp:        Tue Nov 10 17:45:36 2009[/COLOR] (4AF95968)
    CheckSum:         001F1E91
    ImageSize:        001EEF00
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Download and install High Definition Audio Codecs from Realtek .

 

[tonynascar]

OK, I downloaded and installed the Realtek driver, all went well and sound is working...BUT when I launched Firefox to post a reply, I got another BSOD with a STOP.
1. I re-booted Windows normal and got the same STOP error right after the Desktop loaded.
2. Tried Safe Mode with Networking and got the same STOP error right after the Desktop loaded.
3. Able to get in on Safe Mode only so I ran the tool and copied files off to a flash drive.

So attached is Round 3 of our little adventure!
Update-based on the 0x0000001e error, I ran Disk Check with no errors found
Thanks!
Tony

 

[Arc]

These new BSODs are caused by Dell Wireless 1535 Wireless-N Adapter
(Driver => c:\windows\system32\drivers\athrx.sys)

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {0, 0, 0, 0}

*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys

[COLOR=Red][B]Probably caused by : athrx.sys[/B][/COLOR] ( athrx+369ee )

And the driver is very old.

fffff880`0283f000 fffff880`029bc000   athrx    T (no symbols)           
    Loaded symbol image file: athrx.sys
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
[COLOR=Red]    Image name: athrx.sys
    Timestamp:        Sat Oct 24 07:19:44 2009[/COLOR] (4AE25D38)
    CheckSum:         0017F4D3
    ImageSize:        0017D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Update the driver from Dell: Product Selection | Dell US

Let us know the results.

 

[tonynascar]

Sorry so long in responding...work and life got in the way! I could find nothing on the Dell site using my service tag specifically for the Dell Wireless 1535 Wireless-N Adapter that applies to WIN7 64BIT ALIENWARE (some 32 bit drivers that wouldn't even install). I did finally find a driver on the driversforfree website that noted the Dell number which I downloaded from Dell and it blew up during install so I ended up going back to a Restore Point I made just prior to trying it (as is my normal process for driver installs).

Consistently kept keeping 0x000001E and 0x000007E afterward on both Normal and Safe Mode (w/Networking) so I tried Safe Mode and ran sfc /scannow and it didn't find anything. Went to Device Manager to check the Wireless-N Adapter to ensure it was back and enabled AND noticed an "Unknown Device" I had been overlooking (no Yellow Exclamation point). I disabled it and am now typing this reply in IE from a normal boot up. Not sure what this will mean for you, but here are the details:
Hardware Ids - ACPI\CPL0002
*CPL0002
Physical Device Object Name - \Device\00000046
Capabilities - 00000020
CM_DEVCAP_SILENTINSTALL
Base Container ID - {00000000-0000-0000-ffff-ffffffffffff}
Device Instance Path - ACPI\CPL0002\2&DABA3FF&2
Parent - ACPI_HAL\PNP0C08\0
Siblings -
ACPI\GenuineIntel_-_Intel64_Family_6_Model_28_-__________Intel(R)_Atom(TM)_CPU_N450___@_1.66GHz\_0
ACPI\GenuineIntel_-_Intel64_Family_6_Model_28_-__________Intel(R)_Atom(TM)_CPU_N450___@_1.66GHz\_1
ACPI\PNP0A08\2&daba3ff&2
ACPI\FixedButton\2&daba3ff&2
Class Icon Path - %SystemRoot%\System32\setupapi.dll,-18

Let me know next steps...
Thanks again!
Tony

 

[tonynascar]

OK...I think I have this monster beat down now. I found that the Unknown Device was Alienware On Screen Display and that is fixed. I also finally found a Win 7 x64 driver replacement for athrx.sys and now the Network Adapter is reporting as Atheros AR9285 802.11b/g/n WiFi Adapter instead of the Dell Wireless 1535...go figure. The file is still very old (11/21/2009) but it is working and that is what counts at this point.

The machine ran overnight with no crash and I'm speedtesting at 5MB/800k (which is respectable on my 10MB DSL line with 7 other devices connected on wireless and streaming TV on another PC while testing).
Unless you want to see another set of files, I'm happy and ready to mark this solved.
Tony

 

[Arc]

Well done!!

Anyway, if you anytime want to get a newer driver for Atheros AR9285, have a look at http://www.atheros.cz/atheros-wireless-download.php?chipset=37&system=6 .

 

[SandeepP]

OK...I think I have this monster beat down now. I found that the Unknown Device was Alienware On Screen Display and that is fixed. I also finally found a Win 7 x64 driver replacement for athrx.sys and now the Network Adapter is reporting as Atheros AR9285 802.11b/g/n WiFi Adapter instead of the Dell Wireless 1535...go figure. The file is still very old (11/21/2009) but it is working and that is what counts at this point.

The machine ran overnight with no crash and I'm speedtesting at 5MB/800k (which is respectable on my 10MB DSL line with 7 other devices connected on wireless and streaming TV on another PC while testing).
Unless you want to see another set of files, I'm happy and ready to mark this solved.
Tony

Hi Tony,

You should update the driver from the link suggested by Arc. However, if the BSOD still occurs then you should install the dell driver for diagnosing:

Driver Details | Dell US

Also, ensure the hardware is working fine on the system:

http://dell.to/18xQpRy

Keep us posted with the results so we can advise you further.