Repeated BSOD Briefly after Startup, ntoskrnl.sys


  1. Posts : 2
    Windows 10
       #1

    Repeated BSOD Briefly after Startup, ntoskrnl.sys


    Hey all, I upgraded to Win 10 a couple days ago after forcing it to realize that the update was available for download. It had been working fine for a few days, but today my computer crashed several times a few minutes after restarting. The usual process when this happens is to boot up, launch chrome, launch a steam game, then crash a few moments later. Each time this happened however, the responsible driver seems to have changed. Dumps are attached.
    Attachment 95779

    First time it crashed, I updated my ethernet adapter driver and started a antivirus scan. crashed again before scan was finished

    Next time, I tried to update my wireless adapter driver, but it was already updated. started antivirus scan again. crashed again before scan was finished

    Third time, didnt try to scan antivirus, but the problem seemed to move to system drivers that I didn't know how to update. Crashed again

    Fourth time same deal. Now I'm typing this hoping my computer doesnt crash before I hit submit. The difference may be that time time I didn't launch steam or windows defender. Any help much appreciated, let me know if you need any other information.

    --edit-- as per forum rules I just read I've also posted my system info here: Attachment 95783
    Last edited by flash5565; 12 Aug 2016 at 18:27. Reason: Forum rules
      My Computer

  2. Ztruker's Avatar
    Posts : 13,511
    Windows 10 Pro X64 20H4 19042.746
       #2

    Several of the dumps indicate memory_corruption. Time to check your PC memory:
    ===================================================
    RAM:


    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    information   Information

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses


    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.


    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.


    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.
      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 09:36.
Find Us




Windows 10 Forums