Windows 10: BSOD ntoskrnl.exe

Page 7 of 11 FirstFirst ... 56789 ... LastLast

  1. Posts : 19,250
    windows 10 professional version 1607 build 14393.969 64 bit
       29 Mar 2018 #61

    The memory dump debugging displayed the Intel graphics driver as the cause of the latest BSOD.

    Please update this driver:
    igdkmd64.sys
    Intel Graphics driver
    Drivers & Software

    igdkmd64.sys Tue Oct 17 20:39:02 2017 (59E6B0B6)
    22.20.16.4836 1/3/2018 3:22 AM

    In the post dated December 10, 2017, post #36 the Intel driver was a cause of a BSOD.
    igdkmd64.sys Mon Aug 14 01:13:46 2017 (59913F9A)



    Updating a driver. - Microsoft Community


    Code:
    Name    Intel(R) HD Graphics 530PNP Device ID    PCI\VEN_8086&DEV_191B&SUBSYS_07081028&REV_06\3&11583659&0&10
    Adapter Type    Intel(R) HD Graphics Family, Intel Corporation compatible
    Adapter Description    Intel(R) HD Graphics 530
    Adapter RAM    1.00 GB (1,073,741,824 bytes)
    Installed Drivers    C:\WINDOWS\System32\DriverStore\FileRepository\ki126025.inf_amd64_639ca90a507a17dd\igdumdim64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki126025.inf_amd64_639ca90a507a17dd\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki126025.inf_amd64_639ca90a507a17dd\igd10iumd64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\ki126025.inf_amd64_639ca90a507a17dd\igd12umd64.dll
    Driver Version    22.20.16.4836
    INF File    oem1.inf (iSKLD_w10_DS section)
    Color Planes    Not Available
    Color Table Entries    4294967296
    Resolution    3840 x 2160 x 60 hertz
    Bits/Pixel    32
    Memory Address    0xDB000000-0xDBFFFFFF
    Memory Address    0x70000000-0x7FFFFFFF
    I/O Port    0x0000F000-0x0000F03F
    IRQ Channel    IRQ 4294967291
    Driver    c:\windows\system32\driverstore\filerepository\ki126025.inf_amd64_639ca90a507a17dd\igdkmd64.sys (22.20.16.4836, 12.80 MB (13,422,528 bytes), 1/3/2018 3:22 AM)
      My ComputerSystem Spec

  2.    31 Mar 2018 #62

    I updated the Intel GPU drivers to the latest from Alienware after the last post. Not sure why it is still bugging. Will have to try the drivers straight from Intel this time.
      My ComputerSystem Spec

  3.    02 Jun 2018 #63

    Had two more BSODs in the past 6 weeks. Didn't post right away since I've been busy with end of semester finals. I updated both the Intel GPU and Nvidia GPU drivers to the latest from each mfgr (did a clean install of each driver using DDU). Neither BSOD generated a memory dump file, or at least I could not find it in the Windows systems folder.
    BSOD ntoskrnl.exe Attached Files
      My ComputerSystem Spec


  4. Posts : 19,250
    windows 10 professional version 1607 build 14393.969 64 bit
       02 Jun 2018 #64

    The last BSOD in the logs were the end of April.
    Kaspersky was reinstalled in May.
    The crashes in the logs seem to be application related (Adobe).
    Make a brand new restore point.
    If you use a backup image then update it.
    Turn on Windows driver verifier > for BSOD post a beta zip and zipped memory dump for debugging (C:\Windows\memory.dmp)

    Use these settings for the custom settings:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community

    Use the text and images in this thread to turn off and recover from using the tool:
    Enable and Disable Driver Verifier in Windows 10 | Windows 10 Tutorials
      My ComputerSystem Spec

  5.    4 Weeks Ago #65

    Ended up doing a clean install. Didn't help too much. Was suggested I update all my Intel drivers, which helped quite a bit. Not freezing/black screen unresponsive like before. But I have had a couple of BSODs in the past 2 weeks. Wondering what drivers are misbehaving still.
    BSOD ntoskrnl.exe Attached Files
      My ComputerSystem Spec


  6. Posts : 19,250
    windows 10 professional version 1607 build 14393.969 64 bit
       4 Weeks Ago #66

    The website has strict rules on piracy.
    See rule #4:
    Forum Rules - Windows 10 Help Forums
      My ComputerSystem Spec

  7.    4 Weeks Ago #67

    Didn't I already post proof that my Adobe license is authentic?
    I did like 5 pages back.
      My ComputerSystem Spec


  8. Posts : 3,545
    64bit Win 10 Pro ver 1803 Build 17134.191 and W10 Insider Build 18214
       4 Weeks Ago #68

    radji said: View Post
    Ended up doing a clean install. Didn't help too much. Was suggested I update all my Intel drivers, which helped quite a bit. Not freezing/black screen unresponsive like before. But I have had a couple of BSODs in the past 2 weeks. Wondering what drivers are misbehaving still.
    There were no crash dump files in your zip - it looks like they were deleted before you ran the log_collector. Post a new set within 24 hours of your next BSOD.
      My ComputersSystem Spec

  9.    4 Weeks Ago #69

    Will do. Didn't realize the crash dump files need to be logged within 24 hours.
      My ComputerSystem Spec


  10. Posts : 19,250
    windows 10 professional version 1607 build 14393.969 64 bit
       4 Weeks Ago #70

    With the clean install the piracy was rechecked.
    Sorry that I had not remembered that the Adobe piracy issue was checked and verified in November, 2017.
    So you are fine with the Adobe.
    When there is a BSOD there may or may not be a dump file.
    If there is a dump file it can be cleaned by software or deleted by Windows.
    The log collector will collect whatever it finds at the time that it is run.

    The latest zip had no dump files.
    The logs displayed a dump with bugcheck 50 on July 12, 2018:
    Code:
    Event[3406]:  Log Name: System  Source: Microsoft-Windows-WER-SystemErrorReporting  Date: 2018-07-12T08:11:06.656  Event ID: 1001  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ALIENWARE-17R3  Description: The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000050 (0xffffa78b02a9b2b0, 0x0000000000000002, 0xfffff8009023e010, 0x0000000000000000). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 33e0506c-1ff0-4d63-be7e-97e33e89a285.
    On July 11, 2018 the logs displayed that there was an error during dump formation:
    Code:
    Event[3182]:  Log Name: System  Source: volmgr  Date: 2018-07-11T03:34:44.598  Event ID: 161  Task: N/A  Level: Error  Opcode: N/A  Keyword: Classic  User: N/A  User Name: N/A  Computer: ALIENWARE-17R3  Description: Dump file creation failed due to error during dump creation.
    So when the mini and memory dumps form properly and can be collected they can be debugged.

    Whenever there is a BSOD run the BETA log collector and post a new zip into the thread.
    Also use file explorer to search for C:\windows\memory.dmp
    If the memory.dmp file is less than 2 GB then zip it and upload to one drive or drop box and post a share link into the thread..
      My ComputerSystem Spec


 
