Is Windows 7 . . .
- x86 (32-bit) or x64 ?
32 bit
- the original installed OS on the system?
Yes
- an OEM or full retail version?
OEM
- What is the age of system (hardware)?
Around 1 year
- What is the age of OS installation (have you re-installed the OS?)
Around 1 year
My pc goes in to bsod out of no where, i already uninstalled daemon tools but it still goes into bsod. earlier it went to bsod 2 times straight, please help!
Your Avast Antivirus is the cause, please remove it and use MSE instead
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000008E, {c0000005, 82e86fd0, 8ab1b584, 0} *** WARNING: Unable to verify timestamp for aswSnx.SYS *** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS *** WARNING: Unable to verify timestamp for aswSP.SYS *** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS Probably caused by : aswSnx.SYS ( aswSnx+155f0 ) KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 82e86fd0, The address that the exception occurred at Arg3: 8ab1b584, Trap Frame Arg4: 00000000 Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!ExpAllocateHandleTableEntry+1f 82e86fd0 f00fba2800 lock bts dword ptr [eax],0 TRAP_FRAME: 8ab1b584 -- (.trap 0xffffffff8ab1b584) ErrCode = 00000002 eax=0000000c ebx=00000000 ecx=0000000c edx=000f001f esi=00000000 edi=85081a70 eip=82e86fd0 esp=8ab1b5f8 ebp=8ab1b608 iopl=0 nv up ei ng nz ac pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010296 nt!ExpAllocateHandleTableEntry+0x1f: 82e86fd0 f00fba2800 lock bts dword ptr [eax],0 ds:0023:0000000c=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0x8E PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 82e85c30 to 82e86fd0 STACK_TEXT: 8ab1b608 82e85c30 8ab1b628 8ab1b670 aab4f298 nt!ExpAllocateHandleTableEntry+0x1f 8ab1b620 82e6b935 00000000 8ab1b670 00000000 nt!ExCreateHandle+0x1a 8ab1b678 82e6bd37 00000000 aab4f2b0 000f001f nt!ObpCreateHandle+0x2a8 8ab1b820 82e6bc56 00000000 000f001f 00000000 nt!ObInsertObjectEx+0xd8 8ab1b83c 82e79ec2 aab4f2b0 00000000 000f001f nt!ObInsertObject+0x1e 8ab1b8a8 8d2255f0 8ab1bc98 000f001f 00000000 nt!NtCreateSection+0x1df WARNING: Stack unwind information not available. Following frames may be wrong. 8ab1bb24 8d2258f7 000f001f 00000000 00000013 aswSnx+0x155f0 8ab1bb54 8e2c6855 8ab1bc98 000f001f 00000000 aswSnx+0x158f7 8ab1bb84 82c8c42a 8ab1bc98 000f001f 00000000 aswSP+0x1f855 8ab1bb84 82c8a035 8ab1bc98 000f001f 00000000 nt!KiFastCallEntry+0x12a 8ab1bd00 82cb6f2b 80035e2c 00000000 85081a70 nt!ZwCreateSection+0x11 8ab1bd50 82e5766d 00000001 ac32f665 00000000 nt!ExpWorkerThread+0x10d 8ab1bd90 82d090d9 82cb6e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 STACK_COMMAND: kb FOLLOWUP_IP: aswSnx+155f0 8d2255f0 ?? ??? SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: aswSnx+155f0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: aswSnx IMAGE_NAME: aswSnx.SYS DEBUG_FLR_IMAGE_TIMESTAMP: 4dc929a9 FAILURE_BUCKET_ID: 0x8E_aswSnx+155f0 BUCKET_ID: 0x8E_aswSnx+155f0 Followup: MachineOwner ---------
Post in this thread itself, no need to create another one
No probable cause is indicated, run a scan of Malwarebytes
Enable Driver Verifier then upload the new dumps which are created
Driver Verifier - Enable and Disable
Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e) 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. Some common problems are exception code 0x80000003. This means a hard coded breakpoint or assertion was hit, but this system was booted /NODEBUG. This is not supposed to happen as developers should never have hardcoded breakpoints in retail code, but ... If this happens, make sure a debugger gets connected, and the system is booted /DEBUG. This will let us see why this breakpoint is happening. Arguments: Arg1: c0000005, The exception code that was not handled Arg2: 82d012e1, The address that the exception occurred at Arg3: 8ab23b50, Exception Record Address Arg4: 8ab23730, Context Record Address Debugging Details: ------------------ EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. FAULTING_IP: nt!RtlImageNtHeaderEx+4a 82d012e1 663902 cmp word ptr [edx],ax EXCEPTION_RECORD: 8ab23b50 -- (.exr 0xffffffff8ab23b50) ExceptionAddress: 82d012e1 (nt!RtlImageNtHeaderEx+0x0000004a) ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 00000000 Parameter[1]: 7ffa0000 Attempt to read from address 7ffa0000 CONTEXT: 8ab23730 -- (.cxr 0xffffffff8ab23730) eax=00005a4d ebx=8551fbec ecx=00000000 edx=7ffa0000 esi=00000000 edi=8ab23c2c eip=82d012e1 esp=8ab23c18 ebp=8ab23c18 iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 nt!RtlImageNtHeaderEx+0x4a: 82d012e1 663902 cmp word ptr [edx],ax ds:0023:7ffa0000=???? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: chrome.exe CURRENT_IRQL: 0 ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s. EXCEPTION_PARAMETER1: 00000000 EXCEPTION_PARAMETER2: 7ffa0000 READ_ADDRESS: GetPointerFromAddress: unable to read from 82dae718 Unable to read MiSystemVaType memory at 82d8e160 7ffa0000 FOLLOWUP_IP: nt!RtlImageNtHeaderEx+4a 82d012e1 663902 cmp word ptr [edx],ax BUGCHECK_STR: 0x7E LAST_CONTROL_TRANSFER: from 82d05384 to 82d012e1 STACK_TEXT: 8ab23c18 82d05384 00000000 00000000 8551fbb8 nt!RtlImageNtHeaderEx+0x4a 8ab23c50 82c8787d 00000000 8ab23cc8 00000018 nt!RtlImageNtHeader+0x1a 8ab23d00 82cb3f2b 80005554 00000000 8509b4c0 nt!ZwOpenProcess+0x11 8ab23d50 82e5466d 00000001 ac2a083a 00000000 nt!ExpWorkerThread+0x10d 8ab23d90 82d060d9 82cb3e1e 00000001 00000000 nt!PspSystemThreadStartup+0x9e 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: nt!RtlImageNtHeaderEx+4a FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrpamp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007 STACK_COMMAND: .cxr 0xffffffff8ab23730 ; kb FAILURE_BUCKET_ID: 0x7E_nt!RtlImageNtHeaderEx+4a BUCKET_ID: 0x7E_nt!RtlImageNtHeaderEx+4a Followup: MachineOwner ---------
These were caused by a memory exception caused by your ataport.sys driver. Please run a system file check to verify and repair it.
If the problem still exists please update to service pack 1.
Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW
Read here for more information SFC /SCANNOW Command - System File Checker
Let us know the results from the report at the end.
Quote