Windows 10: Stop Code: CRITICAL STRUCTURE CORRUPTION

I recently used the media creation tool to update a computer to Windows 10 Build 18363. The model is a Dell Optiplex 3020, Core13-4130. About a day later, I began receiving BSODs.

This is one of the latest dump files:




******************************************************************************** ** 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: a39ffe60a2b8d541, ReservedArg2: b3b70ae6f53972ce, ReservedArg3: ffffbf0811ea50d0, Failure type dependent informationArg4: 000000000000001c, 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:------------------*** WARNING: Unable to verify checksum for win32k.sysKEY_VALUES_STRING: 1 Key : Analysis.CPU.Sec Value: 4 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on CYNTHIA-PC Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.Sec Value: 5 Key : Analysis.Memory.CommitPeak.Mb Value: 67 Key : Analysis.System Value: CreateObjectADDITIONAL_XML: 1BUGCHECK_CODE: 109BUGCHECK_P1: a39ffe60a2b8d541BUGCHECK_P2: b3b70ae6f53972ceBUGCHECK_P3: ffffbf0811ea50d0BUGCHECK_P4: 1cBLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffff8584`67652e98 00000000`00000000 : 00000000`00000109 a39ffe60`a2b8d541 b3b70ae6`f53972ce ffffbf08`11ea50d0 : nt!KeBugCheckExSYMBOL_NAME: ANALYSIS_INCONCLUSIVEMODULE_NAME: Unknown_ModuleIMAGE_NAME: Unknown_ImageSTACK_COMMAND: .thread ; .cxr ; kbFAILURE_BUCKET_ID: BAD_STACK_0x109OS_VERSION: 10.0.18362.1BUILDLAB_STR: 19h1_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}Followup: MachineOwner---------3: kd> !blackboxbsdStream size mismatch expected = 176, read = 1683: kd> !blackboxntfsNTFS Blackbox Data0 Slow I/O Timeout Records Found0 Oplock Break Timeout Records Found



Can someone tell me if this is fixable without a clean install? If so, how?

:)

 

Critical Structure Corruption Windows 10

I keep getting this error "Critical Structure Corruption" and can't seem to fix it.

It happens while I am busy on my laptop. Here are some of the steps I have tried so far to resolve this with no success.

1. Ran Windows Memory Diagnostic = no problems so RAM looks good.
   
2. Check The CPU with Intel-Processor-Diagnostic-Tool = PASS all
   
3. Drivers update, I used driver booster and did need to update 18 drivers but was able to update with no issues.
   
4. Update software and drivers, well it was suggested that I update BlueStacks but the update failed, bluestacks mentioned that it might be an issue so as I do not use the tool I uninstalled the software altogether.
   
5. Updated Windows, this I do regularly and automatically so no big updates were missed.
   
6. Defragged the machine - system is optimized
   
7. Ran anti-virus check and all's good
   
8. Ran CCleaner
   

Now I might mention I'm not a super user, but I'm able to follow suggestions quite well.

Any help will be appreciated.

Screenshot:

 

BSOD Critical Structure Corruption




And there were no yellow or exclamation points in Device Manager....just a long list of items repeated which I don't understand why.













I did zip the last full Memory Dump and uploaded it to Google Drive. Link was in previous post. Did it not work? Although I can reboot into normal state to really use computer without BSOD Crit Struc Corrup I need to stay in safe mode.

 

Critical structure corruption

my computer bsods again and the error was critical structure corruption what was listed under it was pshed.dll i don't know if that is something with windows or drivers but here is the minidump so someone can look at it and see https://1drv.ms/f/s!Aiv6T9qpPR6GgYRuP7WFKTrsh44jgQ