Windows 10: BSOD: CRITICAL_STRUCTURE_CORRUPTION caused by win32k.sys

I've been getting BSODs with random errors usually FAULTY_HARDWARE_CORRUPTED_PAGE every few days or so for ages and most of them happen while gaming and particularly if I lock my device using Win + L then unlock later.


Here's the analysis of the latest minidump file:


[COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\Minidump\012921-16343-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff803`80c00000 PsLoadedModuleList = 0xfffff803`8182a2f0Debug session time: Fri Jan 29 02:38:26.539 2021 UTC + 4:00System Uptime: 5 days 4:40:52.859Loading Kernel Symbols...................................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list..................................................For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff803`80ff5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb89`22ac6d30=00000000000001095: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************CRITICAL_STRUCTURE_CORRUPTION 109This bugcheck is generated when the kernel detects that critical kernel code ordata have been corrupted. There are generally three causes for a corruption:1 A driver has inadvertently or deliberately modified critical kernel code or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx2 A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time.3 A hardware corruption occurred, e.g. failing RAM holding kernel code or data.Arguments:Arg1: a39fd5d8d8404560, ReservedArg2: b3b6e25f2ac40478, ReservedArg3: ffffde620938b5b7, Failure type dependent informationArg4: 000000000000001e, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification 8 : Object type 9 : A processor IVT a : Modification of a system service function b : A generic session data region c : Modification of a session function or .pdata d : Modification of an import table e : Modification of a session import table f : Ps Win32 callout modification 10 : Debug switch routine modification 11 : IRP allocator modification 12 : Driver call dispatcher modification 13 : IRP completion dispatcher modification 14 : IRP deallocator modification 15 : A processor control register 16 : Critical floating point control register modification 17 : Local APIC modification 18 : Kernel notification callout modification 19 : Loaded module list modification 1a : Type 3 process list corruption 1b : Type 4 process list corruption 1c : Driver object corruption 1d : Executive callback object modification 1e : Modification of module padding 1f : Modification of a protected process 20 : A generic data region 21 : A page hash mismatch 22 : A session page hash mismatch 23 : Load config directory modification 24 : Inverted function table modification 25 : Session configuration modification 26 : An extended processor control register 27 : Type 1 pool corruption 28 : Type 2 pool corruption 29 : Type 3 pool corruption 2a : Type 4 pool corruption 2b : Modification of a function or .pdata 2c : Image integrity corruption 2d : Processor misconfiguration 2e : Type 5 process list corruption 2f : Process shadow corruption 30 : Retpoline code page corruption 101 : General pool corruption 102 : Modification of win32k.sysDebugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4405 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-LLVOKPP Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 27923 Key : Analysis.Memory.CommitPeak.Mb Value: 89 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: 109BUGCHECK_P1: a39fd5d8d8404560BUGCHECK_P2: b3b6e25f2ac40478BUGCHECK_P3: ffffde620938b5b7BUGCHECK_P4: 1eBLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXPNP: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxpnp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: csrss.exeSTACK_TEXT: fffffb89`22ac6d28 00000000`00000000 : 00000000`00000109 a39fd5d8`d8404560 b3b6e25f`2ac40478 ffffde62`0938b5b7 : nt!KeBugCheckExSYMBOL_NAME: win32k!stub_MITSynthesizeKeyboardInput+a7MODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]win32k[/COLOR][COLOR=rgba30, 30, 30, 1]IMAGE_NAME: win32k.sysIMAGE_VERSION: 10.0.19041.1134STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: a7FAILURE_BUCKET_ID: 0x109_1e_win32k!stub_MITSynthesizeKeyboardInputOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {8c3b0343-a7b5-d023-4c9e-df8a94be6134}Followup: MachineOwner---------[/COLOR]

:)

 

Getting Critical_structure_corruption (tcpip/sys) BSOD on Windows 10 computer

Old title: critical_structure_corruption (tcpip/sys)

Hi,

I keeping getting a random BSOD with "critical_structure_corruption (tcpip/sys)" as the reason. I then have to wait approximately 10 seconds during which time Microsoft are collecting information about the error. This seemed to be introduced after the last
Windows update Tuesday. I couldn't find the cause so did a system restore and all was fine again until the following morning when Microsoft automatically installed the updates again. A rollback doesn't fix the problem now.

When are Microsoft going to fix it for me?

I have got an old-ish motherboard who's latest BIOS update was 2010 so I can't help but think this may be the reason. I've tried everything else.

Any ideas?

 

QCAMAIN1.SYS CAUSING BSOD

This was probably caused by the following module:
qcamain1.sys (Qcamain10x64+0x108678)

Bugcheck code: 0x1D3 (0x333, 0x0, 0x0, 0x0)

Error: CUSTOM_ERROR

A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: qcamain1.sys .

Google query: qcamain1.sys CUSTOM_ERROR

Using WhoCrashed I found this thread: QCAMAIN1.SYS CAUSING BSOD (Code 37 Error) however without
solution, locked.

I did get BSOD almost everytime I moved the laptop.

This worked for me:

unscrew wifi module, push a little into the socket. Screw in. DONE

 

CRITICAL_STRUCTURE_CORRUPTION BSOD error message on Windows 10.

Original title: BSOD CRITICAL_STRUCTURE_CORRUPTION on Windows 10?

Hello. Recently, I've met many BSOD with message: CRITICAL_STRUCTURE_CORRUPTION. I don't know which caused it. Here is the dump file:
http://1drv.ms/1NjuKAV