Forum - RE: Asus P8P67 Sandybridge support

#766 | RE: Asus P8P67 Sandybridge support datum

Mon Jul 18, 2016 10:56 pm

Actually it's a p3500 which is the same as the 750NVME drive just re-bran with a different enterprise firmware.

Not sure, why it won't detect the hardware. Do you know if there are any BIOS hacks that allow me to flash the board to another firmware to something like the P68 which is vertically the same. Someone already said they got the drive working on a p68

My current System:Mainboard: Z77A-G41 (ASUS P8P67 now dead), CPU: Intel i7 2600K @ 4.8ghz, Disks: 512 GB Samsung 840 Pro SSD + 2 730 Intel SSD + Intel P3500 NVME, Graphics: EVGA ACX SC 780 GTX, RAM: 4x2 GB G.Skill Trident DDR3-16000 @ 2000 Mhz, OS: Windows 10 Pro x64

reply

#767 | RE: Asus P8P67 Sandybridge support datum

Mon Jul 18, 2016 11:32 pm

Zitat von zazzn im Beitrag #764
Do you know if there are any BIOS hacks that allow me to flash the board to another firmware to something like the P68 which is vertically the same.

No, I don't know such hack.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#768 | RE: Asus P8P67 Sandybridge support datum

Tue Jul 19, 2016 2:36 am

I would try different bios versions until you find the one that might by chance work for you. Your going to have to roll up your sleeves if your going to get this working. I would leave the Sata efi driver in your rom and remove something else like a FireWire module or network boot module you'd probably never use. Check out the Ozmosis tutorials on how they make room in their roms for a whole lot more than one file. Also do your testing with a minimal barebones configuration pulling out sound cards and whatever else might be eating lanes and listen to Fernando about using the igpu if possible. Then work up from there.

reply

#769 | RE: G751jy trying to add nvme support datum

Thu Jul 21, 2016 8:32 pm

Hi, I bought recently a Sm951 nvme for my G751jy but it is not recognised by the bios. What should I do to make it work?
Thanks

reply

#770 | RE: G751jy trying to add nvme support datum

Thu Jul 21, 2016 8:39 pm

@Linux86:
Welcome at Win-RAID Forum!

Zitat von Linux86 im Beitrag #767
Hi, I bought recently a Sm951 nvme for my G751jy but it is not recognised by the bios.

What makes you so sure, that it is not recognized? The SSD will not be listed within the "Advanced" section of the BIOS, but may be bootable nevertheless.

Zitat
What should I do to make it work?

If the SSD is not bootable, you should insert the required NVMe EFI module into the BIOS of the mainboard according to the start post of this thread and install the OS in UEFI mode.
Good luck!
Dieter (alias Fernando)

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#771 | RE: G751jy trying to add nvme support datum

Thu Jul 21, 2016 8:44 pm (Last edited: Fri Jul 22, 2016 10:56 am)

Zitat von winyl im Beitrag #474
I just found out it is not nesseary to modify G751JY bios to let the bios see Samsung NVME 950PRO. I modified the bios succcessfuly, added the NvmeExpressDxE to bios, had to delete Mtftp6D module to do so. Bios flashed with afuwinx64 and worked.
Then I copied main HDD to 950pro with minitool patrition manager. I noticed I lost keyboard backlit(and system Information, Serial number on first page of bios) due to afu ereasing nvram, of course I had made backup of the bios chip with afu before I started to tinker with bios flashing.
After copy of Hdd was made I noticed that I have second boot option "Windows Boot Manager" and one option that always has been there "windows Boot Manager P3 HGST type of Hitachi HDD that come standard with G751. I changed this with shift+ so it is the first one. Now 950pro boot the G751 every time, and the boot time is just ridiculous just 5-7s from power button to desktop. Yay it works! I had to flash my backup of bios chip with "nvram program" to get back keyboard backlit. So there you have it,the full story. I installing now SAmsung nvme driver and Samsung magician.
Just found out that UBU corrupts G751jy bios file when updating IRST efi driver and Orom driver. So don,t try to modify bios with UBU for G751. You dobt have to update the IRST driver as on this laptop there is only one M2 port and you can not make raid. If you must have two 950pros in raid get G752 :).

I have read that winyl had a lot of problems with bios modding and I don't know if it's possible to modify g751jy bios without breaking anything.
If winyl reads this post I hope he will send me the modded bios.
Thanks for the quick reply.

reply

#772 | RE: G751jy trying to add nvme support datum

Thu Jul 21, 2016 8:52 pm

Zitat von Linux86 im Beitrag #769
I have read that winyl had a lot of problems with bios modding and I don't know if it's possible to modify g751jy bios without breaking anything.
If winyl reads this post I hope he will send me the modded bios.

It may be a good idea to send him a PM.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#773 | RE: G751jy trying to add nvme support datum

Thu Jul 21, 2016 9:07 pm (Last edited: Thu Jul 21, 2016 10:16 pm)

Zitat von Fernando im Beitrag #770
It may be a good idea to send him a PM.

I did it, thanks for the advice :)

reply

#774 | RE: G751jy trying to add nvme support datum

Fri Jul 22, 2016 10:21 am

I followed the procedures described in the first post and in the winyl's post (I deleted Mtftpd6d, added NvmeExpressDxE and flashed with afuwinx64) and it worked!
Now the SM951 512gb NVME in my G751JY boots without any problem in few seconds!
Thanks very much.

reply

#775 | RE: G751jy trying to add nvme support datum

