[SOLVED] BSOD every hour after upgrading to Win10

tal.green

tal.green

Member
Joined
Oct 1, 2019
Posts
8
Hi everyone and thank you for having me!


Yesterday, I upgraded my OS from Win7 to Win10 (Home).
Prior to the upgrade, I didn't experience any problem whatsoever.

After the upgrade, I'm getting a BSOD every hour or so, even if I'm away and the computer is idle.
The stop code is: CRITICAL STRUCTURE CORRUPTION.

I've uninstalled+reinstalled my GPU's drivers, but the problem still persists.

I'm attaching the SysnativeBSODCollectionApp output file.


· OS - Windows 10 Home.
· x86 (32-bit) or x64 (64-bit)? - 64-bit.
· What was the originally installed OS on the system? - Windows 7.
· Is the OS an OEM version or full retail version? - OEM.
· Age of system (hardware) - about 6 years (but I'm upgrading the hardware every 1-2 years).
· Age of OS installation - have you re-installed the OS? - for Win7 is 6 years, for Win10 is 1 day.

· CPU - Core i7-3770.
· Video Card - Geforce GTX 1060.
· Memory (RAM) - 16 GB.
· MotherBoard - Intel DH77KC.
· Power Supply - 800 Watts.
· Laptop or Desktop? - Desktop.


I will appreciate any help I can get,
Thank you very much,
Tal.
 

Attachments

Thank you very much for your reply!

The RAM test passed successfully without errors.

I've tried to run the SeaTools test but I wasn't able to - when running the bootable USB version, my computer didn't recognize it as a bootable device for some reason. I was able to boot from the DOS version (on a CD), but the tool didn't recognize any of my drives.

In addition, I installed the GSmartControl tool. It didn't show any signs of errors in the SMART attributes (my SSD drive is pretty new - about 8 month old).
I was only able to run the short self-test (which passed successfully) since my computer BSODs every 40 min or so.

Is there another good bootable SSD test tool I can try?
What other steps/tests I can try in order to determine the root of the problem?

Thank you very much,
Tal.
 
Thank you. Please do the following:


SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
Thank you very much for your response.

I ran the SFC Scan and it didn't find any integrity violations.

I'm attaching the log output file as you requested.

Thank you very much,
Tal.
 

Attachments

Hi, 🤔
pretty much a full flavoured fat Win7 System with a lot of Goodies in?

Code: 
101 : General pool corruption
this is a driver not any longer compatible with Win10, however not named by WinDBG.

rushing through the list of drivers and systemfiles, i stumble over
SPDT.SYS! and this is the beliked Daemontool dated 2009!!! producing a lot of fun, get rid of it.
Next you have still Samsung Magician installed, not usefull in Win10! get RID...
older Speedfan or VMware-product / Virtual-Box may cause fun too.
Saibus.sys Saitek Systemexplorer dated 2013 is a candidate too to be removed until you have a stable system.
once the system comes up, uninstall old Software, clean up Autostarts and test again.

Michael
 
Check the system manufacturer for a BIOS update.

I was unable to determine the system manufacturer from the reports.

Regards. . .

jcgriff2

EDIT: If you have an SSD, go to SSD manufacturer's support site and check for a firmware upgrade.
 
MichaelB said:
Hi, 🤔
pretty much a full flavoured fat Win7 System with a lot of Goodies in?

Code: 
101 : General pool corruption
this is a driver not any longer compatible with Win10, however not named by WinDBG.

rushing through the list of drivers and systemfiles, i stumble over
SPDT.SYS! and this is the beliked Daemontool dated 2009!!! producing a lot of fun, get rid of it.
Next you have still Samsung Magician installed, not usefull in Win10! get RID...
older Speedfan or VMware-product / Virtual-Box may cause fun too.
Saibus.sys Saitek Systemexplorer dated 2013 is a candidate too to be removed until you have a stable system.
once the system comes up, uninstall old Software, clean up Autostarts and test again.

Michael
Click to expand...

Hi and thank you for your response!

How can I get rid of the drivers you mentioned above? (Uninstalling Daemon Tools didn't remove SPDT.SYS).

In addition, what do you mean by saying clean up Autostarts ?

Thank you very much,
Tal.
 
jcgriff2 said:
Check the system manufacturer for a BIOS update.

I was unable to determine the system manufacturer from the reports.

Regards. . .

jcgriff2

EDIT: If you have an SSD, go to SSD manufacturer's support site and check for a firmware upgrade.
Click to expand...

Hi jcgriff2, thank you for your reply.

Ok, I will try to update my BIOS and report back when I've more info.

Thank you very much,
Tal.
 
Ok, thank you! I will try your suggestions and see what happens. Of course I will report back when I have more info.

Thank you,
Tal.
 
A week has passed, and I haven't had any BSOD! I think it really was the SPDT.SYS driver that caused the majority of the trouble.
In addition, I've upgraded my system and removed the other potentially problematic drivers.

softwaremaniac, MichaelB, jcgriff2 - Thank you very very much for your incredible help!!
 
That's great, thanks for letting us know, I've marked this thread as solved.

Great work everyone!
 
It has been quite a while since I've seen sptd.sys in a BSOD'ing system.

Much more common to see back in the days of Vista especially, then less in Windows 7.

I pretty much had forgotten that the driver absolutely is high up on the list for drivers that cause BSODs.

Glad that you got this solved.

Good luck to you.

Regards. . .

jcgriff2
 
@jcgriff2 I think the primary reason for that is the fact that Win8+ supports auto mounting, so people do not have to install software like Alcohol or Daemon Tools to manipulate or load images. Therefore, no sptd driver.
 

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

Back
Top