990FXA-GD80 AHCI Slow boot

I was recently forced to reinstall my pc due to some software problems that i was unable to fix.
Since this my PC is extremely slow upon booting using AHCI.  I have used both the latest ones from the MSI download for the board and the newest ones with the new OMEGA ATI drivers and still the same.
My Hard Disk is a WD Black 2TB SATA 6GBps.
If i switch my Sata Ports to IDE then all is well.

uninstall ATI driver and try with the win 7 built-in driver.

Similar Messages

  • Msi motherboard 990FXA-GD80 wont work only sending debug code

    my motherboard 990FXA-GD80 is not booting to bios ore nothing is coming up to the screen it's only sending debug code:
    FF
    19
    FF
    2b
    3b
    37
    36
    70
    60
    72
    b2
    92
    99
    52
    54
    55
    56
    some times
    44
    45
    46
    why are nothing happening and what can it be
    i have tried out chaining slots for the memory card and to remove/mount the CPU and still it responds the same
    it's a FX-8120 CPU
    i have also tried with a
    is there someone that knows what can be wrong with the motherboard ples i need some help with this.

    FF - means nothing
    19 - Pre-memory South Bridge initialization is started
    FF - means nothing
    2B - Memory initialization. Serial Presence Detect (SPD) data reading
    3B - Post-Memory South Bridge initialization is started
    37 - Post-Memory North Bridge initialization is started
    36 - CPU post-memory initialization. System Management Mode (SMM) initialization
    70 - South Bridge DXE initialization is started
    60 - DXE Core is started
    72 - South Bridge devices initialization
    B2 - Legacy Option ROM Initialization <--- possible Graphics Card Problem too
    92 - PCI Bus initialization is started
    99 - Super IO Initialization
    52 - Memory initialization error. Invalid memory size or memory modules do not match
    54 - Unspecified memory initialization error
    55 - Memory not installed
    56 - Invalid CPU type or Speed
    the Red area is a very bad set of codes as they are mainly Memory and CPU issues
    your some times codes are all DXE IPL is started
    ok from that track of codes it looks to me like either a memory problem (MOST LIKELY) or CPU not Supported problem!
    ok so Read this>>>> >>Posting Guide<< and give us the parts in your Build and exactly what memory and CPU you have?
    also what is the Serial Number of your motherboard (Leave off the last 3 Digits if you do not want to give the full one)? ----- NOTE: its either on the rear of the board or on the UPC label on the Motherboard Box or both!

  • Slow Boot Up, Slow Login caused by AHCI so we used IDE Emulator. What is the ramification of that?

    Hi,
    We have Windows 7 SP1 Enterprise and x64 machines and we have slow boot up and slow login issue for a while.  We thought it was clearly group policy causing it but it can be misleading because we have other machines that use the same
    GPO but has no issue.  On the other hand, the problem is prominent with a specific HP Model (Elitedesk 800G1 SFF) so when we focused on that model, we reinstalled/reformat the computer but to no avail, the machine would still be be slow as soon as it
    joins the domain.  The other option is to minize the services and startup items, but we can prove that other machines boot up fine with all the services and startup items running.  So "Msconfig" helps but as much as possible, we don't want
    to do this because we have several computers with slow issues.  We also installed  KB2775511 but we don't get consistent result.
    What gave us consistent result was changing the BIOS setting from AHCI to IDE but I would like to know what are the ramification of not using AHCI.  Our new machines were delivered with this BIOS setting so we suppose that this is the most appropriate
    setting however, it screws up other things.
    What are we missing, how different is the performance and is this change not recommended?  Any thoughts?
    Thanks!

    Hi,
    I just add another method to diagnose your problem. You can try to use xbootmgr to collect a boot trace of your system.
    Refer to the link below for more details about the trace steps:
    http://blogs.technet.com/b/jeff_stokes/archive/2012/09/17/how-to-collect-a-good-boot-trace-on-windows-7.aspx
    Roger Lu
    TechNet Community Support

  • Bios Takes Five Minutes to Boot - 990FXA-GD80

    Just built a new computer and from the "get go" the bios has taken approximately five minutes to boot. Error codes are 99 (last 4 minutes) than switches to B4 (last 1 minute) than the system boots just fine. I have been able to update the bios to the most recent verison using the MSI USB flasher tool and I have switched out my ram with a different brand to no avail.
    Current System:
    MSI 990FXA-GD80
    AMD FX-8150
    16GB DDR pc2133 G.Skill Ram / Also tried 8GB PNY MD40965D1333
    OCZ SSD Hardrive
    Western Digital Hardrive
    Sapphire 6950 Video Card
    I've tried the following:
    Updated Bios
    Cleared CMOS

    Quote
    On another note, anyone have any thoughts on how I can solve this mouse USB problem?
    Yes. Please open a ticket with MSI Tech Support so they are aware of the mouse problem with your mainboard. They can then try & duplicate it & come up with a revision to hopefully correct the incompatibility; http://support.msi.com

  • 990FXA-GD80 Boot issues

    Just built a PC with this motherboard, more specs below.
    I can start one time, get all the way to the Win7 login screen. Then I shutdown, try to restart and my MB shows the following message:
    2b->FF->19, blinking very rapidly. The DDR_Phase 2 light also blinks.
    THe only way I can reboot is to clear the CMOS and start again. From time to time, the computer will restart if I let this loop carry on.
    I tried putting windows in hibernate mode, and again, the system restarted after a pause and the same symptoms.
    When booted fully, a small red LED light blinks sporadically to the left of the JFP2 panel (left of the debug box). The DDR_Phase 2 light is now solid. I have also tried with a Linux boot.
    My BIOS says I'm running E7640AMS V13.0
    I've cleared the CMOS via battery removal as well.
    I have:
    990FXA-GD80 MB
    AMD Phenom II X4 965 Black Edition Deneb 3.4GHz Processor
    Crucial Ballistix Sport 8GB 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800)  in the slot closest to the processor
    SAMSUNG 840 Pro Series MZ-7PD128BW 2.5" 128GB SATA III MLC SSD
    XFX One ON-XFX1-PLS2 Radeon HD 5450 1GB 64-bit DDR3 PCI Express 2.1 x16 HDCP Video Card
    Anyone know why this might be happening? Thank you.

    you use 1 memory stick only or?
    what PSU you use?
    Quote
    My BIOS says I'm running E7640AMS V13.0
    make system stable and reflash to the latest one 13.3

  • 990FXA-GD80 wont boot pls help

    i got meself a 990FXA-GD80 mainbord with FX1850 3.6 CPU put it all in got it to turn on but had to order a new sata cd drive wile i wait for it to come PC world is sallin a IDE to Sata converter so i grabed on so i could get windows loaded on pluged it all in turned me computer on an nothin well i say nothin all the bord powers up all me little blue light come on fans all go round but it wont start to boot an the debug leds just show up ff really quick then changes to 19 an nothin eles happens thanks Paul

    >>Posting Guide<<

  • MSI 990FXA - GD80 Wont Boot.

    Hi,
    My GD80 board wont boot past code 99, it was fine yesterday but now wont do anything.
    It comes up with a list of the HDD devices, and any optical drives, the unganged status of the ram, and says press F1 to setup or F2 to continue. I have tried different keyboards(several), different mice/no mouse connected, also 1 single stick of ram instead of the 4x4gig corsair. In fact, all of the usual stuff for trouble shooting. this is a premium board, I find it hard to believe this cannot be fixed somehow.
    Any help appreciated.
    thanks.

    The problem is the same as the screenie above. I know that the board in the picture is a GD65, however other than the board version, everything else is the same. I pressed F1, just hangs with prompt entering Setup...... if i press F2 it just sits there doing nothing.

  • 990FXA-GD80 Debug Code 2b won't boot

    Specs:
    990FXA-GD80 v2
    16GB Kingston Predator 2133@1866
    FX 8350
    MSI r9 290 4GB Gaming
    Silverstone ST-1000
    60GB Kingston SSDnow
    2TB Seagate Hybrid Drive
    Problem:
    When I hit power the Debug Code reads 19, FF, 2b then resets continuously.
    History:
    I had a similar problem when I first build the computer in February and reseting the RAM fixed it. About a month ago I had the mobo replaced through RMA. 
    The first time I had this happen when I built the computer it worked for a couple weeks before failing to post. The computer has been working for a few weeks since I RMAed the mobo.
    Steps taken so far:
    1. I reset the cpu
    2. Reset memory
    3. Moved memory from DIMMs 1/3 to 2/4
    4. Reset Video Card
    5. Checked all power cables
    Does anybody have any idea how to fix this? I'm guessing that it is the memory but the memory has worked fine for like 9 months besides having to be reset.
    Is there anyway to test this?
    Edit: I just reset the complementary metal-oxide semiconductor and the debug only read FF (memory error). I reset the memory and the debug is going through the FF,19,2b sequence again. 

    I contacted kingston and they are going to replace the RAM. The online form made me put repair under reason for return because the RAM kit is discontinued. I called tech support and was told that they will either replace the kit with one they have in stock or give me options from kits they do have in stock.
    Thanks for the help. It looks like I'm going to have to pilfer a 4GB stick from my HTPC for the next couple of weeks.

  • 990FXA-GD80 code 26 not booting

    Specs:MSI 990FXA-GD80
    FX-8350
    16GB HyperX Predator 2133 @ 1866
    MSI r9 290 4g gaming
    Silverstone ST1000
    60GB Kingston V300 SSD(os and small programs only)
    2TB Seagate hybrid drive for everything else
    When I hit power the computer doesn't produce an image. The display on the motherboard goes through a few numbers as usual then stays on 26.
    After a few seconds the display starts over and then stops at the 26 again. Does anybody know whats happening?
    I also have a question about the memory. When I set it to 2133 in the bios my 3dmark score goes down. When I set it to 1866 my score goes up but 3dmark reports the memory at 667mz so 2001.
    results:http://www.3dmark.com/fs/1906166

    0x1D – 0x2A = OEM pre-memory initialization codes (its a problem starting your Memory so perform a CMOS clear as your memory setting may be the problem so you need to reset them to default and start over by prehaps adding a little more DRAM voltage to them (something between 1.55-1.65v) 1.575v may be a good spot but it depends on the modules and as i have no idea what they are properly its hard to say for sure)
    do you have 2 or 4 sticks of RAM? (asking because that 16GB HyperX Predator 2133 @ 1866 is vague)
    that 3d mark report may be wrong as 667Mhz is not what your saying its 1333MHz as its DDR (Double Data Rate) RAM and DDR3 is just a revision number (Revision 3 as they are from the 3rd incarnation of DDR memory) so its the number multiplied by 2 not 3! (check the reported speed in CPU-Z and if its really at 1866 it should be around 933MHz as that's the half of the Double Data Rate)
    now as for the drop in performance that's pretty normal as its dependant on your CPU's IMC (Internal Memory Controller) to how good it is and how it handles sending data to it and with memory they have 2 variables:
    1: Bandwidth - this is the Frequency you see and the higher it is the more bandwidth its running
    2: Latency - This is the Timings EG: 11-11-11-30 and with them numbers the higher they are the more latency it has as lower numbers are faster
    so its a Balancing act between Frequency and Timings and one may cancel out the other so like your reporting the Ram at 2133 probably has much more latency and is cancelling out the benefit of more bandwidth and that's always a good possibility as the CPU may not like the slack Timings at all as CPU's usually send small data sets to RAM (a GPU on a graphics card is different as they prefer lots of bandwidth and have no cares about latency) but with a processor you have to get a balance or the 2 factors start to in alot of cases erode performance as its all wrong!
    Note: 1866MHz is usually the sweet spot in terms of performance and above that it starts to degrade!

  • MSI 990FXA-GD80 black screen

    Hello there
    Specs:
    What I had:
    AMD Phenom II X4 955 Black Edition
    GIGABYTE GA-880GA-UD3H
    XFX Radeon HD 6970 2GB GDDR5
    Corsair Vengeance DDR3 1600MHz 16GB CL9
    Western Digital Caviar® Black 1TB
    2x Western Digital Caviar Green WD10EADS 1TB
    OCZ SSD Vertex 4 Series 2.5" 128GB
    My computer suddenly crashed with a BSOD while surfing the web. When it restarted I got past the usual Gigabyte screen - followed by a black screen telling me "Beginning to update backup BIOS ---- Updating " then it restarted again, going into a loop with the same thing happening again and again.
    So I figured that the motherboard had crashed, so I bought:
    MSI 990FXA-GD80
    Thinking that would solve the problem.
    I rebuild my computer today with the new motherboard, plugged everything and was ready to go-
    The first message I got was telling me that my cpu or my ram was changed, and gave me the option to either 1- enter BIOS or 2- boot with default values.
    I entered BIOS, checked that everything was OK, saved and rebooted... Got past the MSI-screen - followed by a black screen telling me "NTLDR is missing, press CTRL+ALT+DELETE to restart", which I did.
    My comp then rebooted, but this time both my screens stayed black :O
    I have now tried to restart my computer several times, but my screens stay black.
    My monitors are plugged in with DVI and HDMI.
    Solutions I have tried:
    Removing the motherboard battery. and starting without it.
    changing to my old graphic card, ATI Radeon 5830.
    Removing the power for 15 mins.
    Unplugging all the hard drives, except the SSD. (which my OS is installed at).
    I have now also ordered AMD FX-8150 8-Core Processor.

    Quote
    "NTLDR is missing, press CTRL+ALT+DELETE to restart",
    Did you use the ame HDD for boot without re-installing the OSD ?
    This could be a case of having an AHCI mode OS HDD and your current board is still set to IDE ?
    That X4 955 only supports 1066 or 1333 memory.
    Borrow the other PSU. Insert only one RAM module.
    Do a full CMOS clear.
    Retest and do a fresh OS installation and all curent drivers.

  • 990FXA-GD80 FX-8350 BIOS 11.13 CPU Problems

    All,
    Any and all help will be greatly appreciated.
    I had an AMD FX-8150 installed on my MSI 990FXA-GD80 and updated to the latest bios: 11.13. This was no problem.
    Windows acted fine after reboot.
    I do NOT Overclock the FX-8150 chip as I was not impressed with the performance potential of the FX-8150 when overclocked vs. stock settings. As such I left ALL BIOS settings at their stock settings with the exception of SATA MODE = AHCI.
    However I do check stability of the stock settings with Prime95 and OCCT. Ran both for 60 minutes. And there were no issues.
    I then reset bios to default status and then powered off my PC. Removed the AMD FX-8150 and installed an AMD FX-8350 (Vishera).
    Powered on, clicked F1 to enter settings. restored defaults. Set SATA Mode = AHCI then saved and exited.
    Windows booted just fine. However, ANY stress testing whether via: Prime95, OCCT or AMD overdrive fails with in 90 seconds.
    The OS does NOT BSOD, however Prime95 recognized an error and stops as does OCCT and/or AMD overdrive. Temps do NOT get higher then 40 degrees Celsius in this short period of time.
    I am NOT altering ANY bios setting: No frequency changes, No voltage changes. ALL default settings are intact.
    I did use the jumper to clear CMOS, got into the BIOS, restored to default, set SATA MODE = AHCI, saved and exited. Reset the date and time. Rebooted, re-attempted the 3 above mentioned stress test software suites and all threes reported errors and stopped.
    Is anyone else experiencing similar issues with this board with BIOS 11.13 using an FX-8350?
    I've ran MemTest on the memory and this passes successfully.
    I have another MSI board: 990FXA-GD80V2. I have the old FX-8150 in it right now. I just did a fresh install of Win 7 Ultimate 64-Bit, installed ALL windows updates and I will now update to the latest BIOS for it via Live Update 5.
    Then swap CPUs and report my results.
    Any and all help you can give will be greatly appreciated.
    Thank you.

    Thanks for your reply.
    I have tested a number of different PSUs with both the 990FXA-GD80V2 and 990FXA-GD80 and the FX-8350:
    Corsair 1200AX
    OCZ ZX Series 1250W
    Rosewill Capstone 750W
    Corsair CX 600
    The result is the same for any and ALL of the above PSUs. So I am convinced, that this issue is NOT PSU related. That is not to say that a faulty PSU could not cause similar issues.
    I also agree that it is not a Thermal issue. With ALL default setting set in the BIOS, Prime95, OCCT, etc. ALL error our within the first 90 seconds and on my systems while using the following Heatsink/fan/Close-loop Liquid cooling solutions temperatures NEVER exceed 50 C before errors occurr:
    Cooler Master Hyper 212 Evo
    Corsair H100
    Zalman CNPS11X
    ThermalRight Silver Arrow
    I've tried the following memory options:
    G.Skill F3-2133C9D-8GAB
    G.Skill F3-17000CL9D-8GBXM
    Muskin 997008
    Muskin 997007
    Muskin 996997
    Muskin 996996
    Patriod PV38G160C9K
    All pass memtest86+
    I have tried leaving the Memory settings set at default.
    I've manually entered the timings and frequecy. (The highest bootstrap on this board is 1866, so If the memory was rated higher than 1866, 1866 was selected and the default clock frequecy of 200 was NOT changed. So for testing purposes 1866 was the highest possible setting).
    Again ALL memory sticks pass memtest86+ on both 990FXA-GD80 and 990FXA-GD80V2
    I've tried 3 separate FX-8350 CPUs on both motherboards. ALL combinations exibit the same symptons. That being under default settings, Prime95, OCCT, ect. fail.
    I am convinced it is a voltage issue. I do not think the MSI 990FXA-GD80 and/or MSI 990FXA-GD80V2 with BIOS v. 11.13 ramps up the voltage fast enough when the CPU is stressed.
    This opinion is speculative. But I think it is grounded in fact.
    On these two motherboards ALL three FX-8350 become stable by changing CPU Voltage = AUTO to CPU Voltage = 1.365000
    Anything less then this will produce an error in Prime95, OCCT, etc. with 15 minutes regardless of which of the above cooling solutions are used.
    Any and all feed back will be greatly appreciated. Thank you.

  • 990FXA-GD80 Sudden Problems

    Motherboard: 990FXA-GD80
    BIOS: 11.10 (most recent)
    CPU: AMD FX-8120 8-Core
    Memory: 2x4GB G.Skill
    Graphics: GeForce 8800GT
    OS: Windows 7
    I get the feeling I'm in for another long stretch of troubleshooting, so posting this with all the current symptoms. Maybe someone has ideas that'll save me some time.
    Computer was working mostly fine when I left the house for about 30 minutes. Came back to a black screen, unresponsive mouse/keyboard, and I couldn't even shut the computer down from the front power button.
    The only odd thing happening prior to this was my USB headset losing sound, forcing me to disable/enable it to get it working again. Maybe related, maybe not.
    Upon restarting the computer, the post screen didn't see my mouse or keyboard, hung for a while trying to load Windows, and went to a "PARITY ERROR" of some sort.
    I moved my mouse and keyboard from the USB3.0 ports to USB2.0 and after a reboot or two, I got into Windows, but Aero was disabled, graphics were set to 800x600, and everything was sluggish.
    Current symptoms:
    - Motherboard showing FF debug code through entire boot sequence
    - BIOS unable to get CPU/case heat and #1/#2 fan reads, CoreTemp reads fine
    - GeForce 8800GT on IRQ10 but "Windows has stopped this device because it has reported problems. (Code 43)"
    - Renesas Electronics USB 3.0 Host Controller: "This device cannot start. (Code 10)"
    - Windows 7 loads slow, sluggish performance
    Have tried:
    - Disabling unnecessary motherboard components (Audio, IEEE 1394, etc.)
    - Reinstalling graphics drivers
    Heat shouldn't be a factor. My system seems to run really cool. According to CoreTemp my CPU's only at 18 Celsius right now. I've reset the BIOS to no avail.
    I'd kind of like to think video card problems could cause all these symptoms since I can justify replacing that, but the on-board problems (Debug LED, BIOS heat/fan reads) are suggesting a motherboard failure. And I bought this motherboard just a month ago after replacing a defective, new 880 series. My luck can't really be this bad, can it? I'm even outside the return window for this motherboard now. 

    Quote from: badboy2k on 02-June-12, 15:34:24
    my computer usually does that too with my graphics setting it to 800x600 usually when my Graphics card has overheated while idle (good sign you need to clean the heatsinc on it or you dont have enougth air flow)!
    I'm fairly confident that's not the issue. As mentioned above, my CPU temp would have been around 18C when this happened (sitting on the desktop). I have 3 fans blowing in from the front and top, 2 blowing out the back.
    I'm pretty sure the graphics card isn't the source of this issue. I just tried booting with it completely disconnected and I still only get FF on the debug LED. It's like the motherboard has lost the ability to detect its own status. And I imagine whatever is causing that is also interfering with the normal operations of the video card and USB3 controller.
    Weird thing is, the graphics card works well enough to be working for me right now, but even nVidia's own software isn't recognizing it.

  • Issue Regarding 990FXA-GD80 BIOS flash

    Hello all
    This is my first post, so please bear with me if i do not include everything needed. Also, this forum looks very informative and helpful from what I've seen. My gratitude extends to all that help out!
    I am having trouble flashing the BIOS on the 990FXA-GD80 mobo. I am currently running v11.12 (7640vBC) and I am trying to upgrade to v11.14 (7640vBE7 or any BE for that matter). Thus far, i have tried BE7 as well as BE6
    For BE7:
    I used the MSI Forum HQ USB Flashing Tool and all goes well with that part of the process and is performed successfully. I clear the CMOS properly (disconnect power cord, hold button for 5 seconds, remove battery, hold down power button)
    After booting back up, I load default settings in the BIOS, yet the BIOS version stays at v11.12 and I have no clue as to why.
    Is there a Boot Sector Protection that I may be overlooking? I didn't see that type of option in the BIOS
    I then tried to update to BE6:
    I haven't actually successfully flashed to this beta whatsoever, because when I do boot up with the usb and try it, this message comes up:
    PI Version in SYS ROM mismatched PI Version in ROM File!
    Force update it may be destroy the system BIOS
    We do not recommend flashing your BIOS
    after seeing this message, I did not go forward with it.
    Please help in this matter, as this is my first attempt at trying to flash my bios
    Thanks in advance
    My system:
    990FXA-GD80
    AMD FX-8350
    G.SKILL Ripjaws X Series 16GB (2 x 8GB) DDR3 1600
    128gb OCZ Vertex 4
    Cooler Master Silent Pro M 850W

    Thanks Svet, I'll try it again and go through with it
    But, why does it only give me the warning message for BE6 and not BE7? I would rather try to solve the issue I'm having with BE7 rather than BE6

  • Windows 8/8.1 slow boot (sudden onset)

    Can anyone help with a slow boot problem on Windows 8/8.1, please?  This concerns an Asus Zenbook.  It's about 15 months old, and has always booted very quickly.  Now, all of a sudden, it takes 5 minutes to get beyond the Windows logo screen. 
    I have tried all the standard things (clean boot, turn off Asus Fast Boot, etc), up to and including Resetting Windows.  No good: on either Windows 8 or 8.1, it still takes 5 minutes.  I have looked at the Windows System Log, and the delay occurs
    right at the beginning of the Boot process.  E.g., on the most recent boot I see as the first 3 entries (note, I'm in Europe, so dates are dd/mm/yyyy, and times are in 24-hour clock):
    Information    10/03/2014 19:36:23    Kernel-General    12    None The operating system started at system time ‎2014‎-‎03‎-‎10T19:36:23.490074300Z.
    Information    10/03/2014 19:36:23    Kernel-Boot    30    None The firmware reported boot metrics.
    Information    10/03/2014 19:40:26    FilterManager    6    None File System Filter 'FileInfo' (6.3, ‎2013‎-‎08‎-‎22T11:38:45.000000000Z) has successfully loaded and registered with Filter Manager.
    and you can see the 4-minute gap between the 2nd and 3rd entries.  That's where the delay always comes, though sometimes the "reported boot metrics" doesn't show.
    A little later in the procedure I do always get the following warning:
    Warning    10/03/2014 19:40:31    Kernel-PnP    219    (212)  The driver \Driver\WudfRd failed to load for the device ACPI\ACPI0008\2&daba3ff&2.
    However because that comes later I can't see how it can be causing the problem, and I suspect it's an independent issue.
    The machine appears to run normally once booted.  It is protected against viruses by Windows Defender.  I have looked at many posts on this and other fora on slow boot, and tried everything suggested, but none of the solutions have worked. 
    I have also looked widely on the web for problems with the File System Filter but nothing relevant comes up.  The machine is under warranty, and could be sent back, but that would be a serious pain so if there is a solution I can implement I would much
    prefer to do so.  Thank you for looking at this.
    There are no stupid rats, only misguided students

    Hi Seglea,
    I have exact the same issue as you have! The only difference is the time period the splash screen / logo screen with the dots spinning in a circle hangs / delays / freezes: exactly 120 seconds. You can set your watch to that delay. During these 120 seconds
    nothing happens, no HDD LED activity, just nothing. Having passed the 120 s, the HDD LED begins to flicker and the logon screen is displayed 15 s later. 
    For the first look at it, I believe that it is a timeout problem. Usually Windows services retry to start after just these 120 seconds (e.g. Software Protection is configured this way, but in my case it does not start although configured as auto delayed).
    I believe that the clue is to find out which service causes this delay.
    My event logs are exactly the same as yours (without boot metrics), I do also have your WudRfd warning!
    When started, the machine operates in a fast and stable way, as if nothing harmful had ever happened.
    I do also have an SSD installed as only (system) disk.
    In my case the startup screen of the BIOS also stays visible for more than 10 seconds, longer as on any other computer I have had before. I also had problems during installation of Windows 8.1. After the first reboot during OS installation the BIOS POST
    screen restarted in an endless loop. I could solve that problem by setting the dedicated internal Graphics memory to less than 1024M, although I own 32 GBytes of RAM.
    Nothing helped so far, I permuted my BIOS settings, even Fast Boot or Ultra Fast Boot did not help.
    I have installed the latest drivers, I even tried to update the firmware of my SSD, but Intels toolbox told me, that my 3 years old 520 series SSD (never had seen any firmware updates before) was up-to date! Thus Windows 8.1 should handle with it. I also
    did a quick analyzation with the tools, but everything was ok.
    I just run chkdsk /r /f, as Zigzag proposed, but I had nearly the same problems as you have had:
    Chkdsk got stuck at 10 % for 10 minutes then the machine rebooted with the 2 minutes delay and event logs do not show any Checkdisk entry.
    In the Applications log, I noticed a igfxCUIService1.0.0.0 sourced entry as the first entry after reboot approximately 2 minutes after the end of the delay: The description of the event-ID "0" from the source "igfxCUIService1.0.0.0" could not be found. Event:
    started/resumed which sounds ok. But it says that the component that caused this event, is not installed. (my translation from the German log)
    The device manager shows that everything is fine and working well.
    Here's my System constellation:
    Gigabyte Z77X-UD3H, Intel Ivy Processor i7-3770 with 32 GBytes RAM, Intel 520 Series SSD via SATA 6G, BD Writer from LG via SATA 3G
    BIOS F20e with UEFI and Secure Boot enabled (Windows 8.1 did install the GPT partitions):
    Fast Boot enabled/disabled doesn't bother,  Intel Virtualization  Technoloy Enabled, VT-d enabled, OS Type Windows 8, Network Stack disabled, Secure Boot Mode standard,  AHCI, USB 3.0 xHCI, Internal Graphics Size now 32M, (didn't bother up
    to 512M, 1024M BIOS POST-screen endless loop), Intel Rapid Start Technology Enabled (disabled same effect) => I installed Windows 8.1 with "Intel SATA Preinstall driver For AHCI  RAID Mode" in the F6 mode, as Intel recommended, Marvell ATA Controller
    for eSATA (disabling same effect), ErP same effects on dis/enabled.
     Windows 8.1 Pro German. Same effect when with or without LAN connected
    I am thinking of Reinstalling Windows 8 with CSM mode without UEFI, but I believe that would not have any effect. Maybe I'll try another system disk for a reinstallation (HDD or other older SSD).
    It would be nice if this problem could be solved by the community or by Microsoft, since I am not the only one!
    Peter

  • 990fxa-gd80 resume issue

    Hello, i hope someone among you good guys can help me with a very annoying issue i am experiencing in my system, that is driving me mad and that i could not solve in a month of tries. I own an HTPC based on the following configuration:
    AMD Phenom II X4 945 CPU
    MSI 990FXA-GD80 M/B
    8Gb Corsair XMS3 DDR (2x4Gb)
    Corsair AX-650 PSU
    Samsung 256Gb 830 SATA SSD (2 partitions, system + data), AHCI SATA mode
    Seagate 3Tb Barracuda SATA HDD with GPT table
    ATI HD 5750 video card (2 displays attached)
    Terratec Cinergy DVB-S2 card
    Hauppauge HVR-2200 DVB-T card
    Silverstone LC-16m case with Imon VFD + Imon Pad remote and USB card reader
    Internal serial port, 1394 and eSATA ports enabled
    Logitech USB Webcam, USB speakers and USB G110 illuminated keyboard
    Toshiba laser mouse
    Windows 7 x64 sp1, windows Media Center + DVBLink TV source, MST and various other programs.
    Hibernation disabled
    No overclok
    I used this HTPC with much satisfaction from nearly 1 year, never experiencing an issue: i used to keep it in S3 mode 24/7 and it always got out from S3 state to record TV programs without any problem.
    I installed the second drive, the 3Tb Seagate Barracuda, the first week of september. Then a day between the firsts of october i installed Mediaportal to give it a try; fearing system modifications by that software, i saved a backup image in my second drive. After a pair of days (or maybe at that time i noticed it for the first time), the issue has started.
    The issue consists in a strange system freeze when the HTPC tries to wake up from S3: when the HTPC tries to exit S3 state the case led gets on, the HDD led blinks once or twice and then fans start running loudly and the HTPC freezes BEFORE the display can show any image (it remains black and goes to power saving mode) - power led on and HDD led off. No blue screen (the display is off). No memory dump. Keyboard's leds off. No manual crash dump possible. All i can do is keep power switch pressed until system complete shutdown.
    But the really strange thing is that it happens ONLY once or twice a day, in the rest of the times the HTPC gets to wake up from S3 normally without any issue: it usually wakes up from S3 a number of times per day (7/8 minimum), but only 1/2 times the freeze issue happens (more often early in the morning or around twilight, seldom in other time slots)... Also, when on, the HTPC runs flawlessly as ever.
    Thinking MP was guilty in some way, i restored the backup image but unfortunately the issue didn't disappear! So MP was no to blame... something different had happened to my PC...
    I think you can understand that such an issue is really serious for an HTPC, because it makes it really untrustable for scheduled recording work: often recordings fail because of the HTPC freezing when it tries to resume... my wife is really sad about it...
    Trying to solve the issue, i made the following:
    running memtest and video card memory test - no error found
    change nearly every MST options - no effect
    reading carefully W7's event viewer logs after and between freezes - nothing found that could clarify the issue
    changing all ACPI and power related BIOS options (C3 support, EUR 2013, CPU phases, DDR phases, shadowing, etc...) - no effect
    updating BIOS and all drivers - no effect
    disabling cool'n'quiet - no effect
    unplugging Segate 3Tb HDD - no effect
    unplugging all external and internal USB devices (except mouse) - no effect
    uninstalling ATI video card and running with legacy drivers - no effect
    disabling embedded Ethernet adapter - no effect
    unplugging the second display (an HDTV) - no effect
    tried to get a manual crash dump - not possible as when the issue happens the HTPC is freezed
    Those tries took very long to be made, because every time i have to wait all day long for the issue to happen: it NEVER takes place if i wake up the HTPC after a few seconds sleep, seems like it needs at least a few hours of S3 state to take place.
    Now, many particulars of the issue seem to lead to a compatibility problem between PSU and motherboard: i read about other users experiencing similar problems using high-end PSUs (min load related?), problems they solved by finding older or cheaper PSUs compatible with their MB (that's a blind try thing, luck was needed)... but in all cases PSU functioning was not bad, so no RMA was possible. Anyway, it is obvious that changing MB solved the issue as well... so Corsair support states it is not a PSU issue but a MB related one.
    This seems to be a frequent problem for intel z68 based MBs, but i suspect my 990fxa MB can show the same compatibility issue with Corsair AX PSU, assuming some power related modification has happened in the last month in PSU or MB circuitry.
    So i would like to know if someone else is/is not experiencing the same issue using same MB and PSU; more, i would like to know what 80+ PSU is SURELY working flawlessly with my MB, in case i should have to solve the issue by replacing the Corsair PSU (that is manufactured by Seasonic); finally, i would like to ask MSI technicians to verify the issue and possibly working around it with a BIOS update (maybe raising resume initial load, if PSU min load is to blame).
    Thanks in advance.

    Even with AMD power reduction, consumption while on is nearly ten times than in standby... it happens me to leave my PC in S3 for 3/4 days, so power consumption would be too much (i write from Italy and here AC current is much expensive!).
    Anyway, i took a more accurate look around about PSU/MB incompatibility and i'm now sure enough that this is the problem. It seems certain MBs in power saving modes (like S3) require a too low power from PSU, so that PSU min load is not achieved, that makes it malfunction. This happens to new, energy efficient PSUs, that eliminate minimum load resistors to achieve maximum efficiency...
    Look at this: http://www.silentpcreview.com/forums/viewtopic.php?t=58802.
    So this issues happen because MB is too efficient (it requires too low power from PSU) and PSU is too efficient itself (it eliminates power used to remain above min load in power saving). Is this true? It seems ridicolous to me!!!!!!! To save a couple of watts we are forced to leave PC on so wasting dozens of watts? Are PC engineers really dummies?
    BUT it looks like this can easily be solved by a BIOS adjustment, isn't it?

Maybe you are looking for