BSOD error 0x0000008e on startup

Welcome to the forum LarryB,

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\mini dump\061014-39421-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.x86fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0x82c54000 PsLoadedModuleList = 0x82d9d5b0
Debug session time: Wed Jun 11 02:16:20.475 2014 (UTC + 6:00)
System Uptime: 0 days 0:01:43.395
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\avgidsdriverx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for avgidsdriverx.sys
*** ERROR: Module load completed but symbols could not be loaded for avgidsdriverx.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 9094cdce, 9e962b3f, 0}

Probably caused by : hardware ( avgidsdriverx+19dce )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 9094cdce, The address that the exception occurred at
Arg3: 9e962b3f, 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: 
avgidsdriverx+19dce
9094cdce 0000            add     byte ptr [eax],al

TRAP_FRAME:  9e962b3f -- (.trap 0xffffffff9e962b3f)
ErrCode = 00000002
eax=00000042 ebx=82cd6f9f ecx=00000040 edx=9e96b8d0 esi=00000000 edi=9e96ba58
eip=9094cdce esp=9e962bb3 ebp=9e96b8b8 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
avgidsdriverx+0x19dce:
9094cdce 0000            add     byte ptr [eax],al          ds:0023:00000042=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  explorer.exe

CURRENT_IRQL:  0

MISALIGNED_IP: 
avgidsdriverx+19dce
9094cdce 0000            add     byte ptr [eax],al

UNALIGNED_STACK_POINTER:  9e962bb3

LAST_CONTROL_TRANSFER:  from 00000000 to 9094cdce

STACK_TEXT:  
9e96b8b8 00000000 0000001a 00000000 82cd6f9f avgidsdriverx+0x19dce


STACK_COMMAND:  kb

FOLLOWUP_IP: 
avgidsdriverx+19dce
9094cdce 0000            add     byte ptr [eax],al

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  avgidsdriverx+19dce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  IP_MISALIGNED_avgidsdriverx.sys

BUCKET_ID:  IP_MISALIGNED_avgidsdriverx.sys

Followup: MachineOwner
---------

Looks like the BSOD's were caused by AVG. Uninstall it and replace with Microsoft Security Essentials.

Recommended antivirus software for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials Download | Free Spyware Protection
• Malwarebytes - The Free version
• Good & Free Security Combination

   Warning

Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

Scan with Kaspersky TDSSKiller:

• Anti-rootkit utility TDSSKiller

ESET online scanner:

• Free Online Virus Scanner | ESET

Reduce items at start-up:

• How to Change, Add, or Remove Startup Programs in Windows 7

Perform a clean boot:

• How to Troubleshoot a Problem by Performing a Clean Startup in Windows 7 or Vista

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• How to Repair Windows 7 System Files with System File Checker

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• How to Run Disk Check in Windows 7

Check for heating issues using Speccy or HWmonitor

Upload a screen shot:

• Screenshots and Files - Upload and Post in Seven Forums

If this does not provide stability, test RAM.

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.

Post back results.

Good luck :)