Forum - RE: Latitude E6420. ME SpiLock failed after CPU change.

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � Intel Management Engine � Latitude E6420. ME SpiLock failed after CPU change.

Page 4 of 5 � Page 1 2 3 4 5 Page �

Topic settings

Print view

Jump to forum

General & Forum related Topics News / Announcements Forum-related Questions & Suggestions Off Topic Important Drivers (AHCI/RAID, NVMe, USB etc.) General: Storage Drivers (AHCI/RAID, NVMe and USB) Specific: Intel AHCI/RAID Drivers Specific: NVIDIA nForce Chipset Drivers (incl. AHCI/RAID) Specific: NVMe Drivers Other Drivers System Performance RAID Performance AHCI/NVMe Performance Solid State Drives BIOS Modding BIOS Modding Guides and Problems BIOS modules (PCI ROM, EFI and others) BIOS Modding Requests Reports: BIOS Modding Results Offers: Already modded special BIOSes Special Topics Intel Management Engine CPU Microcodes NVMe Support for old Systems Other Tools (not BIOS modding related) Interesting PC Hardware & Software OS related Topics Windows 11 Windows 8-10/Server 2012-2019 Windows 7/Vista/Server 2008 Windows XP/2000/Server 2003 DOS/Windows 3.X/9X/ME - Retro Gaming Other Operating Systems

#46 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Sun Mar 17, 2019 9:41 pm (Last edited: Sun Mar 17, 2019 9:43 pm)

May be it's sounds silly, what may means:
"Failed to get ME Kernel Host Interface version ..."

reply

#47 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Mon Mar 18, 2019 7:05 am

plutomaniac thanks, all makes sense, nothing more needed regarding what I mentioned. BIOS in #43 has AltMEDisabled Will try AMT disabled next with ME enabled, if AltMEDisabled fails to help.

@rustam2v - did you test this BIOS yet, in post #43? I'm not sure what you're talking about windows instability, in regards to what, when etc?

Please don't send PM's for help on BIOS edits, I can't help with BIOS in PM's. Please make a thread and I will try to help as soon as I can - thanks!
If you appreciate my efforts and are willing to donate to help improve my hardware, gift cards work for me (Amazn, NuEgg, eBa) - send me a PM
I view the forum like this, please bump your thread 1x every 24-48 hours if no reply

reply

#48 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Mon Mar 18, 2019 3:43 pm (Last edited: Mon Mar 18, 2019 5:20 pm)

Zitat von Lost_N_BIOS im Beitrag #47
plutomaniac thanks, all makes sense, nothing more needed regarding what I mentioned. BIOS in #43 has AltMEDisabled Will try AMT disabled next with ME enabled, if AltMEDisabled fails to help.
@rustam2v - did you test this BIOS yet, in post #43? I'm not sure what you're talking about windows instability, in regards to what, when etc?

Just did it, look like we are on the right way. Laptop started without long dark screen delay as it did with this ES before.
Bios setup - OK
F21 boot manager - OK (without MEBx option, as before, as for stock i5 and as for this ES)
Dell diagnostic started with ES cpu, but only multiprocessor cash test, no CPU test )))
Windows 10 boot failed - about 20 minutes with Windows circle animation, then i turned it off.
Now installing pure windows on another hdd

@Lost_N_BIOS Windows instability - because windows spirit gone to heaven, pure install solved this issue )))

reply

#49 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Mon Mar 18, 2019 5:14 pm

So you've booted with the ES cpu after Lost's modifications?

reply

#50 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Mon Mar 18, 2019 5:18 pm (Last edited: Mon Mar 18, 2019 8:47 pm)

Zitat von plutomaniac im Beitrag #49
So you've booted with the ES cpu after Lost's modifications?

Yes! Waiting for second one mode.

Zitat von Lost_N_BIOS im Beitrag #47
plutomaniac thanks, all makes sense, nothing more needed regarding what I mentioned. BIOS in #43 has AltMEDisabled Will try AMT disabled next with ME enabled

