BSOD (Critical_Structure_Corruption) once every few days or so

Page 1 of 6 123 ... LastLast
  1.    25 Aug 2016 #1

    BSOD (Critical_Structure_Corruption) once every few days or so

    Hello everyone,

    This is going to be my first post here. So, recently, (post-W10 Anniversary Update) I've had BSOD's start to happen. They all seem to be CRITICAL_STRUCTURE_CORRUPTION ones. I don't know if it's because of the Anniversary Update, or because of some things I did. Anyway, I'm going to let you know what changed (which is quite a lot):

    1. Updated from W10 to W10 Anniversary Update. No reinstall, just installed regularly through Windows Update.
    2. Used CCleaner for both registry cleaning and application cleaning purposes.
    4. Updated Nvidia drivers manually to 372.54 by using DDU and then installing the drivers but only PhysX and the drivers themselves, as well as Clean install ticked.
    5. Used SDI (Snappy Driver Installer) for updating drivers.
    6. Used geek to uninstall some programs (like Malwarebytes as Windows Defender should be enough).
    7. Installed LibreOffice and some games.
    8. Ran "Visual C++ Redist Installer V46.exe", essentially it's something someone packed together with all the Visual C++ libraries that you may need for games (except it uninstalls all of them beforehand).

    Here are some ways I've attempted to fix the issue:

    1. Ran the sfc /scannow command. There were no integrity violations.
    2. Ran the Dism /Online /Cleanup-Image /CheckHealth command and there were no issues either.
    3. Googled the issue (BSOD Critical_Structure_Corruption) and it seems to be potentially caused by 3 different issues: hardware (RAM most likely, not sure if it can be something else), programmer debugging (though that can't be because I'm not programming stuff), and faulty drivers (might be this?). Also I read a bit, mostly I found axe0's helpful replies so I hope he posts here too, haha.

    What's important to note is that I haven't changed any hardware after Windows 10 Anniversary Update. Let me know if I should provide you with any logs from SDI, because it seems that the DM Log Collector tool doesn't actually create a folder on my desktop with the necessary files. It seems to create a TFdebugfiles one, but it's removed once DM Log Collector finishes and you press a key to exit it.

    Anyway, right now I'm thinking about reinstalling Windows but I'd rather not have it come to that. Also there is something else I want to ask: do I have to provide the product key once I reinstall W10 Pro 64-bit? In Activation it says "Windows is activated with a digital license", but it's not tied to a MS Account as I use a local one. I don't think I've ever used a MS account either, and last time I reinstalled Windows I don't recall having to enter my product key.

    Let me know what I can do to make DM Log Collector work, as currently it's not really working properly for me as you can see.

    Also, I'm thinking about never using CCleaner/SDI/geek and other stuff similar to that again. I just wonder if they do more harm than good, though SDI is probably nice to update drivers but I don't know if it's updating the proper ones and if it's good to update them (it updated loads of them, again I can post the log files from the program if you wish, but they are pretty big). Let me know if I should continue to use any of these 3 programs.

    There is also an issue with the forum as there is no Romanian time zone.

    Thank you in advance!
      My ComputerSystem Spec

  2.    25 Aug 2016 #2

    Hello RaduAvr,

    What is it saying when you run then DM Log Collector?

      My ComputerSystem Spec

  3.    25 Aug 2016 #3

    Well at the end it says:

    "All files have now been collected and are in a zipped folder on your desktop ready for you to upload to the forum"

    But they are not.
      My ComputerSystem Spec

  4.    25 Aug 2016 #4

    Have you tried it in safe mode?
      My ComputerSystem Spec

  5.    25 Aug 2016 #5

    Same thing in safe mode.
      My ComputerSystem Spec

  6.    25 Aug 2016 #6

    I would also suggest running it in admin mode.

    Now some things I have noticed from you post is that you used a driver installer to detect and install drivers for you? I do not recommend that because it could be possible it grabs the wrong driver. Updating drivers manually can be annoying, but it prevents things like this from happening in the future. So I would suggest to go through and make sure everything is up to date manually and not via driver installer.

    Zip up the TFdebugfiles folder and upload it here. Lets see what's inside. It MAY ​have what we need to get a deeper look into your BSODs.
      My ComputerSystem Spec

  7.    25 Aug 2016 #7

    DM Log Collector runs in admin mode already, by default.

    And yes, I used SDI. Pretty much everyone who used it has recommended it, so I can't imagine it causing many issues though as you say it's possible.

    I'll zip up the TFdebugfiles folder before it disappears (it gets automatically deleted by DM Log Collector at the end). Strange that it doesn't actually zip it itself.

    EDIT: I did try Driver Verifier for a bit as instructed in another post (a few hours) and I did notice that after restarting, it actually turned itself on because I could notice the mouse movement being a bit sluggish. However, upon another restart it seems to not have worked anymore as the mouse was perfectly smooth. Strange, though, because once I went into Driver Verifier, the settings were still there for the drivers... I removed them anyway. Don't know if it's enough testing honestly.
      My ComputerSystem Spec

  8.    25 Aug 2016 #8

    From the way it looks you only have 2 hotfixed installed. Try doing a windows update once more.

    However the overall dump itself came back inconclusive.
      My ComputerSystem Spec

  9.    25 Aug 2016 #9

    2 hotfixes installed? For what?

    Anyway, I tried doing a Windows Update and it came back saying my device is up to date.
      My ComputerSystem Spec

  10.    25 Aug 2016 #10

    Lets try enabling driver verifier to give us more information on what is causing these BSODs. Now most likely if there is a bad driver than it will cause one, but then disable it and upload the information from the new BSOD.

    Driver Verifier - Enable and Disable in Windows 10 - Windows 10 Forums
      My ComputerSystem Spec

Page 1 of 6 123 ... LastLast

Related Threads
I am having BSOD every 40 minutes or so on Windows 10. But there seems to be no BSOD when I switch to another microsoft account.
BSOD Critical_Structure_Corruption in BSOD Crashes and Debugging
Hello, I was playing some games when the BSOD first happened and was trying my usual of troubleshooting it myself. There were two games I installed recently one just tonight which was promptly uninstalled and the other I installed yesterday but...
Solved Critical_structure_corruption bsod in BSOD Crashes and Debugging
I have this configuration: MB:Asus M2n-e CPU: Amd 9650 2.3ghz no overclock Ram: corsair 4gb 1066 (working 800mhz) HDD: WD velociraptor 250gb 10000rpm (win 10 64 bit) + 1tb caviar black + 1tb caviar black sata II psu: 650W high power sirtec...
BSOD Critical_Structure_Corruption in BSOD Crashes and Debugging
Hello, I need help solving something. I recently updated my BIOS, which mainly started the whole BSOD errors. I don't know really what is causing the errors though, I have tested the RAM, which that came out to be perfect with no errors, and when...
Solved Bsod critical_structure_corruption in BSOD Crashes and Debugging
My notebook has been crahing randomly for a while with CRITICAL_STRUCTURE_ERROR BSOD. I read something about SPTD driver installed along with applications like Daemon Tools. I've already uninstalled it but it did not fix it. I've already used...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:24.
Find Us