Upgraded to Windows 10 and getting error CRITICAL STRUCTURE CORRUPTION? Here’s the fix!

Posted 16 September 2015 17:32 CEST by Jan Willem Aldershoff

Many Windows 10 users are complaining about Blue Screen of Deaths (BSODs) that present them error CRITICAL STRUCTURE CORRUPTION. On the Microsoft Answers Forum annoyed users complain that their computer reboots after the BSOD and because the error is unexpected and doesn’t announce itself, users lose data.

Users report the crashes sometimes happen within 5 minutes after they started their PC and sometimes the system runs for a couple of hours before the computer shows the error and reboots.

CRITICAL_STRUCTURE_CORRUPTION

The issue appears to have started about 1.5 months ago and happens to both Windows 7 and Windows 8.1 users who upgraded to Windows 10. Most replies to complaining users are not helpful, but there are appear to be some solutions to this error.

The culprit appears to be a driver installed on the system. Microsoft writes on their website that if the error occurs a driver has inadvertently, or deliberately, modified critical kernel code or data or there is a hardware failure. The latter doesn’t seem to be the issue for most users, so it’s more likely a driver is causing the issue.

Some software appears to install drivers that interfere with Windows 10, therefore we recommend the following:

The error is not limited to Windows 10, also users of other Windows versions complain about it, the same solution applies to them as well.


Related content