X99 SLI - XMP won't boot anymore

Hey,
My cat decided to jump on my PC and in doing so, turned the computer off while I was mid game (Borderlands 2). When I attempted to restart the computer, the splash screen saying something along the lines of "The previous OC settings have failed" was displayed and reset my bios settings to default.
I had been using the XMP profile for a good month without any issues. I did OC testing a while ago and ever further OC'd the machine without issue. Since this fiasco, I've disable the use of the power button to turn the computer off via windows, so it shouldn't happen again, but I can't understand how the computer turning off abruptly can affect hardware in a way it can't boot properly.
Anyone know what could have happened or how I can restore my PC back so it can run in XMP settings?
Build:
Core i7 5820k
MSI X99S SLI
EVGA GTX 970 SSC
Corsair RM 650
GSKILL DDR4 3000 (4x4)
Be Quiet! Dark Rock Pro 3

sudden shutdown of Windows will sometimes cause some unexpected issues,
basically you just need to clear CMOS, load bios default and then enabled again the XMP... that's all 
if your system is unexpectedly shutdown a lot of times, it could also cause Windows to crash 

Similar Messages

  • X99 sli-pluss won't boot.

    Greetings!  I've recently purchased a new computer. The choice fell on the X99 sli-Pluss,  a 5930k and Corsair 2666 mem and - Gtx 690. The computer has been working great the last couple of weeks. Did a reboot 2 install my stream card and a secondary graphics card.  Computer did not boot.  Took the cards out and restarted.  Still no boot. It stops @ 9C Msi x99 sli:

    9C = USB Detect
    that says to me you have a issue with a USB device you have plugged in! so what USB devices do you have plugged in buddy as I cannot see in your video?

  • K9N SLI System won't boot anymore

     
    Hi!
    My system was working fine until I switched it off yesterday. Usually it is switched on for quit a long time, several days or sometimes even weeks (Stuff downloading etc.) As I first built the system I had some temperature issues, but a cool big Zalman CPU Cooler and some well placed Fans in the casing solved it. For three, four months it has been working fine.
    But, since it is pretty hot over here the last few weeks I decided to switch it off at night so it wouldn't produce so much heat in the room. The next day as it wouldn't switch on I noticed that the Power LED was still burning, although everything else had shut down.
    Does anybody know what this could be?
    I already reduced the whole thing to the bare nescessities to find a source for the problem. Regretfully it doesn't change anything. As soon as I switch the power supply on the Power LED starts to burn and nothing else happens...
    Does this mean the MB is a goner??? And if so, why suddenly now, after working fine for several months? Or maybe the CPU? I don't have double parts so I can't test other components. And again: why now after functioning perfectly?
    The specs:
    K9N SLI (MSI 7250 V. 2.1)
    AMD Athlon 64 4600+ DC
    2x OEM 1GB DDR2 667 MHz
    2x Winfast PX7600GT in SLI Mode
    Latest available BIOS & Drivers (LIVE Update)
    The last temperatures I saw were around 42 Degr.Celcius while on but idle and around 51 when active (games etc.) so I wouln't expect that to be the prob.
    Thanks for any useful help!
    Willem

    Well, the question about the PSU made me take a good look at the thing and it turns out it is a dual rail PSU or whatever they call it. When I was looking through the forum for similar problems I noticed that a lot of you out there hate those because they more then once cause problems...
    Since I didn't have any way to check the PSU I yust bought myself a relatively cheap one, single rail, with 420V and what do ya know... It now works perfectly again.
    I don't know if the current temperatures have anything to do with it but maybe the heat was too much for the other one but it just caused a startup problem. Since the system had been running for a while I got stuck with the problem when I switched it off......
    Anyway, I start looking for a decent PSU now. Henry, Thanks for setting me on the right track!

  • Mac mini won't boot anymore

    My Mac mini won't boot anymore. It's been running fine for months.
    It's running Leopard Server 10.5.2 Build 9C31
    It starts to boot, I get the first spinning gear with the gray screen, then the blue desktop blinks, then a second spinning gear on a gray screen and it appears to hang (the gear stops spinning).
    I booted off the install DVD, ran disk utility, repaired the HD, repaired the permissions: the behavior is the same.
    Safe mode doesn't work (same hang as above).
    Single user mode does work.
    I can connect to it via Server Admin while it appears hung.
    The last few lines of the system log are:
    May 15 18:38:58 server emond[67]: SetUpLogs: uid = 0 gid = 0
    May 15 18:38:58 server emond[67]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
    May 15 18:38:59 server kextd[23]: writing kernel link data to /var/run/mach.sym
    May 15 18:39:09 server KernelEventAgent[59]: tid 00000000 received unknown event (12)
    May 15 18:39:20 server kernel[0]: display: Not usable
    May 15 18:39:20 server com.apple.KerberosAutoConfig[126]: Kerberos configuration is up to date
    May 15 18:39:20 server com.apple.ATSServer[125]: FODBCheck: New annex file created
    May 15 18:39:21 server ARDAgent [130]: ******ARDAgent Launched******
    May 15 18:39:21 server com.apple.KerberosAutoConfig[132]: Kerberos configuration is up to date
    May 15 18:39:22 server ARDAgent [130]: call logout from LoginLogoutProxyCallBackFunction
    May 15 18:39:22 server com.apple.launchd[1] (com.apple.RemoteDesktop.agent): Throttling respawn: Will start in 9 seconds
    May 15 18:39:24 server loginwindow[58]: Login Window Started Security Agent
    May 15 18:39:29 server servermgrd[53]: servermgr_calendar: created default calendar virtual host
    May 15 18:39:31 server ARDAgent [146]: ******ARDAgent Launched******
    May 15 18:39:32 server ARDAgent [146]: ******ARDAgent Ready******
    May 15 18:39:33 server mdworker[109]: (Error) SyncInfo: Boot-cache avoidance timed out!
    May 15 18:39:54 server Python[47]: CGImageSourceCreateWithData data parameter is nil
    May 15 18:39:54 server com.apple.wikid[47]: Thu May 15 18:39:54 server.jeff.carpenter.name Python[47] <Error>: CGImageSourceCreateWithData data parameter is nil\n
    May 15 18:39:56 server kernel[0]: AppleYukon2 - bad packet received. length: 1440, packet status bits: MII error
    May 15 18:39:56 server kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSWRITEDATA SBF /dev/dtracehelper 13 (seatbelt)
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /dev/autofs_nowait 13 (seatbelt)
    May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /usr/sbin 13 (seatbelt)
    May 15 18:55:12 server kernel[0]: AppleYukon2 - bad packet received. length: 23, packet status bits: MII error
    Any ideas?

    Yes, it's been running Server since I purchased it.
    I doubt the serial number is in use elsewhere: I purchased the 10-user version at a retail store in a sealed package and I've only installed it once.

  • Won't boot anymore but in safe mode

    My laptop won't boot anymore. I get a gray screen with a prohibition sign. Here's what I found so far:
    If I boot in the verbose mode it gets stuck on something like Looking for boot device.
    I zapped the PRAM. Didn't help.
    I can boot in safe mode.
    I used Disk Utility to check the drive and permisions. Everything ok.
    I can't boot from the original Snow Leopard DVD. I press C, the drive spins then stops.
    I reinstalled Snow Leopard from the safe mode. Didn't help.
    In safe mode Safari is crazy slow. Firefox runs full speed.
    Any idea?

    Reinstall OS X without erasing the drive
    Do the following:
    1. Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list.  In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive.  If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Reinstall Snow Leopard
    If the drive is OK then quit DU and return to the installer.  Proceed with reinstalling OS X.  Note that the Snow Leopard installer will not erase your drive or disturb your files.  After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
    Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.
    Unless you can boot from your installer DVD there's nothing you can do to reinstall OS X, so I'm not sure how you did reinstall as you said.
    Booting From An OS X Installer Disc
    1. Insert OS X Installer Disc into the optical drive.
    2. Restart the computer.
    3. Immediately after the chime press and hold down the "C" key.
    4. Release the key when the spinning gear below the dark gray Apple logo appears.
    5. Wait for installer to finish loading.

  • Powermac G5 1.8Ghz June 2004 won't boot anymore

    Hi all,
    Past week i've bought a second hand PM G5. At first it seems to be all ok, but right now its not working anymore.
    I've managed to install the OSX on the first evening i've had the PM G5. After installing evrything seemed to be fine. But after 30 minutes surfing on the internet, it froze. I had to give it an hard reset by holding down the power button.
    After turning it of, it won't boot anymore. after a few times trying with 10 secconds between it, i unpluged the powercabel for 2 minutes. Wile turning it on after 2 minutes, it was booting , but it stopped booting after 1,5 minute and froze.. after hard resetting it, i've managed to boot it right. The OS seemed to be ok again, but after 5 till 10 minutes it froze again.
    Right now it won't boot anymore... it starts (without the front light, this light only blinks fast once i turn it on, but after that no more. Sometimes it won''t even flash.
    I've been buzzy replacing some components to get to know if it was a hardware fail. I've first replaced the PSU with two other PSU's from the PM G5, but won't do a thing.
    The i've replaced the memory with 4 kind of difrent pairs, but won't do a thing either. At last i replaced the Logic Board, this won't even do a thing about it.
    Of course i replaced the PRAM battery first, but also this won't help me.
    I've tested it in AHT, but evrything was working well, according to AHT. I've managed to get the system log, but nothing scarry though here also, only some 122 errors some times. (download the system log here: http://www.mijnbestand.nl/Bestand-F4DDN66WLRCI.log )
    I've reset al things possible like PRAM reset, PMU reset. Nothing seem to be working.
    What can i do next to get this thing work?? I'm getting nut's here..
    Please help..
    Thanks a Lot
    MArtijn Snoek

    Hi martijnsnoek, and a warm welcome to the forums!
    Can you count the beeps or flashes?
    1 beep = no RAM installed
    2 beeps = incompatible RAM types
    3 beeps = no good banks
    4 beeps = no good boot images in the boot ROM (and/or bad sys config block)
    5 beeps = processor is not usable
    In addition to the beeps, on some computers the power LED will flash a corresponding number of times plus one. The LED will repeat the sequence after approximately a 5-second pause. The tones are only played once.
    Note: In this case, a flash is considered to be 1/4 second or 250 ms or greater in length.
    http://support.apple.com/kb/HT1547
    So, with the info you given, two things come to mind...
    Bad solder joints around the RAM slots, try heating that area with a Hair Dryer for 3 to 5 minutes, then see if it starts.
    If you can get it running, Get Temperature Monitor to see if it's heat related...
    http://www.macupdate.com/info.php/id/12381/temperature-monitor
    And/or iStat Pro...
    http://www.islayer.com/apps/istatpro/
    If you have any temps in the 70°C/160°F range, that's likely it.
    BTW, have you blown the dust out of it since you got it?

  • Won't boot anymore after nvidia-xconfig

    Hey Guys,
    Got a problem with my Arch Linux here, hope you can help.
    Today I tried to install the official Nvidia Driver and BumbleBee following along the great Wiki on this topic.
    Everything worked just fine and I also could run optirun gfxgear or somemthing like this.
    I wanted to switch to the Nvidia Settings in the settings menu and it told me to configure my xconfig and restart x so I typed nvidia-xconfig in the terminal and it gave me an success output.
    I restarted my system and now it hangs on the graphical thing I think. It won't boot anymore.
    Hope you can help me out.
    Thanks alot
    Edit: My Nvidia Card is a Nvidia GT 740M if this matters
    Last edited by Whitz (2015-02-09 11:02:41)

    No, I have a laptop with 2 graphic cards an intel hd4000 and a nvidia gt 740m.
    I ran the Arch Linux installation well until I tried to get the nvidia gt working with bumblebee.
    I followed the wiki of the bumblebee topic and it worked well. I wanted to switch into the nvidia settings and it told me my x isnt configured properly and I should type nvidia-xconfig and restart X.
    After the restart it won't boot to the graphical interface anymore.
    Hope this cleared up the things
    Also I dont get any errors but it just wont load..
    Last edited by Whitz (2015-02-09 12:08:49)

  • Re: Satellite C850 won't boot anymore - broken HDD

    Hello Folks,
    I bought a *Toshiba Satellite C850 - 1F2* with *+Windows 8+*.
    After installing, upgrading to *+Windows 8.1+* and setting up everything, the whole machine worked pretty fine.
    BUT since yesterday the laptop won't boot anymore!
    When I turn it on, the HDD makes click and click and the system tries to boot from DVD, from USB, from HDD, from IPV4, from IPV6 and then it says, that there is no bootable device.
    Unfortunately I wanted to make the +Windows 8 Restoration-/Rescue-DVDs+ this weekend!
    Huh!!!
    Well, I still have an *+original Windows-7-DVD and license+*, which would be good as well (I used it the last years).
    *YET*, I cannot install *+Windows 7+*.
    It says something like that, that +this system is not available for Secure Boot+.
    I read about "Secure Boot".
    So I pressed F2, turned the laptop on and could with this reach the BIOS.
    It is a *+InsydeH20 Rev. 3.7+*.
    *BUT*, when I go to "Boot Mode" I can only see, that this option is greyed and I cannot change from +UEFI Boot+ to +CSM Boot+.
    Even the change of the HDD made no difference.
    I put in my old HDD with Windows 7 installed (wich works in the other laptop), but the system won't boot, for it is +not suitable for Secure Boot+.
    *So, WHAT NOW?*
    I mean, it cannot really be the Toshiba politics, that you need to throw away your laptop, if the HDD breaks, can it?
    For I didn't create the Rescue-DVD, I have just my Windows 7 DVD and another HDD with installed Windows 7.
    Do I need to buy another Windows 8 licence and another HDD, to install Windows 8 (suitable for Secure Boot) again?
    Would it even work like that?
    Or is there any chance to upgrade the BIOS, for that I can then change from UEFI Boot to CSM Boot?
    Or is there any other chance, to use my other HDD with Windows 7, or at least a new clean HDD, on wich I then can install my Windows 7 OS?
    I hope, that someone can give me any good advice, what to do now ... without throwing the Toshiba laptop away ;)
    Thanks in advance!

    If the HDD died, in needs to be replaced.
    If notebook is still covered by warranty, the HDD will be replaced free of charge. If warranty isnt valid, you will need to pay for the new HDD.
    I think this understandable.
    _Now some facts about the Recovery disk._
    If you did not create a recovery disk in the past, you could order the recovery medium on this page: http://backupmedia.toshiba.eu/landing.aspx
    The recovery disk would install the Toshiba image and would set the notebook back to the same state like at the first day of purchase.
    _Regarding the Win 7 installation:_
    Usually to install the non UEFI capable system, the secure boot needs to be disabled and boot mode needs to be set to CSM mode.
    If this isnt possible you should update the BIOS but to do that you need an running Windows system (Win 8).

  • Satellite L40 18P won't boot anymore

    Hello folks,
    my Satellite L40 18P won't boot anymore. All I get is the Power LED to go green. The DVD ROM drive blinks and I can open and close it - but that's it. Nothing else happens.
    Any idea in the forum what I can do to get the notebook boot again ? Or please ask questions for additional details.
    many thanks, Johi 13

    Hi,
    wow, that was fast.
    No, I can't see anything - the screen stays black. I do not hear the HDD start, neither do I hear the fan.
    This behavior appeard for the first time yesterday evening.
    Last activity was (if I remember correctly) closing the lid and sending the notebook to standby.
    So far, I haven't tested it with an external monitor.
    thanks, Johi13

  • SRW248G4P switch won't boot anymore

    I have a Linksys Cisco Small Business switch model SRW248G4P which won't boot anymore. This is what I see with Putty when it boots (console interface):
    Image Loader 1.0.1
    Loading Diagnostic Image File : SRW224G4P_SRW248G4P_boot.bix
    Diagnostic 1.0.1
    in
    The boot file seems to be the problem.
    Does anyone have a solution for this problem? Some kind of hardware reset?
    Kind regards
    (I know it is not officially supported anymore, but I am still looking for some help)

    Hi Aleksandra,
    Thank you for your reply. By pressing Crtl+u rapidly while booting I managed to get in the download/xmodem menu.
    Output:
    Image Loader 1.0.1
    File Name                         S/Up Type Size       Create Time
    $logfile_1                          0    3         64  1193046:28:15
    Factory_Default_Config.cfg          0    5        354  24:01:02
    SRW224G4P_SRW248G4P_boot.bix        1    1    1377600  00:01:03
    SRW224G4P_SRW248G4P_image.bix       1    2    3517532  00:03:42
    certificate                         0    8      18040  24:00:55
    startup-config                      1    5       5596  25:40:57
    startup1.cfg                        0    5       5537  24:01:14
    Free Space : 2097152
    [X]modem Download  [D]elete File  [S]et Startup File
    [Q]uit
    Select>
    Which image should I send to the switch?
    The image provided by the official support page:
    http://software.cisco.com/download/type.html?mdfid=282414078&flowid=3659
    (version 1.0.2 or version 1.3.1)
    Or the image referred to by vasukris (Moorthy) (above) (version 1.2.3 or version 1.2.2b)
    Considering the advice of Tom Watts
    ( https://supportforums.cisco.com/discussion/11733231/srw248g4p-loader-binary-checksum-error-runtime-loading-fail-system-halt )
    "1.2.2a is 1.0.6 boot code.
    1.2.2b is 1.0.1 boot code.
    1.2.3.0 is 1.0.2 boot code
    It looks like you're using 1.0.1 boot code so the 1.2.2b firmware should be for you."
    Thank you in advance!

  • Btrfs: System won't boot anymore after unclean shutdown

    Hi,
    I have a problem with my ArchLinux (kernel 3.19.2-1-ARCH).
    I have my root partition as BTRFS and no /boot partition.
    After an unclean shutdown the system won't boot anymore.
    GRUB loads the kernel and the kernel starts but it hangs saying: Mounted /dev/sda3 on real root.
    Then, I have to start a Live CD and do:
    btrfsck /dev/sda3
    After that the system boots correctly.
    I've tried adding fsck to the HOOKS in the mkinitcpio.conf file and in fact it tries to fsck the filesystem (but with BTRFS, fsck.btrfs doesn't work...)
    What can I do?
    Thanks

    I'm also having this problem. I tried booting up the netinstall image to debug it, but I can't mount my btrfs volume from there either: mount just hangs. After a while, the kernel goes:
    [...] INFO: task mount:612 blocked for more than 120 seconds.
    [...] Not tainted 3.19.2-1-ARCH #1
    [...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [...] INFO: task btrfs-transacti:636 blocked for more than 120 seconds.
    [...] Not tainted 3.19.2-1-ARCH #1
    [...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    From this post I guessed that I might just need to wait so that I could defrag the volume once it was mounted, but it's been hanging for over 15min now (the message above continues to come up periodically).
    Like the OP in the thread I linked to above, my btrfs volume is inside an LVM volume (which is on dm-crypt). Don't know whether that's relevant.
    Output of btrfs-check:
    Checking filesystem on /dev/pixie/btrfs
    UUID: e04cc661-e31a-4dbf-870d-664bc913e34a
    found 76855677062 bytes used err is 1
    total csum bytes: 72928436
    total tree bytes: 2092515328
    total fs tree bytes: 1888452608
    total extent tree bytes: 104644608
    btree space waste bytes: 357251032
    file data blocks allocated: 181197139968
    referenced 109440282624
    btrfs-progs v3.19
    dmesg output:
    [ 36.824998] Btrfs loaded
    [ 36.826713] BTRFS: device fsid e04cc661-e31a-4dbf-870d-664bc913e34a devid 1 transid 98618 /dev/dm-3
    [ 46.219014] BTRFS info (device dm-3): disk space caching is enabled
    [ 46.259830] BTRFS: detected SSD devices, enabling SSD mode
    [ 240.333313] INFO: task mount:539 blocked for more than 120 seconds.
    [ 240.335542] Not tainted 3.19.2-1-ARCH #1
    [ 240.337795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 240.340263] mount D ffff8800cf2837f8 0 539 453 0x00000000
    [ 240.340277] ffff8800cf2837f8 ffff8800cf2331b0 0000000000013f00 ffff8800cf283fd8
    [ 240.340286] 0000000000013f00 ffffffff81818540 ffff8800cf2331b0 ffff8802094f67a8
    [ 240.340291] 0000000000000004 ffff8800cf283758 ffffffffa0a2fc91 ffff8802094f67a8
    [ 240.340298] Call Trace:
    [ 240.340335] [<ffffffffa0a2fc91>] ? set_extent_buffer_dirty+0x71/0xc0 [btrfs]
    [ 240.340357] [<ffffffffa0a05796>] ? btrfs_buffer_uptodate+0x56/0x80 [btrfs]
    [ 240.340366] [<ffffffff8155e999>] schedule+0x29/0x70
    [ 240.340389] [<ffffffffa0a47745>] btrfs_tree_lock+0x65/0x200 [btrfs]
    [ 240.340396] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
    [ 240.340410] [<ffffffffa09e5cd9>] btrfs_search_slot+0x799/0xaa0 [btrfs]
    [ 240.340425] [<ffffffffa09e79f5>] btrfs_insert_empty_items+0x75/0xd0 [btrfs]
    [ 240.340446] [<ffffffffa0a47a37>] btrfs_insert_orphan_item+0x67/0xa0 [btrfs]
    [ 240.340465] [<ffffffffa0a4a12e>] insert_orphan_item+0x5e/0x90 [btrfs]
    [ 240.340482] [<ffffffffa0a4c531>] replay_one_buffer+0x361/0x380 [btrfs]
    [ 240.340504] [<ffffffffa0a2f244>] ? alloc_extent_buffer+0x34/0x370 [btrfs]
    [ 240.340523] [<ffffffffa0a488f3>] walk_down_log_tree+0x1d3/0x410 [btrfs]
    [ 240.340540] [<ffffffffa0a48bfb>] walk_log_tree+0xcb/0x1d0 [btrfs]
    [ 240.340558] [<ffffffffa0a507f7>] btrfs_recover_log_trees+0x1e7/0x490 [btrfs]
    [ 240.340575] [<ffffffffa0a4c1d0>] ? replay_one_dir_item+0xf0/0xf0 [btrfs]
    [ 240.340596] [<ffffffffa0a08b3e>] open_ctree+0x17ae/0x2030 [btrfs]
    [ 240.340609] [<ffffffffa09dd633>] btrfs_mount+0x843/0x920 [btrfs]
    [ 240.340618] [<ffffffff8117b7aa>] ? pcpu_alloc+0x35a/0x680
    [ 240.340628] [<ffffffff811d5d68>] mount_fs+0x38/0x1c0
    [ 240.340634] [<ffffffff8117bb05>] ? __alloc_percpu+0x15/0x20
    [ 240.340641] [<ffffffff811f116b>] vfs_kern_mount+0x6b/0x120
    [ 240.340647] [<ffffffff811f4184>] do_mount+0x224/0xb40
    [ 240.340653] [<ffffffff811f4dae>] SyS_mount+0x7e/0xe0
    [ 240.340661] [<ffffffff81562809>] system_call_fastpath+0x12/0x17
    [ 240.340671] INFO: task btrfs-transacti:561 blocked for more than 120 seconds.
    [ 240.342927] Not tainted 3.19.2-1-ARCH #1
    [ 240.345175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 240.348473] btrfs-transacti D ffff88020b88bd98 0 561 2 0x00000000
    [ 240.348483] ffff88020b88bd98 ffff880211edc590 0000000000013f00 ffff88020b88bfd8
    [ 240.348491] 0000000000013f00 ffff8802162289f0 ffff880211edc590 ffff8802094a70c8
    [ 240.348496] ffff8802094d8000 ffff880200000000 ffff8802094d8000 ffff880200000033
    [ 240.348501] Call Trace:
    [ 240.348511] [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
    [ 240.348525] [<ffffffffa09e07ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
    [ 240.348543] [<ffffffffa0a64213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
    [ 240.348550] [<ffffffff8155e999>] schedule+0x29/0x70
    [ 240.348568] [<ffffffffa0a0b555>] btrfs_commit_transaction+0x2a5/0xbe0 [btrfs]
    [ 240.348573] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
    [ 240.348590] [<ffffffffa0a06fc5>] transaction_kthread+0x1d5/0x240 [btrfs]
    [ 240.348605] [<ffffffffa0a06df0>] ? btrfs_cleanup_transaction+0x5a0/0x5a0 [btrfs]
    [ 240.348611] [<ffffffff81091748>] kthread+0xd8/0xf0
    [ 240.348617] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
    [ 240.348624] [<ffffffff81562758>] ret_from_fork+0x58/0x90
    [ 240.348629] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
    Last edited by ouroboros8 (2015-04-02 12:37:25)

  • MSI X99S SLI PLUS and XP941 - Booting, but very erratic behavior

    I finally got my XP941 to boot in my X99S SLI PLUS using the beta BIOS. I Still can't see it listed as a drive in the system settings, but Windows 8 install sees it just fine, and I can see the "Windows Boot Manager" option available to boot from. Windows is booting just fine now, however it will  freeze up for about 3 seconds about every 10 seconds. I used CrystalDiskMark and found that speeds were over 1000MB as expected for sequential reads, but 4KQD32 reads were absolutely abysmal. I can't remember the exact number, but it was around .012 I've seen other reviews of the XP941 showing much higher speeds than this. I think the slow random read performance is causing the machine to lockup and have erratic behavior.
    Does anybody have any ideas? or can anyone confirm that their SLI Plus is running this m.2 ssd just fine?
    Another note is that I am only using 1 4GB Single Dimm of memory until my real memory kit arrives. Would running just a single dimm cause this?

    Quote from: Smalto on 04-October-14, 19:19:01
    Hello cbutters, I have the same configuration and I cannot manage to have the XP941 working (MZHPU256HCGL-00000).
    The win8.1 setup does see it but after copying the files and rebooting it won't start.
    What bios version do you use ? Can you indicate the specific settings you modified in the bios to have it working ?
    thanks
    Using BIOS 136 from here: https://forum-en.msi.com/index.php?topic=183560.0
    Using default BIOS settings to start from, then enabling windows 8/8.1 features and changing it to M.2 PCIe. I didn't touch the SATA Config after loading defaults. (I don't have any memory remapping settings available to me either).
    Keep in mind that the device won't show up as a sata device, so don't even bother looking for it. You just have to start installing windows and trust that it will show up....  make sure after initially installing windows 8.1 and first reboot that your first boot option is "Windows Boot Manager". The install was really quick. See my youtube video here:

  • My MacBook won't boot anymore. What can I do?

    Hi,
    yesterday I upgraded to Mountain Lion. After the installation, my MacBook booted and everything seemed fine. I started using Mountain Lion. Then I shut my MacBook down and I won't boot up anymore today. What can I do?
    Additional Information:
    MacBook Pro 13" Early 2011
    Upgraded HDD to SSD (OCZ Petrol 256GB)

    What did you do to fix it?

  • Treo 800w won't boot anymore

    For the last few weeks my treo 800w has been having random problems with shutting off and then not wanting to boot or requiring a hard reset to boot again. It now won't boot even doing the hard reset procedure. Also the led doesn't come on when it is plugged in anymore. It comes up to a blue screen with small white boxes in the upper left when it comes on after trying the hard boot. Any ideas what went wrong with it ?
    Post relates to: Treo 800w (Sprint)

    I would bring it in to your local Sprint store to see if they can fix it or replace it under your insurance plan.
    Alan G

  • MSI X99 SLI Plus - Won't Post

    I've got:
    Motherboard: MSI X99 SLI Plus
    Processor: Intel Core i7-5820K
    Memory: G.Skill Ripjaws Series 16GB (4 x 4GB) DDR4-2400
    Power Supply: EVGA 850W 80+ Gold Certified Fully-Modular ATX
    It's a new build and I can't get it to post. When I try to turn it on, a red LED located next to the 24 pin ATX power connector comes on and will not go off until I cut the power at the Power Supply. I can't find anything online concerning the red LED. Is it some overvoltage protection? An issue with the memory? I'm at a loss trying to diagnose this. Please see the images below:

    Hello.
    I'm having the exact same issue.
    My computer was running with no issues for over 1 month and today when i tried to start it this exact issue happened.
    The lights on the rest of the motherboard are working (CMOS, Power, OC Genie) but it won't post.
    I have tried to reset the CMOS, re-seated and tried various configurations for the RAM, tried both BIOS and OC Genie on and off and the issue remains.
    Could this be a PSU issue? If so, would the remaining lights work?
    Anyone else had this issue and how did you fix it?
    Thank you in advance!

Maybe you are looking for