And hope much, that you explain me more detailed, what you did )))
Very strange CPU, chip too big, to be other than quad-core (inc. 1st gen cpu), it's same size as 2nd or 3rd quadcore, but CPU-Z report ... i3 dualcore, with 4MB L3???

Processors
-------------------------------------------------------------------------

Number of sockets 1
Number of threads 4

APICs
-------------------------------------------------------------------------

Socket 0
-- Core 0 (ID 0)
-- Thread 0 0
-- Thread 1 1
-- Core 1 (ID 1)
-- Thread 2 2
-- Thread 3 3

Timers
-------------------------------------------------------------------------

ACPI timer 3.580 MHz
Perf timer 10.000 MHz
Sys timer 1.000 KHz

Processors Information
-------------------------------------------------------------------------

Socket 1 ID = 0
Number of cores 2 (max 2)
Number of threads 4 (max 4)
Name Intel Core i3
Codename Sandy Bridge
Specification Genuine Intel(R) CPU 0 @ 1.60GHz (Engineering Sample)
Package (platform ID) Socket 988B rPGA (0x4)
CPUID 6.A.2
Extended CPUID 6.2A
Core Stepping B2
Technology 32 nm
TDP Limit 35.0 Watts
Tjmax 100.0 °C
Core Speed 1596.2 MHz
Multiplier x Bus Speed 16.0 x 99.8 MHz
Base frequency (cores) 99.8 MHz
Base frequency (ext.) 99.8 MHz
Stock frequency 1600 MHz
Instructions sets MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T, VT-x, AES, AVX
Microcode Revision 0x27
L1 Data cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 2 x 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 2 x 256 KBytes, 8-way set associative, 64-byte line size
L3 cache 4 MBytes, 16-way set associative, 64-byte line size
Max CPUID level 0000000Dh
Max CPUID ext. level 80000008h
Cache descriptor Level 1, D, 32 KB, 2 thread(s)
Cache descriptor Level 1, I, 32 KB, 2 thread(s)
Cache descriptor Level 2, U, 256 KB, 2 thread(s)
Cache descriptor Level 3, U, 4 MB, 16 thread(s)
FID/VID Control yes

IBRS not supported
IBPB not supported
STIBP not supported
RDCL_NO no
IBRS_ALL not supported
Turbo Mode not supported
Max non-turbo ratio 16x
Max turbo ratio 16x
Max efficiency ratio 12x
O/C bins none
Ratio 1 core 16x
Ratio 2 cores 16x
Ratio 3 cores 16x
Ratio 4 cores 16x

