Forum - SSD at 6GB/s and RE: Ivy Bridge microcode update for Samsung NP300E5C

Win-Raid Forum (Drivers - Firmware - Modding) � Special Topics � CPU Microcodes � Sandy/Ivy Bridge microcode update for Samsung notebook

Page 2 of 2 � Page 1 2 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

#16 | SSD at 6GB/s and RE: Ivy Bridge microcode update for Samsung NP300E5C datum

Tue Apr 09, 2019 5:01 pm

Thanks for your answer! Of course there are many ways to update this bios and for most of us it might feel a lot safer to flash a complete bios they could check beforehand!

I ran into another "problem": The older NP300E5A HM65 Notebook has a switch to enable SATA GEN3 Mode on the first SATA port. The newer NP300E5C (HM75) dosn't have that switch and the default is SATA2 (3Gb/s)

I'm afraid I won't 'feel' the difference, but it feels better anyway and I learned a little about EFI- shell and EFI- variables...

I read a lot about EFI variables and how to enable advanced menus in bios- but I'd have to admit: No clear understandig so far
1. Backup the bios: fptw64 -bios -d backup.rom
2. Find the settings store for the advanced settings- searched the backup with UEFItool NE for GEN3 and found 3 regions
A. C3491A75-7600-460F-810B-FC703944D1BE SamsungSetupAdvancedDxe.efi
B. 2D6F37BF-9AFC-4AA5-A026-32B2FCF30FB9 PlatformDxe.efi
C. CFEF94C4-4167-466A-8893-8779459DFA86 PlatformHiiAdvancedDxe.efi
3. Extracted all these regions, ran Donovans Universal IFR Extractor-0.7 over them and got
for B) almost no forms
for C) not SATA but PEG, but
A) has the advanced settings!

