Multiple BSODS with different errors, caused by ntoskrnl.exe

Page 2 of 6 FirstFirst 1234 ... LastLast
  1. Ztruker's Avatar
    Posts : 6,605
    Windows 10 Pro X64 1809 17763.134
       20 Feb 2017 #11

    You're welcome. Hope the problem is resolved.
      My ComputersSystem Spec


  2. Posts : 191
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       22 Feb 2017 #12

    Ok so my computer randomly shutdown (like cable pulled shutdown), turned itself back on and as soon as it got to the windows log in screen it BSOD'd. I have attached the log collector thing, should I turn verifier back on?
      My ComputerSystem Spec

  3. Ztruker's Avatar
    Posts : 6,605
    Windows 10 Pro X64 1809 17763.134
       22 Feb 2017 #13

    No new dumps unfortunately.

    I see this in the evnet viewer log:
    Code:
    Event[11488]:
      Log Name: System
      Source: volmgr
      Date: 2017-02-22T10:58:44.179
      Event ID: 46
      Task: N/A
      Level: Error
      Opcode: N/A
      Keyword: Classic
      User: N/A
      User Name: N/A
      Computer: EthanHome-PC
      Description: 
    Crash dump initialization failed!
    Have you changed or disabled the pagefile in Windows 10? That would cause this as crash dump needs a pagefile at least the size of your RAM. The best way for this to be set is to let the system manage it, don't try to control the size.
      My ComputersSystem Spec


  4. Posts : 191
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       22 Feb 2017 #14

    Hi again,

    I do believe I modified that at one point because windows was not writing dumps and I tried to fix it, will revert it back as you recommend.

    I turned on driver verifier after the crash today (22nd feb) at 19:22:34, and then it blue screened again at 22:25:18 with verifier turned on. I have attached the log collector.

    Thanks :)
      My ComputerSystem Spec

  5. Ztruker's Avatar
    Posts : 6,605
    Windows 10 Pro X64 1809 17763.134
       22 Feb 2017 #15

    Both dumps from 2/11 point to memory_corruption:
    Code:
    BugCheck 1E, {ffffffffc0000005, fffff802e5910c71, 0, b2}
    Probably caused by : memory_corruption
    Followup:     memory_corruption
    ---------
    Code:
    BugCheck 3B, {c0000005, fffff80336ebce76, ffffdc802a2cf6b0, 0}
    Probably caused by : memory_corruption
    Followup:     memory_corruption
    Also see in the thread trace:
    Code:
    ffffc500`7cf31e18  ffffe954`ae7a67a5*** ERROR: Module load completed but symbols could not be loaded for cdd.dll
     cdd+0x67a5
    cdd.dll is the Canonical Display Driver, part of the OS so not a likely candidate but this in indicates a possible video related problem as dxggms2 and nvlddmkm are also in the thread trace. In fact, further up in the trace I see this:
    Code:
    ffffc500`7cf304d8  fffff806`bc9c0e78*** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
     nvlddmkm+0x1e0e78
    The NVIDIA GeForce GTX 660 driver version you have is sort of old: 378.66 09/02/2017

    The current available version is: WHQL Release Date: 2017.2.14

    I suggest completely uninstalling the Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile (near bottom of page) then get the latest driver for you Nvidia card here: NVIDIA Driver Downloads

    Then do a custom install of only the NVidia graphics driver and the PhysX driver.

    See if that gets rid of the problem.
      My ComputersSystem Spec


  6. Posts : 191
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       22 Feb 2017 #16

    Ok will do, I have another BSOD since, should I provide that dump, or simply update the nvidia driver as described, leave verifier on and see what happens?
      My ComputerSystem Spec

  7. Ztruker's Avatar
    Posts : 6,605
    Windows 10 Pro X64 1809 17763.134
       22 Feb 2017 #17

    Update the Nvidia driver then see what happens. Run dm_log_collector and upload zip if another BSOD occurs.
      My ComputersSystem Spec


  8. Posts : 191
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       22 Feb 2017 #18

    Keep verifier on or nah?
      My ComputerSystem Spec

  9. Ztruker's Avatar
    Posts : 6,605
    Windows 10 Pro X64 1809 17763.134
       22 Feb 2017 #19

    Run without first. If problems, try Verifier again.
      My ComputersSystem Spec


  10. Posts : 191
    Microsoft Windows 10 Home 64-bit 10586 Multiprocessor Free
    Thread Starter
       23 Feb 2017 #20

    Ok so I did as you said and my pc froze this morning, what would you recommend, will verifier help with freezes?
      My ComputerSystem Spec


 
Page 2 of 6 FirstFirst 1234 ... LastLast

Related Threads
BSOD randomly happens once or twice per day. I updated all the drivers with Driver Booster program, even updated the BIOS. I did the Windows Memory Diagnostic and passed the test. Throws different errors but seems the culprit is always the same. I...
Solved Random BSODs caused by ntoskrnl.exe in BSOD Crashes and Debugging
Hi all, 3 weeks ago I did a fresh install of Windows 10 and since then I'm getting BSODs at least once every 1-2 hours. These BSODs vary from SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL, SYSTEM_THREAD_EXCEPTION_NOT_HANDLED to...
Multiple BSODs caused by ntoskrnl.exe+142760 in BSOD Crashes and Debugging
This problem has been happening since I built this computer 6 months ago. I've tried changing the motherboard, the memory, and the power supply, and have reinstalled windows many times. I suspect I'll have enough parts for a second computer by...
Good day, I've been using my Dell XPS 8700 for some time now and ever since I've gotten it it randomy blue screens with multiple different errors, as the title implies. When I open up BlueScreenView, the errors seem to be commonly related to...
ntoskrnl.exe causing multiple BSODs a day in BSOD Crashes and Debugging
Hello, I've been having multiple blue screens a day caused by ntoskrnl.exe and have no idea how to fix them. They seem to be happening more frequently when I'm gaming, but I just upgraded from a GTX 650 to a GTX 960 and this hasn't solved...
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 00:23.
Find Us