CRITICAL_STRUCTURE_CORRUPTION: ntoskrnl.exe

I just completely reinstalled Windows 10 fresh due to constant crashing involving the kernel mentioned in the title. It would crash 5, 6 times in 8 hours whether it was logged in or not. The crash at that time was DPC_WATCHDOG_VIOLATION and would occur while I was using it or by itself. It was super inconsistent, some days my PC would go a whole day without a crash, some days it would crash 5 or 6 times. All said the crash occured with ntoskrnl.exe. I never did find a fix for this so I bit the bullet and wiped my PC clean and installed Windows 10 fresh. Since reinstalling and setting everything up just the way I like it, I got a crash last night, CRITICAL_STRUCTURE_CORRUPTION pointing to ntoskrnl.exe yet again. I have not run Memtest86 but ran it a few times for 2 days straight before I reinstalled Windows and it didn't show a single corruption. I just ran verifier and logged into Windows without issue. I didn't run it for long but usually it crashes immediately upon starting Windows when I have verifier running. I had it running with every non-Microsoft driver selected and everything checked except Randomized low resources simulation and DDI compliance checking. I've attached a minidump and screenshots of my system specs. I need to nip this issue in the bud right away because I think previous crashes corrupted my system beyond repair and I don't want to have to go through the nightmare of reinstalling Windows and setting everything up again.

CRITICAL_STRUCTURE_CORRUPTION

This means your HDD has Bad Sectors on it and is starting to Fail.
download DiskGenius from my signature, Select your drive, go up to the toolbar to Disk/View SMART Information. This will give you a Quick snapshot of your drives health. You can also go to View or Repair Bad Sectors/Start Verify this will take a lot longer but it will give you a map of the Bad Sectors on your HDD if any. If there is more then a couple the drive needs to be replaced ASAP.

See here: Memory Management BSOD on Startup They had the same error.

Run MemTest . Bad disk is not the only cause of this error. I could be many things.

Has anything about your system changed recently?

What verifier is that? Can you post a link? What devices did you connect? Does the problem occur if you disconnect them?

Have you checked Windows Event Viewer and Windows Reliability history for potential clues and frequency of errors?

If you removed/replaced any hardware since this started, I would reseat them all including cables, boards, and RAM.

tangre said:

I just used driver verifier and the devices I've connected are just external usb devices. It doesn't seem the crash is seen in event viewer.

Any devices are subject to cause the error including external USB devices.

Are all your drivers and BIOS current according to PC/component manufacturer website or updater app?

tangre said:

I'm currently using Snappy Driver Installer to update all to most recent or optimal.

FYI, most of us here recommend not using 3rd party driver updater apps/snake oils.