This week, when I remove my usb memory or if I undock the computer I received a blues screen with the error: MULTIPLE_IRP_COMPLETE_REQUEST Stop 0x00000044 (0x8…….).This only happened when the computer has more than 2 hours turned on. When I turn on the computer I don’t have the above problems. I have a Dell Latitude with Windows XP SP3.The last thing I installed was the blackberry desktop manager two weeks ago.I already updated the main drivers for the computer included the bios and I still receiving the blue screen.What would it be the problem? If is it a driver, how can I know which one is it?Thank you2 people need an answerI do too

Can you upload the contents of c:\windows\minidump to SkyDrive and provide a link?Consider the following general guidance for dealing bluescreens. Consider running chkdsk on all partitions. Let chkdsk complete on each partition and see if that helps.Also consider running SFC /SCANNOW.If you boot into safe mode, do you still experience bugchecks? What about if you do a clean boot, or device clean boot?Consider testing memory with Windows Memory Diagnostic or memtest86. Note that memory that passes tests is not necessarily good memory - it just hasn't failed a test. Consider systematically eliminating RAM from the system - run with a couple of modules for a while, and see how things go. Then try the other modules.Other common suggestions include ensuring drivers are up to date, as well as ensuring that you're using the latest BIOS. It can be helpful to use Driver Verifier. To enable Driver Verifier... start->verifier.exe->OK->Create standard settings->Next->select driver names from a list->Next->sort by Provider->select all non-Microsoft drivers->Finish, and OK your way out of the dialog.Then, reboot and use the system as you normally would, and wait for a problem. In the event that the system does not boot completely after enabling driver verifier, boot into Safe Mode and run driver verifier, and tell it to delete the changes.Wait for a bugcheck to occur after enabling verifier as described, and then upload the dump to your SkyDrive, and provide a link.

Thank you for you helpI uploades dump files at this link:http://cid-df87a33df48fb017.skydrive.live.com/browse.aspx/Dump%20FilesI already updated my computer drivers, and run the SFC /scannow.Regards

oz776.sys is implicated in all of the dumps. This seems to be the driver for a "O2Micro USB CCID SmartCard Reader". Check for and install driver updates for this piece of hardware.

I’ve updated this driver and now I received a different stop error:IRQL_NOT_LESS_OR_EQUAL Stop: 0x0000000AThank you

Can you upload the new dump file?It may be that the latest driver is not "good enough". But let's see what the dump says. How many of the "new" bugchecks have you had?

