Hello,
Sorry if this is a stupid question but is there a platform ID to socket type translation list available? Failing that could someone tell me how I would translate the Platform ID’s in the example below into socket types? For example, which Platform ID would Socket M or Socket 775 be?
| 3 | 6F4 | F5 (0,2,4,5,6,7) | 26 | 2006-03-12 | PRD | 0x1000 | 0x5F3E0 | No |
| 4 | 6F1 | 27 (0,1,2,5) | 12 | 2005-11-29 | PRD | 0x1000 | 0x603E0 | Yes |
| 9 | 6E4 | 20 (5) | 26 | 2005-08-16 | PRD | 0x1000 | 0x65FE0 | Yes |
Thanks!
How the Platform ID bitmask translates into actual sockets (older, LGA775 etc) or platform types (newer, Mobile with PCH, HEDT etc) is not known to the public. We can only assume certain things based on observation. The always applicable rule of thumb is to pick the same CPUID with the same or more (not less) Platform IDs.
Thanks for the reply, is it something Intel keep confidential on purpose or do they just assume that we would have no use for the information? I was looking at https://newsroom.intel.com/wp-content/up…te-guidance.pdf and it shows some of the more modern Platform ID’s but was trying to understand the older stuff.
I was to try adding support for a Socket M T7600 (6F6) to an older BIOS, I grabbed the microcode listed below so unless it will cause harm I could just add all four. Looking at the standard BIOS I’m working with my barley educated guess would say cpu006F6_plat20_ver000000D1_2010-10-01_PRD_C3EFBA8F relates to Socket M.
cpu006F6_plat01_ver000000D0_2010-09-30_PRD_B61EC71A
cpu006F6_plat04_ver000000D2_2010-10-01_PRD_6618CFFF
cpu006F6_plat20_ver000000D1_2010-10-01_PRD_C3EFBA8F
cpu006F6_plat10_ver0000004A_2006-06-27_PRD_8A944E2B
The odd thing is despite MCE not listing CPUID 6F6 in the unmodified BIOS a T7600 actually seems to work correctly without issue, no error on boot and seems fine in Windows so it this point its just curiosity.
Thanks!
I assume both but have no way of knowing for sure. It is true that end-users don’t really need to know the actual sockets/platform types as long as the aforementioned rule of thumb is followed.
It won’t cause any harm, the BIOS will just ignore incompatible CPU microcodes.
I think older CPUs could start without a microcode patch but that is not optimal. Besides, the operating system can load newer microcodes by itself while it initiates. You can see what CPUID and Platform your system requires from within the OS, usually via certain monitoring tools such as AIDA64, HwInfo etc.
That’s interesting to know, I always thought the BIOS would give some sort of microcode error. I’ve looked for an hour or so now and the only sign of a problem I can find is this from the Windows System Event Log:
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
Log Name: System
Source: Microsoft-Windows-Kernel-Processor-Power
Date: 26/02/2018 11:50:25
Event ID: 35
Task Category: (2)
Level: Error
Keywords:
User: SYSTEM
Computer: Test-1
Description:
Performance power management features on processor 1 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Processor-Power" Guid="{0F67E49F-FE51-4E9F-B490-6F2948CC6027}" />
<EventID>35</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2018-02-26T11:50:25.321763700Z" />
<EventRecordID>7857</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="256" />
<Channel>System</Channel>
<Computer>Media-1</Computer>
<Security UserID="S-1-5-177" />
</System>
<EventData>
<Data Name="Group">0</Data>
<Data Name="Number">1</Data>
</EventData>
</Event>
It might not be related to missing microcode but its worth a shot adding the 6F6 microcode directly, its an old system I'm not too worried about bricking it :)
Yes you should have the compatible microcode patches at the BIOS for the best CPU operation. You can search online to find methods to see from the OS whether a microcode has been loaded, it might be interesting to know that.
With a Socket M T7600 installed (6F6) AIDA64 indicates microcode revision D1 is in use, I can only assume that its being applied by Windows 10 in this case because there is no 6F6 microcode of any revision in the BIOS.
Win10 still loads microcode updates from mcupdate_Genuineintel.dll I don’t remember when microsoft announced that they will no longer be updating this file but the latest microcode in it seems to be from April 2017
as MS-Dll
Position: $00002714
82 Entries found, start at pos: 00002E00 in section: 00001E00 - 000E6E00
Proc Update Flags Checksum Date Loader Data Total
0006F2 005D 0001 9384A573 10-02-2010 0001 0FD0 1000
0006F2 005C 0020 C335A60F 10-02-2010 0001 0FD0 1000
0006F6 00D0 0001 B61EC71A 09-30-2010 0001 0FD0 1000
0006F6 00D2 0004 6618CFFF 10-01-2010 0001 0FD0 1000
-------------------------------------------------------------------------
0006F6 00D1 0020 C3EFBA8F 10-01-2010 0001 0FD0 1000
-------------------------------------------------------------------------
0006F7 006A 0010 9911AAF2 10-02-2010 0001 0FD0 1000
0006F7 006B 0040 CC4DEED3 10-02-2010 0001 0FD0 1000
0006FA 0095 0080 9F4B38D8 10-02-2010 0001 0FD0 1000
0006FB 00C1 0001 0EF87396 10-04-2011 0001 0FD0 1000
0006FB 00BC 0004 9394765A 10-03-2010 0001 0FD0 1000
0006FB 00BB 0008 E7FBF398 10-03-2010 0001 0FD0 1000
0006FB 00BA 0010 ED247070 10-03-2010 0001 0FD0 1000
0006FB 00BA 0020 9777492E 10-03-2010 0001 0FD0 1000
0006FB 00BC 0040 F1A7A484 10-03-2010 0001 0FD0 1000
0006FB 00BA 0080 F953DC67 10-03-2010 0001 0FD0 1000
0006FD 00A4 0001 9ACE6116 10-02-2010 0001 0FD0 1000
0006FD 00A4 0020 9ACE60F7 10-02-2010 0001 0FD0 1000
0006FD 00A4 0080 9ACE6097 10-02-2010 0001 0FD0 1000
000F41 0016 0002 0A12A70A 04-21-2005 0001 13D0 1400
000F41 0017 00BD 326135C1 04-22-2005 0001 13D0 1400
000F43 0005 009D 77812C17 04-21-2005 0001 07D0 0800
000F44 0006 009D 9F60DB18 04-21-2005 0001 0BD0 0C00
000F47 0003 009D AF2CEF0D 04-21-2005 0001 0BD0 0C00
000F48 000C 0001 5B9AFEC7 05-08-2006 0001 0BD0 0C00
000F48 000E 0002 0E158E10 01-15-2008 0001 0BD0 0C00
000F48 0007 005F D0938263 06-30-2005 0001 0BD0 0C00
000F49 0003 00BD F85D53B8 04-21-2005 0001 07D0 0800
000F4A 0004 005C 5E7996D9 12-14-2005 0001 07D0 0800
000F4A 0002 005D DFBC9997 06-10-2005 0001 07D0 0800
000F62 000F 0004 0976D137 12-15-2005 0001 0BD0 0C00
000F64 0002 0001 680B0995 12-15-2005 0001 0BD0 0C00
000F64 0004 0034 C66DBF02 12-23-2005 0001 0BD0 0C00
000F65 0008 0001 5C58F575 04-26-2006 0001 07D0 0800
000F65 0009 0004 1262A7E1 04-28-2006 0001 07D0 0800
000F68 0009 0022 0D8BB650 07-14-2006 0001 07D0 0800
010661 0043 0001 4B64BA3A 10-04-2010 0001 0FD0 1000
010661 0042 0002 0E219073 10-04-2010 0001 0FD0 1000
010661 0044 0080 53BAADCC 10-04-2010 0001 0FD0 1000
010676 060F 0004 8FE1A243 09-29-2010 0001 0FD0 1000
010676 060F 0040 8FE1A207 09-29-2010 0001 0FD0 1000
010676 0610 0091 61DF8B32 10-04-2011 0001 0FD0 1000
010677 070B 0010 A48ED842 10-04-2011 0001 0FD0 1000
01067A 0A0B 0044 B007E7B0 09-28-2010 0001 1FD0 2000
01067A 0A0C 00B1 0BCA2F8B 10-04-2011 0001 1FD0 2000
0106A4 0012 0003 9383A5F1 06-21-2013 0001 37D0 3800
0106A5 0019 0003 58220E71 06-21-2013 0001 27D0 2800
0106C2 0218 0004 8FB7C1BA 04-10-2009 0001 13D0 1400
0106C2 0219 0008 556338C1 04-10-2009 0001 13D0 1400
0106CA 0107 0001 F851A3D9 08-25-2009 0001 13D0 1400
0106CA 0107 0004 7DEB58B2 08-25-2009 0001 13D0 1400
0106CA 0107 0008 BE667CA5 08-25-2009 0001 13D0 1400
0106CA 0107 0010 482CAE0E 08-25-2009 0001 13D0 1400
0106D1 0029 0008 2408D9A1 09-30-2010 0001 0FD0 1000
0106E4 0002 0009 BDBB308A 03-08-2010 0001 13D0 1400
0106E5 0007 0013 C6783666 08-20-2013 0001 1BD0 1C00
020652 000E 0012 8D3E4AF9 06-26-2013 0001 1FD0 2000
020655 0004 0092 3FACC649 06-28-2013 0001 0BD0 0C00
020661 0105 0002 52558795 07-18-2011 0001 13D0 1400
0206A7 0029 0012 C9C91DF0 06-12-2013 0001 27D0 2800
0206C2 000F 0003 FECACCE7 06-18-2010 0001 1BD0 1C00
0206D6 0619 006D F9BFC8BA 05-22-2012 0001 3FD0 4000
0206D7 0710 006D 30EAA2E5 06-17-2013 0001 43D0 4400
0206F2 0037 0005 99E7BDA6 06-18-2013 0001 33D0 3400
030661 010D 0001 B4762578 12-22-2011 0001 13D0 1400
030661 010D 0002 D687F85A 12-22-2011 0001 13D0 1400
030661 010D 0004 85AE225C 12-22-2011 0001 13D0 1400
030661 010D 0008 4268B212 12-22-2011 0001 13D0 1400
030669 010D 0001 3F0531D2 05-15-2013 0001 13D0 1400
0306A9 001B 0012 579AE07A 05-29-2014 0001 2FD0 3000
0306C3 001E 0032 201CAE5E 08-13-2015 0001 53D0 5400
0306D4 001F 00C0 98F2CB63 02-27-2015 0001 3BD0 3C00
0306E4 0428 00ED 8859F3FE 05-29-2014 0001 33D0 3400
0306E7 070D 00ED 7A50A860 05-29-2014 0001 3BD0 3C00
0306F2 003A 006F 27CCCEA2 01-30-2017 0001 7FD0 8000
0306F4 0009 0080 079E5693 07-17-2015 0001 37D0 3800
040651 001D 0072 F4A50FCF 08-13-2015 0001 4FD0 5000
040661 0012 0032 36B2EC1A 07-03-2014 0001 5BD0 5C00
0406E3 00BA 00C0 32658E60 04-09-2017 0001 17FD0 18000
050654 2000022 0097 CE8A8AEC 06-01-2017 0001 63D0 6400
0506E3 00BA 0036 EEB3BD5A 04-09-2017 0001 17FD0 18000
0806E9 0062 00C0 D68226EE 04-27-2017 0001 17BD0 17C00
0906E9 005E 002A 59C0DF6C 04-06-2017 0001 17BD0 17C00
File version 10.0.16299.15, read with showmc (ftp://ftp.heise.de/pub/ct/listings/1607-168.zip)
HelpDat BIOS has posted some info @ocn
Here’s a rough generalization for this instance
Platform No. 0 + 1 = LGA 775
Platform No. 2 + 3 = Xeon LGA 771
Platform No. 4 + 5 = LGA 775 (+ some mobile)
Platform No. 6 = Xeon LGA 771
Platform No. 7 = mobile CPUs