Jump to content
mpe

Haswell-E slowly after waking up

1 post in this topic

Recommended Posts

Hi,

 

After wakeup my system is slow, console input show some duplicate character when I type some commands. Intel Power Gadget is shows no more statistics.

I am looking for solution several days, but I can't find.

 

Maybe some one have the same system or tips for me?

 

I have already attach the Runme.app zip

 

Best regards,

 

mpe

Send me mpe.zip

Share this post


Link to post
Share on other sites
Advertisement

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By simras
      Hello,

      I am trying to make a new Hackintosh under 10.13 with this specs:
      i7 6800K,
      Asus X99-E
      Asus GTX 970

      But the problem is that I can't pass those errors :
      - couldn't allocate runtime area
      - end randomseed ++++++++++++++ _

      I have always passed this thing on all hackintoshs that I have done, but here, impossible.

      Tried those tests :
      - AptioMemoryFix alone,
      - AptioMemoryFix with EmuVariableUefi and RC Scripts,
      - OsxAptioFix2Drv-free2000 with EmuVariableUefi and RC Scripts,
      - Test2-2016.efi with OsxAptioFixDrv, EmuVariableUefi and RC Scripts,
      - Test2-2016.efi with OsxAptioFix2Drv, EmuVariableUefi and RC Scripts,
      - Test2-2016.efi with OsxAptioFix2Drv, OsxAptioFixDrv, EmuVariableUefi and RC Scripts,
      - Test2.efi with OsxAptioFixDrv, EmuVariableUefi and RC Scripts,
      - Test2.efi with OsxAptioFix2Drv, EmuVariableUefi and RC Scripts,
      - Test2.efi with OsxAptioFix2Drv, OsxAptioFixDrv, EmuVariableUefi and RC Scripts.

      I have tried all this with npci=0x3000 that I have never used before instead of npci=0x2000

      I have done an Hackintosh on Asus X99 Deluxe II and it pass with AptioMemoryFix with EmuVariableUefi and RC Scripts....

      I have tried to reset NVRAM with F11.

      I have tried with 1 RAM stick that I have indicate in the SMBIOS :
      https://hackintosher.com/forums/thread/mapping-ram-and-dimm-slots-on-a-hackintosh-with-clover-smbios.365/
       
      I have follow KGP guide for X99 :
       
      The BIOS settings are exactly the same.

      I link my CLOVER folder.

      Thank you.
      CLOVER.zip
    • By Drovosek
      Unfortunately this is not my PC, I just decided to share the found config successful installation.
      https://vk.com/photo-12954845_457251886
       
      Hardware:
      OS X 10.15.0 Beta 2 
      CPU Intel XEON E5 2650 v3
      MB MSI X99A RAIDER
      AMD Radeon RX VEGA 56 video card
      Kingston HyperX Fury DDR4 2133Mhz 20gb memory
      Crucial 4gb 2400Mhz
      Sound E-MU 0202, Alc892 and AMD DisplayPort Audio
      Intel Gigabit LAN network
      WI-FI Broadcom BCM94360CS2
      BCM20702 BT (trackpad and keyboard work in the BIOS)
      BP Enermax Platimax 1000W
      AirDrop works.
      SSD NVMe Reina 480gb
      Samsung 850 Pro 120gb
      Dell U2713H monitor
      USB 15 ports are registered manually. 3.0 works. 
      Services usual, SpeedStep instituted through kekst. 
      Sleep is unstable.
       
      EFI: https://vk.com/doc207634019_512032268
       

      EFI.zip
    • By AwlsomeAlex
      My Laptop:
      ASUS ZenBook UX330UAR
      8GB RAM / 256GB SSD
      Intel i5-8250U
      1920 x 1080 (UHD 620)

      After using this guide to setup my laptop as a Hackintosh (macOS 10.14.6), every once in a while it'll result in the screen flickering, and usually the intervals between the flickering get smaller and smaller to the point where sometimes the screen just panics. I tried injecting my EDID and setting my SMBIOS to iMac18,1 but none of those defeated the dreaded flickering. 

      Any assistance would be greatly appreciated!
      24838.zip
       
      EDIT: I'd also note that this does not happen with Linux nor Windows so it is a macOS issue not a hardware issue. 
×