Right now I don’t have access to skydrive, but this is the content of the last dump file:----- 32 bit Kernel Mini Dump AnalysisDUMP_HEADER32:MajorVersion 0000000fMinorVersion 00000a28DirectoryTableBase 0b5800a0PfnDataBase 81c86000PsLoadedModuleList 8055d720PsActiveProcessHead 805638b8MachineImageType 0000014cNumberProcessors 00000002BugCheckCode 1000000aBugCheckParameter1 3a6e6f7dBugCheckParameter2 00000002BugCheckParameter3 00000000BugCheckParameter4 804f1600PaeEnabled 00000001KdDebuggerDataBlock 8054d2e0MiniDumpFields 00000dff TRIAGE_DUMP32:ServicePackBuild 00000300 SizeOfDump 00010000ValidOffset 0000fffc ContextOffset 00000320 ExceptionOffset 000007d0 MmOffset 00001068UnloadedDriversOffset 000010a0 PrcbOffset 00001878ProcessOffset 000024c8 ThreadOffset 00002728 CallStackOffset 00002980 SizeOfCallStack 00000484 DriverListOffset 00003098 DriverCount 000000a8 StringPoolOffset 00006278 StringPoolSize 00001780 BrokenDriverOffset 00000000 TriageOptions 00000041 TopOfStack a84bfb7cDebuggerDataOffset 00002e08 DebuggerDataSize 00000290 DataBlocksOffset 000079f8 DataBlocksCount 00000004 Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatibleKernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720Debug session time: Thu May 27 18:33:06 2010System Uptime: 0 days 7:41:10 start end module name804d7000 806e4000 nt Checksum: 001FB4F1 Timestamp: Tue Feb 16 07:25:00 2010 (4B7A9CAC)Unloaded modules:ba448000 ba44f000 USBSTOR.SYS Timestamp: unavailable (00000000)a58ab000 a58d6000 kmixer.sys Timestamp: unavailable (00000000)a58ab000 a58d6000 kmixer.sys Timestamp: unavailable (00000000)a58ab000 a58d6000 kmixer.sys Timestamp: unavailable (00000000)a58ab000 a58d6000 kmixer.sys Timestamp: unavailable (00000000)a58ab000 a58d6000 kmixer.sys Timestamp: unavailable (00000000)a58ab000 a58d6000 kmixer.sys Timestamp: unavailable (00000000)a5b56000 a5b81000 kmixer.sys Timestamp: unavailable (00000000)a5b56000 a5b81000 kmixer.sys Timestamp: unavailable (00000000)a5b56000 a5b81000 kmixer.sys Timestamp: unavailable (00000000)a5cc1000 a5cec000 kmixer.sys Timestamp: unavailable (00000000)a7958000 a7983000 kmixer.sys Timestamp: unavailable (00000000)ba6ab000 ba6ac000 drmkaud.sys Timestamp: unavailable (00000000)a7a4b000 a7a6e000 aec.sys Timestamp: unavailable (00000000)a7d5a000 a7d67000 DMusic.sys Timestamp: unavailable (00000000)a7d8a000 a7d98000 swmidi.sys Timestamp: unavailable (00000000)ba650000 ba652000 splitter.sys Timestamp: unavailable (00000000)ba148000 ba151000 processr.sys Timestamp: unavailable (00000000)b9248000 b924c000 kbdhid.sys Timestamp: unavailable (00000000)ba498000 ba49d000 Cdaudio.SYS Timestamp: unavailable (00000000)b93e5000 b93e8000 Sfloppy.SYS Timestamp: unavailable (00000000)Finished dump check

Please upload the dump file when you get a chance.

I already uploaded the dump files in Skydrive.http://cid-df87a33df48fb017.skydrive.live.com/browse.aspx/Dump%20Files?uc=2Thank you for your help

The new one (Mini052810-01.dmp) wasn't there when I checked last.The driver oz776.sys from December 2007 is implicated in this latest bugcheck. It seems the driver still has some problems. If you're using the latest driver, then you would want to contact O2Micro about the problem. If you don't use the smartcard reader, you could disable it.

I checked with a coworker that has the same Dell computer the version of the oz776 driver, and he has an older version and he doesn’t have the problem that I have.When I was updating the dell drivers I saw another problem, the IE8 blocked the java app. of the auto detect computer model of Dell, it says: “To help protect your computer, Windows has closed this program”. This happened with others website too.I uncheck "Enable memory protection to help mitigate online attacks" option on the security of the IE8 and the problem was corrected, but also after that change the computer does not present a blue screen any more when I undock or use my usb memory. Do you know what is the relation of that option in IE8 and the blue screen errors that I had before?Thank you

There are many variables that can come into play to trigger a bug in a driver. Other drivers, the way the system is used, the hardware, firmware/BIOS revisions, etc. all play into it. In your case, each bugcheck clearly implicated oz776.sys as the faulting driver.Disabling DEP/NX (for IE8) as you described would not seem to have any direct relation to the disappearance of the problem, but it may be that it is changing the code path enough such that the bug is not triggered at some later time.Bugchecks / BSODs are caused by faulty hardware or buggy/incompatible drivers, not user-mode programs like Internet Explorer or a web browser.Do note that by disabling DEP for IE, you've turned off a defense-in-depth measure; a better option would be to use components/add-ons/plugins that don't violate the DEP protections. Perhaps a Java update would take care of the problem with the java app you encountered the problem with.I suppose, that re-enabling DEP for IE will cause the bluescreens to return? Have you tried this?