Temperature 0 58 degC (136 degF) (Package)
Temperature 1 58 degC (136 degF) (Core #0)
Temperature 2 55 degC (131 degF) (Core #1)
Voltage 0 1.16 Volts (VID)
Power 00 9.81 W (Package)
Power 01 8.02 W (IA Cores)
Power 02 0.05 W (GT)
Power 03 1.74 W (Uncore)
Clock Speed 0 1596.19 MHz (Core #0)
Clock Speed 1 1596.19 MHz (Core #1)
Core 0 max ratio 16.0 (effective 16.0)
Core 1 max ratio 16.0 (effective 16.0)

Thread dumps
-------------------------------------------------------------------------

CPU Thread 0
APIC ID 0
Topology Processor ID 0, Core ID 0, Thread ID 0

CPUID
0x00000000 0x0000000D 0x756E6547 0x6C65746E 0x49656E69
0x00000001 0x000206A2 0x00100800 0x1FBAEBFF 0xBFEBFBFF
0x00000002 0x55035A01 0x00F0B2FF 0x00000000 0x00CA0000
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x1C004121 0x01C0003F 0x0000003F 0x00000000
0x00000004 0x1C004122 0x01C0003F 0x0000003F 0x00000000
0x00000004 0x1C004143 0x01C0003F 0x000001FF 0x00000000
0x00000004 0x1C03C163 0x03C0003F 0x00000FFF 0x00000002
0x00000005 0x00000040 0x00000040 0x00000003 0x00021120
0x00000006 0x00000075 0x00000002 0x00000001 0x00000000
0x00000007 0x00000000 0x00000000 0x00000000 0x00000000
0x00000008 0x00000000 0x00000000 0x00000000 0x00000000
0x00000009 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000A 0x07300403 0x00000000 0x00000000 0x00000603
0x0000000B 0x00000001 0x00000002 0x00000100 0x00000000
0x0000000B 0x00000004 0x00000004 0x00000201 0x00000000
0x0000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000D 0x00000007 0x00000340 0x00000340 0x00000000
0x0000000D 0x00000001 0x00000000 0x00000000 0x00000000
0x0000000D 0x00000100 0x00000240 0x00000000 0x00000000
0x80000000 0x80000008 0x00000000 0x00000000 0x00000000
0x80000001 0x00000000 0x00000000 0x00000001 0x28100800
0x80000002 0x756E6547 0x20656E69 0x65746E49 0x2952286C
0x80000003 0x55504320 0x20202020 0x20202020 0x20202020
0x80000004 0x20202030 0x20402020 0x30362E31 0x007A4847
0x80000005 0x00000000 0x00000000 0x00000000 0x00000000
0x80000006 0x00000000 0x00000000 0x01006040 0x00000000
0x80000007 0x00000000 0x00000000 0x00000000 0x00000100
0x80000008 0x00003024 0x00000000 0x00000000 0x00000000

MSR 0x0000001B 0x00000000 0xFEE00900
MSR 0x0000003A 0x00000000 0x00000005
MSR 0x000001A0 0x00000000 0x00850089
MSR 0x000000CE 0x00000C00 0x68011000
MSR 0x00000017 0x00100000 0x00000000
MSR 0x00000035 0x00000000 0x00020004
MSR 0x000000C1 0x00000000 0x00000000
MSR 0x000000C2 0x00000000 0x00000000
MSR 0x000000C3 0x00000000 0x00000000
MSR 0x000000C4 0x00000000 0x00000000
MSR 0x00000186 0x00000000 0x00000000
MSR 0x00000187 0x00000000 0x00000000
MSR 0x000001AD 0x00000000 0x10101010
MSR 0x00000194 0x00000000 0x00010000
MSR 0x0000019A 0x00000000 0x00000000
MSR 0x000001A4 0x00000000 0x00000000
MSR 0x000001FC 0x00000000 0x0000005F
MSR 0x00000606 0x00000000 0x000A1003
MSR 0x00000601 0x18141494 0x80000380
MSR 0x00000602 0x18141494 0x80000118
MSR 0x00000610 0x8000815E 0x00148118
MSR 0x00000611 0x00000000 0x216B4933
MSR 0x00000639 0x00000000 0x1A983196
MSR 0x00000641 0x00000000 0x002CA5C0
MSR 0x00000614 0x00120000 0x00000118
MSR 0x0000019C 0x00000000 0x88290000
MSR 0x000001A2 0x00000000 0x00640E00
MSR 0x000001B1 0x00000000 0x88290000
MSR 0x00000198 0x000024FD 0x00001000
MSR 0x00000199 0x00000000 0x00001000

CPU Thread 1
APIC ID 1
Topology Processor ID 0, Core ID 0, Thread ID 1

CPUID
0x00000000 0x0000000D 0x756E6547 0x6C65746E 0x49656E69
0x00000001 0x000206A2 0x01100800 0x1FBAEBFF 0xBFEBFBFF
0x00000002 0x55035A01 0x00F0B2FF 0x00000000 0x00CA0000
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x1C004121 0x01C0003F 0x0000003F 0x00000000
0x00000004 0x1C004122 0x01C0003F 0x0000003F 0x00000000
0x00000004 0x1C004143 0x01C0003F 0x000001FF 0x00000000
0x00000004 0x1C03C163 0x03C0003F 0x00000FFF 0x00000002
0x00000005 0x00000040 0x00000040 0x00000003 0x00021120
0x00000006 0x00000075 0x00000002 0x00000001 0x00000000
0x00000007 0x00000000 0x00000000 0x00000000 0x00000000
0x00000008 0x00000000 0x00000000 0x00000000 0x00000000
0x00000009 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000A 0x07300403 0x00000000 0x00000000 0x00000603
0x0000000B 0x00000001 0x00000002 0x00000100 0x00000001
0x0000000B 0x00000004 0x00000004 0x00000201 0x00000001
0x0000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000D 0x00000007 0x00000340 0x00000340 0x00000000
0x0000000D 0x00000001 0x00000000 0x00000000 0x00000000
0x0000000D 0x00000100 0x00000240 0x00000000 0x00000000
0x80000000 0x80000008 0x00000000 0x00000000 0x00000000
0x80000001 0x00000000 0x00000000 0x00000001 0x28100800
0x80000002 0x756E6547 0x20656E69 0x65746E49 0x2952286C
0x80000003 0x55504320 0x20202020 0x20202020 0x20202020
0x80000004 0x20202030 0x20402020 0x30362E31 0x007A4847
0x80000005 0x00000000 0x00000000 0x00000000 0x00000000
0x80000006 0x00000000 0x00000000 0x01006040 0x00000000
0x80000007 0x00000000 0x00000000 0x00000000 0x00000100
0x80000008 0x00003024 0x00000000 0x00000000 0x00000000

MSR 0x0000001B 0x00000000 0xFEE00800
MSR 0x0000003A 0x00000000 0x00000005
MSR 0x000001A0 0x00000000 0x00850089
MSR 0x000000CE 0x00000C00 0x68011000
MSR 0x00000017 0x00100000 0x00000000
MSR 0x00000035 0x00000000 0x00020004
MSR 0x000000C1 0x00000000 0x00000000
MSR 0x000000C2 0x00000000 0x00000000
MSR 0x000000C3 0x00000000 0x00000000
MSR 0x000000C4 0x00000000 0x00000000
MSR 0x00000186 0x00000000 0x00000000
MSR 0x00000187 0x00000000 0x00000000
MSR 0x000001AD 0x00000000 0x10101010
MSR 0x00000194 0x00000000 0x00010000
MSR 0x0000019A 0x00000000 0x00000000
MSR 0x000001A4 0x00000000 0x00000000
MSR 0x000001FC 0x00000000 0x0000005F
MSR 0x00000606 0x00000000 0x000A1003
MSR 0x00000601 0x18141494 0x80000380
MSR 0x00000602 0x18141494 0x80000118
MSR 0x00000610 0x8000815E 0x00148118
MSR 0x00000611 0x00000000 0x216B8565
MSR 0x00000639 0x00000000 0x1A9864D5
MSR 0x00000641 0x00000000 0x002CA5FC
MSR 0x00000614 0x00120000 0x00000118
MSR 0x0000019C 0x00000000 0x88290000
MSR 0x000001A2 0x00000000 0x00640E00
MSR 0x000001B1 0x00000000 0x88290000
MSR 0x00000198 0x000024FD 0x00001000
MSR 0x00000199 0x00000000 0x00001000

CPU Thread 2
APIC ID 2
Topology Processor ID 0, Core ID 1, Thread ID 0

CPUID
0x00000000 0x0000000D 0x756E6547 0x6C65746E 0x49656E69
0x00000001 0x000206A2 0x02100800 0x1FBAEBFF 0xBFEBFBFF
0x00000002 0x55035A01 0x00F0B2FF 0x00000000 0x00CA0000
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x1C004121 0x01C0003F 0x0000003F 0x00000000
0x00000004 0x1C004122 0x01C0003F 0x0000003F 0x00000000
0x00000004 0x1C004143 0x01C0003F 0x000001FF 0x00000000
0x00000004 0x1C03C163 0x03C0003F 0x00000FFF 0x00000002
0x00000005 0x00000040 0x00000040 0x00000003 0x00021120
0x00000006 0x00000075 0x00000002 0x00000001 0x00000000
0x00000007 0x00000000 0x00000000 0x00000000 0x00000000
0x00000008 0x00000000 0x00000000 0x00000000 0x00000000
0x00000009 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000A 0x07300403 0x00000000 0x00000000 0x00000603
0x0000000B 0x00000001 0x00000002 0x00000100 0x00000002
0x0000000B 0x00000004 0x00000004 0x00000201 0x00000002
0x0000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000D 0x00000007 0x00000340 0x00000340 0x00000000
0x0000000D 0x00000001 0x00000000 0x00000000 0x00000000
0x0000000D 0x00000100 0x00000240 0x00000000 0x00000000
0x80000000 0x80000008 0x00000000 0x00000000 0x00000000
0x80000001 0x00000000 0x00000000 0x00000001 0x28100800
0x80000002 0x756E6547 0x20656E69 0x65746E49 0x2952286C
0x80000003 0x55504320 0x20202020 0x20202020 0x20202020
0x80000004 0x20202030 0x20402020 0x30362E31 0x007A4847
0x80000005 0x00000000 0x00000000 0x00000000 0x00000000
0x80000006 0x00000000 0x00000000 0x01006040 0x00000000
0x80000007 0x00000000 0x00000000 0x00000000 0x00000100
0x80000008 0x00003024 0x00000000 0x00000000 0x00000000

MSR 0x0000001B 0x00000000 0xFEE00800
MSR 0x0000003A 0x00000000 0x00000005
MSR 0x000001A0 0x00000000 0x00850089
MSR 0x000000CE 0x00000C00 0x68011000
MSR 0x00000017 0x00100000 0x00000000
MSR 0x00000035 0x00000000 0x00020004
MSR 0x000000C1 0x00000000 0x00000000
MSR 0x000000C2 0x00000000 0x00000000
MSR 0x000000C3 0x00000000 0x00000000
MSR 0x000000C4 0x00000000 0x00000000
MSR 0x00000186 0x00000000 0x00000000
MSR 0x00000187 0x00000000 0x00000000
MSR 0x000001AD 0x00000000 0x10101010
MSR 0x00000194 0x00000000 0x00010000
MSR 0x0000019A 0x00000000 0x00000000
MSR 0x000001A4 0x00000000 0x00000000
MSR 0x000001FC 0x00000000 0x0000005F
MSR 0x00000606 0x00000000 0x000A1003
MSR 0x00000601 0x18141494 0x80000380
MSR 0x00000602 0x18141494 0x80000118
MSR 0x00000610 0x8000815E 0x00148118
MSR 0x00000611 0x00000000 0x216BB6AD
MSR 0x00000639 0x00000000 0x1A988D4C
MSR 0x00000641 0x00000000 0x002CA638
MSR 0x00000614 0x00120000 0x00000118
MSR 0x0000019C 0x00000000 0x882B0000
MSR 0x000001A2 0x00000000 0x00640E00
MSR 0x000001B1 0x00000000 0x882B0000
MSR 0x00000198 0x000024FD 0x00001000
MSR 0x00000199 0x00000000 0x00001000

CPU Thread 3
APIC ID 3
Topology Processor ID 0, Core ID 1, Thread ID 1

CPUID
0x00000000 0x0000000D 0x756E6547 0x6C65746E 0x49656E69
0x00000001 0x000206A2 0x03100800 0x1FBAEBFF 0xBFEBFBFF
0x00000002 0x55035A01 0x00F0B2FF 0x00000000 0x00CA0000
0x00000003 0x00000000 0x00000000 0x00000000 0x00000000
0x00000004 0x1C004121 0x01C0003F 0x0000003F 0x00000000
0x00000004 0x1C004122 0x01C0003F 0x0000003F 0x00000000
0x00000004 0x1C004143 0x01C0003F 0x000001FF 0x00000000
0x00000004 0x1C03C163 0x03C0003F 0x00000FFF 0x00000002
0x00000005 0x00000040 0x00000040 0x00000003 0x00021120
0x00000006 0x00000075 0x00000002 0x00000001 0x00000000
0x00000007 0x00000000 0x00000000 0x00000000 0x00000000
0x00000008 0x00000000 0x00000000 0x00000000 0x00000000
0x00000009 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000A 0x07300403 0x00000000 0x00000000 0x00000603
0x0000000B 0x00000001 0x00000002 0x00000100 0x00000003
0x0000000B 0x00000004 0x00000004 0x00000201 0x00000003
0x0000000C 0x00000000 0x00000000 0x00000000 0x00000000
0x0000000D 0x00000007 0x00000340 0x00000340 0x00000000
0x0000000D 0x00000001 0x00000000 0x00000000 0x00000000
0x0000000D 0x00000100 0x00000240 0x00000000 0x00000000
0x80000000 0x80000008 0x00000000 0x00000000 0x00000000
0x80000001 0x00000000 0x00000000 0x00000001 0x28100800
0x80000002 0x756E6547 0x20656E69 0x65746E49 0x2952286C
0x80000003 0x55504320 0x20202020 0x20202020 0x20202020
0x80000004 0x20202030 0x20402020 0x30362E31 0x007A4847
0x80000005 0x00000000 0x00000000 0x00000000 0x00000000
0x80000006 0x00000000 0x00000000 0x01006040 0x00000000
0x80000007 0x00000000 0x00000000 0x00000000 0x00000100
0x80000008 0x00003024 0x00000000 0x00000000 0x00000000

MSR 0x0000001B 0x00000000 0xFEE00800
MSR 0x0000003A 0x00000000 0x00000005
MSR 0x000001A0 0x00000000 0x00850089
MSR 0x000000CE 0x00000C00 0x68011000
MSR 0x00000017 0x00100000 0x00000000
MSR 0x00000035 0x00000000 0x00020004
MSR 0x000000C1 0x00000000 0x00000000
MSR 0x000000C2 0x00000000 0x00000000
MSR 0x000000C3 0x00000000 0x00000000
MSR 0x000000C4 0x00000000 0x00000000
MSR 0x00000186 0x00000000 0x00000000
MSR 0x00000187 0x00000000 0x00000000
MSR 0x000001AD 0x00000000 0x10101010
MSR 0x00000194 0x00000000 0x00010000
MSR 0x0000019A 0x00000000 0x00000000
MSR 0x000001A4 0x00000000 0x00000000
MSR 0x000001FC 0x00000000 0x0000005F
MSR 0x00000606 0x00000000 0x000A1003
MSR 0x00000601 0x18141494 0x80000380
MSR 0x00000602 0x18141494 0x80000118
MSR 0x00000610 0x8000815E 0x00148118
MSR 0x00000611 0x00000000 0x216BF1F4
MSR 0x00000639 0x00000000 0x1A98BFC2
MSR 0x00000641 0x00000000 0x002CA673
MSR 0x00000614 0x00120000 0x00000118
MSR 0x0000019C 0x00000000 0x882B0000
MSR 0x000001A2 0x00000000 0x00640E00
MSR 0x000001B1 0x00000000 0x882A0000
MSR 0x00000198 0x000024FD 0x00001000
MSR 0x00000199 0x00000000 0x00001000

And after attempt to detect VGA system goes to very strange "standby", as Dell diag says, - CPU not detected.
Laptop functioning normal only with discreet graphics.

reply

#51 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Mon Mar 18, 2019 7:16 pm (Last edited: Mon Mar 18, 2019 7:27 pm)

plutomaniac

Administrator

Show info

Posts:	5347
Registered since:	09.16.2014

After some google searching, based on the numbers in the first picture, it seems you have these two CPUs:

1
2
3
4
5
 
912095	Yes	SANDY BRIDGE-M-2	3192-1.2	AV8062701022800Q ACT	QACT	FC-BGA10C	12/16/2010
SR08Q	AV8062701022800	FC-BGA10C	SANDY BRIDGE-M-2	12/17/2010
 
912171	Yes	SANDY BRIDGE-M-2	3302-1.2	FF8062701072400Q AD0	QAD0	FC-PGA10	12/16/2010
SR082	FF8062701072400	FC-PGA10	SANDY BRIDGE-M-2	12/17/2010
 

I can't find anything for "SR082" but searching for "FF8062701072400" does return some sort of listing for an "Intel Celeron B1030" for which no other info exists. On the other hand, "SR08Q" seems to be an early i5-2400 3.10GHz CPU.

reply

#52 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Mon Mar 18, 2019 8:58 pm (Last edited: Mon Mar 18, 2019 9:15 pm)

CPU Chip too big to be anything other than quad core...So needs to find other 25 revisions of 206A2 microcode )))
Another one idea to detect uma graphics, today have no time for this, only most stupid "update driver" from windows, and very strange "standby" after this step.
Tomorrow I'll try Win7 without uefiboot. It's more recoverable os for tests )))
@ Lost_N_BIOS Can you explain me or any links to procedure, which you did with this "A08" bios?

