Windows 10: Funktionsupdate 1903 fails pn hp EliteBook 8560p repeatedly, setupDiag output given

Hi there,


the Function Update 1903 (previous and now again running Windows is 1803 (Build 17134.829)) did not install in 4 Trials, Kaspersky has been deinstalled. setpupDiag did run and says:


C:\Users\baerbel\Downloads>SetupDiag.exe /Verbose /Format:xml

SetupDiag v1.5.0.0
Copyright (©) Microsoft Corporation. All rights reserved.

Searching for setup logs...
Found C:\$WINDOWS.~BT\Sources\Panther\setupact.log with update date 24.06.2019 11:00:44 to be the correct setup log.
Found C:\$WINDOWS.~BT\Sources\Rollback\setupact.log with update date 24.06.2019 11:27:17 to be the correct rollback log.

Gathering baseline information from setup logs...

SetupDiag: processing rule: CompatScanOnly.
...No match.


SetupDiag: processing rule: PlugInComplianceBlock.
...No match.


SetupDiag: processing rule: BitLockerHardblock.
...No match.


SetupDiag: processing rule: VHDHardblock.
...No match.


SetupDiag: processing rule: PortableWorkspaceHardblock.
...No match.


SetupDiag: processing rule: AuditModeHardblock.
...No match.


SetupDiag: processing rule: SafeModeHardblock.
...No match.


SetupDiag: processing rule: InsufficientSystemPartitionDiskSpaceHardblock.
...No match.


SetupDiag: processing rule: CompatBlockedApplicationAutoUninstall.
...No match.


SetupDiag: processing rule: CompatBlockedApplicationDismissable.
...No match.


SetupDiag: processing rule: CompatBlockedApplicationManualUninstall.
...No match.


SetupDiag: processing rule: HardblockDeviceOrDriver.
...No match.


SetupDiag: processing rule: HardblockMismatchedLanguage.
..No match.


SetupDiag: processing rule: HardblockFlightSigning.
..No match.


SetupDiag: processing rule: DiskSpaceBlockInDownLevel.
..No match.


SetupDiag: processing rule: DiskSpaceFailure.
..No match.


SetupDiag: processing rule: PreReleaseWimMountDriverFound.
..No match.


SetupDiag: processing rule: DebugSetupMemoryDump.
..DebugSetupMemoryDump: DirectiveDebugMemoryDump - C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp -
Microsoft (R) Windows Debugger Version 10.0.17134.12 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred SRV*
Deferred *http://symweb
Symbol search path is: SRV*;*http://symweb
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`05400000 PsLoadedModuleList = 0xfffff802`05843370
Debug session time: Mon Jun 24 11:01:12.388 2019 (UTC + 2:00)
System Uptime: 0 days 0:06:47.261
Loading Kernel Symbols
...............................................................
................................................................
................................................................
............................................................
Loading User Symbols

Loading unloaded module list
.......................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffdc8f53b78000, 0, fffff802078c10a5, 2}

*** ERROR: Module load completed but symbols could not be loaded for WwanUsbMp64.sys
Probably caused by : WwanUsbMp64.sys ( WwanUsbMp64+2179d )

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

3: kd> *******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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

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


KEY_VALUES_STRING: 1


TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_MANUFACTURER: Hewlett-Packard

SYSTEM_PRODUCT_NAME: HP EliteBook 8560p

SYSTEM_SKU: LY441EA#UUZ

SYSTEM_VERSION: A0001D02

BIOS_VENDOR: Hewlett-Packard

BIOS_VERSION: 68SCF Ver. F.22

BIOS_DATE: 12/22/2011

BASEBOARD_MANUFACTURER: Hewlett-Packard

BASEBOARD_PRODUCT: 1618

BASEBOARD_VERSION: KBC Version 97.4A

DUMP_TYPE: 1

BUGCHECK_P1: ffffdc8f53b78000

BUGCHECK_P2: 0

BUGCHECK_P3: fffff802078c10a5

BUGCHECK_P4: 2

