BSOD Usually once per boot

Page 2 of 2 FirstFirst 12

  1. Posts : 13
    Windows 10
    Thread Starter
       #11

    I would say that the current crashes are the same. They all happen shortly after I boot up the PC for the first time. Many times, I also get additional crashes after rebooting. These can take the form of additional BSOD, BIOS stalling right before the memory test, or motherboard beeps. Eventually, after these reboots and maybe going through the windows recovery screens to just say restart, I am always able to get into my PC and use it successfully for the rest of the night.
      My Computer


  2. Posts : 13
    Windows 10
    Thread Starter
       #12

    Another BSOD tonight. It took a little longer than usual - probably 10 minutes after booting up.

    New file attached.
      My Computer


  3. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #13

    That last crash was probably caused by: atikmdag.sys (just like we found 4 weeks ago)

    Code:
    ffffe680`4d835698  fffff801`7bdccd32Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for atikmdag.sys
    *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
     atikmdag+0xccd32
    Code:
    1: kd> lmvm atikmdag
    Browse full module list
    start             end                 module name
    fffff801`7bd00000 fffff801`7d20f000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
        Image name: atikmdag.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Nov 04 21:39:32 2015 (563A7B14)
        CheckSum:         014AB74E
        ImageSize:        0150F000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

    It would be worth trying again to reinstall the graphics driver and try a newer version.

    Use the method I gave you in post #2:

    1. Update your graphics driver: the best way to do this is to uninstall everything of AMD using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the AMD website. I would advise to only install the driver and not the Catalyst software for tweaking and control.
      My Computers


  4. Posts : 13
    Windows 10
    Thread Starter
       #14

    Thanks for everyone's help. I removed my graphics card, disassembled it, thoroughly cleaned it, applied new thermal paste, and installed it back. I then used the Radeon Crimson software to identify everything that was needed. In addition to the HDMI sound and the normal graphics driver, it had me install a third (I'm not remembering the name) that I did not have installed, so I installed it.

    Since all of this... no issues.. yet.
      My Computer


  5. Posts : 13
    Windows 10
    Thread Starter
       #15

    Late last week, I had some more BSOD. Since, I've done the following:
    I disabled C1E in the bios.
    I turned off the fast-start feature.
    Finally, I have used your method (again) to uninstall my drivers and have installed the latest driver on AMDs website.
      My Computer


  6. Posts : 13
    Windows 10
    Thread Starter
       #16

    Had 4 BSOD tonight. Dump files attached.

    I've now removed my graphics card and am running off of on board graphics.

    Is there anything new in the dump files? Anything else I can try? Is it worth buying a new graphics card to see if it solves it, or is there a chance it is my motherboard or something else?
      My Computer


  7. Posts : 13
    Windows 10
    Thread Starter
       #17

    I have installed a different graphics card (borrowed from someone). I can recreate a BSOD by knocking my tower into the metal desk that sits next to (see photo). I know that some of the historical BSOD have been caused by an inadvertent knock (usually a kick as I swivel my chair around), but not all. Some just happen out of nowhere.

    Am I dealing with two separate issues? Or are they the same? Seems that something is loose...

    Dump attached.

    Thanks for all the help.
      My Computer


  8. Posts : 654
    windows 10 Pro
       #18

    Check all your connection/cables on your mobo and from/to your mobo esp. from the PSU.
    Look for loose cables and/or damaged cables etc.
    These kinds of knocks could cause some kind of short-circuit in your system when you bump into the metal desk.
    Is your mobo inserted the right way with all the screws and standoffs in the right place?
    No loose or fallen screws in your system?
    etc.
      My Computer


  9. Posts : 13
    Windows 10
    Thread Starter
       #19

    I removed my motherboard, disconnected all of my RAM, and thoroughly cleaned the CPU fan, memory, memory slots, and the general MOBO surface.

    I'm 99% sure that root cause was the CPU fan blowing dust directly into the RAM slots as the one closest to the SPU would cause a BSOD if I barely touched it while the machine was running. After cleaning, and a few weeks later no BSODs... Let's hope it's solved for good.

    Thanks all for the help.
      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 13:12.
Find Us




Windows 10 Forums