Random BSOD errors. No video on boot. Fans full speed.

  1. Posts : 3
    Windows 10 64 bit

    Random BSOD errors. No video on boot. Fans full speed.

    I built this PC at the end of the school year to be my primary PC for film color correction. A couple of months after the build, I was updating a driver and during reboot, the fans went to 100% and there was no video. KB + Mouse would light up though and I was even able to login (as confirmed by KB lights going from a wave to static) and then shut down the computer with a quick press of the power button (not a forced shutdown).

    I removed the card and put it in an old build, and took my GTX 970 and put it in this PC. The 2080 worked in the old build just fine. I reinstall the card, and I get video again. A few weeks later, it happens again. I re-seat the card and get video back. I DDU the graphics drivers and reinstall them. Now I am getting BSOD errors randomly, and different errors every time. I have tried to save event logs whenever I encounter a BSOD.

    A friend suggested I update the BIOS and make sure my chipset drivers are up to date. I install the chipset drivers again, and I notice when I check the BIOS that the update lists "Compatibility for i9-9920X". I flash the BIOS. Today I just got another BSOD and will be re-installing windows once I finish up a couple of projects I am on right now.

    I have attached a log gathered with the V2 log collector. Due to work, I was not able to post at the latest BSOD date. Known BSOD dates are 9/21, 9/26, and 10/08. Attachment 252689
    Windows Version 1903 (OS Build 18362.418)

    I am at my wit's end with this computer and desperate for any assistance or ideas you might have. Any and all help is appreciated.
      My Computer

  2. Posts : 392

    First step (when it's working properly) is to make a System Restore point. That way you can try to restore to that point without having to take things apart. It doesn't always work, but it does work often enough to make it worth trying.

    Last 4 memory dumps shows: STOP 0x1A; STOP 0x7E; STOP 0x1E x 2
    Error report folder shows numerous other errors - some related to video
    Lot's of older drivers - I am particularly concerned about the Oculus software and the ASMedia SATA drivers.

    Please continue to do a clean install of Windows (no extra 3rd party software installed) and see if that helps with the BSOD's.
    Ensure that you run Windows Update after the clean install to get ALL available updates
    Then check Device Manager for any problem devices. Post back if there are any (and describe what they are please).
    If this doesn't help with the BSOD's, then please run the log collector again and submit it.

    FYI - a clean install of Windows is one of the troubleshooting steps to help rule out a hardware problem - that's why I ask that you don't install any 3rd party programs just yet.

    Good luck!
      My Computer

  3. Posts : 3
    Windows 10 64 bit
    Thread Starter

    With the install of Windows, would that be Windows with the manufacture's drivers for all components as well? I believe those ASMedia SATA drivers should be the latest ones provided by Gigabyte but I could be wrong.

    I also have no reliable way of telling if something has fixed the BSOD or video yet. It usually occurs during reboots, either installing a driver or otherwise, but sometimes it might just be during average use. How long should I give it with just the clean Windows install before going on further?
      My Computer

  4. Posts : 392

    The reason I jumped on the "clean" install was that in your first post you mentioned reinstalling Windows. That's an ideal time to try troubleshooting with a "clean" install.

    The concept of a "clean install" is a slippery thing.
    What we're looking for is having the system setup the way it was designed to run. The point being that this is the way the system was "tested" when being designed (and it's how the OEM's diagnose hardware problems).
    For OEM products, that's installing from the OEM installation media (if available)
    For custom build systems, it's installing as Microsoft intended. I would hold off on the Gigabyte drivers until you see if the problem occurs with the Microsoft drivers (that's how we tested them at work (a PC shop)).
    If there is no OEM installation media, then you just have to use the Microsoft installer

    BUT, there's some exceptions here:
    - if the system was designed to run on an earlier version of Windows - then that's the version that should be "clean installed", even if you're currently running a later version (yes, it's a pain - but it's necessary to get the most effective troubleshooting). Again, if you don't have the ability to install the older version, then you have to use the latest version - but this hampers the effectiveness of the troubleshooting.
    - Microsoft software not bundled with Windows is considered 3rd party software (such as Office and XBox software)
    - devices missing drivers must have drivers (as seen in Device Manager) - so we reluctantly ask that the appropriate drivers be installed
    - then we start to worry about older drivers - and the ability/willingness of the manufacturer's to continue to support older products on the newer versions of Windows.
    - BIOS/UEFI should always be updated to the latest version from the manufacturer's website. Read the complete instructions/specifications for this - they can remove features (such as CPU support - which I found out the hard way).

    Now, some older drivers aren't a problem, but most are.
    The download of the ASMedia SATA drivers will give you a date that it was released.
    BUT, the package may contain several drivers - all with different ages (dates).

    Since we're not able to develop our own drivers, we have to use what we're given.
    And, we then must take the manufacturer's word that the driver is compatible with the version of Windows that you are using. Most times this isn't a problem, but some less common drivers may not be subjected to the rigorous testing that the more common drivers are subject to.

    There is no utility to tell you that a BSOD is fixed.
    I usually suggest waiting a week or two to figure that it's probably fixed,
    And then another week or two to figure that it's most likely fixed.
    Note the use of "probably" and "most Likely" - there are no certainties here

    In the end, the point is...
    If the system functions well with a clean install - the problem was probably with the previous software that was installed
    If the system doesn't function well with a clean install - the problem is probably with the hardware (and you'll have to start hardware troubleshooting.

    Remember that the only 100% effective hardware diagnostic test is trying another, known to be good device.
    The next best test is using a new (out of the box) device - but even they can be faulty
    Another option is trying the components in another, known to be good system.
    Software diagnostics aren't 100% reliable, but can help to isolate problems (sometimes) without having to replace every component in the system for testing.

    And, just to throw a monkey wrench into things:
    Depending on how old the hardware is, there may also be compatiblity issues. These may crop up when updating the system - so then you'll have to test the system with the latest version of Windows being the "clean" install

    Good luck!

    P.S. Windows installation media also contains some 3rd party drivers. But these have been thoroughly tested and certifeid by Microsoft, so we assume that they've been tested to be stable with the Microsoft installation.
      My Computer


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 08:43.
Find Us

Windows 10 Forums