READ_ADDRESS: Unable to get offset of nt!_MI_VISIBLE_STATE.SpecialPool
Unable to get value of nt!_MI_VISIBLE_STATE.SessionSpecialPool
ffffdc8f53b78000

FAULTING_IP:
NDIS!memcpy+a5
fffff802`078c10a5 f30f6f4c1110 movdqu xmm1,xmmword ptr [rcx+rdx+10h]

MM_INTERNAL_CODE: 2

IMAGE_NAME: WwanUsbMp64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4edf36a8

FAULTING_MODULE: fffff80207880000 NDIS

CPU_COUNT: 4

CPU_MHZ: aea

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 2a

CPU_STEPPING: 7

CPU_MICROCODE: 6,2a,7,0 (F,M,S,R) SIG: 2E'00000000 (cache) 2E'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: RIHANNA

ANALYSIS_SESSION_TIME: 06-28-2019 16:17:22.0375

ANALYSIS_VERSION: 10.0.17134.12 amd64fre

TRAP_FRAME: ffffdc8f53b76810 -- (.trap 0xffffdc8f53b76810)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000006 rbx=0000000000000000 rcx=ffff8008dc52ca90
rdx=00005c867764b558 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802078c10a5 rsp=ffffdc8f53b769a8 rbp=fffff8020794c600
r8=0000000000000006 r9=00000000000000eb r10=ffff8008d4d02000
r11=ffff8008dc52b588 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
NDIS!memcpy+0xa5:
fffff802`078c10a5 f30f6f4c1110 movdqu xmm1,xmmword ptr [rcx+rdx+10h] ds:ffffdc8f`53b77ff8=????????????????????????????????
Resetting default scope

LOCK_ADDRESS: fffff8020585d760 -- (!locks fffff8020585d760)

Resource @ nt!PiEngineLock (0xfffff8020585d760) Exclusively owned
Contention Count = 51
NumberOfExclusiveWaiters = 1
Threads: ffff8008d9626040-01<*>

Threads Waiting On Exclusive Access:
ffff8008da7ee2c0
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff8020585d760
Thread Count : 1
Thread address: 0xffff8008d9626040
Thread wait : 0x65d0

LAST_CONTROL_TRANSFER: from fffff802055dfd54 to fffff802055bc8a0

STACK_TEXT:
ffffdc8f`53b76568 fffff802`055dfd54 : 00000000`00000050 ffffdc8f`53b78000 00000000`00000000 ffffdc8f`53b76810 : nt!KeBugCheckEx
ffffdc8f`53b76570 fffff802`0547aaef : 00000000`00000000 00000000`00000000 00000000`00000000 ffffdc8f`53b78000 : nt!MiSystemFault+0x1d2d64
ffffdc8f`53b76670 fffff802`055ca79a : 00000000`0000001b ffffdc8f`53b76904 fffff802`018cd2a8 00000000`00000000 : nt!MmAccessFault+0x34f
ffffdc8f`53b76810 fffff802`078c10a5 : fffff802`078aea9f ffff8008`dc52b1a0 fffff802`0794c600 ffff8008`dc52b588 : nt!KiPageFault+0x35a
ffffdc8f`53b769a8 fffff802`078aea9f : ffff8008`dc52b1a0 fffff802`0794c600 ffff8008`dc52b588 ffffdc8f`53b76ae0 : NDIS!memcpy+0xa5
ffffdc8f`53b769b0 fffff802`078ae72d : ffff8008`dc52b1a0 00000000`00000014 ffff8008`dc1f7430 ffffdc8f`53b76b20 : NDIS!ndisMSetPowerManagementCapabilities+0x77
ffffdc8f`53b76a00 fffff802`078ae345 : ffff8008`00140280 ffff8008`dc52b1a0 fffff802`0794c6c8 00000000`00000000 : NDIS!ndisMSetGeneralAttributes+0x1f9
ffffdc8f`53b76a60 fffff802`018b179d : 00000000`00000000 ffffdc8f`53b76f30 ffff8008`dc52d000 00000000`00000000 : NDIS!NdisMSetMiniportAttributes+0x325
ffffdc8f`53b76ac0 fffff802`018d428b : 00000000`00000000 00000000`00000000 00000000`c0000001 00000000`000031b8 : WwanUsbMp64+0x2179d
ffffdc8f`53b76d10 fffff802`07986ba8 : ffff8008`dc52b1a0 ffffdc8f`53b76f30 ffff8008`00000070 ffffdc8f`53b76f30 : WwanUsbMp64+0x4428b
ffffdc8f`53b76dc0 fffff802`079aebcd : ffff8008`d844e580 00000000`00000000 ffff8008`dc52b1a0 00000000`00000001 : NDIS!ndisMInvokeInitialize+0xa0
ffffdc8f`53b76e30 fffff802`078ab8b9 : ffff8008`dc5269a0 ffff8008`d844e580 00000000`00000000 01d52a6b`5f1a5df8 : NDIS!ndisMInitializeAdapter+0x5c1
ffffdc8f`53b77500 fffff802`078abefc : ffff8008`dc5269a0 00000000`00000000 fffff802`0794d790 ffff8008`dc52b1a0 : NDIS!ndisInitializeAdapter+0x91
ffffdc8f`53b77570 fffff802`078add8b : ffff8008`dc52b1a0 ffff8008`dc52b1a0 00000000`00000004 00000000`00000000 : NDIS!ndisPnPStartDevice+0x14c
ffffdc8f`53b77600 fffff802`078cea90 : ffff8008`dc52b1a0 ffff8008`dc52b1a0 ffff8008`dc5269a0 00000000`00000009 : NDIS!ndisStartDeviceSynchronous+0x73
ffffdc8f`53b77670 fffff802`078982ec : ffff8008`dc5269a0 ffffdc8f`53b77710 00000000`00000000 ffff8008`dc52b1a0 : NDIS!ndisPnPIrpStartDevice+0x20be8
ffffdc8f`53b776d0 fffff802`05431cc9 : ffffdc8f`53b77801 ffff8008`dc5269a0 00000000`00000001 ffff8008`dc52b050 : NDIS!ndisPnPDispatch+0x27c
ffffdc8f`53b77740 fffff802`05b0d02e : ffff8008`d9c79060 ffff8008`dc589520 00000000`00000000 00000000`00000000 : nt!IofCallDriver+0x59
ffffdc8f`53b77780 fffff802`054d652a : ffff8008`d9c79060 00000000`00000000 ffff8008`dc589520 fffff802`00000000 : nt!PnpAsynchronousCall+0xea
ffffdc8f`53b777c0 fffff802`0555405c : 00000000`00000000 ffff8008`d9c79060 fffff802`0553fbc0 fffff802`0553fbc0 : nt!PnpSendIrp+0x5e
ffffdc8f`53b77830 fffff802`05b0c3e4 : 00000000`00000000 00000000`00000000 ffff8008`dc589520 00000000`00000000 : nt!PnpStartDevice+0x88
ffffdc8f`53b778c0 fffff802`05b0c2b3 : ffff8008`da0d3aa0 00000000`00000000 00000000`00000001 fffff802`05540046 : nt!PnpStartDeviceNode+0xec
ffffdc8f`53b77950 fffff802`05af0d08 : ffff8008`da0d3aa0 ffffdc8f`53b77a18 00000000`db9eab00 00000000`00000001 : nt!PipProcessStartPhase1+0x6f
ffffdc8f`53b779a0 fffff802`05c72612 : ffff8008`da0d3a00 ffff8008`db9eab01 ffffdc8f`53b77ab0 fffff802`00000000 : nt!PipProcessDevNodeTree+0x3b0
ffffdc8f`53b77a60 fffff802`05669df0 : 00000001`00000003 ffff8008`da0d3aa0 ffff9c01`00000000 ffff8008`db9eabc0 : nt!PiRestartDevice+0xbe
ffffdc8f`53b77ab0 fffff802`054c4855 : ffff8008`d9626040 ffff8008`d41579e0 fffff802`0585c000 fffff802`0585c100 : nt!PnpDeviceActionWorker+0x111230
ffffdc8f`53b77b70 fffff802`0552f725 : ffff8008`d9626040 00000000`00000080 ffff8008`d40b7280 00000404`ad9bbffe : nt!ExpWorkerThread+0x105
ffffdc8f`53b77c10 fffff802`055c3dfa : ffff9c01`d7c8b180 ffff8008`d9626040 fffff802`0552f6d0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffffdc8f`53b77c60 00000000`00000000 : ffffdc8f`53b78000 ffffdc8f`53b72000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