Page 7 of 11 FirstFirst ... 56789 ... LastLast

Related Threads
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...
BSOD various ntoskrnl in BSOD Crashes and Debugging
Hi guys! Made a fresh Win10 install with just basic software (Like whocrashed) I have tried using the Guru3Ds tool to remove all traces of old video card drivers and installed the newest ones without any extra software or bloatware. Have ran...
Solved BSoD ntoskrnl.exe in BSOD Crashes and Debugging
So I've had this BSoD three times while playing on a game (Squad). These all occurred randomly within games and the Error calls itself 'page fault in nonpaged area'. Upon checking the dmp file with BluescreenViewer it highlights the ntoskrnl.exe....
BSOD - NTOSKRNL.exe in BSOD Crashes and Debugging
53020 Hi all I've been getting BSOD since playing Fallout 4. Initially I saw it was Nvidia related so I update my graphics and it seems to have cured that one, however now I've been getting a different error. I ran a memtest and all seemed good,...
BSOD because of ntoskrnl.exe in BSOD Crashes and Debugging
Hello guys, I had trouble with my windows 7 : bosd because of ntoskrnl.exe so i decided to do a clean install windows 10 for a new fresh start. But the bsod is still here so i think its probably Hardware problems but wich one ? I've only...
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 21:33.
Find Us