reply

#53 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Mon Mar 18, 2019 10:16 pm

The size of the CPU does not change depending on its core count. A SNB CPU with 2/4 and another with 4/8 Cores/Threads are exactly the same size. If CPU-Z says it's a dual core with HT and no TurboBoost then that's what it is. The other one will probably be an i5 with TurboBoost and no HT (4/4), thus better. Why find other 206A2 microcodes? There is no logical explanation for that.

reply

#54 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Tue Mar 19, 2019 6:39 am

CPU-z can sometimes be showing wrong info for cores/threads if cores disabled for any reason (ie incorrect MSInfo setting, or BIOS disabled cores/not enabling cores etc)

This CPU may not have, or may have disabled, integrated graphics, so you may not be able to use that.

@rustam2v - great it's working! Now, we do same with A25 BIOS, this may solve some of your current other issues. We should also test ME enabled again, in case the ME or some settings in it etc was messed up before.

What I did was clean and transfer ME into new clean ME file, using Intel Flash Image Tool (FITc) from ME System Tools package from section "C" in this thread
Intel Management Engine: Drivers, Firmware & System Tools
The ME was cleaned and settings transferred using this guide - [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization
Stock ME as source input file during the transfer comes from repo thread here - Intel Engine: Firmware Repositories
To disable ME via AltMEDisable, you do as plutomaniac said in this post #42 (Do this at end of cleaning guide, before your first save) - Latitude E6420. ME SpiLock failed after CPU change. (3)
Before, or after all that, I replaced "BIOS region" in BIOS with one from Dell HDR

Here is two A25 BIOS with ME version 7.1.80.1214. These have ME disabled in one and ME enabled in the other, please test ME enabled one first in case there was simply some ME setting issue or BIOS region issue previously causing all the problems.
http://s000.tinyupload.com/index.php?fil...978537830626593

reply

#55 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Tue Mar 19, 2019 3:19 pm (Last edited: Thu Mar 21, 2019 2:13 pm)

Zitat von plutomaniac im Beitrag #53
The size of the CPU does not change depending on its core count. A SNB CPU with 2/4 and another with 4/8 Cores/Threads are exactly the same size.

of course, you partially right ))) But ... Dual core i5 & i7 on left, same size. SB quad-core on the top middle.

