I recently followed these instructions to shrink my main Windows 7 volume on my SSD. They involved temporarily disabled System Restore and Paging. Since doing so I have gotten a few blue screens. I used WinDbg to examine memory.dmp as well as the core dumps in my C:\Windows\Minidump folder. They all indicate a CRITICAL_STRUCTURE_CORRUPTION (109). The MSDN page is at .
- Use System Restore. I cannot do this because when I disabled System Restore to do the volume shrink it deleted my restore files.
- Use the Action Center. Yeah right.
- Check Windows Update. Done.
- Search for drivers on the manufacturer website. Unless I know which driver is problematic, this is just trial and error.
- Use Safe Mode. What would I do in Safe Mode that I haven't already done?
- Check for hard disk and memory errors. memtest and chkdsk both indicated no problems.
I assume the problem has something to do with shrinking the volume, but the error codes indicate a driver problem.
Is there anything else I can do to help narrow the problem down? A more thorough chkdsk that will make sure Windows is happy with the location of its paging file, etc. now that the volume is smaller?
Is there any way to view drivers chronologically in Windows?
CRITICAL_STRUCTURE_CORRUPTION (109) This bugcheck is generated when the kernel detects that critical kernel code or data have been corrupted. There are generally three causes for a corruption: 1) A driver has inadvertently or deliberately modified critical kernel code or data. See (removed link) 2) A developer attempted to set a normal kernel breakpoint using a kernel debugger that was not attached when the system was booted. Normal breakpoints, "bp", can only be set if the debugger is attached at boot time. Hardware breakpoints, "ba", can be set at any time. 3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data. Arguments: Arg1: a3a039d8959c8728, Reserved Arg2: b3b7465ee81ac29e, Reserved Arg3: 00000000c0000082, Failure type dependent information Arg4: 0000000000000007, Type of corrupted region, can be 0 : A generic data region 1 : Modification of a function or .pdata 2 : A processor IDT 3 : A processor GDT 4 : Type 1 process list corruption 5 : Type 2 process list corruption 6 : Debug routine modification 7 : Critical MSR modification
02fd95d8 0000000000000000 : 00000000
00000109 a3a039d8959c8728 b3b7465e
e81ac29e 00000000c0000082 : nt!KeBugCheckEx