Fri Jul 22, 2016 10:59 am

@Linux86:
Thanks for your feedback!
Enjoy the performance of your Samsung SM951 running as system drive!

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#776 | RE: Lenovo D30 (C602-based board) datum

Sat Jul 23, 2016 7:03 am (Last edited: Sat Jul 23, 2016 7:18 am)

Zitat von Fernando im Beitrag #763
The Win10 Setup always creates a separate small sized and usually hidden partition containing the boot sector. The only question is, where (on which disk) it is situated.

Hi Fernando, here's a view from Disk manager (run from USB Win10 PE)

(The 120GB SATA SSD was not connected at any time during my testing with the 512GB M.2)

Disk 0 is a SATA SSD that I think I tried to install CentOS on
Disk 1 is the 512GB Samsung Pro in question
Disk 2 is the Win10-PE
Disk 3 is my GPT-UEFI Win10 install USB stick

Does that shed any more info? That look like the necessary partitions have been installed on the 512, no?

When I go to the BIOS boot selection menu I can see a UEFI option for the 120GB SATA SSD of "Windows Boot manager"... not sure why that is but it was not connected at all when I was playing with the 512.

[edit]

Hmm that's interesting. When I go to install Win7 on the 120 and see the partition options I notice there are *four* partitions that the Win10 installer made, not 3 like on the 512:

P1: Recovery - 450MB - OEM Reserve
P2: 100MB - System
P3: 16MB - MSR (Reserved)
P4: 111GB - Primary

So.. the 512 was missing the 16MB MSR Reserved Partition.

Lenovo D30 board (BIOS A1KT57A4), 2 x Xeon 2670, 64GB RAM

reply

#777 | RE: Asus P8P67 Sandybridge support datum

Sat Jul 23, 2016 2:59 pm (Last edited: Sat Jul 23, 2016 4:04 pm)

Zitat von Fernando im Beitrag #750
Since you obviously are running the on-board Intel SATA Controller in AHCI mode, I recommend to remove the Intel EFI RAID module named "SataDriver" and to save the altered BIOS module before you try to insert the NVMe BIOS module.

Hi Fernado,

I want to give this a shot anyways, it seems there is one user that had a P8p67 on the forums that was able to get it to work with the Samsung drive and a PCI-E adapter. I don't see why my p3500 can't be detected.
I don't see "satadriver".
I was thinking of removing TCG, since I don't plan on using the TPM.

This is what the AMI Aptio MMTool shows:

+-----------------------------------------------------------------------------+
| MMTOOL 4.50.0023 |
| Copyright (c)2010 American Megatrends, Inc. |
+-----------------------------------------------------------------------------+
| Firmware Image Information |
+-----------------------------------------------------------------------------+
| Image Size : 400000 |
+------+-------------------------------+--------------+-----------+-----------+
| FV | FV TYPE | Location | Length | FFSs |
+------+-------------------------------+--------------+-----------+-----------+
| 00 | Non-FFS FV | 00180000 | 010000 | 001 |
| 01 | Non-FFS FV | 001A0000 | 1F0000 | 160 |
| 02 | Boot Block FV | 00390000 | 070000 | 053 |
+------+-------------------------------+--------------+-----------+-----------+
| Nested Firmware Volume Information |
+-----------------------------------------------------------------------------+
| Image contains no nested firmware |
+------+-------------------------------+--------------+-----------+-----------+
| NCB Information |
+-----------------------------------------------------------------------------+
| NCB No : 0 Location : 00000000 Length : 180000 |
| NCB No : 1 Location : 00190000 Length : 010000 |
+-----------------------------------------------------------------------------+
| Driver Information |
+-----------------------------------------------------------------------------+
| Firmware Volume : 00 Location : 00180000 Length : 010000 |
+---+---------------+------------------------------------+--------+------+----+
|NO | FileName | GUID |Location| Size |Type|
+---+---------------+------------------------------------+--------+------+----+
|000| |CEF5B9A3-476D-497F-9FDC-E98143E0422C|00180048|00FFB8|RAW |
+---+---------------+------------------------------------+--------+------+----+
| Bytes Free : 000000 ( 0 KB) Bytes Used : 010000 ( 64 KB) |
+-----------------------------------------------------------------------------+
| Firmware Volume : 01 Location : 001A0000 Length : 1F0000 |
+---+---------------+------------------------------------+--------+------+----+
|NO | FileName | GUID |Location| Size |Type|
+---+---------------+------------------------------------+--------+------+----+
|000| |17088572-377F-44EF-8F4E-B09FFF46A070|001A0048|002018|RAW |
|001|CpuDxe |E03ABADF-E536-4E88-B3A0-B77F78EB34FE|001A2060|00187C|DRVR|
|002|ASUSPOSTMessage|1A931FB8-C466-454A-B684-73ADA2CB050B|001A38E0|0003CE|PEIM|
|003|FileSystem |93022F8C-1F09-47EF-BBB2-5814FF609DF5|001A3CB0|004650|DRVR|
|004| |DAC2B117-B5FB-4964-A312-0DCC77061B9B|001A8300|005E97|FRFM|
|005| |9221315B-30BB-46B5-813E-1B1BF4712BD3|001AE198|0002D6|FRFM|
|006|CORE_DXE |5AE3F37E-4EAE-41AE-8240-35465B5E81EB|001AE470|0218A7|DXEC|
|007|Runtime |CBC59C4A-383A-41EB-A8EE-4498AEA567E4|001CFD18|006EED|DRVR|
|008|ReFlash |70E1A818-0BE1-4449-BFD4-9EF68C7F02A8|001D6C08|001D70|DRVR|
|009|PciBus |3C1DE39F-D207-408A-AACC-731CFB7F1DD7|001D8978|007274|DRVR|
|010|AmiBoardInfo |9F3A0016-AE55-4288-829D-D22FD344C347|001DFBF0|004FD6|DRVR|
|011|EBC |13AC6DD0-73D0-11D4-B06B-00AA00BD6DE7|001E4BC8|001B0A|DRVR|
|012|ECDXE |E79A7050-8109-40D1-B3C0-2A3C74090702|001E66D8|001058|DRVR|
|013|ECFWUpdate |585C6240-A0FD-46C3-9B25-1E30648F95C8|001E7730|001948|DRVR|
|014| |2CA21958-67A7-441A-A04A-7090992AAAB3|001E9078|005B23|FRFM|
|015|SIOBasicIODxe |D31EAA20-8436-4E34-9A06-C47C78E19F18|001EEBA0|0006EF|DRVR|
|016|CpuInitDxe |62D171CB-78CD-4480-8678-C6A2A797A8DE|001EF290|0066FA|DRVR|
|017|SmmRelocDxe |7FED72EE-0170-4814-9878-A8FB1864DFAF|001F5990|00072D|DRVR|
|018|SmmRelocPeim |ABB74F50-FD2D-4072-A321-CAFC72977EFA|001F60C0|0005C7|PEIM|
|019|SmmBaseRuntime |5552575A-7E00-4D61-A3A4-F7547351B49E|001F6688|001AB6|DRVR|
|020|SmmDisp |9CC55D7D-FBFF-431C-BC14-334EAEA6052B|001F8140|002D7A|DRVR|
|021|SmmThunk |8D3BE215-D6F6-4264-BEA6-28073FB13AEA|001FAEC0|00073C|DRVR|
|022|CpuPolicyDxe |15B9B6DA-00A9-4DE7-B8E8-ED7AFB88F16E|001FB600|000D38|DRVR|
|023|MicrocodeUpdate|F3331DE6-4A55-44E4-B767-7453F7A1A021|001FC338|002ABB|DRVR|
|024|CpuSmmSaveRes |326E7ACE-2133-1BA2-800A-B9C00ACCB17D|001FEDF8|000D56|DRVR|
|025|CpuSpSMI |116E1ACF-2533-4CC2-820A-BBC10A2AB07C|001FFB50|000A2E|DRVR|
|026|SBDXE |B7D19491-E55A-470D-8508-85A5DFA41974|00200580|003DFC|DRVR|
|027|SBRun |E23F86E1-056E-4888-B685-CFCD67C179D4|00204380|00141E|DRVR|
|028| |22046D50-F390-498C-92E5-5BA4F8E7F8B6|002057A0|000202|FRFM|
|029|SmmChildDispatc|753630C9-FAE5-47A9-BBBF-88D621CD7282|002059A8|00155A|DRVR|
|030|SmmChildDispatc|E53734A3-E594-4C25-B1A2-081445650F7F|00206F08|001CE1|DRVR|
|031|AcpiModeEnable |750890A6-7ACF-4F4F-81BD-B400C2BEA95A|00208BF0|001022|DRVR|
|032|SleepSmi |6298FE18-D5EF-42B7-BB0C-2953283F5704|00209C18|0013C9|DRVR|
|033|SBSMI |7B8DB049-C7C7-4D3B-809F-926DEE47CCA2|0020AFE8|001807|DRVR|
|034|PchSpiWrap |B716A6F8-F3A1-4B8E-8582-5A303F1CDD64|0020C7F0|0006D9|DRVR|
|035|WdtAppDxe |CE366D33-B057-4C03-8561-CAF17738B66F|0020CED0|000789|DRVR|
|036|ActiveBios |BFD59D42-FE0F-4251-B772-4B098A1AEC85|0020D660|00041F|DRVR|
|037|IoTrap |2374EDDF-F203-4FC0-A20E-61BAD73089D6|0020DA80|000E2D|DRVR|
|038|IntelLegacyInte|C1C418F9-591D-461C-82A2-B9CD96DFEA86|0020E8B0|00022E|DRVR|
|039|PchInitDxe |DE23ACEE-CF55-4FB6-AA77-984AB53DE823|0020EAE0|00575E|DRVR|
|040|PchSmiDispatcher|B0D6ED53-B844-43F5-BD2F-61095264E77E|00214240|0024B0|DRVR|
|041|PchPcieSmm |ACAEAA7A-C039-4424-88DA-F42212EA0E55|002166F0|00150B|DRVR|
|042|PchReset |BB1FBD4F-2E30-4793-9BED-74F672BC8FFE|00217C00|000791|DRVR|
|043|PchS3Peim |271DD6F2-54CB-45E6-8585-8C923C1AC706|00218398|00153C|PEIM|
|044|PchS3Support |08F2C63B-08DE-4CCD-8670-ACFE644A1C48|002198D8|000799|DRVR|
|045|SataController |BB65942B-521F-4EC3-BAF9-A92540CF60D2|0021A078|000E18|DRVR|
|046|PchSerialGpio |FC1B7640-3466-4C06-B1CC-1C935394B5C2|0021AE90|000755|DRVR|
|047|SmartTimer |90CB75DB-71FC-489D-AACF-943477EC7212|0021B5E8|00044D|DRVR|
|048|PchSmbusDxe |E052D8A6-224A-4C32-8D37-2E0AE162364D|0021BA38|000F26|DRVR|
|049|SmmControl |A0BAD9F7-AB78-491B-B583-C52B7F84B9E0|0021C960|000598|DRVR|
|050|PchSpiSmm |27F4917B-A707-4AAD-9676-26DF168CBF0D|0021CEF8|0015DA|DRVR|
|051|PchSpiRuntime |C194C6EA-B68C-4981-B64B-9BD271474B20|0021E4D8|0016A3|DRVR|
|052|PchSmbusSmm |59287178-59B2-49CA-BC63-532B12EA2C53|0021FB80|000C00|DRVR|
|053|WdtDxe |5AAB83E5-F027-4CA7-BFD0-16358CC9E453|00220780|000640|DRVR|
|054|NBDXE |E4ECD0B2-E277-4F2B-BECB-E4D75C9A812E|00220DC0|00256C|DRVR|
|055|NBSMI |D933DEDE-0260-4E76-A7D9-2F9F2440E5A5|00223330|00109F|DRVR|
|056|MiscSubclassDxe|16271FCA-55D9-4A33-93FC-5A3EB128DE21|002243D0|0007C8|DRVR|
|057|UpdateMemoryRec|24CCD374-3DF6-4181-86F6-E3C66920A145|00224B98|00113F|DRVR|
|058|PciExpressDxe |A89EC8E0-0BA1-40AA-A03E-ABDDA5295CDE|00225CD8|0014E8|DRVR|
|059|PciHostBridge |8D6756B9-E55E-4D6A-A3A5-5E4D72DDF772|002271C0|0016C4|DRVR|
|060|SmBiosMemory |EDA39402-F375-4496-92D3-83B43CB8A76A|00228888|00178A|DRVR|
|061|SmmAccess |1323C7F8-DAD5-4126-A54B-7A05FBF41515|0022A018|0006C7|DRVR|
|062| |27E569D5-0AFC-4D8F-8C90-783AC4A318AB|0022A6E0|00009F|FRFM|
|063|SaInitDxe |DE23ACEE-CF55-4FB6-AA77-984AB53DE811|0022A780|002EBB|DRVR|
|064|BdatAccessHandl|6DB9486F-6AF6-4090-984D-238482CE3EA4|0022D640|0004D4|DRVR|
|065|SaLateInitSmm |2D1E361C-7B3F-4D15-8B1F-66E551FABDC7|0022DB18|001289|DRVR|
|066|ACPI |16D0A23E-C09C-407D-A14A-AD058FDD0CA1|0022EDA8|004705|DRVR|
|067| |26A2481E-4424-46A2-9943-CC4039EAD8F8|002334B0|0017DE| |
|068|S3Restore |EFD652CC-0E99-40F0-96C0-E08C089070FC|00234C90|0014FC|PEIM|
|069|EzFlash_Compati|F54D676F-ED6F-43CE-B4E5-A8CC580B0BC2|00236190|0006CA|DRVR|
|070|ASUSBackup |98584C0B-49D6-4BAF-B542-ECEE2582409C|00236860|002B0E|DRVR|
|071|ASUSBackupSmm |174CF46D-B167-4E6A-B1CD-D41E24EFA0F9|00239370|000ADD|DRVR|
|072|MSOA |A1902AB9-5394-45F2-857A-12824213EEFB|00239E50|0011DA|DRVR|
|073|AGI |E79A7050-8109-40D1-B3C0-2A3C74C40204|0023B030|0035B3|DRVR|
|074|AHCI |8F5A2E02-538C-4D59-B920-C4786ACBC552|0023E5E8|0037C4|DRVR|
|075|AINT13 |67820532-7613-4DD3-9ED7-3D9BE3A7DA63|00241DB0|000F73|DRVR|
|076|AhciSmm |BC3245BD-B982-4F55-9F79-056AD7E987C5|00242D28|001667|DRVR|
|077|AMITSE |B1DA0ADF-4F77-4070-A88E-BFFE1C60529A|00244390|028A9F|DRVR|
|078| |A59A0056-3341-44B5-9C9C-6D76F7673817|0026CE30|0000A1|FRFM|
|079| |294B1CEF-9BEB-42D5-9971-0C8963CDAF02|0026CED8|000AE6|FRFM|
|080|ASUSPOSTMessage|177B2C74-9674-45F4-AAEB-43F5506AE0FE|0026D9C0|002941|DRVR|
|081|ACPIRAM |37DA43A1-BB9A-4805-9B92-0BDE11191149|00270308|0012E0|DRVR|
|082|ASUSFTMDXE |3C35B99D-D4B7-4885-ABD9-2BEA4B9F3A01|002715E8|000773|DRVR|
|083|ASUS_MEUpdate_D|68DB9E58-4B9C-4E60-8DA6-9A714DC3EDD3|00271D60|0016DC|DRVR|
|084|AcpiPlatform |8B5FBABD-F51F-4942-BF16-16AAA38AE52B|00273440|001B0F|DRVR|
|085|AcpiPlatformSmi|DFD8D5CC-5AED-4820-A2B6-5C55E4E640EF|00274F50|000904|DRVR|
|086|PlatformInfo |1314216C-CB8D-421C-B854-06231386E642|00275858|000648|DRVR|
|087|SMBIOSUpdateData|B98999A4-E96F-475A-99FC-762126F50F5A|00275EA0|00060E|DRVR|
|088|CSMCORE |A062CF1F-8473-4AA3-8793-600BC4FFE9A8|002764B0|0302C9|DRVR|
|089| |A08276EC-A0FE-4E06-8670-385336C7D093|002A6780|000409|FRFM|
|090|BIOSBLKIO |25ACF158-DD61-4E64-9A49-55851E9A26C7|002A6B90|001949|DRVR|
|091|CsmVideo |29CF55F8-B675-4F5D-8F2F-B87A3ECFD063|002A84E0|00242A|DRVR|
|092|CmosManagerSmm |6869C5B3-AC8D-4973-8B37-E354DBF34ADD|002AA910|001AC8|DRVR|
|093|EzFlashDxe |FC63ED62-949D-4FB0-B754-D558A6367C56|002AC3D8|000A89|DRVR|
|094|EzFlash |3470CCF0-6054-11DD-AD8B-0800200C9A66|002ACE68|006FDE|APPN|
|095| |3DCE5A33-0152-4B67-99DC-B8E0A25DDF59|002B3E48|0057EA|FRFM|
|096| |0E0DB566-F7A9-4DBF-9A74-FA5B1371A12F|002B9638|003118|FRFM|
|097|EzSetup |210DCB72-BC14-4A19-A29B-F696EB7DE12B|002BC750|007FE5|DRVR|
|098| |4B13CE01-3370-466E-A251-4D0AB6B5A9E8|002C4738|039AEA|FRFM|
|099|EzSetupPortingD|84DDA68C-CA5A-4C30-9261-DD6DE7E45A95|002FE228|001EBD|DRVR|
|100|ScreenCap |9257B1B6-82DF-4B69-A83B-C16D671B9A9F|003000E8|001AFB|DRVR|
|101|FsIso9660 |D5D52FED-F8A6-49AC-97AC-7291A60405A6|00301BE8|001246|DRVR|
|102|HWM_SetupDXE |80023209-6386-4C1D-909B-63506A2146FF|00302E30|00092B|DRVR|
|103|QFanDXE |157C666C-7C74-4E4A-B639-7BBA21487CE1|00303760|000CEE|DRVR|
|104|IdeSMART |D57C852E-809F-45CF-A377-D77BC0CB78EE|00304450|0017CE|DRVR|
|105|HeciDxe |55E76644-78A5-4A82-A900-7126A5798892|00305C20|001BF3|DRVR|
|106|HeciSmm |921CD783-3E22-4579-A71F-00D74197FCC8|00307818|000E98|DRVR|
|107|PlatformReset |9A9A912B-5F53-4586-8820-704485A29D21|003086B0|000800|DRVR|
|108|MdesStatusCodeD|DF5CD25A-8E55-46BA-8CDA-BC7DB7BF9C64|00308EB0|000752|DRVR|
|109|MeFwDowngrade |5820EEB4-C135-4854-9D2A-AA9EFC4475E9|00309608|000782|DRVR|
|110|MePlatformPolicy|BA67550C-3628-4137-A53E-42660E081604|00309D90|0009FF|DRVR|
|111|IccOverclocking|CA5D7EB0-1B67-4B0B-964A-F2A861F0D640|0030A790|000AD1|DRVR|
|112|OCMR_DXE |472A583E-70CF-465A-BB77-53ADFCDB5883|0030B268|002045|DRVR|
|113|MePciPlatform |459C70C3-9344-4484-9F93-7822530D0D11|0030D2B0|00045B|DRVR|
|114|IccPlatform |14257B56-BDA2-4FAF-8E4F-C885DF75583C|0030D710|000B10|DRVR|
|115|IccOverClocking|5BBA83E5-F027-4CA7-BFD0-16358CC9E123|0030E220|00250A|DRVR|
|116|Ntfs |BE33A7B9-13CB-464E-BF5B-B97A9F5730CA|00310730|00172F|DRVR|
|117|NvRamFailureRec|EAA45AAF-947A-44A2-AF38-5984C149D5E6|00311E60|000841|DRVR|
|118| |CEF5B9A3-476D-497F-9FDC-E98143E0422C|003126A8|000371|FRFM|
|119|OCMR_PEI |C7542254-A8F7-40BA-9BB9-390D31977775|00312A20|002B9A|PEIM|
|120| |77840A38-8AB1-4D7A-9181-03B2F5B34C0B|003155D8|001A18|RAW |
|121|PEfirmwareupdat|97AF1D95-203C-42DE-8D6B-D13EB7E5A55A|00316FF0|001932|DRVR|
|122| |4ED407CE-411E-4ADE-8A93-8A34D79F4B52|00318928|005E18|RAW |
|123|PEbiosinterface|AEF82756-87F2-4CF6-BE80-E59055295AA1|0031E740|004CD1|DRVR|
|124|PowerManagement|8C783970-F02A-4A4D-AF09-8797A51EEC8D|00323418|002EDC|DRVR|
|125| |299141BB-211A-48A5-92C0-6F9A0A3A006E|003262F8|000938|FRFM|
|126|AmiPpmPolicy |1CE12314-AFBC-11F0-8A3E-AB44B8EE3120|00326C30|000EC0|DRVR|
|127|ResLoader |5C0FB3B9-F7BB-467B-A4DC-89D7D5A58432|00327AF0|0008DA|DRVR|
|128|SMBiosBoard |CEF68C66-06AB-4FB3-A3ED-5FFA885B5725|003283D0|000C72|DRVR|
|129|SMBios64 |B13EDD38-684C-41ED-A305-D7B7E32497DF|00329048|00282C|DRVR|
|130|SmbiosGetFlashD|DED7956D-7E20-4F20-91A1-190439B04D5B|0032B878|00075F|DRVR|
|131| |DAF4BF89-CE71-4917-B522-C89D32FBC59F|0032BFD8|0004BA|FRFM|
|132|SmbiosDMIEdit |E2A74738-8934-48F5-8412-99E948C8DC1B|0032C498|0017A7|DRVR|
|133|SMIFlash |BC327DBD-B982-4F55-9F79-056AD7E987C5|0032DC40|002CA7|DRVR|
|134|TcgPlatformSetu|196CA3D8-9A5A-4735-B328-8FFC1D93D188|003308E8|0009D3|DRVR|
|135|TcgDxe |5E9CABA3-F2B1-497A-ADAC-24F575E9CDE9|003312C0|0029A2|DRVR|
|136|TcgDxeplatform |2688B232-9C02-4C12-BE1F-857C0FF2AAE3|00333C68|0007EA|DRVR|
|137|TCGSmm |FD93F9E1-3C73-46E0-B7B8-2BBA3F718F6C|00334458|000CE8|DRVR|
|138|TcgLegacy |858EBE6F-360F-415B-B7DC-463AAEB03412|00335140|000CC4|DRVR|
|139|AmiTcgPlatformD|A29A63E3-E4E7-495F-8A6A-07738300CBB3|00335E08|0032BF|DRVR|
|140| |0AA31BC6-3379-41E8-825A-53F82CC0F254|003390C8|00134F|FRFM|
|141| |142204E2-C7B1-4AF9-A729-923758D96D03|0033A418|0006D0|FRFM|
|142| |7D113AA9-6280-48C6-BACE-DFE7668E8307|0033AAE8|0003B6|FRFM|
|143|AmiTcgNvflagSam|50F6096D-7C98-4C78-9A1D-C5A1833B6A88|0033AEA0|0009AD|DRVR|
|144| |3D9D911C-510E-4834-95A7-7E3E1DEE6778|0033B850|015E74|FRFM|
|145|USBRT |04EAAAA1-29A1-11D7-8838-00500473D4EB|003516C8|008C1F|DRVR|
|146|UHCD |580DD900-385D-11D7-883A-00500473D4EB|0035A2E8|00602E|DRVR|
|147|USBINT13 |4C006CD9-19BA-4617-8483-609194A1ACFC|00360318|000D05|DRVR|
|148|OEMDXE |BFE205C9-5B17-4F8F-9375-89614AF8E199|00361020|000801|DRVR|
|149|Setup |899407D7-99FE-43D8-9A21-79EC328CAC21|00361828|01E30E|DRVR|
|150| |7BB28B99-61BB-11D5-9A5D-0090273FC14D|0037FB38|00689B|FRFM|
|151|CspLibDxe |CD84562C-6864-40A3-A081-C8D35E82B920|003863D8|0000C5|DRVR|
|152|AsusPostErrPei |52715B77-04A5-487A-B980-CDC371B5BEC8|003864A0|0006FA|PEIM|
|153|AsusPostErrDxe |54AB7A17-AD08-4F86-83C2-4CF398EBC0AD|00386BA0|000EB9|DRVR|
|154|EpuHwModeDxe |21E34727-3881-4DEE-8020-D8908A980311|00387A60|000BA1|DRVR|
|155|OnBrdDevDXE |1DACE8EE-CD97-491E-8A0C-305D6437323C|00388608|001C06|DRVR|
|156|ASUS_EUPSxSMI |D36DDD2D-1C66-4210-B77A-2FD9F920E51F|0038A210|000AA4|DRVR|
|157|ProjectSxSMI |3F78CB8D-72EE-414E-B023-DACA003BDDF5|0038ACB8|00130B|DRVR|
|158|ProjectDXE |010216CD-9C09-4EB5-B7DA-D0A2865092D4|0038BFC8|000C26|DRVR|
|159|PcieLaneDXE |2F4DDD35-F8C0-46D2-B0E3-A701360D7499|0038CBF0|000CD4|DRVR|
+---+---------------+------------------------------------+--------+------+----+
| Bytes Free : 002750 ( 9 KB) Bytes Used : 1ED8B0 (1974 KB) |
+-----------------------------------------------------------------------------+
| Firmware Volume : 02 Location : 00390000 Length : 070000 |
+---+---------------+------------------------------------+--------+------+----+
|NO | FileName | GUID |Location| Size |Type|
+---+---------------+------------------------------------+--------+------+----+
|000|MemoryInit |3B42EF57-16D3-44CB-8632-9FDB06B41451|00390048|02B162|PEIM|
|001| |17088572-377F-44EF-8F4E-B09FFF46A070|003BB1C8|005018|RAW |
|002|UsbBotPeim |8401A046-6F70-4505-8471-7015B40355E3|003C01E0|002C5B|PEIM|
|003|Recovery |E008B434-0E73-440C-8612-A143F6A07BCB|003C2E40|00280E|PEIM|
|004|CRBPEI |0D1ED2F7-E92B-4562-92DD-5C82EC917EAE|003C5650|0007DA|PEIM|
|005|ECPEI |1B2501AD-1116-4958-B8C3-2739C188710A|003C5E30|000954|PEIM|
|006|WdtPei |1D88C542-9DF7-424A-AA90-02B61F286938|003C6788|000796|PEIM|
|007|CORE_PEI |92685943-D810-47FF-A112-CC8490776A1F|003C6F20|00A352|PEIC|
|008|SIOBasicIOPei |0B4BDCFF-74B2-45AD-91E1-8F6634C8A1DC|003D1278|000824|PEIM|
|009|CpuInitPei |01359D99-9446-456D-ADA4-50A711C03ADA|003D1AA0|001D2E|PEIM|
|010|CpuS3Peim |C866BD71-7C79-4BF1-A93B-066B830D8F9A|003D37D0|001490|PEIM|
|011|SmmBasePeim |8B8214F9-4ADB-47DD-AC62-8313C537E9FA|003D4C60|000560|PEIM|
|012|CpuPolicyPei |0AC2D35D-1C77-1033-A6F8-7CA55DF7D0AA|003D51C0|000B22|PEIM|
|013|CpuPeiBeforeMem|1555ACF3-BD07-4685-B668-A86945A4124D|003D5CE8|000240|PEIM|
|014|CpuPei |2BB5AFA9-FF33-417B-8497-CB773C2B93BF|003D5F28|00150E|PEIM|
|015|SBPEI |C1FBD624-27EA-40D1-AA48-94C3DC5C7E0D|003D7438|0036D8|PEIM|
|016|AcpiPlatformPei|333BB2A3-4F20-4C8B-AC38-0672D74315F8|003DAB10|00039C|PEIM|
|017|SmBusPei |9EA28D33-0175-4788-BEA8-6950516030A5|003DAEB0|000FAA|PEIM|
|018|WdtAppPei |0F69F6D7-0E4B-43A6-BFC2-6871694369B0|003DBE60|00042C|PEIM|
|019|PchInitPeim |FD236AE7-0791-48C4-B29E-29BDEEE1A838|003DC290|0032E0|PEIM|
|020|PchResetPeim |FF259F16-18D1-4298-8DD2-BD87FF2894A9|003DF570|000862|PEIM|
|021|PchSmbusArpDisa|643DF777-F312-42ED-81CC-1B1F57E18AD6|003DFDD8|000BA0|PEIM|
|022|PchSpiPeim |AA652CB9-2D52-4624-9FAE-D4E58B67CA46|003E0978|00159E|PEIM|
|023|PchUsb |6B4FDBD2-47E1-4A09-BA8E-8E041F208B95|003E1F18|000372|PEIM|
|024|NBPEI |79AA6086-035A-4AD9-A89A-A6D5AA27F0E2|003E2290|002878|PEIM|
|025|SmmAccessPeim |6ECFCE51-5724-450C-A38A-58553E954422|003E4B08|000884|PEIM|
|026|SaInitPeim |FD236AE7-0791-48C4-B29E-29BDEEE1A811|003E5390|0047E2|PEIM|
|027|BootPriority |5F6A843E-D188-41A3-BA3C-A83D8997DC7F|003E9B78|00080C|DRVR|
|028| |9A1E0C57-9FA9-437B-84E6-8254FEF3ACE3|003EA388|000246|RAW |
|029|HeciPei |9CF30325-DC5C-4556-A8B0-74215C5F7FC4|003EA5D0|000BF8|PEIM|
|030|PchMeUma |8C376010-2400-4D7D-B47B-9D851DF3C9D1|003EB1C8|00092E|PEIM|
|031|MePeiPolicyInit|12C67BE1-AD2E-4F13-A95F-6EDC2C4392DE|003EBAF8|000538|PEIM|
|032|MouseDriver |2ADB8F5B-C7D4-4E7E-BE2A-23634DF668A1|003EC030|001400|DRVR|
|033| |FD44820B-F1AB-41C0-AE4E-0C55556EB9BD|003ED430|000228|FRFM|
|034|TcgPlatformSetu|0FE9DA53-043D-4265-A94D-FD77FEDE2EB4|003ED658|00064C|PEIM|
|035|TcgPei |34989D8E-930A-4A95-AB04-2E6CFDFF6631|003EDCA8|0024F6|PEIM|
|036|TcgPeiAfterMem |12345678-930A-4A95-AB04-2E6CFDFF6631|003F01A0|000ED6|PEIM|
|037|TcgPeiplatform |6B844C5B-6B75-42CA-8E8E-1CB94412B59B|003F1078|000416|PEIM|
|038|AmiTcgPlatformP|9B3F28D5-10A6-46C8-BA72-BD40B847A71A|003F1490|0013E2|PEIM|
|039|AmiTcgPlatformP|E9312938-E56B-4614-A252-CF7D2F377E26|003F2878|00120E|PEIM|
|040| |0DCA793A-EA96-42D8-BD7B-DC7F684E38C1|003F3A88|0000BC|FRFM|
|041|CRBDXE |16271FCA-55D9-4A33-93FC-5A3EB128DEB6|003F3B48|0004A5|DRVR|
|042|CRBSMI |221F1D4F-034C-4BEA-B2BB-B7A9672B06D7|003F3FF0|000936|DRVR|
|043| |3FD1D3A2-99F7-420B-BC69-8BB1D492A332|003F4928|0000A4|FRFM|
|044|ASUSHeaderPEI |4CC14F19-C626-4AB6-9DEA-CA6C01FD10CD|003F49D0|00031C|PEIM|
|045|RemoveASFDXE |077AFE00-4404-47E7-A4C7-B673580F8D5D|003F4CF0|0005E7|DRVR|
|046|BBVideo |E1AF9F5B-7CDE-4F98-91ED-5E67868282B8|003F52D8|003067|PEIM|
|047| |532CED8F-1BA8-46CB-A437-C6C2E9058A5A|003F8340|00030D|RAW |
|048|EpuHwModePei |362C7275-4D8F-4607-8D8F-28893A8ACD60|003F8650|00111A|PEIM|
|049|ASUS_EUPPEI |7DADBC98-6489-4D1C-907A-8EE243AF805B|003F9770|000520|PEIM|
|050|SynBootabletVar|BFD8ABE9-C091-6543-A94D-136E5BADD22D|003F9C90|000F5E|DRVR|
|051|ProjectPEI |29BE380A-FBC0-462B-A6C2-5C5A076CAFDE|003FABF0|00043E|PEIM|
|052| |1BA0062E-C779-4582-8566-336AE8F78F09|003FF4A0|000B60|SECC|
+---+---------------+------------------------------------+--------+------+----+
| Bytes Free : 004488 ( 17 KB) Bytes Used : 06BB78 (430 KB) |
+-----------------------------------------------------------------------------+
| Total Bytes Free : 006BD8 ( 26 KB) Total Bytes Used : 3F9428 (4069 KB) |
+-----------------------------------------------------------------------------+

