• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
We have new content about Hotkey issue, Click here to check it out!
Locked

‎01-28-2016 02:12 AM - edited ‎01-28-2016 02:25 AM

HP Recommended
Product: ProOne 400 G2
Operating System: Microsoft Windows 10 (64-bit)

Hi

 

I have an issue I have been working on for the last couple of weeks without any result. I have two HP ProOne 400 G2 that makes Blue Screen of Death whenever I run Sysprep on them. I have successful installed and sysprep the computers with Windows 8.1, but with Windows 10 it crash everytime I try.

 

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PCIEXPRESS

 

I guess it has something to do with a bad driver for a device connected to the PCIExpress BUS, but not sure what to do from here.

 

I get the following from my BSOD analysis:

 

 

Windows 10 Kernel Version 10586 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.0.amd64fre.th2_release.151029-1700
Machine Name:
Kernel base = 0xfffff801`02e7f000 PsLoadedModuleList = 0xfffff801`0315dcb0
Debug session time: Thu Jan 14 11:35:23.343 2016 (UTC + 1:00)
System Uptime: 0 days 0:27:03.005

 

ebugging Details:
------------------


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  10586.0.amd64fre.th2_release.151029-1700

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  HP ProOne 400 G2 20-in Touch AiO

SYSTEM_SKU:  L3N70AV

BIOS_VENDOR:  HP

BIOS_VERSION:  N13 Ver. 02.02

BIOS_DATE:  11/12/2015

BASEBOARD_MANUFACTURER:  HP

BASEBOARD_PRODUCT:  8063

BASEBOARD_VERSION:  KBC Version 05.26

DUMP_TYPE:  2

BUGCHECK_P1: 4

BUGCHECK_P2: ffffe00025cbc038

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 2

CPU_MHZ: b58

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 49'00000000 (cache) 49'00000000 (init)

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  5

ANALYSIS_SESSION_HOST:  TNI-PC2

