Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

Sign in to follow this  

Win 7 freezes/bluescreen with bccode 44

Recommended Posts

Hi everyone,


Yup I am new here, and I need some advice on my Win7 32bit bluescreen issue.


Below is the detail, plus a link to a dumpfile which i know is being asked, everytime someone post a bluescreen issue. 


Appreciate some advice, thanks.



Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.
  Locale ID: 1033

Additional information about the problem:
  BCCode: 44
  BCP1: 88776008
  BCP2: 00000EAE
  BCP3: 00000000
  BCP4: 00000000
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 256_1

Files that help describe the problem:

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:



And link to my dumpfile:-






Share this post

Link to post
Share on other sites

please install all Updates for Win7 Sp1. You still use the Sp1 RTM without any update (7601.17514.x86fre.win7sp1_rtm.101119-1850). Debugging shows Powermanagement operations.

********************************************************************************                                                                             **                        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: 88776008, Address of the IRPArg2: 00000eaeArg3: 00000000Arg4: 00000000Debugging Details:------------------IRP_ADDRESS: 88776008FOLLOWUP_IP: pci!PciBusDevicePowerCompletion+628c315b10 5f              pop     ediCUSTOMER_CRASH_COUNT:  1DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULTBUGCHECK_STR:  0x44PROCESS_NAME:  SystemCURRENT_IRQL:  2ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64freDPC_STACK_BASE:  FFFFFFFF8E921000LAST_CONTROL_TRANSFER:  from 8c315b10 to 82e8fcbdSTACK_TEXT:  8e920e2c 8c315b10 85c7b910 c8bb6d98 8e920e64 nt!IopfCompleteRequest+0x4b08e920e3c 82e2db03 863f4d68 c8bb6d03 00000004 pci!PciBusDevicePowerCompletion+0x628e920e64 82e9aa63 00000000 85c7b910 c8bb6d03 nt!PopRequestCompletion+0x388e920e8c 82e8f933 00000000 85c7b910 889e63d8 nt!IopUnloadSafeCompletion+0x4a8e920ed0 8c2c3573 89f00770 8e920efc 8c2c3425 nt!IopfCompleteRequest+0x1288e920edc 8c2c3425 859eda60 85c7b910 00000000 ACPI!ACPIDeviceIrpCompleteRequest+0x278e920efc 8c2c3777 89f00770 8c2e3bb8 8c2e3b98 ACPI!ACPIDeviceCompleteRequest+0x938e920f20 8c2c3ba6 8c2e3b78 8c2e1a6c 00000001 ACPI!ACPIDevicePowerProcessGenericPhase+0x718e920f48 82e8f1b5 8c2e3b40 00000000 00000000 ACPI!ACPIDevicePowerDpc+0x1848e920fa4 82e8f018 8e900120 85a7baf0 00000000 nt!KiExecuteAllDpcs+0xf98e920ff4 82e8e7dc 8eb49b54 00000000 00000000 nt!KiRetireDpcList+0xd58e920ff8 8eb49b54 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2cWARNING: Frame IP not in any known module. Following frames may be wrong.82e8e7dc 00000000 0000001a 00d6850f bb830000 0x8eb49b54STACK_COMMAND:  kbSYMBOL_STACK_INDEX:  1SYMBOL_NAME:  pci!PciBusDevicePowerCompletion+62FOLLOWUP_NAME:  MachineOwnerMODULE_NAME: pciIMAGE_NAME:  pci.sysDEBUG_FLR_IMAGE_TIMESTAMP:  4ce788e5IMAGE_VERSION:  6.1.7601.17514FAILURE_BUCKET_ID:  0x44_pci!PciBusDevicePowerCompletion+62BUCKET_ID:  0x44_pci!PciBusDevicePowerCompletion+62ANALYSIS_SOURCE:  KMFAILURE_ID_HASH_STRING:  km:0x44_pci!pcibusdevicepowercompletion+62

Share this post

Link to post
Share on other sites

Thanks for the replies.


This happens once while I was logging off. Another time was while opening IE.


I will proceed with the windows updates and see whether there is an improvement. I didnt realise I was using the SP1 RTM version. May take me a few days to verify.


Thanks again.

Share this post

Link to post
Share on other sites

Yup all is well. After the Windows update, the freezes/bluescreen were cured! :-)


Thanks to MagicAndre1981 for your time and advice.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.