Windows 10: Constant BSOD ntkrnlmp.exe - win32kfull.sys

Hello.

I've been having a lot of BSOD recently, my pc is almost unusable.

I thought It may be a software problem, so I made a clean windows install, buy it keeps crashig. I also ran a memtest86, and it showed no error.

here is the minidump





******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a critical data structure. The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments:Arg1: 0000000000000003, A LIST_ENTRY has been corrupted i.e. double remove.Arg2: ffffc50f1badf270, Address of the trap frame for the exception that caused the bugcheckArg3: ffffc50f1badf1c8, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, ReservedDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2656 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-6SM3QN9 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 2673 Key : Analysis.Memory.CommitPeak.Mb Value: 91 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 139BUGCHECK_P1: 3BUGCHECK_P2: ffffc50f1badf270BUGCHECK_P3: ffffc50f1badf1c8BUGCHECK_P4: 0TRAP_FRAME: ffffc50f1badf270 -- .trap 0xffffc50f1badf270NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffff9f0aaa36d158 rbx=0000000000000000 rcx=0000000000000003rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8041ac653e5 rsp=ffffc50f1badf400 rbp=ffffca81a1100180 r8=00000000000176c4 r9=0000000000000000 r10=0000000000000000r11=0000000000000003 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na pe cynt!KiQueueReadyThread+0x17b305:fffff804`1ac653e5 cd29 int 29hResetting default scopeEXCEPTION_RECORD: ffffc50f1badf1c8 -- .exr 0xffffc50f1badf1c8ExceptionAddress: fffff8041ac653e5 nt!KiQueueReadyThread+0x000000000017b305 ExceptionCode: c0000409 Security check failure or stack buffer overrun ExceptionFlags: 00000001NumberParameters: 1 Parameter[0]: 0000000000000003Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: csrss.exeERROR_CODE: NTSTATUS 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.EXCEPTION_CODE_STR: c0000409EXCEPTION_PARAMETER1: 0000000000000003EXCEPTION_STR: 0xc0000409BAD_STACK_POINTER: ffffc50f1badef48STACK_TEXT: ffffc50f`1badef48 fffff804`1abefa29 : 00000000`00000139 00000000`00000003 ffffc50f`1badf270 ffffc50f`1badf1c8 : nt!KeBugCheckExffffc50f`1badef50 fffff804`1abefe50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69ffffc50f`1badf090 fffff804`1abee1e3 : 00000000`00000000 ffffca81`a1100180 ffff9f0a`aa36d080 fffff804`1aa3f046 : nt!KiFastFailDispatch+0xd0ffffc50f`1badf270 fffff804`1ac653e5 : ffffca81`a11088f0 ffffca81`a1100180 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x323ffffc50f`1badf400 fffff804`1aa3e966 : ffff9f0a`aa3f0220 ffff9f0a`aa36d000 ffffc50f`00000000 00000000`00000000 : nt!KiQueueReadyThread+0x17b305ffffc50f`1badf480 fffff804`1aa3e2aa : 00000000`00000000 fffff804`00000000 ffff9f0a`a8cfb370 00000000`00000000 : nt!KiExitDispatcher+0x286ffffc50f`1badf4f0 fffff758`a8667d43 : fffff720`00000000 fffff720`0062a8a0 00000000`000f0003 ffff9f0a`aa3f00a0 : nt!KeSetEvent+0xeaffffc50f`1badf580 fffff758`a87011c8 : 00000000`00000001 00000000`00007ffe ffffd473`d184271d fffff758`a8620520 : win32kfull!InternalSetTimer+0x4f3ffffc50f`1badf610 fffff758`a86ffb40 : fffff720`01200040 ffffc50f`1badfb00 00000000`00000020 00000000`00000004 : win32kfull!SetRITTimer+0x28ffffc50f`1badf650 fffff758`a86ffacb : 00000000`00000007 00000000`00000010 00000000`00000000 00000000`00000000 : win32kfull!AdjustRITDelayableTimers+0x2cffffc50f`1badf690 fffff758`a8a69aff : 00000000`00000000 ffffc50f`1badf7c0 00000000`00000000 00000000`00000000 : win32kfull!SetTimerCoalescingTolerance+0x5bffffc50f`1badf6c0 fffff758`a8a69742 : ffff9f0a`afcd21a0 ffff9f0a`afcd21a0 00000000`00000001 00000000`00000000 : win32kbase!xxxUserPowerEventCalloutWorker+0x22fffffc50f`1badfa30 fffff758`a86a9fd0 : ffff9f0a`aa36d080 00000000`00000000 00000000`00000025 00000000`00000025 : win32kbase!xxxUserPowerCalloutWorker+0xe2ffffc50f`1badfaa0 fffff758`a852474d : ffff9f0a`aa36d080 fffff804`1abef2d8 00000000`00000000 00000000`00040246 : win32kfull!NtUserCallNoParam+0x70ffffc50f`1badfad0 fffff804`1abef478 : 00000000`00000170 00000000`00000025 00000000`00000000 00000000`00000000 : win32k!NtUserCallNoParam+0x15ffffc50f`1badfb00 00007ffc`0cb810e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x2800000096`34f3fe38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`0cb810e4SYMBOL_NAME: win32kfull!InternalSetTimer+4f3MODULE_NAME: win32kfullIMAGE_NAME: win32kfull.sysIMAGE_VERSION: 10.0.19041.388STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 4f3FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_STACKPTR_ERROR_win32kfull!InternalSetTimerOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {d6d41284-2d8d-9f4e-8a85-83d570096469}Followup: MachineOwner---------10: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************KERNEL_SECURITY_CHECK_FAILURE 139A kernel component has corrupted a critical data structure. The corruptioncould potentially allow a malicious user to gain control of this machine.Arguments:Arg1: 0000000000000003, A LIST_ENTRY has been corrupted i.e. double remove.Arg2: ffffc50f1badf270, Address of the trap frame for the exception that caused the bugcheckArg3: ffffc50f1badf1c8, Address of the exception record for the exception that caused the bugcheckArg4: 0000000000000000, ReservedDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2327 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-6SM3QN9 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 2328 Key : Analysis.Memory.CommitPeak.Mb Value: 92 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 139BUGCHECK_P1: 3BUGCHECK_P2: ffffc50f1badf270BUGCHECK_P3: ffffc50f1badf1c8BUGCHECK_P4: 0TRAP_FRAME: ffffc50f1badf270 -- .trap 0xffffc50f1badf270NOTE: The trap frame does not contain all registers.Some register values may be zeroed or incorrect.rax=ffff9f0aaa36d158 rbx=0000000000000000 rcx=0000000000000003rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000rip=fffff8041ac653e5 rsp=ffffc50f1badf400 rbp=ffffca81a1100180 r8=00000000000176c4 r9=0000000000000000 r10=0000000000000000r11=0000000000000003 r12=0000000000000000 r13=0000000000000000r14=0000000000000000 r15=0000000000000000iopl=0 nv up ei ng nz na pe cynt!KiQueueReadyThread+0x17b305:fffff804`1ac653e5 cd29 int 29hResetting default scopeEXCEPTION_RECORD: ffffc50f1badf1c8 -- .exr 0xffffc50f1badf1c8ExceptionAddress: fffff8041ac653e5 nt!KiQueueReadyThread+0x000000000017b305 ExceptionCode: c0000409 Security check failure or stack buffer overrun ExceptionFlags: 00000001NumberParameters: 1 Parameter[0]: 0000000000000003Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: csrss.exeERROR_CODE: NTSTATUS 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.EXCEPTION_CODE_STR: c0000409EXCEPTION_PARAMETER1: 0000000000000003EXCEPTION_STR: 0xc0000409BAD_STACK_POINTER: ffffc50f1badef48STACK_TEXT: ffffc50f`1badef48 fffff804`1abefa29 : 00000000`00000139 00000000`00000003 ffffc50f`1badf270 ffffc50f`1badf1c8 : nt!KeBugCheckExffffc50f`1badef50 fffff804`1abefe50 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69ffffc50f`1badf090 fffff804`1abee1e3 : 00000000`00000000 ffffca81`a1100180 ffff9f0a`aa36d080 fffff804`1aa3f046 : nt!KiFastFailDispatch+0xd0ffffc50f`1badf270 fffff804`1ac653e5 : ffffca81`a11088f0 ffffca81`a1100180 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x323ffffc50f`1badf400 fffff804`1aa3e966 : ffff9f0a`aa3f0220 ffff9f0a`aa36d000 ffffc50f`00000000 00000000`00000000 : nt!KiQueueReadyThread+0x17b305ffffc50f`1badf480 fffff804`1aa3e2aa : 00000000`00000000 fffff804`00000000 ffff9f0a`a8cfb370 00000000`00000000 : nt!KiExitDispatcher+0x286ffffc50f`1badf4f0 fffff758`a8667d43 : fffff720`00000000 fffff720`0062a8a0 00000000`000f0003 ffff9f0a`aa3f00a0 : nt!KeSetEvent+0xeaffffc50f`1badf580 fffff758`a87011c8 : 00000000`00000001 00000000`00007ffe ffffd473`d184271d fffff758`a8620520 : win32kfull!InternalSetTimer+0x4f3ffffc50f`1badf610 fffff758`a86ffb40 : fffff720`01200040 ffffc50f`1badfb00 00000000`00000020 00000000`00000004 : win32kfull!SetRITTimer+0x28ffffc50f`1badf650 fffff758`a86ffacb : 00000000`00000007 00000000`00000010 00000000`00000000 00000000`00000000 : win32kfull!AdjustRITDelayableTimers+0x2cffffc50f`1badf690 fffff758`a8a69aff : 00000000`00000000 ffffc50f`1badf7c0 00000000`00000000 00000000`00000000 : win32kfull!SetTimerCoalescingTolerance+0x5bffffc50f`1badf6c0 fffff758`a8a69742 : ffff9f0a`afcd21a0 ffff9f0a`afcd21a0 00000000`00000001 00000000`00000000 : win32kbase!xxxUserPowerEventCalloutWorker+0x22fffffc50f`1badfa30 fffff758`a86a9fd0 : ffff9f0a`aa36d080 00000000`00000000 00000000`00000025 00000000`00000025 : win32kbase!xxxUserPowerCalloutWorker+0xe2ffffc50f`1badfaa0 fffff758`a852474d : ffff9f0a`aa36d080 fffff804`1abef2d8 00000000`00000000 00000000`00040246 : win32kfull!NtUserCallNoParam+0x70ffffc50f`1badfad0 fffff804`1abef478 : 00000000`00000170 00000000`00000025 00000000`00000000 00000000`00000000 : win32k!NtUserCallNoParam+0x15ffffc50f`1badfb00 00007ffc`0cb810e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x2800000096`34f3fe38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`0cb810e4SYMBOL_NAME: win32kfull!InternalSetTimer+4f3MODULE_NAME: win32kfullIMAGE_NAME: win32kfull.sysIMAGE_VERSION: 10.0.19041.388STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 4f3FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_STACKPTR_ERROR_win32kfull!InternalSetTimerOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {d6d41284-2d8d-9f4e-8a85-83d570096469}Followup: MachineOwner---------