EDIT by Fernando: To save space, I have inserted the MMTool details into a "spoiler" and removed unneeded parts of the fully quoted text and blank lines.

My current System:Mainboard: Z77A-G41 (ASUS P8P67 now dead), CPU: Intel i7 2600K @ 4.8ghz, Disks: 512 GB Samsung 840 Pro SSD + 2 730 Intel SSD + Intel P3500 NVME, Graphics: EVGA ACX SC 780 GTX, RAM: 4x2 GB G.Skill Trident DDR3-16000 @ 2000 Mhz, OS: Windows 10 Pro x64

reply

#778 | RE: Asus P8P67 Sandybridge support datum

Sat Jul 23, 2016 4:26 pm

@daynomate:

Zitat von daynomate im Beitrag #774
Does that shed any more info?

Not really.

Zitat
That look like the necessary partitions have been installed on the 512, no?

The shown partitions of Disk 1 (your 512 GB Samsung NVMe SSD) look fine and don't indicate any reason why you were not able to reboot after the first part of the OS installation.
Maybe your special mainboard BIOS needs an NVMe EFI module with a slightly different code.

Zitat
Hmm that's interesting. When I go to install Win7 on the 120 and see the partition options I notice there are *four* partitions that the Win10 installer made, not 3 like on the 512:
So.. the 512 was missing the 16MB MSR Reserved Partition.

