Bsod critical_structure_corruption

  1. Posts : 210
    Windows 10 Pro

    Bsod critical_structure_corruption

    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 Memtest86+ but it did not report any RAM hardware errors. Thanks in advance.

    Attachment 55285
      My Computer

  2. Posts : 14,903
    Windows 10 Pro

    Please search 'msinfo32' and open it.
    If you can open it, save it as msinfo32.nfo.
    Try to open it, if you can right click > copy > zip and upload the zip.

    The msinfo32 file is corrupted and is currently essential for analysis.
      My Computers

  3. Posts : 210
    Windows 10 Pro
    Thread Starter

    It's not corrupted apparently, I can open it with Notepad++. I've uploaded it.

    Attachment 55287

    I used BlueScreenView tool to read the dump files and generated a log, which is attached. According to it, these drivers are the culprit:


    The Bug Check String is "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED", whatever it means.

    Attachment 55363
    Last edited by ksio89; 25 Dec 2015 at 16:48.
      My Computer

  4. Posts : 14,903
    Windows 10 Pro

    Can you open the .nfo file?
    It is again corrupted when I open it.

    Programs claiming to read those dumps for you won't help, they can't get deep enough in the dump to find the actual cause.
      My Computers

  5. Posts : 210
    Windows 10 Pro
    Thread Starter

    OK, I tried again, here it is:

    Attachment 55380
      My Computer

  6. Posts : 14,903
    Windows 10 Pro

    It is recommended to remove Advanced SystemCare, it is known for causing bluescreens.

    How many passes were completed with MemTest86+?
    Have you run the SPTD remover already? An SPTD2 driver is still present on your system.
    Are you using both your GPU's?

    Please check your manufacturer for driver updates.

    Diagnostics Test

     System File Check

    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
      My Computers

  7. Posts : 210
    Windows 10 Pro
    Thread Starter

    I performed 2 passes with Memtest86+, no errors reported. You were right, there was still a SPTD driver (stpd2.sys) in my system. I deleted it and so far the BSODs have stopped. SFC as usual did not find any integrity violations. Thanks for the help, let's hope it's a definitive fix.

    I will test the system all day long to check if the issue is indeed gone. Once I'm 100% sure the BSODs have ceased, I'll mark this issue solved.

    edit: no, BSODs are still happening, usually when gaming. Here's the latest log:

    Attachment 56173

    I see that you recommend performing at least 8 passes in Memtest86+. I'll do it tonight and send a photo of the result later.

    I used Memtest86 6.2.0 Free instead of Memtest86+ 5.01 because the latter has a bug with CPU multicore support, as it freezes after a while. Memtest86 does not have this bug, so it can perform the testes much faster than Memtest86+ in which only single core mode is working. Here is the report:

    Attachment 56449

    As you can see, after 4 passes, it didn't find any errors. I used the ePSA diagnostics tool for Dell notebooks to perform RAM testes, and it didn't find any issues either. I suspect the cause of BSODs is some buggy Radeon drivers. I reverted from Radeon Software 15.12 to Catalysy 15.11.1, and I'll check if BSODs still happen.

    edit 2: it was caused by some buggy driver from Radeon Software 15.12, amdkmpfd.sys, as reported by BlueScreenView, and not the SPTD driver. I went back to Catalyst 15.11.1 (using Display Driver Uninstaller to wipe every trace of previous drivers) and the BSODs have stopped, no crashes for over a week.
    Last edited by ksio89; 06 Jan 2016 at 09:54.
      My Computer


  Related Discussions
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 06:32.
Find Us

Windows 10 Forums