I've activated again the Enable memory protection to help mitigate online attacks in the IE8, and it works ok for a while. Then the Bugchecks come agian.I've activated the driver verifier again, but this time with the all drivers option. After restart the computer and ask for the user/password, the computer goes to blue screen with this message:IO SYSTEM VERIFICATION ERROR IN Wmiacpi.sys (WDM driver error 20e)Thank you for your help.

Este es el error del dump fileLoading User SymbolsLoading unloaded module list............******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck C9, {20e, b9c6052f, 895475f8, 0}Unable to load image wmiacpi.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for wmiacpi.sysUnable to load image WMILIB.SYS, Win32 error 0n2*** WARNING: Unable to verify timestamp for WMILIB.SYSProbably caused by : wmiacpi.sys ( wmiacpi!WmiAcpiFunctionControl+4f )

Bugcheck 0x20e is a non-fatal error meaning "A PNP IRP has an invalid status". You got the bugcheck because you ran verifier on all drivers. Disable verifier on the WMI drivers.What are the details of wmiacpi.sys?

This is the detail******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)The IO manager has caught a misbehaving driver.Arguments:Arg1: 0000020e, A PNP IRP has an invalid status. Any PNP IRP must have its status initialized to STATUS_NOT_SUPPORTED.Arg2: b9c6052f, The address in the driver's code where the error was detected.Arg3: 895475f8, IRP address.Arg4: 00000000Debugging Details:------------------BUGCHECK_STR: 0xc9_20eDRIVER_VERIFIER_IO_VIOLATION_TYPE: 20eFAULTING_IP: wmiacpi!WmiAcpiFunctionControl+4fb9c6052f 8bd8 mov ebx,eaxFOLLOWUP_IP: wmiacpi!WmiAcpiFunctionControl+4fb9c6052f 8bd8 mov ebx,eaxIRP_ADDRESS: 895475f8DEVICE_OBJECT: 00000000CUSTOMER_CRASH_COUNT: 3DEFAULT_BUCKET_ID: DRIVER_FAULTPROCESS_NAME: wmiprvse.exeLAST_CONTROL_TRANSFER: from 80661e0b to 804f9f43STACK_TEXT: a13331e8 80661e0b 0000004c 000000c9 a1333208 nt!_woutput+0x414a1333370 80662571 a133364b 80691090 00040000 nt!KiAmdK6HandleWcRegionRequest+0xe4a1333614 80662657 80695630 0000020e a1333640 nt!MmAddPhysicalMemoryEx+0x277a1333704 80663776 0000020e 00000009 b9c6052f nt!MmAddPhysicalMemoryEx+0x35da1333730 8066169b 00000000 8954768c 87f9d0d0 nt!MiResetVirtualMemory+0xafa1333754 80665f64 00000000 8954768c 87f9d0d0 nt!KiCompleteEffectiveRangeChange+0x1b6a13337b4 80658116 00f23d00 8a8a6e64 895475f8 nt!PopWriteHiberPages+0x269a13337dc b9c5f836 98194fc0 8a8a6e30 00000000 nt!HvRefreshHive+0x4bea13337f4 b9c6052f 8a8a6e30 8a955a18 b9c604e0 wmiacpi!WmiAcpiGetAcpiInterfaces+0x8ea1333810 ba5aa9a3 8a8a6d78 89552008 00000002 wmiacpi!WmiAcpiFunctionControl+0x4fa1333880 b9c5ffae 00000002 8a8a6d78 89552008 WMILIB!WmiSystemControl+0x3dba13338a4 804ef19f 00000000 89552008 806e6428 wmiacpi!WmiAcpiSystemControlDispatch+0x20a13338d8 80604acc a1333958 89552008 a1333a9c nt!MiFlushSectionInternal+0x256a1333904 80604b95 89552008 c357e404 8a8a6d03 nt!WmipQueryLogger+0x25da1333930 8060209a c357e404 8a8a6d78 a1333ab4 nt!WmipQueryLogger+0x319a1333960 806022a8 c357e404 e1a94850 a1333a9c nt!SepAccessCheckAndAuditAlarm+0x736a1333ae0 806023e9 c357e404 e1abf204 00000001 nt!NtOpenObjectAuditAlarm+0x337a1333b0c 80602638 e1abf204 00000004 e1abf200 nt!NtCloseObjectAuditAlarm+0xf4a1333b3c 8060647a e1abf200 00224140 87f5bfc0 nt!SeObjectReferenceAuditAlarm+0x55a1333b64 806054e7 00224140 00000001 00000000 nt!WmipQueryWmiDataBlock+0x42a1333c1c 804ef19f 8a9bf030 91d72e00 806e6428 nt!WmipTranslateFileHandle+0x1baa1333c50 8057f982 91d72fd8 89422480 91d72e00 nt!MiFlushSectionInternal+0x256a1333c64 805807f7 8a9bf030 91d72e00 89422480 nt!ObQueryNameString+0x5aba1333d00 80579274 0000024c 00000160 00000000 nt!NtSetInformationThread+0x125a1333d34 8054163c 0000024c 00000160 00000000 nt!SepOpenTokenOfThread+0x87a1333d64 7c90e514 badb0d00 00c4f0e8 00000000 nt!RtlIpv4StringToAddressExW+0xbdWARNING: Frame IP not in any known module. Following frames may be wrong.a1333d78 00000000 00000000 00000000 00000000 0x7c90e514STACK_COMMAND: kbSYMBOL_STACK_INDEX: 9SYMBOL_NAME: wmiacpi!WmiAcpiFunctionControl+4fFOLLOWUP_NAME: MachineOwnerMODULE_NAME: wmiacpiIMAGE_NAME: wmiacpi.sysDEBUG_FLR_IMAGE_TIMESTAMP: 480252b5FAILURE_BUCKET_ID: 0xc9_20e_wmiacpi!WmiAcpiFunctionControl+4fBUCKET_ID: 0xc9_20e_wmiacpi!WmiAcpiFunctionControl+4fFollowup: MachineOwnerThank you

