BSOD on startup (ntoskrnl.exe)


  1. Posts : 4
    Windows 10
       #1

    BSOD on startup (ntoskrnl.exe)


    When I started up windows, the little white dotted circle in the black screen stopped spinning for a good minute, then had to reboot again, and I got a dump file. I read it, and had an issue with ntoskrnl.exe. I looked it up, and read that most of the time, it means bad RAM. I did the windows memory diagnostic, and got no problems detected. So, whats the issue?
      My Computer


  2. Posts : 14,903
    Windows 10 Pro
       #2

    Hi jonathan4210,

    Welcome to the 10forums :)

    Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD. Be sure to install as less as possible software using custom/advanced options, you can use this tutorial for the installation part AMD Graphics Drivers - Install Without Catalyst Install Manager - Windows 7 Help Forums
    Attachment 100324
    Code:
    6: kd> lmvm atikmdag
    Browse full module list
    start             end                 module name
    fffff801`28080000 fffff801`297dc000   atikmdag T (no symbols)           
        Loaded symbol image file: atikmdag.sys
        Image path: atikmdag.sys
        Image name: atikmdag.sys
        Browse all global symbols  functions  data
        Timestamp:        Wed Feb 10 04:25:15 2016 (56BAAD9B)
        CheckSum:         016E3C29
        ImageSize:        0175C000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computers


  3. Posts : 4
    Windows 10
    Thread Starter
       #3

    Last time I had a BSOD, the issue was related to atikmdag.sys, for which I had used DDU, and this was roughly 2 weeks ago. Only difference is that I reinstalled the drivers with the catalyst package. Now I followed the link you provided, and only installed the correct drivers (and set auto driver installation to No). Only time will tell if my problem has actually been fixed this time. So for now, thanks :)

    Also, I noticed that the last 2 times it crashed, it happened after I cleaned my registry (not right away, after shutting down and booting up again). Is this a coincidence or can it be related to the issue?
      My Computer


  4. Posts : 14,903
    Windows 10 Pro
       #4

    Keep me posted on how it goes please :)
      My Computers


  5. Posts : 4
    Windows 10
    Thread Starter
       #5

    Would you recommend me trying the Windows Driver Verifier? It looks like it can tell me if the driver is good right away instead of waiting for a BSOD (cause I dont get them often), but I also read it can be dangerous.
      My Computer


  6. Posts : 14,903
    Windows 10 Pro
       #6

    I wouldn't until I'm certain it would be necessary to catch a driver.
      My Computers


 

  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 06:14.
Find Us




Windows 10 Forums