BSOD After cold boot

[DougG]

Hi,
I've been getting intermittent BSODs, typically after a cold boot or after wake-up from hibernation.
Reboot after BSOD (start Windows normally) is typically successful.

Thanks,
DougG

 

[Arc]

So apparently you are having this issue over years.

Some HP bloatware are causing the issue, as the crash dumps report. It is called the HP Mobile Data Protection System Disk Filter.

hpdskflt    HP Filter    c:\windows\system32\drivers\hpdskflt.sys    Kernel Driver    Yes    Boot    Running    OK    Normal    No    Yes

I'd recommend you to http://www.sevenforums.com/tutorials/219576-clean-up-factory-bloatware.html, with a special reference to Point #13

13. Consider a Clean Reinstall - Factory OEM Windows 7 which is often better than getting a new computer considering how pre-installed bloatware can corrupt Windows 7 even if it's completely cleaned up.

Let us know how it went.
____________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa81081b8380, 0, fffff8000348ae90, 5}

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

Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hpdskflt.sys ( hpdskflt+14c2 )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffa81081b8380, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff8000348ae90, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800036bf100
GetUlongFromAddress: unable to read from fffff800036bf1c0
 fffffa81081b8380 Nonpaged pool

FAULTING_IP: 
nt!RtlCompareMemory+80
fffff800`0348ae90 f3a6            repe cmps byte ptr [rsi],byte ptr [rdi]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

TRAP_FRAME:  fffff88003daf360 -- (.trap 0xfffff88003daf360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000005
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000348ae90 rsp=fffff88003daf4f8 rbp=fffffa8004aee9d0
 r8=0000000000000005  r9=0000000000000030 r10=fffff88003b63ac0
r11=fffffa8007f77220 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!RtlCompareMemory+0x80:
fffff800`0348ae90 f3a6            repe cmps byte ptr [rsi],byte ptr [rdi]
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003504603 to fffff80003488e80

STACK_TEXT:  
fffff880`03daf1f8 fffff800`03504603 : 00000000`00000050 fffffa81`081b8380 00000000`00000000 fffff880`03daf360 : nt!KeBugCheckEx
fffff880`03daf200 fffff800`03486fae : 00000000`00000000 fffffa81`081b8380 fffffa80`0917da00 fffffa80`081b8900 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`03daf360 fffff800`0348ae90 : fffffa80`07f9b210 fffffa80`08049a20 fffff880`024294c2 fffffa80`04aee9d0 : nt!KiPageFault+0x16e
fffff880`03daf4f8 fffff880`024294c2 : fffffa80`04aee9d0 00000000`00000000 fffffa80`07f9b210 00000000`00000000 : nt!RtlCompareMemory+0x80
fffff880`03daf510 fffffa80`04aee9d0 : 00000000`00000000 fffffa80`07f9b210 00000000`00000000 00000002`00000002 : hpdskflt+0x14c2
fffff880`03daf518 00000000`00000000 : fffffa80`07f9b210 00000000`00000000 00000002`00000002 ffffffff`80000888 : 0xfffffa80`04aee9d0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
hpdskflt+14c2
fffff880`024294c2 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  hpdskflt+14c2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hpdskflt

IMAGE_NAME:  hpdskflt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4dcd7ca6

FAILURE_BUCKET_ID:  X64_0x50_hpdskflt+14c2

BUCKET_ID:  X64_0x50_hpdskflt+14c2

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_hpdskflt+14c2

FAILURE_ID_HASH:  {d99630a2-e4c1-470d-f44b-2bd2d5b0a531}

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

2: kd> lmvm hpdskflt
start             end                 module name
fffff880`02428000 fffff880`02432000   hpdskflt T (no symbols)           
    Loaded symbol image file: hpdskflt.sys
    Image path: \SystemRoot\system32\DRIVERS\hpdskflt.sys
    Image name: hpdskflt.sys
    Timestamp:        Sat May 14 00:17:02 2011 (4DCD7CA6)
    CheckSum:         0000E6A7
    ImageSize:        0000A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4