Was more curious about the file attributes of wmiacpi.sys. The bugcheck can be ignored since you were verifying the driver. It was a non-fatal error.

I've started the driver verifier with the non-microsoft drivers, but in this way I cannot reproduce the bugcheck. I undock the computer several times and there is no error.Why do you thing that the bugcheck cannot be reproduced with the driver verifier on?Thank you,Regards

The original bugchecks you were getting were 0x00000044 (MULTIPLE_IRP_COMPLETE_REQUESTS). The latest bugcheck was a verifier bugcheck. The documentation for that bugcheck in that context indicates that it is a non-fatal problem. The system only bugchecked because specific verifier tests were enabled for that module, and the non-fatal error was trapped. If you can't reproduce the 0x00000044 bugcheck under normal usage or the previous conditions that could cause thebugceck, then there would not seem to be a problem?

No, without the driver verifier I can reproduce the 0x44 bugcheck and this is the last dump file from today again with the oz776.sys driver that I had changed many times:******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 44, {8676b008, d64, 0, 0}*** WARNING: Unable to verify timestamp for usbhub.sysUnable to load image oz776.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for oz776.sys*** ERROR: Module load completed but symbols could not be loaded for oz776.sysProbably caused by : oz776.sys ( oz776+2678 )MULTIPLE_IRP_COMPLETE_REQUESTS (44)A driver has requested that an IRP be completed (IoCompleteRequest()), butthe packet has already been completed. This is a tough bug to find becausethe easiest case, a driver actually attempted to complete its own packettwice, is generally not what happened. Rather, two separate drivers eachbelieve that they own the packet, and each attempts to complete it. Thefirst actually works, and the second fails. Tracking down which driversin the system actually did this is difficult, generally because the trailsof the first driver have been covered by the second. However, the driverstack for the current request can be found by examining the DeviceObjectfields in each of the stack locations.Arguments:Arg1: 8676b008, Address of the IRPArg2: 00000d64Arg3: 00000000Arg4: 00000000Debugging Details:------------------IRP_ADDRESS: 8676b008CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0x44PROCESS_NAME: SystemLAST_CONTROL_TRANSFER: from 804f18ec to 804f9f43STACK_TEXT: ba4ff9a0 804f18ec 00000044 8676b008 00000d64 nt!_woutput+0x414ba4ff9d8 ba23e99e 881010e8 8676b008 866163d8 nt!ExpLuidIncrement+0x12cba4ff9ec 804f1605 8ade7de8 8676b008 881010e8 usbhub!USBH_PortIdleNotificationCancelRoutine+0xa2ba4ffa04 ba2aa678 8676b008 866164b4 ba4ffa2c nt!KeStackAttachProcess+0x46WARNING: Stack unwind information not available. Following frames may be wrong.ba4ffa10 ba4ffa2c ba2b25a7 881010e8 866164d8 oz776+0x2678ba4ffa14 ba2b25a7 881010e8 866164d8 8ae9e900 0xba4ffa2cba4ffa2c 804ef19f 00000007 866163d8 ba4ffaac oz776+0xa5a7ba4ffa68 804f6de7 88101030 ba4ffa88 8ae3fde8 nt!MiFlushSectionInternal+0x256ba4ffab0 8058ee79 00000000 8ade7de8 00000001 nt!FsRtlRemoveMcbEntryPrivate+0x68ba4ffac8 805922db 8ae3fd08 00000001 86b9a6b8 nt!MiProtectVirtualMemory+0x249ba4ffd20 8059271a 8b1421b0 00000001 00000000 nt!FsRtlAddToTunnelCache+0x182ba4ffd54 804f6981 00000003 8055b5c0 8056485c nt!RtlGenerate8dot3Name+0x56ba4ffd7c 80538789 00000000 00000000 8b1268b8 nt!RtlDeleteElementGenericTableAvl+0x35ba4ffdac 805cff62 00000000 00000000 00000000 nt!MiTrimPte+0x20aba4ffddc 8054611e 8053869a 00000001 00000000 nt!IopQueryReconfiguration+0x15ba4ffdf8 00000000 ba4feeb0 00000010 00001f80 nt!ExpRemovePoolTracker+0xabSTACK_COMMAND: kbFOLLOWUP_IP: oz776+2678ba2aa678 ?? ???SYMBOL_STACK_INDEX: 4SYMBOL_NAME: oz776+2678FOLLOWUP_NAME: MachineOwnerMODULE_NAME: oz776IMAGE_NAME: oz776.sysDEBUG_FLR_IMAGE_TIMESTAMP: 45bff2ccFAILURE_BUCKET_ID: 0x44_oz776+2678BUCKET_ID: 0x44_oz776+2678 What else can I do?THANK YOU FOR YOUR HELP

