BSDO with Critical Structure Corruption
For the pas few hours, I've kept having a BSDO with the Critical Structure Corruption message. I upgraded to 8.1 as soon as I got my new laptop, about a month ago. I never had any issues until today. Here's a link to my latest dumpfiles: https://onedrive.live.com/redir?resid=B8CECE5565641511!1003&authkey=!AM64SZw2e3Ka3zo&ithint=file%2c.rar
I hope the link works - it's the first time I use SkyDrive.
If anyone could help, that would be much appreciated.
All of the attached DMP files are of the
CRITICAL_STRUCTURE_CORRUPTION (109) bug check.
This indicates that the kernel has detected critical kernel code or data corruption.
There are generally two causes for this bug check:
- A driver has inadvertently, or deliberately, modified critical kernel code or data. Microsoft Windows Server 2003 with Service Pack 1 (SP1) and later versions of Windows for x64-based computers do not allow the kernel to be patched except through authorized Microsoft-originated hot patches. For more information, see Patching Policy for x64-based Systems.
- A hardware corruption occurred. For example, the kernel code or data could have been stored in memory that failed.
1. Remove and replace AVG with Windows 8's built-in Windows Defender for temporary troubleshooting purposes as it's likely causing conflicts:
AVG removal - http://www.avg.com/us-en/utilities
Windows Defender (how to turn on after removal) - http://www.eightforums.com/tutorials/21962-windows-defender-turn-off-windows-8-a.html
2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.
3. sptd.sys is listed and loaded in your modules list; SCSI Pass Through Direct Host - Daemon Tools (known BSOD issues with Win 7 and 8). Please remove it ASAP with the uninstaller tool - http://www.duplexsecure.com/en/downloads
Great to hear, thanks for the update. I would have removed it as it's a problematic driver. You can keep it if you'd like, just as long as you don't crash. If you do, remove it this time.
If and when you are comfortable and feel your issue has been solved, I'd recommend marking any posts of mine that answered your question as answered so this thread no longer shows up as requiring an answer.