This partition is not essential. The Disk Management of my Win10 system doesn't show this partition either.

@zazzn:

Zitat von zazzn im Beitrag #775
I want to give this a shot anyways, it seems there is one user that had a P8p67 on the forums that was able to get it to work with the Samsung drive and a PCI-E adapter. I don't see why my p3500 can't be detected.
I don't see "satadriver". I was thinking of removing TCG, since I don't plan on using the TPM.

Good luck!

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

#779 | RE: Asus P8P67 Sandybridge support datum

Sat Jul 23, 2016 4:43 pm

@Fernando Looks like it still doesn't detect. The very strange thing is if I force to UEFI, the machine will hang at the splash screen, until I clear the CMOS. then it will work and be forced to legacy.

Microcode will not help here right it's just updating the CPU detection? Is there something that I can rip out of another newer Asus BIOS that is responsible for hardware detection at all?

My current System:Mainboard: Z77A-G41 (ASUS P8P67 now dead), CPU: Intel i7 2600K @ 4.8ghz, Disks: 512 GB Samsung 840 Pro SSD + 2 730 Intel SSD + Intel P3500 NVME, Graphics: EVGA ACX SC 780 GTX, RAM: 4x2 GB G.Skill Trident DDR3-16000 @ 2000 Mhz, OS: Windows 10 Pro x64

