Can't boot after ATIH 2014 install
I had to reinstall Windows 7 Ultimate before the holidays, and have done the following:
1) Installed Windows 7 onto my primary SSD drive (Samsung 840);
2) Installed Windows 7 Service Pack 1;
3) Installed all the KBxxxx updates from Microsoft;
4) Installed IDrive online backup (may or may not be relevant);
5) Installed various utilities, like WinZip, Microsoft Security Essentials;
6) Created restore point in Windows;
7) Installed ATIH 2014;
8) I believe it requested a reboot, so I restarted the system;
9) Windows attempts to start, then only showed a black screen after my USB devices (i.e., keyboard) comes online. It then BSODs after a long while;
10) Attempted another restart, hitting F8 to go into safe mode, it stops at classpnp.sys;
11) Attempted another restart, this time restoring my 'windows restore point' back in step 6;
12) Windows allows me to start again, so I use WinDbg to analyze the MiniDump;
13) MiniDump provides some information that it's crashing on VIDSFLT.SYS (will provide full info below).
I've tried reinstalling ATIH 2014 with basically the same steps above with the same results (crash, having to restore). I also tried downloading the latest version of 2014, just to be sure, but no luck so far. Did, perhaps, an older vidsflt.sys get 'stuck' from the first install, if that's the problem?
A side-effect of doing the windows restore point, is that I now can only log in with a 'temporary profile', which is very annoying, but probably not related to the Acronis issue.
I've had trouble with IDrive and Acronis before, when they're both running at the same time, it'll BSOD (but pointing to an IDrive driver problem). I made sure I disabled IDrive during the installation, just to make sure there were no conflicts. (Note that IDrive is either unable or unwilling to fix their problem).
I'm not sure what's going on, as I had ATIH 2014 installed fine (having upgraded from 2013) prior to my reinstallation of Windows. I'm not immediately seeing anyone else having this issue on the forums, so not sure how to proceed. I need to get my backups going as soon as possible. Please help! Thanks in advance.
Miscellaneous information:
OS: Windows 7 Ultimate 64-bit, SP1
Motherboard: ASUS PQ5 PRO
CPU: Intel Core 2 Duo E8500 @3.16ghz
RAM: 8gb 1066ghz
DISK0: Samsung PM810 SSD, 256GB
DISK1: Western Digital 2TB, WD20EARS-00MVWB0
DISK2: Seagate 4TB ST4000DM000-1F1268
External USB 3.0 Drive which contains the backups: Seagate 3TB ST3000DM001-1CH166
CrystalDiskInfo reports no drive errors/problems for what it's worth.
The MiniDump results from using WinDBG:
Loading User Symbols
Loading unloaded module list
...
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff880075ab5d0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\vidsflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vidsflt.sys
*** ERROR: Module load completed but symbols could not be loaded for vidsflt.sys
Probably caused by : vidsflt.sys ( vidsflt+5180 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880075ab5d0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
+6264646662643162
fffff880`075ab5d0 f8 clc
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbd100
0000000000000000
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: MsMpEng.exe
CURRENT_IRQL: 0
EXCEPTION_RECORD: fffff880075ac4f8 -- (.exr 0xfffff880075ac4f8)
ExceptionAddress: fffff880076b3180 (vidsflt+0x0000000000005180)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000003fff8
Attempt to read from address 000000000003fff8
TRAP_FRAME: fffff880075ac5a0 -- (.trap 0xfffff880075ac5a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa800af0b000 rbx=0000000000000000 rcx=fffffa800af2b000
rdx=0000057ff5115000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880076b3180 rsp=fffff880075ac738 rbp=0000000000000100
r8=0000000000020000 r9=0000000000001000 r10=00000000000004c5
r11=fffffa800af0b000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
vidsflt+0x5180:
fffff880`076b3180 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002b1717b to fffff80002a85b80
STACK_TEXT:
fffff880`075ab518 fffff800`02b1717b : 00000000`0000001e ffffffff`c0000005 fffff880`075ab5d0 00000000`00000000 : nt!KeBugCheckEx
fffff880`075ab520 fffff800`02ad8d08 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KipFatalFilter+0x1b
fffff880`075ab560 fffff800`02ab0cdc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x83d
fffff880`075ab5a0 fffff800`02ab075d : fffff800`02bd1d74 fffff880`075ad4e0 00000000`00000000 fffff800`02a10000 : nt!_C_specific_handler+0x8c
fffff880`075ab610 fffff800`02aaf535 : fffff800`02bd1d74 fffff880`075ab688 fffff880`075ac4f8 fffff800`02a10000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`075ab640 fffff800`02ac04e1 : fffff880`075ac4f8 fffff880`075abd50 fffff880`00000000 fffffa80`0a3f4520 : nt!RtlDispatchException+0x415
fffff880`075abd20 fffff800`02a85202 : fffff880`075ac4f8 fffffa80`0af0b000 fffff880`075ac5a0 00000000`00020000 : nt!KiDispatchException+0x135
fffff880`075ac3c0 fffff800`02a83d7a : 00000000`00000000 00000000`0003fff8 fffff880`076c6100 fffffa80`0af0b000 : nt!KiExceptionDispatch+0xc2
fffff880`075ac5a0 fffff880`076b3180 : fffff880`076b510a 00000000`00000246 00000000`00020000 fffff800`02c00e80 : nt!KiPageFault+0x23a
fffff880`075ac738 fffff880`076b510a : 00000000`00000246 00000000`00020000 fffff800`02c00e80 fffffa80`06a19040 : vidsflt+0x5180
fffff880`075ac740 00000000`00000246 : 00000000`00020000 fffff800`02c00e80 fffffa80`06a19040 fffffa80`0af0b000 : vidsflt+0x710a
fffff880`075ac748 00000000`00020000 : fffff800`02c00e80 fffffa80`06a19040 fffffa80`0af0b000 fffff880`076b0365 : 0x246
fffff880`075ac750 fffff800`02c00e80 : fffffa80`06a19040 fffffa80`0af0b000 fffff880`076b0365 fffffa80`099d9200 : 0x20000
fffff880`075ac758 fffffa80`06a19040 : fffffa80`0af0b000 fffff880`076b0365 fffffa80`099d9200 00000000`00000000 : nt!KiInitialPCR+0x180
fffff880`075ac760 fffffa80`0af0b000 : fffff880`076b0365 fffffa80`099d9200 00000000`00000000 00000000`00000000 : 0xfffffa80`06a19040
fffff880`075ac768 fffff880`076b0365 : fffffa80`099d9200 00000000`00000000 00000000`00000000 fffff880`076b1928 : 0xfffffa80`0af0b000
fffff880`075ac770 fffffa80`099d9200 : 00000000`00000000 00000000`00000000 fffff880`076b1928 00000000`00000000 : vidsflt+0x2365
fffff880`075ac778 00000000`00000000 : 00000000`00000000 fffff880`076b1928 00000000`00000000 ffffd39a`caa0f0ce : 0xfffffa80`099d9200
STACK_COMMAND: kb
FOLLOWUP_IP:
vidsflt+5180
fffff880`076b3180 ?? ???
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: vidsflt+5180
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: vidsflt
IMAGE_NAME: vidsflt.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 511c8c89
FAILURE_BUCKET_ID: X64_0x1E_c0000005_vidsflt+5180
BUCKET_ID: X64_0x1E_c0000005_vidsflt+5180
Followup: MachineOwner
---------
1: kd> lmvm vidsflt
start end module name
fffff880`076ae000 fffff880`076cd000 vidsflt T (no symbols)
Loaded symbol image file: vidsflt.sys
Image path: \SystemRoot\system32\DRIVERS\vidsflt.sys
Image name: vidsflt.sys
Timestamp: Thu Feb 14 01:04:41 2013 (511C8C89)
CheckSum: 0002A634
ImageSize: 0001F000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
