New
#21
Problem Devices:Please remove any CD/DVD virtualization software, such as Daemon Tools/Alcohol 120%, as they use a driver called sptd.sys that is known to cause BSODs. Use add/remove programs to remove the software. After removing the software, use the sptd.sys uninstaller to remove sptd.sys from the system.Code:sptd ROOT\LEGACY_SPTD\0000 This device is not present, is not working properly, or does not have all its drivers installed.
I prefer TotalMounter as my CD/DVD virtualization software as it allows me to burn images to a virtual CD/DVD if I just want an ISO file instead of a disc, and it is free.
Many use MagicISO - Convert BIN to ISO, Create, Edit, Burn, Extract ISO file, ISO/BIN converter/extractor/editor as well, which is also free.
Appears to be related to avast! which has been common of late... Not sure if it is due to an issue with avast! itself, or if it is conflicting with certain systems, or maybe an update caused it to be corrupted. Try installing the latest version of avast! after uninstalling it using the avast! Uninstall Utility | Download aswClear for avast! RemovalCode:Loading Dump File [D:\Kingston\BSODDmpFiles\Neophile\Windows_NT6_BSOD_jcgriff2\042112-21543-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505 Machine Name: Kernel base = 0xfffff800`0384b000 PsLoadedModuleList = 0xfffff800`03a8f650 Debug session time: Sat Apr 21 01:12:15.419 2012 (UTC - 6:00) System Uptime: 0 days 0:09:17.839 Loading Kernel Symbols ............................................................... ................................................................ .......................................................... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {0, 2, 0, fffff800038cc415} Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2 *** WARNING: Unable to verify timestamp for aswSP.SYS *** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS Probably caused by : aswSP.SYS ( aswSP+5ff1 ) Followup: MachineOwner --------- 2: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 0000000000000000, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, bitfield : bit 0 : value 0 = read operation, 1 = write operation bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status) Arg4: fffff800038cc415, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003af9100 0000000000000000 CURRENT_IRQL: 2 FAULTING_IP: nt!KeSetEvent+1e3 fffff800`038cc415 488b00 mov rax,qword ptr [rax] CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xA PROCESS_NAME: System TRAP_FRAME: fffff880030cb840 -- (.trap 0xfffff880030cb840) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=fffff88006c3e4e0 rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff800038cc415 rsp=fffff880030cb9d0 rbp=0000000000000002 r8=0000000000000000 r9=0000000000000000 r10=0000000000000000 r11=fffffa8003760560 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe cy nt!KeSetEvent+0x1e3: fffff800`038cc415 488b00 mov rax,qword ptr [rax] ds:00000000`00000000=???????????????? Resetting default scope LAST_CONTROL_TRANSFER: from fffff800038c7229 to fffff800038c7c80 STACK_TEXT: fffff880`030cb6f8 fffff800`038c7229 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx fffff880`030cb700 fffff800`038c5ea0 : 00000000`00000202 fffff800`038e6a43 fffffa80`000000ff fffff880`06c3e4d8 : nt!KiBugCheckDispatch+0x69 fffff880`030cb840 fffff800`038cc415 : 00000000`00000000 00000000`00000000 00000000`00000014 00000000`00000000 : nt!KiPageFault+0x260 fffff880`030cb9d0 fffff880`0453aff1 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSetEvent+0x1e3 fffff880`030cba40 fffffa80`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`03f011b0 : aswSP+0x5ff1 fffff880`030cba48 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`03f011b0 fffff800`038cb6c1 : 0xfffffa80`00000000 STACK_COMMAND: kb FOLLOWUP_IP: aswSP+5ff1 fffff880`0453aff1 ?? ??? SYMBOL_STACK_INDEX: 4 SYMBOL_NAME: aswSP+5ff1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: aswSP IMAGE_NAME: aswSP.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4d65203e FAILURE_BUCKET_ID: X64_0xA_aswSP+5ff1 BUCKET_ID: X64_0xA_aswSP+5ff1 Followup: MachineOwner ---------