Bios Mods -The Best BIOS Update and Modification Source

Full Version: Please help with asus black screen (no logo, no bios)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8 9 10 11
Not sure on this 15 second stall, Intel ME is messed up, check with device manager and see if it's got a yellow warning, and see if ME version shows in the BIOS or HWINFo64. Could also be some BIOS setting not same now as you had before

Key is in the BIOS, but maybe not all hardware ID needed components in the NVRAM, that's why I made those other BIOS just now for you, those are the last two things I left out this time around that I put before when it did activate properly.
Okay.

I am trying the bios New-DBX-PK-SMI-Only303-HDWCFG.

Patience please. Smile Smile Smile


*EDIT:


This is the New-DBX-PK-SMI-Only303-AEDID-HDWCFG.rom file with small changes: Smile

But no sound on boot, no static logo and still stalling 15 seconds.

[Image: jtp6cy.png]

[Image: 157ghlg.png]


Impossible to install the ME. I do not understand.

"This computer does not meet the minimum requirements for installing the software"

In the device manager, everything is OK.


[Image: 2vvp6iw.png]

[Image: w02n36.png]
ME drivers is all you install in windows, ME FW is BIOS stuff, and just because you see it in ME Analyzer does not mean it is functional.
Let's check ME functionality, this may be why it's stalling 15 second at startup (This is what I thought of as soon as you mentioned), and could also be the cause of the logo/audio issue (Or maybe this BIOS does not contain the related files (img + audio file)

Download this package, not sure if I linked you to complete tools package before or not?
https://mega.nz/#!uQV12IxD!KGAUutQZrdL7T...zGkt5K5EWU

Download this and inside find MEInfo folder, then run both of the following commands and post an image of the complete output from each
MEInfoWin -verbose
MEInfoWin -fwsts
Quote:Let's check ME functionality, this may be why it's stalling 15 second at startup (This is what I thought of as soon as you mentioned), and could also be the cause of the logo/audio issue)

I think so.


Quote:Or maybe this BIOS does not contain the related files (img + audio file)

The asus logo exists, sometimes appears for 1-2 seconds.


Quote:MEInfoWin -verbose


Code:
Intel(R) MEInfo Version: 9.1.45.3000
Copyright(C) 2005 - 2017, Intel Corporation. All rights reserved.
FW Status Register1: 0x00004191
FW Status Register2: 0x167B2100
FW Status Register3: 0x00000200
FW Status Register4: 0x00000000
FW Status Register5: 0x00000000
FW Status Register6: 0x00000000

  CurrentState:                         Init
  ManufacturingMode:                    Enabled
  FlashPartition:                       Valid
  OperationalState:                     Bring Up
  InitComplete:                         Initializing
  BUPLoadState:                         Success
  ErrorCode:                            Debug Error
  ModeOfOperation:                      Normal
  Phase:                                BringUp
  ICC:                                  No valid OEM data, ICC not programmed
  ME File System Corrupted:             No
  PhaseStatus:                          PCH ID MISMATCH

HECI device is found to be disabled.
Error 9256: Communication error between application and Intel(R) ME module (FW Update client)
Error 0099: Unknown error code
Error 9256: Communication error between application and Intel(R) ME module (FW Update client)
Error 0099: Unknown error code
Error 9256: Communication error between application and Intel(R) ME module (FW Update client)
Error 0099: Unknown error code

  Windows OS Version : 6.1.7601 "Service Pack 1"
  OS BIOS Support    : Legacy  


SMBIOS Table Data
    SM BIOS Spec Version :    2.7
    Starting address:         0x EBF30
    Table Size in Bytes:        1577   ( 0x629 )
    Number of Table Entries:   the    22   ( 0x16 )

    Virtual mapping of complete Table:  2 4kB Pages
    Table Type   0 ( 0x 00 ) found, size of  24 (0x 18 ) bytes

  Windows OS Version : 6.1.7601 "Service Pack 1"
  OS BIOS Support    : Legacy  


