Windows 10: BSOD Shortly After Startup - CRITICAL_STRUCTURE_CORRUPTION

A while ago I had this BSOD and after some shot-in-the-dark attempts to fix it like reinstalling some drivers, chkdsk, and that sort of thing, it worked again and I thought it was over. Recently it has came back with a vengeance. This happened after I updated and used Malwarebytes, but it persists after uninstalling it.

Note: Everything works just fine in safe mode

Things I have tried:

• sfc to check for corruption
• Some other command to check online for corruption
• chkdsk (it wouldn't let me do a /scan so it just sat there with a few unresolved errors)
• Hardware tests - RAM and CPU - Passed with flying colors
• Dump analyzer (No help at all. Just says the kernel DLL caused it, which is obvious.)

My untried last resorts:

• Sysprep
• Reinstall

Currently I am running a boot with only my two monitors, a basic wireless mouse (not my G502 which has fancy drivers), my keyboard, my speakers, and my Ethernet plugged in. I have also disabled all startup items. So far, everything is working, but I haven't ran it that long.


My normal peripherals (in case any are known to cause BSODs)

• A G502 Gaming Mouse
• A G930 Headset
• A Bluetooth dongle
• An XBox 360 controller
• A basic gaming keyboard. No RGB. No fancy drivers.

I'm sure the rest of what you need to know is in the zip file.

Thank you all,


Edit: I will update if it occurs again during the clean boot.

:)

 

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

 

DRIVER_VERIFIED_DETECTED_VIOLATION and other BSOD errors on Windows 10.

I understand that a clean boot isnt the source of the bsod, I have now done 3 fresh installs. Also turning off fast startup I doubt will fix the issue. Since it doesnt affect restart. Whether I restart or completly shutdown i have a high chance of BSOD.
Ive gone days without out a BSOD if i never shutdown or restart my computer. the moment I do shortly after I BSOD.

Thanks for the response, ill try it out the fast startup change.

 

Your recent crash dumps are empty. The one from back in October does not show the cause since the stack is corrupted.

Continue with your clean boot process and if it remains stable then you can add services and start-up items back a few at a time until it crashes, by a process of elimination you should be able to find out what is causing the crash.

 

Windows Event Manager says it straight up failed to create any dumps.

 

1) Open Ccleaner > click windows tab > scroll down to system and advanced > post an image into the thread
2) In the left lower corner search type clean > open disk cleanup > scroll up and down > post images into the thread
3) In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > on the advanced tab under startup and recovery click settings > post an image into the thread.
4) Download and install Whocrashed > in the left upper corner above analyze click on tools > crash dump test > type: ACCEPT
Resplendence Software - WhoCrashed, automatic crash dump analyzer
5) Click analyze > look for dead or deaddead in the results > post the results into the thread
6) Run the DM log collector after all of the above steps and post a zip into the thread:
BSOD - Posting Instructions - Windows 10 Forums