So i'll look carefully, under microscope with multi-tester to look if any hardware difference present, and maybe try to unlock cores and multiplier. I'm old-school overclocker ))) But i'm sure that this 32nm quad core processors naturaly ))) First idea to replace 206A2 microcode with 206A7

Zitat von Lost_N_BIOS im Beitrag #54

Here is two A25 BIOS with ME version 7.1.80.1214. These have ME disabled in one and ME enabled in the other, please test ME enabled one first in case there was simply some ME setting issue or BIOS region issue previously causing all the problems.
http://s000.tinyupload.com/index.php?fil...978537830626593

I think that A25 bios dump provided before maybe wrong, because it was made on base of @plutomaniac mods + soft flash with Dell flasher to A25. As i found in this case not all parts of bios flashing. As example, yesterday I've flashed A25 over your dump and as result have hybrid firmware. Laptop started with this hybrid A25, and ask for cpu microcode for 206A2, after skiping this, windows start booting, but crashed on the way.
Of course, i'll test with dumps you provided with detailed reports. And i'll made A25 pure dump before this testing.

reply

#56 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Tue Mar 19, 2019 10:00 pm (Last edited: Tue Mar 19, 2019 10:01 pm)

Sorry, my country under national holidays pressing, so I have no time for test these bioses complex. Please give me vacation till tomorrow evening.
About your bios base on A8, no problem to install w7 or w10, but not possible to activate UMA graphics, after drivers install system reboot and ...upsss ... dark screen just as drivers loaded. Usual PID_0106. HD2000 or HD3000.

