[BSOD] I got random BSOD with ntoskrnl, please save me!

  1. Posts : 5
    Windows 10 x64

    [BSOD] I got random BSOD with ntoskrnl, please save me!

    Hello, my PC recently has been receiving a lot of random BSODs . It comes suddenly when I surf the internet, or watching youtube videos.

    I was thinking that it all comes from my VGA card, but I can still play games such as Dota2 in Ultra settings for hours without any errors.

    I've already installed BlueScreen viewer then noticed something. Firstly it comes from Ntoskrnl.exe +14e7c0, then it changed to Ntoskrnl.exe +0x0000001e but I am not able to analyze the minidump file. Please help me!!! Thank you so much!

    Belows are my files, please help me to take a look!
      My Computer

  2. Posts : 5,184
    64bit Win 10 Pro ver 21H2

    Hello lynhbn,

    Sorry for the delay in replying. I have looked at your crash dump files in the logs, the first two both indicate hardware related problems:
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: ffffd98d7c700028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000be000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000800400, Low order 32-bits of the MCi_STATUS value.
    0: kd> !errrec ffffd98d7c700028
    Common Platform Error Record @ ffffd98d7c700028
    Record Id     : 01d2b4d5b8a97b7b
    Severity      : Fatal (1)
    Length        : 928
    Creator       : Microsoft
    Notify Type   : Machine Check Exception
    Timestamp     : 4/14/2017 4:27:22 (UTC)
    Flags         : 0x00000000
    Section 0     : Processor Generic
    Descriptor    @ ffffd98d7c7000a8
    Section       @ ffffd98d7c700180
    Offset        : 344
    Length        : 192
    Flags         : 0x00000001 Primary
    Severity      : Fatal
    Proc. Type    : x86/x64
    Instr. Set    : x64
    Error Type    : Micro-Architectural Error
    Flags         : 0x00
    CPU Version   : 0x00000000000206a7
    Processor ID  : 0x0000000000000000
    Section 1     : x86/x64 Processor Specific
    Descriptor    @ ffffd98d7c7000f0
    Section       @ ffffd98d7c700240
    Offset        : 536
    Length        : 128
    Flags         : 0x00000000
    Severity      : Fatal
    Local APIC Id : 0x0000000000000000
    CPU Id        : a7 06 02 00 00 08 10 00 - ff e3 ba 1f ff fb eb bf
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                    00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
    Proc. Info 0  @ ffffd98d7c700240
    Section 2     : x86/x64 MCA
    Descriptor    @ ffffd98d7c700138
    Section       @ ffffd98d7c7002c0
    Offset        : 664
    Length        : 264
    Flags         : 0x00000000
    Severity      : Fatal
    Error         : Internal timer (Proc 0 Bank 3)
      Status      : 0xbe00000000800400
      Address     : 0x00003809c332c4aa
      Misc.       : 0x000000000003ffff
    The other errors suggest memory corruption whioch could be driver related or bad RAM.

    I would suggest you perform two tests and report back on the results:

    Diagnostic Test


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note

    MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

    Make a photo of the result and post it.

    If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat. This will help you identify which stick or slot is faulty.


    Run Prime95 to stress test your CPU. Prime95 - Stress Test Your CPU - Windows 10 Forums

    warning   Warning
    Your CPU temperatures will rise quickly while under this stress test. Keep a keen eye on them and abort the test if overheating occurs.
      My Computers

  3. Posts : 5
    Windows 10 x64
    Thread Starter

    Thank you so much philc43 for your comment. Sorry for my late reply. I just want to report about my analysis
    After plenty of BSODs, I try to unplug my dedicated sound card from my PC (I'm using Focusrite Solo Gen 1 as a device for recording & playback)
    After that, no BSODs happen for 2 weeks!
    I was just thinking that it is the root cause!

    But today, I suddenly expricenced BSOD again. This time the cause is from nvlddmkm.sys+620738 and ntoskrnl.exe

    Please help me to take a look to my attached files. Thank you!!!!!
      My Computer

  4. Posts : 5,184
    64bit Win 10 Pro ver 21H2

    Run the DM_Log_collector again and post a new set of files
      My Computers

  5. Posts : 5
    Windows 10 x64
    Thread Starter


    I re-attached the file. Please help me to take a look.

    Best regards,
      My Computer

  6. Posts : 5,184
    64bit Win 10 Pro ver 21H2

    Did you run the CPU and RAM tests? The first crash is hardware related but this can sometimes be triggered by a faulty driver.

    The second crash has indicated the following drivers may be involved.

    BugCheck 1E, {ffffffffc000001d, fffff802cc53b6bc, fffff802cc891a40, ffffda003480dc10}
    *** WARNING: Unable to verify timestamp for athuw8x.sys
    *** ERROR: Module load completed but symbols could not be loaded for athuw8x.sys
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : athuw8x.sys ( athuw8x+228060 )
    Please update the NVidia driver. The best way to do this is to uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from your Graphics card manufacturer or from the NVidia website. When you do this be sure the "clean install" box is checked and only install the Graphics driver and the PhysX driver.

    The other driver is the wireless network adapter, your driver details are shown below:
    0: kd> lmvm athuw8x
    Browse full module list
    start             end                 module name
    fffff808`25fa0000 fffff808`26270000   athuw8x  T (no symbols)           
        Loaded symbol image file: athuw8x.sys
        Image path: \SystemRoot\System32\drivers\athuw8x.sys
        Image name: athuw8x.sys
        Browse all global symbols  functions  data
        Timestamp:        Tue May 14 05:06:43 2013 (5191B853)
        CheckSum:         002D0C6B
        ImageSize:        002D0000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    See if you can find more recent drivers for your wireless network card.
      My Computers

  7. Posts : 5
    Windows 10 x64
    Thread Starter

    Thank you very much for your analysis. I've just updated the clean version for the vga driver and buy a new wifi adapter (because my previous one TL-WN722N_V1 do not have any native driver for windows 10)

    I'm monitoring if the BSOD may happen again, I will inform you soon.

    Best regards!
      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 03:44.
Find Us

Windows 10 Forums