:)

 

KernelBase.dll is broken constant BSOD's constant game crashing.

Hi Darry,

User Profile corruption is one of the possible reasons why you are experiencing constant BSOD's on your computer. You mentioned that you ran the
System File Checker (SFC) tool, but is still getting a stop code. To further troubleshoot the issue, we suggest that you create a new User Profile and check if the issue persists.

To create a user profile, follow these steps:

• Go to Settings. Click Accounts.
• Select Family & other people.
• Select the Add someone else to this PC tab.
• Name the user as Test.
• Leave the password field blank.
• Hit Next.
• Sign in as Test user.

You may also check this link
to fix BSOD errors. Choose the situation when you experienced the problem and follow the troubleshooting steps.

 

BSOD win32kfull.sys

Hi,

Thank you for writing to Microsoft Community Forums.

We have analyzed the dump file you have provided, looks like the issue is because of driver failure.

Below are few of the troubleshooting you can try to further eliminate the root cause of the issue.

Method 1:

Uninstall and reinstall drivers.

1. I suggest you to
   uninstall all the
   Intel display driver from
   device manager.
   
2. Expand the Display driver category in device manager and uninstall it with the help of above article.
   
3. Reboot the computer and check.
   
4. If you still face the issue,
   
   update the display drivers.
   

Method 2:

Running driver verifier.

1. Press and hold Windows + R key on the keyboard.
   
2. Type verifier and click on
   OK.
   
3. If you receive any User Account Control prompt, please click on
   OK.
   
4. Now, select Create standard settings and click on
   Next.
   
5. Click on Select Driver names from a list and click on Next.
   
6. Scroll down and look for win32kfull.sys.
   
7. Click on the check box beside win32kfull.sys.
   
8. Now, click on Finish and click on
   OK.
   
9. Restart the computer.
   

This will check the driver in stress level, verify why the driver is crashing, and create a log.

Once the PC is restarted, please follow the steps mentioned below to open the log:

1. Type Command Prompt in the search on the taskbar.
   
2. Right click on the black console icon and select
   Run as Administrator.
   
3. Now, type verifier /log and press Enter on the keyboard it will show you the logs.
   

Once you have the logs, please share it with me to assist you further.

After sharing the logs, please follow the steps mentioned below to disable verifier:

1. Press and hold Windows + R key on the keyboard.
   
2. Type verifier and click on
   OK.
   
3. If you receive any User Account Control prompt, please click on
   OK.
   
4. Click on Delete existing settings and click on
   Finish.
   
5. Click on Yes and click on
   OK.
   
6. Restart the computer.
   

If you still face the issue, reply to this post with more information.

Hope it helps.

Amit Sunar

Microsoft Community – Moderator

 

Constant BSOD and Error: 0x80080005 while downloading Windows updates

Hi Jose,



Thank you for writing to Microsoft Community Forums.



I understand that you are facing BSOD after performing installation of Windows 10 on your PC. Thank you for sharing the dump files and the necessary details of the PC.



I have analyzed the dump files and found out that the files Win32kfull.sys and
segurazokd.sys are the reason for causing the BSOD.



Regarding the BSOD caused by the file Win32kfull.sys, I would suggest you to run a memory diagnostic test to check for faulty RAM. As you have mentioned that you have performed a memory test but one RAM stick was disconnected, please
perform this test once again with both the RAM sticks connected.

1. Open Start Menu and type
   Memory.
   
2. Now click on Windows Memory Diagnostic.
   
3. Click on Restart now and check for problems.
   
4. Follow the on screen instructions
   

Regarding the BSOD caused by segurazokd.sys, I would suggest you to re-install any programs related to
Seagate, as you are using a Seagate hard drive it could be possible that the storage drivers are causing the BSOD.



However, regarding the Windows updates issue you can refer the article
Fix Windows Update errors.



Note: The article talks about performing a clean install, it is advised to backup all the data before performing the steps.



If the issue persists, please get back to us with the results of the troubleshooting steps to assist you better.



Regards,

Prakhar Khare

Microsoft Community – Moderator