reply

#57 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Wed Mar 20, 2019 6:29 pm (Last edited: Wed Mar 20, 2019 8:31 pm)

Original Dell E6420 A25 dump by programmer
@Lost_N_BIOS Testing ME enable-disable dumps
By the way, not sure if it important or not, but UEFIextract shown special message for both outimage.bin files:
parseNvarStore: file can't be parsed as NVAR variables store
ME-enable: Boots till first Dell "welcome" choice screen with F1-F2-F3 selection, then keyboard non-functioing ... upsss, not possible to select any choice
ME-disabled: Booted with stock i5. It was possible to install UMA graphics driver in Win7. Blue screen after cpu replacement with ES. Halts so huge, that i need to remove battery to turn it off.
Now making "image restore" to Win7 without any drivers. Operation failed.
Tried to zero install of Win7 - failed with same hard blue screen halts
Returning to original A25 with programmer

reply

#58 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Fri Mar 22, 2019 12:56 am (Last edited: Fri Mar 22, 2019 1:44 am)

@Lost_N_BIOS What you think about this parameter activation in FITc
ME Region / Configuration / ME / Processor Emulation
This maybe reason of ME fail with ES cpu?

reply

#59 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Thu Apr 11, 2019 6:28 am

@rustam2v - sorry for delays, I'm very far behind lately. UEFITool message is normal, maybe depends on BIOS I used as source, and I checked now and have many files for you here (Some with NVRAM, some without), so some have this message, some do not, and some with NVRAM have it and some do not.
So yes, quite the mess of files we have here, and regarding your flashing hybrid thoughts - reflashing stock may not fix things, some parts of the BIOS are not programmed during flash, depending on how you flash, and some BIOS (Stock) do not have fully populated or both NVRAM volumes, so this creates it's own issue too.
If you want all fixed, proper BIOS, once we figure out what all works for you. I need your original BIOS dump from both chips via programmer (Or FPT with jumper on or FD unlocked via pinmod), or at least FPT BIOS region dump untouched and original from this system (So both NVRAM volumes intact)
A25 failure at both ME enable and disabled may be due to some of what we discussed above, source BIOS I used. We may need to redo both of those and test again, it shouldn't have failed on both since A08 worked (Unless Dell put in CPU block list, which I doubt, but it's possible)