reply

#780 | RE: Asus P8P67 Sandybridge support datum

Sat Jul 23, 2016 6:39 pm

Zitat von zazzn im Beitrag #777
Looks like it still doesn't detect.

What do you mean? The BIOS and Windows obviously both have detected the NVMe SSD.
The problem seems to be the initialization of the SSD as bootable drive.

Zitat
The very strange thing is if I force to UEFI, the machine will hang at the splash screen, until I clear the CMOS. then it will work and be forced to legacy.

What do you mean with "force to UEFI"? You should not try to disable the CSM completely, because your mainboard BIOS doesn't contain working EFI modules for all important devices (Intel Graphics, LAN etc.).

Zitat
Microcode will not help here right it's just updating the CPU detection?

The CPU Microcode has nothing to do with your boot problem.

Zitat
Is there something that I can rip out of another newer Asus BIOS that is responsible for hardware detection at all?

You can replace the recetly inserted NVMe module by another one taken from a newer ASUS mainboard and look, what happens, but I am rather unsure, whether this procedure will solve your current problem.

My current System:
MB: ASRock X570 Pro4, CPU: AMD Ryzen 5 3600, System Drive: 500 GB Samsung 980 Pro, Graphics: Sapphire Radeon RX570, OS: Win10 x64 Pro
Donation Link:
If you are satisfied with my Forum activities, you can send a donation to my personal PayPal account by clicking onto >this< link.

reply

Please enter a reason for warning.