THREAD_SHA1_HASH_MOD_FUNC: 9b207df6307284fbb5e5065aa3ba6dd579005e97

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d9efabba55274be7ef2b82413b0f63e3ede9d344

THREAD_SHA1_HASH_MOD: b942e1eaea53137733fccf78abdc7c33c16b9607

FOLLOWUP_IP:
WwanUsbMp64+2179d
fffff802`018b179d 8bd8 mov ebx,eax

FAULT_INSTR_CODE: 3b41d88b

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: WwanUsbMp64+2179d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: WwanUsbMp64

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 2179d

FAILURE_BUCKET_ID: AV_R_INVALID_WwanUsbMp64!unknown_function

BUCKET_ID: AV_R_INVALID_WwanUsbMp64!unknown_function

PRIMARY_PROBLEM_CLASS: AV_R_INVALID_WwanUsbMp64!unknown_function

TARGET_TIME: 2019-06-24T09:01:12.000Z

OSBUILD: 18362

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 3845

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_r_invalid_wwanusbmp64!unknown_function

FAILURE_ID_HASH: {8ee49df4-dd30-00cd-2b95-78d553225ab5}

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

lmv m ntfs - 3: kd> start end module name
fffff802`08a00000 fffff802`08c9e000 Ntfs (deferred)
Image path: \SystemRoot\System32\Drivers\Ntfs.sys
Image name: Ntfs.sys
Image was built with /Brepro flag.
Timestamp: D9A3CE82 (This is a reproducible build file hash, not a timestamp)
CheckSum: 0029E269
ImageSize: 0029E000
File version: 10.0.18362.145
Product version: 10.0.18362.145
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft« Windows« Operating System
InternalName: ntfs.sys
OriginalFilename: ntfs.sys
ProductVersion: 10.0.18362.145
FileVersion: 10.0.18362.145 (WinBuild.160101.0800)
FileDescription: NT File System Driver
LegalCopyright: ® Microsoft Corporation. All rights reserved.
||. - 3: kd> . 0 64-bit Kernel bitmap dump: C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp

SetupDiag found 1 matching issue.

SetupDiag results were logged to: .\SetupDiagResults.xml
Logs ZipFile created at: .\Logs.zip

C:\Users\baerbel\Downloads>




has somebody an idea, please? I can deliever the Dumps setupDiag analysed, but I cannot make sense of the Output of kd.exe. It should be something with Drivers, but I've actually no clue.


Many thanks in advance

Dent.


Funny Detail, if you install Windows Kits Debuggers, it starts with directory arm, arm64 and setupDiag cannot find the right kd.exe in C:\Program Files (x86)\Windows Kits\10\Debuggers\x64 until you deleted the arm and arm64 directories (tells it found an kd.exe but for another architecture (just arm*)…. argghhh)



[moved from German forums]

:)

 

Windows Hello isn't available for HP Elitebook 8470p

Hello,

The problems is not solved. I have HP elitebook 8560p, it is not supported by Windows Hello. Why?

is there any solution ?

I can't use my fingerprint in my device, is there any other software that might help?

Thanks

 

Camera is not working with Error code 0XA00F4244(0XC00D36D5) - HP Elitebook 8560P





Hi,

I am currently using HP-ELITEBOOK 8560p and i am facing Problem regarding builtin
Camera.

Laptop Camera is not working at all. i have tried all the methods already which is available on website.

one thing is very surprising that Images and Devices are not being displayed under
Device Manager.

So anybody have any solution. Please i need you people help to solve this issue.

Currently i am using Windows 10 Pro (64bit).

Thanks in Advance.

 

Windows 10: Doesn't detect audio devices

My laptop is a HP EliteBook 8560p.