bug check 1001 windows 7 32bit helppp

sad now i have to even remove avast

guys u better teach me how to open a crash dump file. m again and again sorry to disturb u guys. again got 2 ****ing eroors check em out plzzz i did as u said but why the hell is it coming again and again

****ing i again got a bsod when i was about to run the memtest i get it on startup after 2-3 minutes and i have learned to open crash dump file here check this


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


Loading Dump File [C:\Windows\Minidump\062911-15943-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 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82a52000 PsLoadedModuleList = 0x82b9a810
Debug session time: Wed Jun 29 14:36:54.844 2011 (UTC + 5:30)
System Uptime: 0 days 0:01:00.374
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c000001d, 82c90021, a253c9fc, 0}

Probably caused by : ntkrpamp.exe ( nt!ExpAllocateHandleTableEntry+70 )

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

1: 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: c000001d, The exception code that was not handled
Arg2: 82c90021, The address that the exception occurred at
Arg3: a253c9fc, Trap Frame
Arg4: 00000000

Debugging Details:
------------------


EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

FAULTING_IP:
nt!ExpAllocateHandleTableEntry+70
82c90021 f00fc102 lock xadd dword ptr [edx],eax

TRAP_FRAME: a253c9fc -- (.trap 0xffffffffa253c9fc)
ErrCode = 00000000
eax=ffffffff ebx=000009b0 ecx=40000000 edx=40000000 esi=a1eda420 edi=877c41b0
eip=82c90021 esp=a253ca70 ebp=a253ca80 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
nt!ExpAllocateHandleTableEntry+0x70:
82c90021 f00fc102 lock xadd dword ptr [edx],eax ds:0023:40000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: SearchIndexer.

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 82c8ec30 to 82c90021

FAILED_INSTRUCTION_ADDRESS:
nt!ExpAllocateHandleTableEntry+70
82c90021 f00fc102 lock xadd dword ptr [edx],eax

STACK_TEXT:
a253ca80 82c8ec30 a253caa0 a253cae8 a2efd510 nt!ExpAllocateHandleTableEntry+0x70
a253ca98 82c74935 00000000 a253cae8 00000000 nt!ExCreateHandle+0x1a
a253caf0 82cccfde 00000001 a2efd528 00000000 nt!ObpCreateHandle+0x2a8
a253cc70 82ccd043 a2efd528 00000000 00000000 nt!ObOpenObjectByPointerWithTag+0xc1
a253cc98 82c8e0f2 a2efd528 00000000 00000000 nt!ObOpenObjectByPointer+0x24
a253cd04 82c8e907 ffffffff 00000008 00000000 nt!NtOpenProcessTokenEx+0xb4
a253cd20 82a9542a ffffffff 00000008 0084f2e8 nt!NtOpenProcessToken+0x16
a253cd20 776b64f4 ffffffff 00000008 0084f2e8 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0084f2c4 00000000 00000000 00000000 00000000 0x776b64f4


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!ExpAllocateHandleTableEntry+70
82c90021 f00fc102 lock xadd dword ptr [edx],eax

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!ExpAllocateHandleTableEntry+70

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc007

FAILURE_BUCKET_ID: 0x8E_BAD_IP_nt!ExpAllocateHandleTableEntry+70

BUCKET_ID: 0x8E_BAD_IP_nt!ExpAllocateHandleTableEntry+70

Followup: MachineOwner
---------
i m also uploading the mini dump file check it and help me if i need to replace anything say me i'll return it to ****ing vendor m just fed up of this shit

m srry to disturb u guys again and again

i think my motherboard is ****ed up