What version of the driver is that from? You indicated with the new driver, you were now getting stop code 0xa / 0x1000000a - IRQL_NOT_LESS_OR_EQUAL.Looking at a previous 0x44 bugcheck - !irp on the IRP address indicates that the thing at that location is probably not an IRP. This would perhaps suggest some kind of corruption. Looking at the part of pool associated with that address, it seems to be associated with tag NDCM. Tag NDCM is associated with some Symantec product; you appear to have such a product installed.So, to test the issue, you could uninstall the Symantec software on your system, to see if it may be contributing to the behavior. (Don't just disable the software - uninstall it, to remove the drivers from the Symantec product.)But ultimately, the 0xa bugcheck pretty clearly flags the oz776.sys driver as the culprit; seeing that driver also flagged in the 0x44 bugcheck would seem to add further evidence against it. However, if you wish to try something other than not using the SmartCard reader or letting the party responsible for the driver know about the problem, you could try the aforementioned suggestion regarding the Symantec software.

I already uninstall symantec antivirus and symanec firewall and the 0x44 bugcheck is still present.What else do you recomend?Thank you for your help

Another question, I’ve installed the Blackberry Desktop Manager one week before the bugcheck started.Do you think that maybe this software (BB) could be the problem? Thank you

Sorry - Alerts apparently weren't working (I'm still not getting all of them).Do you have dumps from the bugchecks, with the Symantec software removed?Does the BBDM software include drivers? If so, the possibility does exist that it could be involved, but nothing in any of the dumps indicates that software is involved (nothing indicates that it's not involved either). You could of course uninstall it to test the behavior. I assume the coworker does not have this software installed?

Hello,Yes he has BBDM installed in his computer.This is the last dump file from the bugcheck without symantec software:******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 44, {87488008, 1bc0, 0, 0}*** WARNING: Unable to verify timestamp for usbhub.sysUnable to load image oz776.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for oz776.sys*** ERROR: Module load completed but symbols could not be loaded for oz776.sysProbably caused by : oz776.sys ( oz776+2b16 )Followup: MachineOwner---------1: kd> !analize -vNo export analize found1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************MULTIPLE_IRP_COMPLETE_REQUESTS (44)A driver has requested that an IRP be completed (IoCompleteRequest()), butthe packet has already been completed. This is a tough bug to find becausethe easiest case, a driver actually attempted to complete its own packettwice, is generally not what happened. Rather, two separate drivers eachbelieve that they own the packet, and each attempts to complete it. Thefirst actually works, and the second fails. Tracking down which driversin the system actually did this is difficult, generally because the trailsof the first driver have been covered by the second. However, the driverstack for the current request can be found by examining the DeviceObjectfields in each of the stack locations.Arguments:Arg1: 87488008, Address of the IRPArg2: 00001bc0Arg3: 00000000Arg4: 00000000Debugging Details:------------------IRP_ADDRESS: 87488008CUSTOMER_CRASH_COUNT: 1DEFAULT_BUCKET_ID: DRIVER_FAULTBUGCHECK_STR: 0x44PROCESS_NAME: SystemLAST_CONTROL_TRANSFER: from 804ef4d4 to 804f9f43STACK_TEXT: ba503998 804ef4d4 00000044 87488008 00001bc0 nt!_woutput+0x414ba5039c0 ba24e3fd 87488008 ba5039e8 ba24e948 nt!CcGetVirtualAddressIfMapped+0x1ba5039cc ba24e948 8ad9bb90 87488008 880940e8 usbhub!USBH_HubCancelIdleIrp+0x2dba5039e8 804f1605 8ac55de8 876375d8 880940e8 usbhub!USBH_PortIdleNotificationCancelRoutine+0x4cba503a00 ba30ab16 876375d8 874f935c 874f9280 nt!KeStackAttachProcess+0x46WARNING: Stack unwind information not available. Following frames may be wrong.ba503a14 ba31398d 000940e8 874f9380 8adced78 oz776+0x2b16ba503a2c 804ef19f 00000007 874f9280 ba503aac oz776+0xb98dba503a68 804f6de7 88094030 ba503a88 8ac51fc8 nt!MiFlushSectionInternal+0x256ba503ab0 8058ee79 00000000 8ac55de8 00000001 nt!FsRtlRemoveMcbEntryPrivate+0x68ba503ac8 805922db 8ac51ee8 00000001 8aee6e80 nt!MiProtectVirtualMemory+0x249ba503d20 8059271a 8b10a168 00000001 00000000 nt!FsRtlAddToTunnelCache+0x182ba503d54 804f6981 00000003 8055b5c0 8056485c nt!RtlGenerate8dot3Name+0x56ba503d7c 80538789 00000000 00000000 8b126640 nt!RtlDeleteElementGenericTableAvl+0x35ba503dac 805cff62 00000000 00000000 00000000 nt!MiTrimPte+0x20aba503ddc 8054611e 8053869a 00000001 00000000 nt!IopQueryReconfiguration+0x15ba503df8 00000000 ba502eb0 00000010 00001f80 nt!ExpRemovePoolTracker+0xabSTACK_COMMAND: kbFOLLOWUP_IP: oz776+2b16ba30ab16 ?? ???SYMBOL_STACK_INDEX: 5SYMBOL_NAME: oz776+2b16FOLLOWUP_NAME: MachineOwnerMODULE_NAME: oz776IMAGE_NAME: oz776.sysDEBUG_FLR_IMAGE_TIMESTAMP: 476b05beFAILURE_BUCKET_ID: 0x44_oz776+2b16BUCKET_ID: 0x44_oz776+2b16Followup: MachineOwner---------Thank you,Regards

Can you upload the dump?