Windows 10: BSOD 0x000000fc - Random Times (Or atleast as it appears)

Discus and support BSOD 0x000000fc - Random Times (Or atleast as it appears) in Windows 10 BSOD Crashes and Debugging to solve the problem; Hello All, I have aquired a computer which seems to BSOD at random times. I have cleaned, reformated, full deep erase of the drive and stress tested... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by ekeel, Nov 3, 2016.

  1. ekeel Win User

    BSOD 0x000000fc - Random Times (Or atleast as it appears)


    Hello All,

    I have aquired a computer which seems to BSOD at random times. I have cleaned, reformated, full deep erase of the drive and stress tested components on the machine. The stress tests I have done seem to indicate the RAM, CPU and SSD are fine.

    The computer still Blue screen's, this is when left idle on the windows 10 desktop so no external applications were in play. There are 3 logs in the zip attached, 2 of these are prior to the stress testing and deep erase of the drive with the latest being since doing a clean install. As it stands the computer is a clean windows 10 which is as up to date update wise from the media creation tool (as of this week). Computer is:
    SanDisk 128GB SSD
    i7-4770
    24gb DDR3 RAM

    From looking at the dumps the common occurance is 'ntoskrnl.exe' which means very little to me and a quick google search seems to indicate a wide array of issues. As the BSOD's appear random I am unable to work out where this problem occurs. My own personal guess would have been the onboard satacontroller or PSU as the system does not seem to always like a 2nd HDD, though this could be coincidence. The PSU idea stems from the fact the 2nd HDD seems to be blank(no longer in the machine) and for a while looked dead. This HDD has been looked at by another person and besides being blank the sectors and what not seem to be fine.

    Any help would be great. Thank you, as this is during work, I may not see all responses till Monday!

    :)
     
    ekeel, Nov 3, 2016
    #1

  2. Windows 10 freezing, shutdown, BSOD errors and constant 100% disk usage.

    Specs added to post.

    BSOD errors happen every couple of days, but random shutdowns after a few minutes of online time are more common. Also there is the constant high disk usage, >90%.

    Tried the driver verifier method some time ago but it does not makes my pc crash for the BSOD errors to appear nor do i know what exactly makes my pc crash.
     
    SanndyTheManndy, Nov 3, 2016
    #2
  3. "WHEA_UNCORRECTABLE_ERROR" BSOD while watching video in browsers (Google Chrome, Mozilla Firefox)

    Here are the bsod_minidumps, MSInfo32_export, Speccy_export.

    It's very strange that this behaviour is random - it appears from time to time. Sometimes I watch video and there is nothing, sometimes there are several BSODs in a row. I didn't find a straight corellation between watching videos in a browser and BSODs,
    but I have noticed that BSOD doesn't appear when I do all the other things (watching video in a local desktop player, playing games, working with Office, etc.).
     
    Nikita Glukhov, Nov 3, 2016
    #3
  4. axe0 New Member

    BSOD 0x000000fc - Random Times (Or atleast as it appears)

    Hi ekeel,

    Welcome to the 10forums and apologies for the delay.

    Are you still in need of help?
     
    axe0, Nov 6, 2016
    #4
  5. ekeel Win User
    No problems with the delay I wouldn't have been able to do anything during the weekend anyways. Yes I would still like help.
     
    ekeel, Nov 6, 2016
    #5
  6. axe0 New Member
    Please provide information about the stress tests performed.
     
    axe0, Nov 6, 2016
    #6
  7. ekeel Win User
    I ran prime95 as a CPU and Memory stress test for 12 hours. I also ran the a 'System Stability Tester', and a 'CPUstress' tool. All of this was done using the 'ultimatebootcd'. I also used 'Memtest86+' and the Windows memory diagnostic tool. Finally I tried a drive checker on 'parted magic' Nothing arose during this period and all tests were claimed to be 'successful'. Besides under heavy load the CPU did not overheat.

    Edit:
    The CPU's under normal use (dev environments) sat at around 30-40 degrees celcius. Under Prime95 the peak temprature was 80 degrees, which is higher than I would like. There has been 0 overclocking done on the machine. The last time it BSOD the average temprature of the CPU was 33 degrees celcius.
     
    ekeel, Nov 6, 2016
    #7
  8. axe0 New Member

    BSOD 0x000000fc - Random Times (Or atleast as it appears)

    When did you apply thermal paste the last time?


    Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
    The PSU, cooling and other stuff are NOT mentioned in the tool.
    In the left corner below in your post you find 'My System Specs'. After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.

    BSOD 0x000000fc - Random Times (Or atleast as it appears) [​IMG]


    BSOD 0x000000fc - Random Times (Or atleast as it appears) [​IMG]
     
    axe0, Nov 7, 2016
    #8
  9. ekeel Win User
    I have updated the information, however with the PC being some stock HP not all the information is obtainable. With regards to thermal paste that will be somewhere between 4 and 3 years ago when the PC was being built.

    As a note the pc only touched peak tempratures whilst using Prime95 and at no other point have I noticed it get past 50 degrees celcius.
     
    ekeel, Nov 7, 2016
    #9
  10. axe0 New Member
    How many passes did MemTest86+ reach?
     
  11. ekeel Win User
    I stopped it somewhere between 9 and 10 as I deemed this okay for the system and wanted to rule out other components. Though this was prior to the latest BSOD. I am running it again now and will leave it going overnight to make sure it still gets past 8.

    Edit: It got past 8 and I decided to exit as it was running for 27hours with no problems.
     
    ekeel, Nov 8, 2016
    #11
  12. axe0 New Member
    Again, apologies for the huge delay. I had an exam that required more attention than expected.

    Please remove either of your memory sticks, running mixed memory can cause various of problems that can be difficult to diagnose properly. Please know that it does not matter if your running this setup for a long period.
    As a note, it is best to run on a single stick while testing, this makes it easier to troubleshoot if the memory appears to be causing issues.
     
