Many upgrade attempts for 1909 to no avail - same error from minidumps

  • Thread starter Thread starter Prideslaw
  • Start date Start date
P

Prideslaw

Guest
Like many others I cannot upgrade Win 10 pro 1909 to 2004 or 20H2.

Started out with message from Microsoft that support would end for my version - click click - upgrade assistant - failure!

Running a bare bones Dell Optiplex 7010


Cores 4

Threads 8

Name Intel Core i7 3770

Code Name Ivy Bridge

Package Socket 1155 LGA

Technology 22nm

Specification Intel Core i7-3770 CPU @ 3.40GHz

Family 6

Extended Family 6

Model A

Extended Model 3A

Stepping 9

Revision E1/L1

Instructions MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, Intel 64, NX, AES, AVX

Virtualization Not supported

Hyperthreading Supported, Enabled

Bus Speed 99.3 MHz

Stock Core Speed 3400 MHz

Stock Bus Speed 100 MHz

Average Temperature 30 °C


with Logitech Keyboard & Mouse and Brother printer both USB attached.


Tried all the solutions so far, sfc, dism, media creation tool, direct iso update, disabled all non microsoft services - all seem to fail around 60% of install phase (2+hrs into the process!!)

Minidump(s) have the same caused by message of ntoskrnl.exe+1c3ab0. 1st dump was 20H2 iso update and 2nd was 2004 iso update.

de51b3a9-5656-4adf-b961-46ed94904c7f?upload=true.jpg

Last bit of setupact.log (from 2004 update) is

------------------------------------------------------

2021-03-26 20:20:34, Info CSI 00001014 Begin executing advanced installer phase 9 index 83 (sequence 90)

Old component: [l:0]''

New component: [l:140 ml:141]'HyperV-VmChipset, Culture=neutral, Version=10.0.19041.153, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS'

Install mode: delta

Smart installer: false

Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}

Installer name: 'Events'

2021-03-26 20:20:34, Info CSI 00001015 Performing 1 operations as follows:

(0) LockComponentPath: flags: 0 comp: {l:16 b:8a983a019f22d7015c2000006c25cc07} pathid: {l:16 b:8a983a019f22d7015d2000006c25cc07} path: [l:98]'\??\X:\Windows\WinSxS\amd64_hyperv-vmchipset_31bf3856ad364e35_10.0.19041.153_none_b32940cfeb827fac' pid: 256c starttime: 132612778207400884

2021-03-26 20:20:34, Info CSI 00001016@2021/3/27:00:20:34.648 CSI Advanced installer perf trace:

CSIPERF:AIDONE;{3bb9fd2b-351e-4b9c-b1fc-ed0758805998};HyperV-VmChipset, version 10.0.19041.153, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35};5751us

2021-03-26 20:20:34, Info CSI 00001017 End executing advanced installer (sequence 90)

Completion status: S_OK



2021-03-26 20:20:34, Info CSI 00001018 Begin executing advanced installer phase 9 index 0 (sequence 0)

Old component: [l:0]''

New component: [l:0]''

Install mode: delta

Smart installer: true

Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}

Installer name: 'Events'

2021-03-26 20:20:34, Info CSI 00001019 Registry root HKLM\Software: HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SOFTWARE\



2021-03-26 20:20:34, Info CSI 0000101a Registry root HKLM\System: HKLM\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/$WINDOWS.~BT/NewOS/Windows/System32/config/SYSTEM\

------------------------------------------------Nothing after the line above----------

Don't know what Phase 9 index 0 is but somewhere I saw that it may have something to do with an overworked (clocked) processor.

Does anyone have any ideas?

Thanks

Continue reading...
 
Back
Top