2 BSOD, Windows 10 64 bit, ntoskrnl.exe, need help identifying problem


  1. Posts : 3
    Windows 10 64 bit
       #1

    Getting different multiple BSODs, please help


    I recently upgraded my PC and I recently started getting BSODs during my gaming time. Please help me identify the issue, I attached the rar of my dumpfile
    EDIT: After posting this thread I received a SECOND BSOD on a different issue.
    EDIT: I keep getting crazy amounts of BSOD, even one after another or before the computer can even start up. I am desperate for help
    Last edited by Tainysi; 06 Nov 2015 at 20:11.
      My Computer


  2. Posts : 3
    Windows 10 64 bit
    Thread Starter
       #2

    I am extremely desperate for help, if anyone can please take a look at my problem
      My Computer


  3. Posts : 14,901
    Windows 10 Pro
       #3

    Hi Tainysi,

    Welcome to the 10forums.

    There have been 2 drivers flagged and a few dumps are pointing to memory corruption which could be due to drivers.

    Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
    Code:
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    7: kd> lmvm nvlddmkm
    start             end                 module name
    fffff801`ce3a0000 fffff801`cee97000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Mon Nov 02 13:59:49 2015 (56375E45)
        CheckSum:         00AC236B
        ImageSize:        00AF7000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    This is a driver from Windows, I suggest you run SFC
    Code:
    *** WARNING: Unable to verify timestamp for peauth.sys
    *** ERROR: Module load completed but symbols could not be loaded for peauth.sys



    Diagnostics Test

     System File Check


    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

    Then we also have
    Code:
    Probably caused by : memory_corruption
    Just to rule the RAM out, please run MemTest86+



    Diagnostic Test

     RAM TEST


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

    Note   Note


    MemTest86+ needs to be run for at least 8 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.
      My Computers


  4. Posts : 3
    Windows 10 64 bit
    Thread Starter
       #4

    axe0 said:
    Hi Tainysi,

    Welcome to the 10forums.

    There have been 2 drivers flagged and a few dumps are pointing to memory corruption which could be due to drivers.

    Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver.
    Code:
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    7: kd> lmvm nvlddmkm
    start             end                 module name
    fffff801`ce3a0000 fffff801`cee97000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Mon Nov 02 13:59:49 2015 (56375E45)
        CheckSum:         00AC236B
        ImageSize:        00AF7000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    This is a driver from Windows, I suggest you run SFC
    Code:
    *** WARNING: Unable to verify timestamp for peauth.sys
    *** ERROR: Module load completed but symbols could not be loaded for peauth.sys



    Diagnostics Test

     System File Check


    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.

    Then we also have
    Code:
    Probably caused by : memory_corruption
    Just to rule the RAM out, please run MemTest86+



    Diagnostic Test

     RAM TEST


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

    Note   Note


    MemTest86+ needs to be run for at least 8 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.
    Hey Axe! I see that you reply to everyone. I fixed my problem by simply updating my bios. You should add that to your list of fixes. It seems to be a lot with the asrock H170S and Z170s
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #5

    I reply whenever I am able to

    Their are many different fixes for different BSOD crashes, it isn't really something I can simply add to a list of possible fixes for specific crashes (some are an exception), but it was already on the list for generic troubleshooting

    Glad to hear your problem is solved, thank you for reporting back your solution :)
      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 04:25.
Find Us




Windows 10 Forums