Good Day,

I'm receiving the following error:

Problem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.1.7601.2.1.0.256.48
  Locale ID: 1033

Additional information about the problem:
  BCCode: 9f
  BCP1: 0000000000000003
  BCP2: FFFFFA8007605A00
  BCP3: FFFFF800108074D8
  BCP4: FFFFFA8008039210
  OS Version: 6_1_7601
  Service Pack: 1_0
  Product: 256_1

This started after a rebuild of the HP Computer, we have confirmed that it is not fixed by any available KBs that we have found relating to BCCode: 9f. Your assistance would be greatly apprecited.

The dump link will be added once my account is verified or look below. :)

Many thanks,

Tony Morton

tmorton@slpipe.com

<a href="https://onedrive.live.com/redir?resid=5a11f99140b9e440!108&authkey=!AK7U7e6FocfDIl8&ithint=folder%2cxml"></a></p

• Edited by Tony Morton Sr Monday, April 06, 2015 6:32 PM

I believe 9f is driver power state failure. That means a driver is in an inconsistent or invalid power state.  I will take a look at your minidump shortly.

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8007605a00, fffff800108074d8, fffffa8008039210}

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

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8007605a00, Physical Device Object of the stack
Arg3: fffff800108074d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8008039210, The blocked IRP

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

DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa8006b92040

DRIVER_OBJECT: fffffa8007609060

IMAGE_NAME:  HPM1210FAX.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bb2cd00

MODULE_NAME: HPM1210FAX

FAULTING_MODULE: fffff880075a2000 HPM1210FAX

IRP_ADDRESS:  fffffa8008039210

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF8001080DFB0

STACK_TEXT: 
fffff800`10807488 fffff800`10101b92 : 00000000`0000009f 00000000`00000003 fffffa80`07605a00 fffff800`108074d8 : nt!KeBugCheckEx
fffff800`10807490 fffff800`1009ccfc : fffff800`108075c0 fffff800`108075c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`10807530 fffff800`1009cb96 : fffff800`10243140 00000000`000a7ff3 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`108075a0 fffff800`1009ca7e : 00000018`fe5d0330 fffff800`10807c18 00000000`000a7ff3 fffff800`102120e8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`10807bf0 fffff800`1009c867 : 00000006`d1a34bc1 00000006`000a7ff3 00000006`d1a34bbe 00000000`000000f3 : nt!KiTimerExpiration+0x1be
fffff800`10807c90 fffff800`10088bca : fffff800`1020de80 fffff800`1021bcc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`10807d40 00000000`00000000 : fffff800`10808000 fffff800`10802000 fffff800`10807d00 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_HPM1210FAX.sys

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_HPM1210FAX.sys

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

0: kd> lmvm HPM1210FAX
start             end                 module name
fffff880`075a2000 fffff880`075ac000   HPM1210FAX T (no symbols)          
    Loaded symbol image file: HPM1210FAX.sys
    Image path: HPM1210FAX.sys
    Image name: HPM1210FAX.sys
    Timestamp:        Tue Mar 30 21:18:08 2010 (4BB2CD00)
    CheckSum:         0000D06D
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

looks like its pointing to HP1210FAX.SYS. Do you have an hp fax machine connected to your computer

• Edited by aw00tMicrosoft employee Tuesday, April 07, 2015 1:28 AM

Yes, there is a HP MFP attached, and the Fax side is used often for both incoming and outgoing Faxes.

The printer model is a M1212nf MFP, and the primary driver name is hpm1210sd.dll. I can upload the printer test page if that will help.

• Edited by Tony Morton Sr Tuesday, April 07, 2015 1:32 PM

I would start by removing the HP software/drivers and reinstalling with an updated version.

Any update on this?

I've taken another look at the users computer, and during my conversation with the end user discovered that it was possible that the BSOD occurred within a short time of them receiving a Fax. They stated that the problem started around the same time that they first started getting a popup about reciving a Fax, they did not know why this popup started. Since the printer is sitting next to them they did not require the popup, so I disabled notification within the HP driver.

So far they have received multiple Faxes, and no longer get a notification popup, and neither has there been a BSOD reoccurrence.

I have decided to give this fix a try first, and if no other BSODs occur, then we'll call it good. However, if another BSOD occurs we will remove all the HP Drivers (Multiple HP Printers are installed) and reinstall those required, with the latest set of HP drivers.

Thank you for pointing us in this direction, hopefully this will resolve the issue.

• Edited by Tony Morton Sr 13 hours 38 minutes ago

sounds good. Let me know