ANALYSIS_SESSION_TIME:  01-28-2016 09:26:11.0835

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT: 
ffffd001`a3529e08 fffff801`02e41f1f : 00000000`00000124 00000000`00000004 ffffe000`25cbc038 00000000`00000000 : nt!KeBugCheckEx
ffffd001`a3529e10 fffff801`0308fe88 : ffffe000`25cbc038 ffffe000`25d0ca98 ffffe000`25d0ca98 ffffe000`25d275c0 : hal!HalBugCheckSystem+0xcf
ffffd001`a3529e50 fffff800`acb08838 : 00000000`00000750 00000000`00000000 ffffe000`25d0ca04 ffffe000`27994010 : nt!WheaReportHwError+0x258
ffffd001`a3529eb0 fffff800`acb015c2 : ffffd001`9eff6c80 ffffd001`a3529f50 ffffd001`a34f1180 ffffe000`24add200 : pci!ExpressRootPortAerInterruptRoutine+0x24c
ffffd001`a3529f10 fffff801`02e83387 : ffffd001`9eff6c80 00000000`00000000 ffff6dd1`158aa449 00000000`00000010 : pci!ExpressRootPortInterruptRoutine+0x22
ffffd001`a3529f70 fffff801`02fc2168 : ffffd001`9eff6c80 ffffe000`27a49040 00000000`000001ba ffffe000`27414440 : nt!KiCallInterruptServiceRoutine+0x87
ffffd001`a3529fb0 fffff801`02fc23f7 : 00000000`0000002f 00000000`00000000 00000000`00000001 fffff801`0319c180 : nt!KiInterruptSubDispatch+0x108
ffffd001`a9ca5490 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch+0x37


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  0e50fe8fa1ecf43925e43bd200d7bb6400cb19fc

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  b3258f674ee33805ab3940241ac9889fab704dc3

THREAD_SHA1_HASH_MOD:  7ec0dd05e870653df55cacfdf5a6b10cad863ce2

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION: 

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PCIEXPRESS

BUCKET_ID:  0x124_GenuineIntel_PCIEXPRESS

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PCIEXPRESS

TARGET_TIME:  2016-01-14T10:35:23.000Z

OSBUILD:  10586

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:  2015-10-30 03:15:45

BUILDDATESTAMP_STR:  151029-1700

BUILDLAB_STR:  th2_release

BUILDOSVER_STR:  10.0.10586.0.amd64fre.th2_release.151029-1700

ANALYSIS_SESSION_ELAPSED_TIME: 6261

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_pciexpress

FAILURE_ID_HASH:  {0aebd40d-d4c8-456d-b299-4fede7e8bf0c}

 

Best Regards

 

Thomas

Best regards

Thomas
http://www.techwork.dk
1 ACCEPTED SOLUTION

Accepted Solutions

‎07-01-2016 05:29 AM

HP Recommended

Hi

 

HP found a workaround for me and are working on a new BIOS to fix the issue permantly.

 

Go to F10 BIOS Setup -> Advanced -> System Options -> and uncheck "Allow PCIe/PCI SERR# Interrupt"

 

Then you are able to run Sysprep without BlueScreen of death.

 

I can see that HP released a new BIOS version 02.03 last month. You might want to try that first, but otherwise try the workaround above.

 

 

Best Regards

Thomas

Best regards

Thomas
http://www.techwork.dk

View solution in original post

Was this reply helpful? Yes No
5 REPLIES 5

‎07-01-2016 04:55 AM

HP Recommended

Hey Thomas,

 

 

I have the same issue on a ProDesk 400 G3. BSOD on sysprep. Did you manage to fix it?

 

Alternatively could someone else help me out? There are no PCIe devices connected on MoBo, have uninstalled network and gfx drivers to no avail.

 

MEMORY.DMP debug output as follows.

 

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000004, PCI Express Error
Arg2: ffffe001f37ec8d8, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000
Arg4: 0000000000000000

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

Page 10de02 not present in the dump file. Type ".hh dbgerr004" for details
Page 980 not present in the dump file. Type ".hh dbgerr004" for details
Page 980 not present in the dump file. Type ".hh dbgerr004" for details
Page 980 not present in the dump file. Type ".hh dbgerr004" for details

DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING:  10586.420.amd64fre.th2_release_sec.160527-1834

SYSTEM_MANUFACTURER:  HP

SYSTEM_PRODUCT_NAME:  HP ProDesk 400 G3 SFF

SYSTEM_SKU:  T4R68ET#ABU

BIOS_VENDOR:  HP

BIOS_VERSION:  N03 Ver. 02.04

BIOS_DATE:  01/06/2016

BASEBOARD_MANUFACTURER:  HP

BASEBOARD_PRODUCT:  8062

BASEBOARD_VERSION:  KBC Version 05.26

DUMP_TYPE:  1

BUGCHECK_P1: 4

BUGCHECK_P2: ffffe001f37ec8d8

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BUGCHECK_STR:  0x124_GenuineIntel

CPU_COUNT: 4

CPU_MHZ: c78

CPU_VENDOR:  GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R)  SIG: 6A'00000000 (cache) 6A'00000000 (init)

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  b

ANALYSIS_SESSION_HOST:  DESKTOP-JLRJV8K

ANALYSIS_SESSION_TIME:  07-01-2016 11:44:00.0632

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT: 
fffff800`43671e08 fffff800`41a4cf1f : 00000000`00000124 00000000`00000004 ffffe001`f37ec8d8 00000000`00000000 : nt!KeBugCheckEx
fffff800`43671e10 fffff800`41c9a8c8 : ffffe001`f37ec8d8 ffffe001`f37a7a98 ffffe001`f37a7a98 ffffe001`f37eb7a0 : hal!HalBugCheckSystem+0xcf
fffff800`43671e50 fffff801`8b4788b8 : 00000000`00000750 00000000`00000000 ffffe001`f37a7a04 ffffe001`f21f4010 : nt!WheaReportHwError+0x258
fffff800`43671eb0 fffff801`8b4715c2 : ffffd000`fdd27c80 fffff800`43671f50 fffff800`41da7180 fffff800`00000000 : pci!ExpressRootPortAerInterruptRoutine+0x24c
fffff800`43671f10 fffff800`41b77197 : ffffd000`fdd27c80 00000000`00000000 ffff04a1`412daf4e 00000000`00000010 : pci!ExpressRootPortInterruptRoutine+0x22
fffff800`43671f70 fffff800`41bcd988 : ffffd000`fdd27c80 00000000`c0000034 00000000`00000001 ffffe001`f2ce3cd0 : nt!KiCallInterruptServiceRoutine+0x87
fffff800`43671fb0 fffff800`41bcdc17 : fffff800`41e83fa0 ffffc001`118b0760 fffff800`41e83fa0 fffff800`41e8e71c : nt!KiInterruptSubDispatch+0x108
ffffd000`254a4530 fffff800`41b06881 : 00000000`00000001 00000000`00000000 ffffe001`f2ce3b10 ffffe001`f2ce3b10 : nt!KiInterruptDispatch+0x37
ffffd000`254a46c0 fffff800`41e8d2ba : ffffe001`f2ce3b10 ffffd000`254a4760 ffffc001`00000040 ffffe001`f2146a20 : nt!SeClearLearningModeObjectInformation+0x11
ffffd000`254a46f0 fffff800`41ebf676 : 00000008`00000001 ffffe001`f2146a20 00000079`a187d548 00000000`00000000 : nt!ObOpenObjectByNameEx+0x3fa
ffffd000`254a4810 fffff800`41ebf3c3 : 0000017d`2c536101 0000017d`2c5a1a00 00000079`a187d850 00007ffb`940ea170 : nt!CmOpenKey+0x2a6
ffffd000`254a49c0 fffff800`41bd70a3 : ffffe001`f4dbc080 0000017d`2c561d50 ffffe001`f4dbc080 ffffd000`254a4a80 : nt!NtOpenKeyEx+0xf
ffffd000`254a4a00 00007ffb`a84672b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000079`a187d4d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`a84672b4


STACK_COMMAND:  kb

THREAD_SHA1_HASH_MOD_FUNC:  159c55eda9d238d8c9dba83c286d270d65320ffb

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  d78669deae44b03333d9ffc1f81e86996c8dcde2

THREAD_SHA1_HASH_MOD:  1cda1b252abfd348cb3926e9ab6c0650cbfa8a35

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

IMAGE_VERSION: 

FAILURE_BUCKET_ID:  0x124_GenuineIntel_PCIEXPRESS

BUCKET_ID:  0x124_GenuineIntel_PCIEXPRESS

PRIMARY_PROBLEM_CLASS:  0x124_GenuineIntel_PCIEXPRESS

TARGET_TIME:  2016-06-30T13:01:56.000Z

OSBUILD:  10586

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:  2016-05-28 04:59:07

BUILDDATESTAMP_STR:  160527-1834

BUILDLAB_STR:  th2_release_sec

BUILDOSVER_STR:  10.0.10586.420.amd64fre.th2_release_sec.160527-1834

ANALYSIS_SESSION_ELAPSED_TIME: 714

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x124_genuineintel_pciexpress

FAILURE_ID_HASH:  {0aebd40d-d4c8-456d-b299-4fede7e8bf0c}

Followup:     MachineOwner

Was this reply helpful? Yes No

‎07-01-2016 05:29 AM

HP Recommended

Hi

 

HP found a workaround for me and are working on a new BIOS to fix the issue permantly.

 

Go to F10 BIOS Setup -> Advanced -> System Options -> and uncheck "Allow PCIe/PCI SERR# Interrupt"

 

Then you are able to run Sysprep without BlueScreen of death.

 

I can see that HP released a new BIOS version 02.03 last month. You might want to try that first, but otherwise try the workaround above.

 

 

Best Regards

Thomas

Best regards

Thomas
http://www.techwork.dk
Was this reply helpful? Yes No

‎07-04-2016 02:23 AM

HP Recommended

Hi Thomas,

 

I was already on the latest BIOS version, but that workaround is exactly what I needed. Thanks very much for getting back so promptly with an answer. 

 

Regards,

 

Tristan

 

Was this reply helpful? Yes No

‎07-04-2016 02:29 AM - edited ‎07-04-2016 02:32 AM

HP Recommended

Glad I could help Tristan. HP has told me they will make a BIOS update for this model in the future that will fix this issue. You might want to check for new BIOS in the near future, but now you can at least move on with your tasks.

 

Best regards

Thomas
http://www.techwork.dk
Was this reply helpful? Yes No

‎07-21-2016 03:42 AM

HP Recommended

You Sir are a life saver, remember not all heroes wear capes (Y)

Thanks, so much.

Though I experienced a new BIOS version doesn't fix it for ProDesk 400 G2, unfortunately, but your tip ended my desperation.

Was this reply helpful? Yes No
Warning
Be alert for scammers posting fake support phone numbers and/or email addresses on the community.
If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.

Didn't find what you were looking for? Ask the community

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.