Windows 10 May 2020 update is now available

CrazyKats 19,420 Reputation points Volunteer Moderator
2020-05-27T17:08:19+00:00
Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

562 answers

Sort by: Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2020-06-06T05:14:03+00:00

    So, for the last few weeks, I've been experiencing 4 or 5 GSODs (green screens) a day. 

    I have been able to isolate and fix a few, but I can't get past the Kernel errors. 

    DPC_WATCHDOG_VIOLATION

    Kernel_Security_Check_Failure

    When I pull up nir's bluescreenview to investigate the minidumps, I see these:

    filename: ntoskrnl.exe   

    address in stack:  ntoskrnl.exe+3ef929   

    From Address:  fffff800`76c00000   

    To Address:  fffff800`77c46000   

    Size:  0x01046000   

    TimeSTamp:  0xbb5cde6c   

    Time String:  8/11/2069 12:47:24 AM   

    Product:  Microsoft® Windows® Operating System   

    File desc:  NT Kernel & System   

    Version:  10.0.19041.264 (WinBuild.160101.0800)   

    Company:  Microsoft Corporation   

    File Loc:  C:\WINDOWS\system32\ntoskrnl.exe   

    (different error, same layout as above)

    ntoskrnl.exe   

    ntoskrnl.exe+4593ee   

    fffff801`1c400000   

    fffff801`1d446000   

    0x01046000   

    0xbb5cde6c   

    8/11/2069 12:47:24 AM   

    Microsoft® Windows® Operating System   

    NT Kernel & System   

    10.0.19041.264 (WinBuild.160101.0800)   

    Microsoft Corporation   

    C:\WINDOWS\system32\ntoskrnl.exe   

    Any thoughts, or help would be appreciated.  I've dumped the files to one drive if you need them for more analysis.  (Drive info, msinfo32, dumps).

    ~Dan

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  4. Anonymous
    2020-06-06T05:35:45+00:00

    Yoichitsutsumi,

    I've gone thru all of the known issues already, corrected anything I had, and am running the latest in NVIDIA drivers. 

    Outside of that, I'm not sure what you're posting about.  Please explain further what you mean by pasting a portion of the OP into a reply. 

    Thanks,.

    ~D

    (For the record, none of these issues are in the 'known issues' )

    System Information (local)


    Computer name: DAN-PC

    Windows version: Windows 10 , 10.0, build: 19041

    Windows dir: C:\WINDOWS

    Hardware: Z97X-UD5H, Gigabyte Technology Co., Ltd.

    CPU: GenuineIntel Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz Intel8664, level: 6

    8 logical processors, active mask: 255

    RAM: 34164662272 bytes (31.8GB)

    *** * Crash Dump Analysis*


    Crash dumps are enabled on your computer.

    Crash dump directories:

    C:\WINDOWS

    C:\WINDOWS\Minidump

    On Fri 6/5/2020 11:09:22 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\MEMORY.DMP

    This was probably caused by the following module: usbxhci.sys (USBXHCI+0x2DFD)

    Bugcheck code: 0x139 (0x3, 0xFFFFF8007D6F45C0, 0xFFFFF8007D6F4518, 0x0)

    Error: KERNEL_SECURITY_CHECK_FAILURE

    file path: C:\WINDOWS\system32\drivers\usbxhci.sys

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: USB XHCI Driver

    Bug check description: The kernel has detected the corruption of a critical data structure.

    The crash took place in a storage driver or controller driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.

    On Fri 6/5/2020 6:39:04 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\060520-12296-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)

    Bugcheck code: 0x133 (0x0, 0x501, 0x500, 0xFFFFF8011D0FA318)

    Error: DPC_WATCHDOG_VIOLATION

    file path: C:\WINDOWS\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above. This could be caused by either a non-responding driver or non-responding hardware. This bug check can also occur because of overheated CPUs (thermal issue).

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Fri 6/5/2020 5:34:07 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\060520-12531-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)

    Bugcheck code: 0x139 (0x3, 0xFFFFF805644F45B0, 0xFFFFF805644F4508, 0x0)

    Error: KERNEL_SECURITY_CHECK_FAILURE

    file path: C:\WINDOWS\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: The kernel has detected the corruption of a critical data structure.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Fri 6/5/2020 11:09:22 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\060520-12078-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)

    Bugcheck code: 0x139 (0x3, 0xFFFFF8007D6F45C0, 0xFFFFF8007D6F4518, 0x0)

    Error: KERNEL_SECURITY_CHECK_FAILURE

    file path: C:\WINDOWS\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: The kernel has detected the corruption of a critical data structure.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Fri 6/5/2020 7:44:44 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\060520-12312-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)

    Bugcheck code: 0x139 (0x3, 0xFFFFF8062D8ED250, 0xFFFFF8062D8ED1A8, 0x0)

    Error: KERNEL_SECURITY_CHECK_FAILURE

    file path: C:\WINDOWS\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: The kernel has detected the corruption of a critical data structure.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    On Fri 6/5/2020 7:40:13 PM your computer crashed or a problem was reported

    crash dump file: C:\WINDOWS\Minidump\060520-12250-01.dmp

    This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)

    Bugcheck code: 0x139 (0x3, 0xFFFFF805502ED260, 0xFFFFF805502ED1B8, 0x0)

    Error: KERNEL_SECURITY_CHECK_FAILURE

    file path: C:\WINDOWS\system32\ntoskrnl.exe

    product: Microsoft® Windows® Operating System

    company: Microsoft Corporation

    description: NT Kernel & System

    Bug check description: The kernel has detected the corruption of a critical data structure.

    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more