The only way you can return to original A25 with programmer is if you have an original A25 dumped via programmer. Do you have that? If yes, send to me.
On UMA, I doubt that will work without ME Enabled, so for now don't worry about it until later.

Yes, you may be onto something with the Processor Emulation setting, here is how it's used (It even mentioned pre-production silicon too)

plutomaniac do you think we should change this, do you have any experience with that and ES CPU? If you are unsure I guess we can just test and see.

reply

#60 | RE: Latitude E6420. ME SpiLock failed after CPU change. datum

Thu Apr 11, 2019 1:06 pm (Last edited: Thu Apr 11, 2019 1:13 pm)

I have tested with ME disabled and AltM (with ME cleaner). ME disable not always functioning well. But AltM mode functioning perfect.
Also I have test with several option with ME Emulation (FITc). As i found there were no differents, if ME enable. By the way, FITc rebuild not always safety. In case of AltM activation with FITc system not always starts. This depend on bios version. If ME cleaner change only one byte in bios, FITc rebuild making much more, by BeyComp report.
The only problem left is UMA graphics. After driver install OS failed.
I have no ideas why, it's not looking as locked if CPU itself, but may be locked by intel drivers

Attached original A25 bios dump with programmer
And the modded one, which stable, currently in use
till -7FFFFF = dump of first 64MB chip
From 800000 till the end = dump of 2nd 16MB chip

reply

Cannot get CSME to work after PCH replacement � � Yoga 2 Pro shutdowns every 30 minutes

Page 4 of 5 � Page 1 2 3 4 5 Page �

Please enter a reason for warning.