SMBIOS Table Data
    SM BIOS Spec Version :    2.7
    Starting address:         0x EBF30
    Table Size in Bytes:        1577   ( 0x629 )
    Number of Table Entries:   the    22   ( 0x16 )

    Virtual mapping of complete Table:  2 4kB Pages
    Table Type   0 ( 0x 00 ) found, size of  24 (0x 18 ) bytes
    Table Type   1 ( 0x 01 ) found, size of  27 (0x 1B ) bytes
    Table Type   2 ( 0x 02 ) found, size of  15 (0x 0F ) bytes
    Table Type   3 ( 0x 03 ) found, size of  22 (0x 16 ) bytes
    Table Type  10 ( 0x 0A ) found, size of  26 (0x 1A ) bytes
    Table Type  11 ( 0x 0B ) found, size of   5 (0x 05 ) bytes
    Table Type  12 ( 0x 0C ) found, size of   5 (0x 05 ) bytes
    Table Type  32 ( 0x 20 ) found, size of  20 (0x 14 ) bytes
    Table Type   4 ( 0x 04 ) found, size of  42 (0x 2A ) bytes
    Table Type   7 ( 0x 07 ) found, size of  19 (0x 13 ) bytes
    Table Type   7 ( 0x 07 ) found, size of  19 (0x 13 ) bytes
    Table Type   7 ( 0x 07 ) found, size of  19 (0x 13 ) bytes
    Table Type  16 ( 0x 10 ) found, size of  23 (0x 17 ) bytes
    Table Type  17 ( 0x 11 ) found, size of  34 (0x 22 ) bytes
    Table Type  20 ( 0x 14 ) found, size of  35 (0x 23 ) bytes
    Table Type  17 ( 0x 11 ) found, size of  34 (0x 22 ) bytes
    Table Type  17 ( 0x 11 ) found, size of  34 (0x 22 ) bytes
    Table Type  17 ( 0x 11 ) found, size of  34 (0x 22 ) bytes
    Table Type  19 ( 0x 13 ) found, size of  31 (0x 1F ) bytes
    Table Type 136 ( 0x 88 ) found, size of   6 (0x 06 ) bytes
    Table Type  13 ( 0x 0D ) found, size of  22 (0x 16 ) bytes
    Table Type 127 ( 0x 7F ) found, size of   4 (0x 04 ) bytes

Error 9256: Communication error between application and Intel(R) ME module (FW Update client)
Error 0099: Unknown error code
Error 9459: Internal error (Could not determine FW features information)



Quote:MEInfoWin -fwsts


[Image: fwsts.png]


EDIT:

I have looked at my friend's laptop and the IME is present in the device manager. The boot of the laptop is very fast.

I think that on my motherboard the IME is the cause of the problem.
Asus logo may go by too quickly, if you are using SSD that could be why, it's too fast loading Big Grin If you want to slow it down and enjoy the logo you'll need old slow hard drive Smile

