Windows 10: BSOD for no apparent reason - Critical Structure Corruption

My computer was working fine with Windows 10... but has developed a BSOD issue. I can't think of any changes I've made/programs installed etc, though this is likely the cause. I've run SFC /Scannow along with dism.exe /online /cleanup-image /scanhealth &dism.exe /online /cleanup-image /restorehealth

Everything says it's fine... but I'm still crashing. I've attached a copy of the file created as requested... but I'm very much at my wits end. Very frustrated (as I'm sure you can imagine!).

Any help would be greatly appreciated!

Attachment 34003


Edit: when first running Scannow, it showed an issue with this file: MicrosoftEdgeSquare44x44.scale-125_contrast-white.png, which I have replaced with another version. However, the issue remains, hence this post. *Smile

:)

 

critical structure corruption windows 10

i got a critical structure corruption bsod does anyone know how to fix this?

 

PC Constantly crashing in Windows 10

Latest BSOD came today as a surprise..I was actually able to use the PC for about 2 hours without an incident and then BSOD error critical structure corruption, or something along those lines..

 

All of your dumps are 0x109s but are giving inconclusive analysis. Dumping the stack is providing no useful information unfrotunately but there are a couple of things we can try.
Code: BugCheck 109, {a3a01f59268e250e, b3b72bdf790e34f9, ffffe00089df3ed0, 1c} Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data 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.mspx 2) 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.[/quote]
Download and run MemTest86+ - Test RAM - Windows 10 Forums



Note



Run MemTest86+ for at least 8 passes. Ideally set it off before you go to bed and leave it overnight, we're looking for zero errors here. A single error will show something's going bad with your RAM.

Report back with the results and we'll work from there.

1. Uninstall Alcohol 120% via Add/Remove Programs, a known cause of BSODs.
2. Download the SPTD standalone installer and perform the following steps.
3. Double click the executable to open it.
4. Click the button shown below.







Information If the button it is grayed out as shown in the image, there is no more SPTD installation on your system and you can just close the window.

 

No idea what this means... but your comments make me think that's a good thing?

You sir, may be a genius. I *DID* recently install Alcohol and had forgotten. I have uninstalled and gone through the process of the SPTD (although for future info, Chrome wouldn't allow the download, I had to use a different browser as Chrome kept saying it was malicious and deleting it).

I will run the Memtest tonight to check the RAM, but I'm really hoping it was Alcohol... and it was also around that time I started having an issue.

Thank you very much in advance, and I'll report back tomorrow morning with the results of Memtest.

 

Keep us posted. *Thumbs

 

So... I didn't actually run Memtest since I was pretty confident that it was Alcohol based on timing. Since uninstalling, I've had no issues at all, so I'm happy.

Thank you so much for the help!

 

You're welcome, and thanks for letting us know.