[SOLVED] Help with "CRITICAL_STRUCTURE_CORRUPTION" BSOD after upgrading from Windows 7 to Windows 10. FIX: SPTD driver removed.

B

bLight

Member
Joined
Feb 19, 2020
Posts
7
After upgrading from a fully updated (and stable) Windows 7 to Windows 10 and making sure it's fully updated post-upgrade, I started encountering "CRITICAL_STRUCTURE_CORRUPTION" BSOD, even when not interacting with the computer.

I read a similar thread on the forum that resulted from Asus drivers, however I'm running on a Gigabyte board.

· OS - Windows 10 Pro, 10.0.18363.

· x86 (32-bit) or x64 (64-bit) - 64bit
· What was the originally installed OS on the system? - Windows 7 Professional, latest build+patches.
· Is the OS an OEM version (came pre-installed on system) or full retail version (YOU purchased it from retailer)?
Purchased it with a custom built silent computer from a local computer store franchise, paid separately for the license, but I can't recall if it was OEM or not.
· Age of system (hardware) - The motherboard/cpu are about 8 years old, I replaced the disk drive and display card since.
· Age of OS installation - have you re-installed the OS?
I installed it today.

· CPU - Intel Sandy Bridge i7-2600K (Intel64 Family 6 Model 42 Stepping 7 GenuineIntel ~3701 Mhz)
· Video Card - NVIDIA 1030GT
· MotherBoard - Gigabyte Z68XP-UD4
· Power Supply - Hard to reach
· System Manufacturer - Custom build
· Exact model number - doesn't apply
· Laptop or Desktop? - desktop

Here's what I tried so far:
1. Installed the latest NVIDIA driver.
2. Disabled the integrated display (Intel HD 3000) in the bios.
3. Disabled non-essential services.
4. Uninstalled non-essential applications.
5. Uninstalled non-essential drivers.
6. Disabled unsigned drivers.
7. With "verifier" I tried selecting drivers built for older versions of windows and none were found.
8. With "verifier" I tried selecting unsigned drivers none were found.
9. I've run SysnativeBSODCollectionApp and attached the resulting zip.

The CPU/Motherboard hardware is somewhat old, I'm hoping this doesn't mean I have to revert to Windows 7.
 

Attachments

Last edited:
Hi!

I would suggest you test your RAM and HDD first:

Test RAM with PassMark MemTest86

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:


  • Download the portable version of GSmartControl and save it on your Desktop;
  • Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
  • Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
  • You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
  • Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
  • Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
  • Please note: If the SMART Status reads: Unsupported, stop and let me know.
    info_failing.png
 
softwaremaniac:
My System drive is an SSD (Samsung 850 PRO), not an HDD, there's nothing highlighted on the attributes page.
This is the result:
---
"Test #","Type","Status","% Completed","Lifetime hours","LBA of the first error"
1,"Extended offline","Completed without error","100%","23","-"
---

Regarding memory test, isn't it enough to use Window's built in memory diagnostic tools?

And I remind you, this system was working 100% stable for years and started with the BSOD right after upgrading to Win10 (within 30min), I doubt there's any RAM/Drive issues.
Also, the BSOD is "CRITICAL_STRUCTURE_CORRUPTION" with the 4th parameter having a value of "1c" which according to documentation I read usually means that it's a driver issue.
 
If available, please zip the following file and then post it to a file sharing site such as Google Drive, OneDrive or DropBox.

Code: 
%systemroot%\MEMORY.DMP
 
Could you please send me the dropbox link as well?

@jcgriff2

EDIT: Did you ever encounter BSODs under Windows 7?

What method did you use to upgrade to Windows 10?
 
jcgriff2 said:
Could you please send me the dropbox link as well?

@jcgriff2

EDIT: Did you ever encounter BSODs under Windows 7?

What method did you use to upgrade to Windows 10?
Click to expand...

1. No BSOD under Windows 7, worked stable for years.
2. I used the Update Assistant (Download Windows 10) to upgrade from within Windows to maintain my app/data (not a clean install).
3. I sent you a private message with a link to the memory dump file.
 
Please remove the following driver:

Rich (BB code): 
2: kd> lmvm sptd
Browse full module list
start             end                 module name
fffff807`39c80000 fffff807`39da6000   sptd       (no symbols)           
    Loaded symbol image file: sptd.sys
    Image path: \SystemRoot\System32\Drivers\sptd.sys
    Image name: sptd.sys
    Browse all global symbols  functions  data
    Timestamp:        Sun Oct 11 13:55:14 2009 (4AD24632)
    CheckSum:         000D6B26
    ImageSize:        00126000
    File version:     1.62.0.0
    Product version:  1.62.0.0
    File flags:       8 (Mask 3F) Private
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0000.04b0
    Information from resource tables:
        CompanyName:      Duplex Secure Ltd.
        ProductName:      SCSI Pass Through Direct
        InternalName:     SPTD.SYS
        OriginalFilename: sptd.sys
        ProductVersion:   1.62.0.0
        FileVersion:      1.62.0.0 built by: WinDDK
        FileDescription:  SCSI Pass Through Direct Host
        LegalCopyright:   Copyright (C) 2004

A removal tool can be found here - DuplexSecure - FAQ
 
x BlueRobot said:
Please remove the following driver:

Rich (BB code): 
    Loaded symbol image file: sptd.sys
    Image path: \SystemRoot\System32\Drivers\sptd.sys
    Image name: sptd.sys

A removal tool can be found here - DuplexSecure - FAQ
Click to expand...

I don't have this file on my system.
I may have had it previously through a CD emulation app, but I think the last BSOD occured after I already removed it (I may be wrong), are you basing your suggestion on the memory file or from past experience?

I took another step and disconnected my old webcam which adds an audio driver which may have been outed, so far more than 24h since the last BSOD.
 
That's what was in the dump file, is there any remnants in your registry?

Rich (BB code): 
2: kd> !reg querykey \REGISTRY\MACHINE\SYSTEM\CONTROLSET001\SERVICES\SPTD


Found KCB = ffffc98d578eb160 :: \REGISTRY\MACHINE\SYSTEM\CONTROLSET001\SERVICES\SPTD
 
x BlueRobot said:
That's what was in the dump file, is there any remnants in your registry?
Click to expand...

Yes, there are remnants in the registry.

So far ~34h since the last BSOD, I hope it's resolved, I'll re-post again if I experience another one.

Thank you everyone for the help.
 
Thanks for updating us, and I suspect that it would have been part of the CD Emulation tool you had previously. Hopefully you won't have any other issues.

Are you happy for me to mark this thread as solved?
 
It's possible that I uninstalled the CD Emulation tool and it only scheduled the driver for removal on reboot and then it blue-screened and got removed on the subsequent boot.

In either case, it's been around 3 days since the last BSOD so I'm hoping everything is cool and you can mark this as solved.

Thank again!
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top