Thanks for the MEInfo results! Please show CPU-z motherboard tab, and AIDA64 >> Motherboard >> Chipset >> Select South Bridge and show image of bottom area info (uppermost is what I'm needing to see, south bridge name and Intel Platform name). Hopefully you can see both of those with freeware version.... if not, there is cracked out there Big Grin

Which BIOS are you using now? I will use that one to Fix ME in and send you new to reflash the ME
Quote:Asus logo may go by too quickly, if you are using SSD that could be why, it's too fast loading


SSD = solid state drive = super speed drive Big Grin Big Grin Big Grin  


Quote:If you want to slow it down and enjoy the logo you'll need old slow hard drive


Yes, yes, yes, I'm interested, if you have an old hard drive I can buy it Big Grin Big Grin Big Grin 



Quote:Thanks for the MEInfo results!

You are welcome!


Quote:Which BIOS are you using now?


New-DBX-PK-SMI-Only303-HDWCFG.bin

What is the difference between New-DBX-PK-SMI-Only303-HDWCFG.bin and New-DBX-PK-SMI-Only303-AEDID-HDWCFG.bin?



Quote:I will use that one to Fix ME in and send you new to reflash the ME

Friend...you are my angel. Angel Angel Angel  I will pray for you in the church Wink Wink Wink

Can you make a file without ME firmware and without the 15 second delay? (Deactivate the ME from the bios) (only for test) Smile



Quote:CPU-z and AIDA64

I know him, I've been using for years. Rolleyes Shy Rolleyes Shy


North Bridge:

Code:
[ North Bridge: Intel Haswell-MB IMC ]
    North Bridge Properties:
      North Bridge                                      Intel Haswell-MB IMC
      Intel Platform                                    Shark Bay-MB
      Supported Memory Types                            DDR3-1066, DDR3-1333, DDR3-1600 SDRAM
      Maximum Memory Amount                             16 GB
      Revision                                          06
      Process Technology                                22 nm
      VT-d                                              Supported
      Extended APIC (x2APIC)                            Supported

[Image: 302s0sh.png]

South Bridge:

Code:
[ South Bridge: Intel Lynx Point HM86 ]
    South Bridge Properties:
      South Bridge                                      Intel Lynx Point HM86
      Intel Platform                                    Shark Bay-MB
      Revision / Stepping                               05 / C2
      Package Type                                      695 Pin FC-BGA
      Package Size                                      20 mm x 20 mm
      Process Technology                                32 nm
      Die Size                                          47.87 mm2
      Core Voltage                                      1.05 V
      TDP                                               4.1 W

[Image: 2qjx7us.png]

[Image: fbc0hs.png]

[Image: 9ks66a.png]
New-DBX-PK-SMI-Only303-HDWCFG.bin and New-DBX-PK-SMI-Only303-AEDID-HDWCFG.bin and New-DBX-PK-SMI-Only303-AEDID.bin, the differences are the last module in the file name has those modules from NVRAM off your Test2_OK BIOS. One HDWCFG only, one AEDID only, one with both. Of course many other stuff done to each as noted in the change logs as we worked though all those BIOS tests, but those were last tests we did to figure out which one of those additionally was needed to make windows activate properly like the first BIOS I sent you that activated properly.

That BIOS New-DBX-PK-SMI-Only303-HDWCFG.bin, activates windows properly like before correct?

ME Is messed up, so disabled at the BIOS now Big Grin Thus the delay, if I disabled it through other methods it may be worse issue, you need ME anyway, so goal even for testing can't be to try and make this worse, only better Big Grin

Here is new test BIOS, please program to the chip if you still have the system open, if not then use FPT as follows
http://s000.tinyupload.com/index.php?fil...7774840996

FPTw.exe -rewrite -me -f outimage.bin
FPTw.exe -greset

If greset does not reboot the system, please shut down, unplug PSU block from the system, then remove CMOS battery if you can easily, if not it's OK. Then press and hold the power on button for 1 minute (Make sure it's 60 seconds or more). Then put it back together, CMOS battery back, plug back in, boot to BIOS and load optimal, then back into windows and see if windows boots properly and if those errors are gone in
MEInfoWin -fwsts
MEInfoWin -verbose

Also, can you run, or have your friend run this and see if he also gets this same error
MEInfoWin -fwsts
PhaseStatus: PCH ID MISMATCH

And ask him if he knows with 100% certainty if he has two memory slots or three
HM86 = 2 slots
HM87 three slots

Both you guys BIOS files open as HM87 in Intel FITc app for Intel ME programming, and I assume this is what's maybe causing that PCH ID Mismatch. The above BIOS I set to HM86, but if it still fails, we'll put back to HM87 and try these ME rewrite again and see if that fixes it.
I don't have enough time but everything is going better.

The start is very, very fast.

For the moment I installed only the win 7 so.
I formatted the SSD because I received various blue screens on the boot.

Regards.

The motherboard model is X550JD Rev. 2.0


[Image: 314doba.png]

[Image: 34yupv5.png]
So, second image if front/back of GPU, correct?
On the first image, is that a single memory installable slot, or double? And, is that memory soldered to the board there too, I assume not GPU related since it's not near that at all.

So, sounds like the BIOS above maybe fixed the ME issue eh?
(11-13-2018, 05:26 PM)Lost_N_BIOS Wrote: [ -> ]So, second image if front/back of GPU, correct? 

Yes.

Quote:On the first image, is that a single memory installable slot, or double?

Single.

 
Quote:And, is that memory soldered to the board there too, I assume not GPU related since it's not near that at all.

Correct. This is the system memory module.

Quote:So, sounds like the BIOS above maybe fixed the ME issue eh?

I tried only a little but I like how it goes. Everything has changed. Smile Smile Smile
Pages: 1 2 3 4 5 6 7 8 9 10 11