Suppress If {0A 82}
64 Bit Unsigned Int: 0x1 {45 0A 01 00 00 00 00 00 00 00}
Gray Out If {19 82}
Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
Not {17 02}
End {29 02}
One Of: SATA GEN3 Mode, VarStoreInfo (VarOffset/VarName): 0x148, VarStore: 0x6, QuestionId: 0xD, Size: 1, Min: 0x0, Max 0xFF, Step: 0x0 {05 A6 17 00 18 00 0D 00 06 00 48 01 00 10 00 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
One Of Option: Disabled, Value (8 bit): 0x2 (default) {09 0E 2C 00 10 00 02 00 00 00 00 00 00 00}
One Of Option: Enabled, Value (8 bit): 0x3 {09 0E 2B 00 00 00 03 00 00 00 00 00 00 00}
End One Of {29 02}
End If {29 02}
End If {29 02}

UEFI Protocol Detected
--------------------------------------------------------------------------------

String Packages
--------------------------------------------------------------------------------
Offset: Language:
--------------------------------------------------------------------------------
0x35C en-US (0x0)
0x1769 fr-FR (0x1)
0x17B4 ja-JP (0x2)
0x17F5 ko-KR (0x3)
0x18BE ru-RU (0x4)

Form Sets
--------------------------------------------------------------------------------
Offset: Title:
--------------------------------------------------------------------------------
0x190C Advanced (0x2 from string package 0x0)

Internal Forms Representation
--------------------------------------------------------------------------------
Offset: Instruction:
--------------------------------------------------------------------------------
0x1910 Form Set: Advanced [5FB10979-5AE2-4622-A98E-270956BB8D35], ClassGuid0 [93039971-8545-4B04-B45E-32EB8326040E] {0E A7 79 09 B1 5F E2 5A 22 46 A9 8E 27 09 56 BB 8D 35 02 00 2A 00 01 71 99 03 93 45 85 04 4B B4 5E 32 EB 83 26 04 0E}
0x1937 Guid: [0F0B1735-87A0-4193-B266-538C38AF48CE] {5F 15 35 17 0B 0F A0 87 93 41 B2 66 53 8C 38 AF 48 CE 03 01 00}
0x194C Guid: [0F0B1735-87A0-4193-B266-538C38AF48CE] {5F 15 35 17 0B 0F A0 87 93 41 B2 66 53 8C 38 AF 48 CE 04 00 00}
0x1961 Default Store: en-US, DefaultId: 0x0 {5C 06 00 00 00 00}
0x1967 Default Store: en-US, DefaultId: 0x1 {5C 06 00 00 01 00}
0x196D VarStore: VarStoreId: 0x1 [5FB10979-5AE2-4622-A98E-270956BB8D35], Size: 0x5, Name: ADVANCED_INFO {24 24 79 09 B1 5F E2 5A 22 46 A9 8E 27 09 56 BB 8D 35 01 00 05 00 41 44 56 41 4E 43 45 44 5F 49 4E 46 4F 00}
0x1991 VarStore: VarStoreId: 0x2 [E6A849B2-36EC-4C2F-9B84-CD89907EECB1], Size: 0xA0, Name: SamsungSetup {24 23 B2 49 A8 E6 EC 36 2F 4C 9B 84 CD 89 90 7E EC B1 02 00 A0 00 53 61 6D 73 75 6E 67 53 65 74 75 70 00}
0x19B4 VarStore: VarStoreId: 0x3 [E947FCF9-DD01-4965-B808-32A7B6815657], Size: 0x46, Name: System {24 1D F9 FC 47 E9 01 DD 65 49 B8 08 32 A7 B6 81 56 57 03 00 46 00 53 79 73 74 65 6D 00}
0x19D1 VarStore: VarStoreId: 0x4 [7D4ADCE1-930D-40C7-9CD2-6D2148413DC7], Size: 0x33, Name: CpuProtocolSetupVar {24 2A E1 DC 4A 7D 0D 93 C7 40 9C D2 6D 21 48 41 3D C7 04 00 33 00 43 70 75 50 72 6F 74 6F 63 6F 6C 53 65 74 75 70 56 61 72 00}
0x19FB VarStore: VarStoreId: 0x5 [4DFBBAAB-1392-4FDE-ABB8-C41CC5AD7D5D], Size: 0x105, Name: Setup {24 1C AB BA FB 4D 92 13 DE 4F AB B8 C4 1C C5 AD 7D 5D 05 00 05 01 53 65 74 75 70 00}
0x1A17 VarStore: VarStoreId: 0x6 [04BD8413-15F9-43F3-9675-4618E03240E3], Size: 0x224, Name: PchProtocolSetupVar {24 2A 13 84 BD 04 F9 15 F3 43 96 75 46 18 E0 32 40 E3 06 00 24 02 50 63 68 50 72 6F 74 6F 63 6F 6C 53 65 74 75 70 56 61 72 00}
0x1A41 Form: Advanced, FormId: 0x1 {01 86 01 00 02 00}
0x1A47 Suppress If {0A 82}
0x1A49 True {46 02}
0x1A4B One Of: , VarStoreInfo (VarOffset/VarName): 0x2, VarStore: 0x1, QuestionId: 0x1, Size: 1, Min: 0x0, Max 0x0, Step: 0x0 {05 A6 2A 00 2A 00 01 00 01 00 02 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1A71 One Of Option: , Value (8 bit): 0x0 {09 0E 2A 00 00 00 00 00 00 00 00 00 00 00}
0x1A7F End One Of {29 02}
0x1A81 End If {29 02}
0x1A83 Suppress If {0A 82}
0x1A85 True {46 02}
0x1A87 One Of: , VarStoreInfo (VarOffset/VarName): 0x3, VarStore: 0x1, QuestionId: 0x2, Size: 1, Min: 0x0, Max 0x0, Step: 0x0 {05 A6 2A 00 2A 00 02 00 01 00 03 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1AAD One Of Option: , Value (8 bit): 0x0 {09 0E 2A 00 00 00 00 00 00 00 00 00 00 00}
0x1ABB End One Of {29 02}
0x1ABD End If {29 02}
0x1ABF Suppress If {0A 82}
0x1AC1 QuestionId: 0x1 equals value 0x0 {12 86 01 00 00 00}
0x1AC7 QuestionId: 0x2 equals value 0x0 {12 06 02 00 00 00}
0x1ACD And {15 02}
0x1ACF End {29 02}
0x1AD1 Gray Out If {19 82}
0x1AD3 Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1AE5 Not {17 02}
0x1AE7 End {29 02}
0x1AE9 One Of: CPU Power Saving Mode, VarStoreInfo (VarOffset/VarName): 0x20, VarStore: 0x2, QuestionId: 0x3, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 03 00 04 00 03 00 02 00 20 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1B0F One Of Option: Disabled, Value (8 bit): 0x0 {09 0E 2C 00 00 00 00 00 00 00 00 00 00 00}
0x1B1D One Of Option: Enabled, Value (8 bit): 0x1 (default) {09 0E 2B 00 10 00 01 00 00 00 00 00 00 00}
0x1B2B End One Of {29 02}
0x1B2D End If {29 02}
0x1B2F End If {29 02}
0x1B31 Suppress If {0A 82}
0x1B33 True {46 02}
0x1B35 One Of: , VarStoreInfo (VarOffset/VarName): 0x4, VarStore: 0x1, QuestionId: 0x4, Size: 1, Min: 0x0, Max 0x0, Step: 0x0 {05 A6 2A 00 2A 00 04 00 01 00 04 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1B5B One Of Option: , Value (8 bit): 0x0 {09 0E 2A 00 00 00 00 00 00 00 00 00 00 00}
0x1B69 End One Of {29 02}
0x1B6B End If {29 02}
0x1B6D Suppress If {0A 82}
0x1B6F QuestionId: 0x4 equals value 0x0 {12 06 04 00 00 00}
0x1B75 Gray Out If {19 82}
0x1B77 Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1B89 Not {17 02}
0x1B8B End {29 02}
0x1B8D One Of: Hyperthreading, VarStoreInfo (VarOffset/VarName): 0x0, VarStore: 0x4, QuestionId: 0x5, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 05 00 06 00 05 00 04 00 00 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1BB3 One Of Option: Disabled, Value (8 bit): 0x0 {09 0E 2C 00 00 00 00 00 00 00 00 00 00 00}
0x1BC1 One Of Option: Enabled, Value (8 bit): 0x1 (default) {09 0E 2B 00 10 00 01 00 00 00 00 00 00 00}
0x1BCF End One Of {29 02}
0x1BD1 End If {29 02}
0x1BD3 End If {29 02}
0x1BD5 Gray Out If {19 82}
0x1BD7 Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1BE9 Not {17 02}
0x1BEB End {29 02}
0x1BED One Of: EDB (Execute Disable Bit), VarStoreInfo (VarOffset/VarName): 0x3, VarStore: 0x4, QuestionId: 0x6, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 07 00 08 00 06 00 04 00 03 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1C13 One Of Option: Disabled, Value (8 bit): 0x0 {09 0E 2C 00 00 00 00 00 00 00 00 00 00 00}
0x1C21 One Of Option: Enabled, Value (8 bit): 0x1 (default) {09 0E 2B 00 10 00 01 00 00 00 00 00 00 00}
0x1C2F End One Of {29 02}
0x1C31 End If {29 02}
0x1C33 Gray Out If {19 82}
0x1C35 True {46 02}
0x1C37 Text: Statement.Prompt: , TextTwo: en-US {03 08 2A 00 2A 00 00 00}
0x1C3F End If {29 02}
0x1C41 Suppress If {0A 82}
0x1C43 True {46 02}
0x1C45 One Of: , VarStoreInfo (VarOffset/VarName): 0x0, VarStore: 0x1, QuestionId: 0x7, Size: 1, Min: 0x0, Max 0x0, Step: 0x0 {05 A6 2A 00 2A 00 07 00 01 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1C6B One Of Option: , Value (8 bit): 0x0 {09 0E 2A 00 00 00 00 00 00 00 00 00 00 00}
0x1C79 End One Of {29 02}
0x1C7B End If {29 02}
0x1C7D Suppress If {0A 82}
0x1C7F QuestionId: 0x7 equals value 0x1 {12 06 07 00 01 00}
0x1C85 Gray Out If {19 82}
0x1C87 Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1C99 Not {17 02}
0x1C9B End {29 02}
0x1C9D One Of: Fast BIOS Mode, VarStoreInfo (VarOffset/VarName): 0x1C, VarStore: 0x3, QuestionId: 0x8, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 0F 00 10 00 08 00 03 00 1C 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1CC3 One Of Option: Disabled, Value (8 bit): 0x1 (default) {09 0E 2C 00 10 00 01 00 00 00 00 00 00 00}
0x1CD1 One Of Option: Enabled, Value (8 bit): 0x0 {09 0E 2B 00 00 00 00 00 00 00 00 00 00 00}
0x1CDF End One Of {29 02}
0x1CE1 End If {29 02}
0x1CE3 End If {29 02}
0x1CE5 Suppress If {0A 82}
0x1CE7 True {46 02}
0x1CE9 One Of: , VarStoreInfo (VarOffset/VarName): 0x0, VarStore: 0x1, QuestionId: 0x9, Size: 1, Min: 0x0, Max 0x0, Step: 0x0 {05 A6 2A 00 2A 00 09 00 01 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1D0F One Of Option: , Value (8 bit): 0x0 {09 0E 2A 00 00 00 00 00 00 00 00 00 00 00}
0x1D1D End One Of {29 02}
0x1D1F End If {29 02}
0x1D21 Suppress If {0A 82}
0x1D23 QuestionId: 0x9 equals value 0x0 {12 06 09 00 00 00}
0x1D29 Gray Out If {19 82}
0x1D2B Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1D3D Not {17 02}
0x1D3F End {29 02}
0x1D41 One Of: Fast BIOS Mode, VarStoreInfo (VarOffset/VarName): 0x2A, VarStore: 0x2, QuestionId: 0xA, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 0F 00 10 00 0A 00 02 00 2A 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1D67 One Of Option: Disabled, Value (8 bit): 0x1 {09 0E 2C 00 00 00 01 00 00 00 00 00 00 00}
0x1D75 One Of Option: Enabled, Value (8 bit): 0x0 (default) {09 0E 2B 00 10 00 00 00 00 00 00 00 00 00}
0x1D83 End One Of {29 02}
0x1D85 End If {29 02}
0x1D87 End If {29 02}
0x1D89 Gray Out If {19 82}
0x1D8B Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1D9D Not {17 02}
0x1D9F End {29 02}
0x1DA1 One Of: AHCI Mode Control, VarStoreInfo (VarOffset/VarName): 0x22, VarStore: 0x2, QuestionId: 0xB, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 11 00 12 00 0B 00 02 00 22 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1DC7 One Of Option: Auto, Value (8 bit): 0x0 (default) {09 0E 13 00 10 00 00 00 00 00 00 00 00 00}
0x1DD5 One Of Option: Manual, Value (8 bit): 0x1 {09 0E 14 00 00 00 01 00 00 00 00 00 00 00}
0x1DE3 End One Of {29 02}
0x1DE5 End If {29 02}
0x1DE7 Suppress If {0A 82}
0x1DE9 QuestionId: 0xB equals value 0x0 {12 06 0B 00 00 00}
0x1DEF Gray Out If {19 82}
0x1DF1 Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1E03 Not {17 02}
0x1E05 End {29 02}
0x1E07 One Of: Set AHCI Mode, VarStoreInfo (VarOffset/VarName): 0x12, VarStore: 0x5, QuestionId: 0xC, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 15 00 16 00 0C 00 05 00 12 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1E2D One Of Option: Disabled, Value (8 bit): 0x0 {09 0E 2C 00 00 00 00 00 00 00 00 00 00 00}
0x1E3B One Of Option: Enabled, Value (8 bit): 0x1 (default) {09 0E 2B 00 10 00 01 00 00 00 00 00 00 00}
0x1E49 End One Of {29 02}
0x1E4B End If {29 02}
0x1E4D End If {29 02}
0x1E4F Suppress If {0A 82}
0x1E51 64 Bit Unsigned Int: 0x1 {45 0A 01 00 00 00 00 00 00 00}
0x1E5B Gray Out If {19 82}
0x1E5D Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1E6F Not {17 02}
0x1E71 End {29 02}
0x1E73 One Of: SATA GEN3 Mode, VarStoreInfo (VarOffset/VarName): 0x148, VarStore: 0x6, QuestionId: 0xD, Size: 1, Min: 0x0, Max 0xFF, Step: 0x0 {05 A6 17 00 18 00 0D 00 06 00 48 01 00 10 00 FF 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1E99 One Of Option: Disabled, Value (8 bit): 0x2 (default) {09 0E 2C 00 10 00 02 00 00 00 00 00 00 00}
0x1EA7 One Of Option: Enabled, Value (8 bit): 0x3 {09 0E 2B 00 00 00 03 00 00 00 00 00 00 00}
0x1EB5 End One Of {29 02}
0x1EB7 End If {29 02}
0x1EB9 End If {29 02}
0x1EBB Gray Out If {19 82}
0x1EBD True {46 02}
0x1EBF Text: Statement.Prompt: , TextTwo: en-US {03 08 2A 00 2A 00 00 00}
0x1EC7 End If {29 02}
0x1EC9 Suppress If {0A 82}
0x1ECB 64 Bit Unsigned Int: 0x1 {45 0A 01 00 00 00 00 00 00 00}
0x1ED5 Gray Out If {19 82}
0x1ED7 Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1EE9 Not {17 02}
0x1EEB End {29 02}
0x1EED One Of: Fan Silent Mode, VarStoreInfo (VarOffset/VarName): 0x23, VarStore: 0x2, QuestionId: 0xE, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 19 00 1A 00 0E 00 02 00 23 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1F13 One Of Option: Low, Value (8 bit): 0x0 {09 0E 1B 00 00 00 00 00 00 00 00 00 00 00}
0x1F21 One Of Option: Auto, Value (8 bit): 0x1 (default) {09 0E 1C 00 10 00 01 00 00 00 00 00 00 00}
0x1F2F End One Of {29 02}
0x1F31 End If {29 02}
0x1F33 End If {29 02}
0x1F35 Gray Out If {19 82}
0x1F37 Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1F49 Not {17 02}
0x1F4B End {29 02}
0x1F4D One Of: Battery Life Cycle Extension, VarStoreInfo (VarOffset/VarName): 0x25, VarStore: 0x2, QuestionId: 0xF, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 1D 00 1E 00 0F 00 02 00 25 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1F73 One Of Option: Disabled, Value (8 bit): 0x0 (default) {09 0E 2C 00 10 00 00 00 00 00 00 00 00 00}
0x1F81 One Of Option: Enabled, Value (8 bit): 0x1 {09 0E 2B 00 00 00 01 00 00 00 00 00 00 00}
0x1F8F End One Of {29 02}
0x1F91 End If {29 02}
0x1F93 Suppress If {0A 82}
0x1F95 64 Bit Unsigned Int: 0x0 {45 8A 00 00 00 00 00 00 00 00}
0x1F9F 64 Bit Unsigned Int: 0x0 {45 0A 00 00 00 00 00 00 00 00}
0x1FA9 Equal {2F 02}
0x1FAB End {29 02}
0x1FAD Gray Out If {19 82}
0x1FAF Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x1FC1 Not {17 02}
0x1FC3 End {29 02}
0x1FC5 One Of: USB Charge In Sleep Mode, VarStoreInfo (VarOffset/VarName): 0x24, VarStore: 0x2, QuestionId: 0x10, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 1F 00 20 00 10 00 02 00 24 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x1FEB One Of Option: Disabled, Value (8 bit): 0x0 (default) {09 0E 2C 00 10 00 00 00 00 00 00 00 00 00}
0x1FF9 One Of Option: Enabled, Value (8 bit): 0x1 {09 0E 2B 00 00 00 01 00 00 00 00 00 00 00}
0x2007 End One Of {29 02}
0x2009 End If {29 02}
0x200B End If {29 02}
0x200D Gray Out If {19 82}
0x200F Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x2021 Not {17 02}
0x2023 End {29 02}
0x2025 One Of: USB S3 Wake-up, VarStoreInfo (VarOffset/VarName): 0x26, VarStore: 0x2, QuestionId: 0x11, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 21 00 22 00 11 00 02 00 26 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x204B One Of Option: Disabled, Value (8 bit): 0x0 (default) {09 0E 2C 00 10 00 00 00 00 00 00 00 00 00}
0x2059 One Of Option: Enabled, Value (8 bit): 0x1 {09 0E 2B 00 00 00 01 00 00 00 00 00 00 00}
0x2067 End One Of {29 02}
0x2069 End If {29 02}
0x206B Suppress If {0A 82}
0x206D True {46 02}
0x206F Gray Out If {19 82}
0x2071 Security: Permissions: [85B75607-F7CE-471E-B7E4-2AEA5F7232EE] {60 92 07 56 B7 85 CE F7 1E 47 B7 E4 2A EA 5F 72 32 EE}
0x2083 Not {17 02}
0x2085 End {29 02}
0x2087 One Of: LID Open S3 Wake-up, VarStoreInfo (VarOffset/VarName): 0x27, VarStore: 0x2, QuestionId: 0x12, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 23 00 24 00 12 00 02 00 27 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x20AD One Of Option: Disabled, Value (8 bit): 0x0 (default) {09 0E 2C 00 10 00 00 00 00 00 00 00 00 00}
0x20BB One Of Option: Enabled, Value (8 bit): 0x1 {09 0E 2B 00 00 00 01 00 00 00 00 00 00 00}
0x20C9 End One Of {29 02}
0x20CB End If {29 02}
0x20CD End If {29 02}
0x20CF Suppress If {0A 82}
0x20D1 True {46 02}
0x20D3 One Of: , VarStoreInfo (VarOffset/VarName): 0x0, VarStore: 0x1, QuestionId: 0x13, Size: 1, Min: 0x0, Max 0x0, Step: 0x0 {05 A6 2A 00 2A 00 13 00 01 00 00 00 00 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
0x20F9 One Of Option: , Value (8 bit): 0x0 {09 0E 2A 00 00 00 00 00 00 00 00 00 00 00}
0x2107 End One Of {29 02}
0x2109 End If {29 02}
0x210B Suppress If {0A 82}
0x210D QuestionId: 0x13 equals value 0x0 {12 06 13 00 00 00}
0x2113 Gray Out If {19 82}
0x2115 True {46 02}
0x2117 Text: Statement.Prompt: , TextTwo: en-US {03 08 2A 00 2A 00 00 00}
0x211F End If {29 02}
0x2121 Gray Out If {19 82}
0x2123 True {46 02}
0x2125 Text: Statement.Prompt: Purchase Date, TextTwo: {03 08 27 00 2A 00 28 00}
0x212D End If {29 02}
0x212F End If {29 02}
0x2131 End Form {29 02}
0x2133 End Form Set {29 02}

Problem is- it's not the default store, so trying to read the variable as mentioned somewhere here like "setvar adress" didn't work. But there's mentioned VarStor 0x6 and in the beginning of the file is a list of stores:
VarStore: VarStoreId: 0x6 [04BD8413-15F9-43F3-9675-4618E03240E3], Size: 0x224, Name: PchProtocolSetupVar.....
Searching for the guid or the name in Uefitool NE doesn't help much, lets try an Efi shell on an USB stick:
There seem to be quite a lot of shells out there- was happy with an older one (EDKII UEFI Shell 2.0, link on this page), It has 2 options- setvar and dumpstore

Displays or modifies a UEFI variable.

SETVAR variable-name [-guid guid][-bs][-rt][-nv] [=data]

variable-name - Specifies the name of the UEFI variable to modify or display.
-guid - Specifies the GUID of the UEFI variable to modify or display.
If not present, GUID EFI_GLOBAL_VARIABLE is assumed.
-bs - Indicates that the variable is a boot variable. Applies to a new variable;
otherwise, it is ignored.
-rt - Indicates that the variable is a runtime variable. Applies to a new variable;
otherwise, it is ignored.
-nv - Indicates that the variable is non-volatile. If not present,
then the variable is assumed to be volatile. Applies to a new variable;
otherwise, it is ignored.
=data - Specifies there is new data for the variable. If there is nothing after the '='
then the variable is deleted. If '=' is not present, then the
current value of the variable is dumped as hex bytes.
The data can consist of zero or more of the following:
xx[xx] - Hexadecimal bytes
^"ascii-string^" - ASCII-string with no null-terminator
L^"UCS2-string^" - UCS-2 encoded string with no
null-terminator
--device - Device path text format

NOTES:
1. This command changes the UEFI variable specified by name and GUID.
2. If = is specified, but data is not, the variable is deleted, if it exists.
3. If = is not specified, then the current variable contents are displayed.
4. If =data is specified, then the variable's value is changed to the value
specified by data.
5. -bs, -rt and -nv are only useful if the variable does not exist.
6. If the variable already exists, the attributes cannot be changed, and the flags will be ignored.

Manages all UEFI variables.

DMPSTORE [-b] [-d] [-all | ([variable] [-guid guid])] [-sfo]
DMPSTORE [-all | ([variable] [-guid guid])] [-s file]
DMPSTORE [-all | ([variable] [-guid guid])] [-l file]

-b - Displays one screen at a time.
-guid - Specifies the GUID of the variables to be displayed in
standard text format. If not specified and -all is not
specified, the EFI_GLOBAL_VARIABLE GUID is assumed.
-sfo - Displays information as described in Standard-Format Output.
-all - Dumps all variables, including those
with a different GUID than EFI_GLOBAL_VARIABLE.
-d - Delete variables.
-s - Saves variables to a file.
-l - Loads and sets variables from a file.
variable - Specifies a variable name. This can be a literal name or
a pattern as specified in the MetaiMatch() function of the
EFI_UNICODE_COLLATION2_PROCOOL.

NOTES:
1. This command manages the UEFI variables. The variables
displayed or deleted depend on the command line options, as specified in
the following table:
Variable GUID -all Description
--- --- --- All variables with the GUID EFI_GLOBAL_VARIABLE will
be operated on.
--- --- X All variables (regardless of GUID or name) will be
operated on.
--- X --- All variables with the specified GUID will be
operated on.
X --- --- The variable with the GUID EFI_GLOBAL_VARIABLE and
the name Variable will be operated on.
X X --- The variable with the specified GUID and name
Variable will be operated on.
2. The variable value is printed as a hexadecimal dump.
3. Option -d is used to delete variables. Option -s and -l are used to save
and load variables to and from a file. The variable name can be specified
when using these flags so that the operation only takes effect on
that variable.

EXAMPLES:
* To dump all variables with the GUID EFI_GLOBAL_VARIABLE:
Shell> dmpstore

* To dump all variables (regardless of GUID or name):
Shell> dmpstore -all

* To dump the 'path' variable with the GUID '158DEF5A-F656-419C-B027-
7A3192C079D2':
Shell> dmpstore path -guid 158DEF5A-F656-419C-B027-7A3192C079D2

* To save all variables (regardless of GUID or name) to a file 'VarDump.txt':
fs0:\> dmpstore -all -s VarDump.txt

* To delete the 'BootOrder' variable with the GUID EFI_GLOBAL_VARIABLE:
Shell> dmpstore -d BootOrder

setvar PchProtocolSetupVar -guid 04BD8413-15F9-43F3-9675-4618E03240E3
will deliver the 224 bytes of this store and the byte I'm looking for should be on 0x148 with a value 02 and should be changed to 03.
(VarStoreId: 0x6 [04BD8413-15F9-43F3-9675-4618E03240E3], Size: 0x224, Name: PchProtocolSetupVar...)
(One Of: SATA GEN3 Mode, VarStoreInfo (VarOffset/VarName): 0x148, VarStore: 0x6, ........
One Of Option: Disabled, Value (8 bit): 0x2 (default) ....
One Of Option: Enabled, Value (8 bit): 0x3 )
Dmpstore does the same, but has the option to save this store to / load from a file. The file has a header, I didn't try to restore the variable store this way.

Now there are several ways to just change this setting:
- Change the byte in the store, save this store back via Dmpstore
- Find the stores in the bios, change it there and flash the complete bios. In this bios there are two places. As the store is described in the list of all stores as non-volatile and boot- variable that sounded reasonable.
"Variable NV+BS '04BD8413-15F9-43F3-9675-4618E03240E3:PchProtocolSetupVar' DataSize = 0x224"
- Change just the bits for the variable. That's what I did, one needs to know the location in the bios, too.

I couldn't find out why this entry for SATA GEN3 is not visible?! As far as I could see the conditions were not different form other entries that are visible?

reply

#17 | RE: Sandy/Ivy Bridge microcode update for Samsung notebook datum

Thu Apr 11, 2019 8:06 am (Last edited: Thu Apr 11, 2019 8:07 am)

Replying to post #15 - Correct way to do that, or possibly safer/easier, simply extract the body of 17088572-377F-44EF-8F4E-B09FFF46A070 (extract body), then edit as you need, then replace body.
Be sure to check your original extract at the very end, some BIOS have a line here as a "Footer" with MPDT as part of it's text, that is not part of microcodes , if you see this put back at the end of your final edit before you replace
You can see example image of that here in my guide, right above "Fixing the FIT Table" section
[GUIDE] Update CPU Microcode + Fix FIT Using UEFITool / Hex

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

#18 | RE: SSD at 6GB/s and Ivy Bridge microcode update for Samsung NP300E5C datum

Wed Apr 17, 2019 8:20 pm (Last edited: Wed Apr 17, 2019 9:50 pm)

Both Phoenix bios I described do look different (NP300E5A 0*QA and NP300E5C 0*RAP). The block with the microcodes cannot be extracted separately. There are two important adresses: Start address for the first microcode and the start address for the next block (CMDB store). Both addresses may not be changed. The microcodes itself are simply stringed together, starting in this block after a header from 0x48.
In addition UEFItool dosen't show the structure of this block, so only possibility is to extract it complete. Since this region is not compressed it doesn't make any difference if you extract something or work with the complete bios or spibackup.

The start addresses for the two blocks one can find in 'Phoenix SCT flash map'.

reply

#19 | RE: SSD at 6GB/s and Ivy Bridge microcode update for Samsung NP300E5C datum

Wed Apr 17, 2019 9:34 pm

Ohh, I see what you mean now that I dig into your BIOS again. Sorry, my previous comment I was thinking in general this BIOS was similar to most others, and I didn't look at the microcode location in your BIOS again, I was only going by rustam2V's images and his BIOS (not the same as yours)
What I mentioned applies to his BIOS, that layout is more normal, and nothing like your BIOS.

reply

#20 | RE: SSD at 6GB/s and Ivy Bridge microcode update for Samsung NP300E5C datum

Wed Apr 17, 2019 10:45 pm (Last edited: Wed Apr 17, 2019 10:56 pm)

I was still looking for a possibility to make the options of the module PlatformHiiAdvancedDxe.efi visible. All the bios pages are in blocks 'SamsungSetup*.efi' and as written before Donovan6000s Universal IFR Extractor can extract the structure/ rules.

I was searching quite a while for a the place where all the GUIDs of the corresponding Bios menus were listed/ chosen. The solution is much easier:
I found accidentally this page [LINK] and it works: Boot into bios (F2), press CTRL + ALT + SHIFT + F4 simultaneously and you get:
On the Info page additional version information and
On the Exit page additional menus, among other items the menus from PlatformHiiAdvancedDxe.efi (CFEF94C4-4167-466A-8893-8779459DFA86), too.

This works for both Samsung notebooks I own- NP300E5A (HM65) and NP300E5C (HM75).
(For the NP300E5A the module is named PlatformSetupAdvacedDxe.efi, but has same Guid)

lfb6 has attached files to this post

PlatformHiiAdvancedDxe.efi.txt

reply

#21 | RE: SSD at 6GB/s and Ivy Bridge microcode update for Samsung NP300E5C datum

Wed Feb 10, 2021 6:51 pm (Last edited: Wed Feb 10, 2021 6:53 pm)

Sorry for resurrecting the thread but I'm encoutering some difficulties with my NP300V5A. What I want to do is updating the BIOS (current version is 05FI, one of the oldest if not the eldest, I think) to latest 10FI with updated microcode for current CPU (i7-2670QM). I also want to add latest microcode for i7-3840QM.
First thing I did was to download Samsung update utility which identified the latest BIOS available and let me download it. Then I followed the first method described by lfb6, so I run the executable and picked up the ROM from AppData/Temp. After this I downladed the two microcode files I needed. Unfortunately, when I run the command with winflash (version 1.5.66) I get a PAGE_FAULT_IN_NONPAGED_AREA BSOD, winFlash64.sys being the crashing module. I am running the latest Windows 10 version (10.0.19042.789): could it be a compatibility issue of the OS with Winflash driver? Because other apps I used to run before are having similar problems with 20H2. I must stress the fact that the BSOD occurs even if I run the regular .exe and follow all the standard procedure to flash the unmodded BIOS.

At this point I've switched to the second method via Phoenix Tool and it seems that I correctly injected the updated microcodes, as shown by MC Extractor (in the link to the screenshot left side is original BIOS, right side modded one):

https://drive.google.com/file/d/1a7gSh5w...iew?usp=sharing

I made sure that the sizes of the two ROMs were identical by overwritingthe empty FFFFFF sections of the original. However, when I try to flash the final rom with Winflash, I receive the following error message at the third stage of the process (I moved a bit the smaller window in order to make everything readable:

https://drive.google.com/file/d/1ySp072f...iew?usp=sharing

What could I try next? Is there something I'm missing? I followed the two procedures, but I'm far from being competent in the matter, so it is of course possible that I'm doing something wrong. Thanks in advance!

reply

#22 | RE: SSD at 6GB/s and Ivy Bridge microcode update for Samsung NP300E5C datum

Wed Feb 10, 2021 6:52 pm (Last edited: Wed Feb 10, 2021 6:53 pm)

@Salve1412
Your laptop is based on HM65 chipset without support Ivy Bridge.
Adding microcode doesn't add support for new CPU.

reply

#23 | RE: Ivy Bridge microcode update for Samsung NP300E5C datum

Wed Feb 10, 2021 7:00 pm (Last edited: Wed Feb 10, 2021 7:08 pm)

Zitat von lfb6 im Beitrag #13
Just to make things complete: The microcode update on te NP300E5C works for an Ivy- Bridge processor, too
For this board with 40 pin LVDS/ camera connector the screen can be updated to 1920 x 1080 (N156HGE-L11). One needs a different LVDS- cable (ba39-01166a) and for models with thin display different mountings/frame.
The older notebook NP300E5A (HM65, i5-2450M) does accept 16 GB of memory, too. Windows 10 works fine and its memory diagnostics reports no fault (2 8 GB- modules Crucial CT102464BF160B).

Zitat von DeathBringer im Beitrag #22
@Salve1412
Your laptop is based on HM65 chipset without support Ivy Bridge.
Adding microcode doesn't add support for new CPU.

Isn't that CMD picture an example of a working Ivy-Bridge CPU on an HM65 chipset board?

EDIt: my bad, it's a HM75 based laptop! Didn't even check it before posting, sorry.
So I guess the only thing I could do would be to update the 2670QM microcode, but still there are these annoying issues with Winflash...

reply

#24 | RE: Ivy Bridge microcode update for Samsung NP300E5C datum

Wed Feb 10, 2021 7:21 pm (Last edited: Wed Feb 10, 2021 7:44 pm)

Samsung built these laptop series with SNB and later on with IVB chipsets, boards are interchangeable. I bought a used E5C board (BA92-11488) and tried first with a SNB CPU (i5-2450M) and switched thereafter to i5-3380M and i7-3820QW (45 instead of 35W), so I wasn't able to check the IVB µcode update in the beginning.

So you might buy a used mainboard on ebay, but there are differences regarding LVDS connector and som boards are HM70 (no core-i support), one has to be careful. In the end it's cheaper to buy a used laptop which is some generations younger...

Otherwise were those Phoenix SNB bioses not very tricky to handle. Probably possible to dump your bios with fpt (ME tools 7 package) to have a backup, change mcode and flash the bios region back. Don't use a stock bios for that, you'd lose your board specific data. And get a backup of the complete bios first.

fpt(w(64)) -d spi.bin should dump the complete bios

In case of an error (locked flash descriptor) would
fpt(w(64)) -bios -d biosreg.bin dump the bios- region

If you want to use a programmer- had to disconnect one wire from the clamp, 2 pins were connected on the board, CH341 didn't like that
[GUIDE] The Beginners Guide to Using a CH341A SPI Programmer/Flasher (With Pictures!) (3)

Good luck!

reply

#25 | RE: Ivy Bridge microcode update for Samsung NP300E5C datum

Wed Feb 10, 2021 7:44 pm (Last edited: Wed Feb 10, 2021 7:45 pm)

Yeah, I was thinking to upgrade the CPU (I found a very cheap 3840QM) only if it wouldn't have entailed purchasing or modding other components. After all it is not a real necessity, I can just stick to the current processor.
Regardind the microcode update of the 2670QM, do you think that those Blue screens when running Winflash could be due to incompatibility with Windows 20H2?
EDIT Oh, I just saw the second part of your post, thanks for the tips!

reply

#26 | RE: Ivy Bridge microcode update for Samsung NP300E5C datum

Wed Feb 10, 2021 7:52 pm

BTW 2670QM is 45W, too, that's 10W plus!

Not using oem tools increases danger for bricking. Do a backup og the bios before you begin! Showing µcode correct in MCE doesn't mean anything, you could put the µcode overwrting vital parts of the bios, mce would display it the same way. Check structure with UEFItoolNE.

reply

7700t es on Zoltac B150 � � [GA-B85-HD3] i5 4460 CPU Microcode 7 - what I'm doing wrong?

Page 2 of 2 � Page 1 2 Page �

Please enter a reason for warning.