Thema:

BSOD 0x000000fc - Random Times (Or atleast as it appears)

Loading...
  1. BSOD 0x000000fc - Random Times (Or atleast as it appears) - Similar Threads - BSOD 0x000000fc Random

  2. BSOD at random times

    in Windows 10 Software and Apps
    BSOD at random times: In the past few weeks I've received a couple of BSODs during seemingly unrelated activities. One was triggered during the shut down process MEMORY_MANAGEMENT. The other triggered randomly during a gaming session IRQL_NOT_LESS_OR_EQUAL. BlueScreenView info and google searches...
  3. BSOD appears randomly

    in Windows 10 Gaming
    BSOD appears randomly: Hello, I was running a game on my windows 10, when suddenly it crashed and I got a bsod. ever since, I will get a bsod seemingly randomly without running any programme or game. it could be in a few minutes or a couple of hours after I turn my device on. Sometimes I can boot...
  4. BSOD appears randomly

    in Windows 10 Software and Apps
    BSOD appears randomly: Hello, I was running a game on my windows 10, when suddenly it crashed and I got a bsod. ever since, I will get a bsod seemingly randomly without running any programme or game. it could be in a few minutes or a couple of hours after I turn my device on. Sometimes I can boot...
  5. BSOD appears randomly

    in Windows 10 BSOD Crashes and Debugging
    BSOD appears randomly: Hello, I was running a game on my windows 10, when suddenly it crashed and I got a bsod. ever since, I will get a bsod seemingly randomly without running any programme or game. it could be in a few minutes or a couple of hours after I turn my device on. Sometimes I can boot...
  6. BSOD appearing randomly

    in Windows 10 Installation and Upgrade
    BSOD appearing randomly: Hi everyone, i'm coming to you hoping that you would be able to give me some advice regarding some BSOD that a friend has been receiving randomly on his computer; the configuration is as follows:Motherboard: Gigabyte Aorus B360M Gaming 3 with F15 bios versionCPU: Intel i5...
  7. BSOD appearing randomly

    in Windows 10 Gaming
    BSOD appearing randomly: Hi everyone, i'm coming to you hoping that you would be able to give he some advice regarding some BSOD that a friend has been receiving randomly on his computer; the configuration is as follows:Motherboard: Gigabyte Aorus B360M Gaming 3 with F15 bios versionCPU: Intel i5...
  8. BSOD appearing randomly

    in Windows 10 Software and Apps
    BSOD appearing randomly: Hi everyone, i'm coming to you hoping that you would be able to give he some advice regarding some BSOD that a friend has been receiving randomly on his computer; the configuration is as follows:Motherboard: Gigabyte Aorus B360M Gaming 3 with F15 bios versionCPU: Intel i5...
  9. Random BSOD in random times

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD in random times: Hi, I'm really hoping to solve the problem since it's starting to distract seriously. I think since early summer BSODs been flashing now and then and now more and more often. Naturally I've tried memory solutions found online for memory related BSODs but now the different...
  10. BSOD at what appears to be random times

    in Windows 10 BSOD Crashes and Debugging
    BSOD at what appears to be random times: Hi, so this is the first time I've had the BSOD. From my point of view it appears to happen randomly once every 3 or 4 days. I had issues before but upon inspection the wireless receiver I had didn't fit well enough into its socket and had 2 or 3 pins that weren't connected...