New
#1
0x0000001E error
Hello!
0x0000001E error. Happens very randomly
Attached minidump file.
Please help!
Hello!
0x0000001E error. Happens very randomly
Attached minidump file.
Please help!
BSOD caused by the Acronis True Image Product Line, remove such product or update it to the latest version
Code:BugCheck 1E, {0, 0, 0, 0} Unable to load image \SystemRoot\system32\DRIVERS\snapman.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for snapman.sys *** ERROR: Module load completed but symbols could not be loaded for snapman.sys Probably caused by : snapman.sys ( snapman+19089 )Information
Please remove any CD virtualization programs such as Daemon Tools and Alcohol 120%. They use a driver, found in your dmp, sptd.sys, that is notorious for causing BSODs. Use this SPTD uninstaller when you're done: DuplexSecure - Downloads
You can use MagicDisc as an alternative.
Code:sptd.sys fffff880`01000000 fffff880`01127000 0x00127000 0x4bbd315c 08/04/2010 05:29:00
Thanks, i`ll try it and report.
Hi there! After uninstalling Acronis, Daemon tools and STPD driver it was no BSODs, but today a can`t start Windows at all.
I get 0x0000007B BSOD.
I tried to change ICH SATA Control Mode in BIOS, but it didn`t help. Not IDE\RAID\AHCI
Got the dump from recovery mode, safe mode dont work.
The acronis driver is still the cause, it may have messed up your system
Go to C:\Windows\System32, locate snapman.sys and rename it to snapman.sys.old
Code:******************************************************************************* * * * 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: 0000000000000000, The exception code that was not handled Arg2: 0000000000000000, 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: (Win32) 0 (0) - The operation completed successfully. FAULTING_IP: +0 00000000`00000000 ?? ??? EXCEPTION_PARAMETER1: 0000000000000000 EXCEPTION_PARAMETER2: 0000000000000000 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x1E PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from fffff800032cf46e to fffff800032d7710 STACK_TEXT: fffff880`035fa878 fffff800`032cf46e : 00000000`00000000 fffff880`07f68202 fffff880`035fb080 fffff800`03304668 : nt!KeBugCheck fffff880`035fa880 fffff800`032fd40d : fffff800`034e5b7c fffff800`0341fea4 fffff800`03267000 fffff880`035fafe0 : nt!KiKernelCalloutExceptionHandler+0xe fffff880`035fa8b0 fffff800`03304a90 : fffff800`03426b34 fffff880`035fa928 fffff880`035fafe0 fffff800`03267000 : nt!RtlpExecuteHandlerForException+0xd fffff880`035fa8e0 fffff800`0330606a : fffff880`035fafe0 fffff880`035fb080 00000000`00000001 00000000`00000006 : nt!RtlDispatchException+0x410 fffff880`035fafc0 fffff800`032e0610 : fffffa80`05f6e868 00000000`00000001 fffff880`00000000 00000000`00000000 : nt!RtlRaiseStatus+0x4e fffff880`035fb560 fffff880`01fdc089 : 00000000`00000000 fffffa80`00000001 fffff880`035d3180 fffff880`01fee100 : nt!KeReleaseMutant+0x260 fffff880`035fb610 00000000`00000000 : fffffa80`00000001 fffff880`035d3180 fffff880`01fee100 fffffa80`0797c258 : snapman+0x19089 STACK_COMMAND: kb FOLLOWUP_IP: snapman+19089 fffff880`01fdc089 ?? ??? SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: snapman+19089 FOLLOWUP_NAME: MachineOwner MODULE_NAME: snapman IMAGE_NAME: snapman.sys DEBUG_FLR_IMAGE_TIMESTAMP: 45265d99 FAILURE_BUCKET_ID: X64_0x1E_snapman+19089 BUCKET_ID: X64_0x1E_snapman+19089 Followup: MachineOwner ---------
Renamed, it didnt help
And there is no new minidumps in windows/minidump
Boot stops at classpnp.sys i think.
This is my ntbtlog.txt
Do a Startup Repair