8 Replies Latest reply on Nov 4, 2017 11:21 PM by Shonky

    DQ77MK PCIE BIOS BUG

    Shonky

      So i have two machines with Intel DQ77MK Boards

       

      And have found two bios bugs

      On S3 Suspend to ram (UEFI OS) the PCH PCIE ports on wakeup only initialize at PCIE 1.0 x 4 Speed

      and are stuck that way a straight reboot fixes this so the bios manages to initialize fine on boot

      and just has issues on wakeup

       

      I350-T2=Locked at PCIE 1.0 x 4 after S3 UEFI

      Toshiba XG3=Locked at PCIE 1.0 x 4 after S3 UEFI

       

      PCIE 3.0 x 16 Slot doesnt have this problem

      PCIE 2.0 x 1 Slots i have no idea as my Intel AC-7260's are 1.1

       

      Windows Event Log moans about a HAL problem after S3 in UEFI Mode

      and points at a faulty bios if the OS isnt in UEFI Mode this doesnt happen after S3 in the eventlog

       

      No idea if the PCH PCIE 1.0 x 4 Bug happens in non UEFI OS as i only noticed this bug the other day

      but noticed the Event Log UEFI Mode S3 Problem quite some time ago

       

      this isnt just a case of PCIE power management before anyone mentions it

      but the device is locked at PCIE 1.0 after S3 as can be confirmed by NVME SSD benchmarks of

      700 MB/S instead of 1400 MB/S after S3

       

      I have 100% confirmed this is a bios bug im not looking for help on my specific devices

      BUT Requesting a Firmware Update that fixes this Problem

       

      Machine 1

      Board=Intel Desktop Board DQ77MK

      CPU=Intel Xeon E3 1240 V2

      Ram=32GB 1600 Mhz

      PCIE 3.0 16x Slot=MSI R9 280 3GB OC

      PCIE 2.0 4x Slot=Intel I350-T2 (PCIE 2.0 x 4 Card)

      PCIE 2.0 1x Mini Slot=Intel AC-7260 (PCIE 1.0 x 1 Card)

      OS = Windows 10 Fall Creators Update Uefi Mode

      Boot Drive =KINGSTON SV300S37A240G 240GB SSD

      PSU=Corsair HX750

       

      Machine 2

      Board=Intel Desktop Board DQ77MK

      CPU=Intel i7 3770

      Ram=32GB 1600 Mhz

      PCIE 3.0 16x Slot=Sapphire R9 290 4GB Tri-X OC

      PCIE 2.0 4x Slot=Toshiba THNSN5256GPU7 XG3 256GB M.2 2280 NVMe (PCIE 3.0 x 4 Card) (non bootable)

      PCIE 2.0 1x Mini Slot=Intel AC-7260 (PCIE 1.0 x 1 Card)

      OS = Windows 10 Fall Creators Update Uefi Mode

      Boot Drive=Crucial M550 512GB SSD

      PSU=Corsair HX750

       

      Maximum Link Width:                                                         4x
      Current Link Width:                                                         4x
      Maximum Link Speed:                                                         8.0 GT/s
      Current Link Speed:                                                         2.5 GT/s
      Device/Port Type:                                                           PCI Express Endpoint

       

      Maximum Link Width:                                                         4x
      Current Link Width:                                                         4x
      Maximum Link Speed:                                                         5.0 GT/s
      Current Link Speed:                                                         2.5 GT/s
      Device/Port Type:                                                           PCI Express Endpoint
        • 1. Re: DQ77MK PCIE BIOS BUG
          Shonky

          This was posted in the support forums a few times when support was still active for desktop boards

          Intel support came back that it couldnt be reproduced so it must be an error at the users end

          but the reality was consumers where using the board in uefi mode

          and support where using legacy mode and nobody put two and two together

           

          In the past i would have fixed the bios myself but intel sign the bios

          and as such this can only be fixed by intel

           

          large bugs are still being fixed by intel for desktop boards

          e.g. ME bug was patched a few months ago

           

          I request a fix for broken UEFI mode as this has been broken since day1 of release

           

           

          Log Name: System
          Source:   Microsoft-Windows-HAL
          Date:     24/02/2190 20:50:32
          Event ID: 12

          Task Category: None

          Level:    Error
          Keywords: (1)
          User:     N/A
          Computer: DQ77MK2

          Description:

          The platform firmware has corrupted memory across the previous system power transition.  Please check for updated firmware for your system.

          Event Xml:

          <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

            <System>

          <Provider Name="Microsoft-Windows-HAL" Guid="{63D1E632-95CC-4443-9312-AF927761D52A}" />
          <EventID>12</EventID>
          <Version>0</Version>
          <Level>2</Level>
          <Task>0</Task>
          <Opcode>0</Opcode>
          <Keywords>0x8000000000000001</Keywords>
          <TimeCreated SystemTime="2190-02-24T20:50:32.911762400Z" />
          <EventRecordID>5047</EventRecordID>
          <Correlation />
          <Execution ProcessID="4" ThreadID="32" />
          <Channel>System</Channel>
          <Computer>DQ77MK2</Computer>
          <Security />

            </System>

            <EventData>

          <Data Name="Count">1</Data>
          <Data Name="FirstPage">159</Data>
          <Data Name="LastPage">159</Data>

            </EventData>

          </Event>

          • 2. Re: DQ77MK PCIE BIOS BUG
            N.Scott.Pearson

            Intel exited from the Desktop Boards business a number of years ago. All Desktop Boards are subsequently long past their End-Of-Life dates and long past their End-Of-Interactive-Support dates as well. The sustaining team was disbanded quite some time ago. There is simply no one left to work on any bugs. Yes, it is totally true that Intel delivered updates last year that delivered fixes for a set of security flaws in the Management Engine (ME) firmware, but what you need to understand is that the ME firmware team is part of the Chipset organization and thus active sustaining for this portion of the firmware is (still) ongoing. This is not the case here. There is no one to work on any BIOS bugs. Putting together a team at this point to deliver a fix for this issue would cost many thousands of dollars. It simply isn't going to happen.

             

            Sorry (and remember that I am just the messenger),

            ...S

            • 3. Re: DQ77MK PCIE BIOS BUG
              Shonky

              Im sure you know alot more about the teams than me

               

              but they clearly still have bios engineers on site as the nuc's also suffered with this problem

              which they promptly replaced a bios module and fixed it

               

              being such a large bug that has been present since release

              the least they could do is get one of the nuc team to package up a fix

               

              they clearly know what fixes it as they fixed the nuc bios's

               

              i could fix this myself if i had the capability to sign the firmware

              in what 10 mins

               

              Its a simple case of saying fred fix that uefi bug that the nuc's had

              on the dq77mk firmware ok jim will have it fixed in 10 mins

              • 4. Re: DQ77MK PCIE BIOS BUG
                N.Scott.Pearson

                No, it is not that simple. First of all, these BIOS were developed on completely different code bases, which means that a fix would need to be independently developed. As I said, doing so and then going through the required regression, validation and release cycles (nothing leaves Intel without it) would take a team of engineers and cost many thousands of dollars. I am sorry, but this is the reality of the situation; it simply isn't going to happen.

                ...S

                • 5. Re: DQ77MK PCIE BIOS BUG
                  Shonky

                  This is the problem with signed firmware nobody can fix it apart from the oem

                   

                  My only hope tbh is if it doesnt happen in legacy mode

                   

                  I know the os doesnt moan after coming out of standby in legacy

                  as mine only started doing it after a fresh install in uefi mode

                   

                  will wipe one of them in the next few days and check

                   

                  the event log didnt bother me i just stopped windows logging it

                  but didnt realise until yesterday that the 4x slot was being downgraded after standby

                  • 6. Re: DQ77MK PCIE BIOS BUG
                    Shonky

                    I did a fresh legacy install

                    it fixed the event log error after standby

                    but the 4x slot still gets dropped down to gen 1 after standby

                     

                    so its two different bug's

                    • 7. Re: DQ77MK PCIE BIOS BUG
                      N.Scott.Pearson

                      Thanks for the into. Unfortunately, at this point, all we can do is document the issues in case someone else runs into it.

                      ...S

                      • 8. Re: DQ77MK PCIE BIOS BUG
                        Shonky

                        Im looking into forcing a link speed now in the registry with RMPcieLinkSpeed

                        i just need to find the area for the i350-t2 and the nvme ssd

                         

                        Here's the reg fix to stop windows moaning about s3

                         

                        Windows Registry Editor Version 5.00

                         

                        [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\WMI\Autologger\EventLog-System\{63d1e632-95cc-4443-9312-af927761d52a}]

                        "Enabled"=dword:00000000