Windows 7 crash

[mannyi]

Hi There guys,

Some of them I was able to fix I think.....yesterday but the one that crash the system today was the fltmgr.sys

Please help

thx in advanced Manny

P.S The OS is W7 32bit

 

[CarlTR6]

Mannyi, please start a new thread in the Crashes and Debugging section. I will look at the dumps for you and ask the moderators to move your post into a new thread for you.

You have a lot of dump files and I looked at the five most recent. You have a hardware or hardware related issue(s) going on. Memory is indicated. Faulty drivers, incompatible software or hardware can corrupt memory. It does not necessarily mean bad RAM; though that is a possibility. Three of the dumps indicated memory corruption.

BugCheck 34 CACHE_MANAGER - Usual causes: Insufficient physical memory, Indexing, Device driver

BugCheck A IRQL_NOT_LESS_OR_EQUAL - Usual causes: Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

BugCheck D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL - Usual causes: Device driver

BugCheck 8E KERNEL_MODE_EXCEPTION_NOT_HANDLED - Usual causes: Insufficient disk space, Device driver, Video card, BIOS, Breakpoint in startup without having a debugger attached, Hardware incompatibility, Faulty system service, 3rd party remote control, Memory

Notice that device driver is mentioned in each of these error codes and memory is mentioned in two of them. That is where we will start troubleshooting.

To begin, please uninstall ESet NOD32 antivirus using this uninstall tool > Info > Tool. Eset was blamed in one of your dumps for causing the crash. It is know to cause BSOD's on some Win 7 systems. For troubleshooting, download and install Microsoft Security Essentials. It will not cause a system crash. After you get your system running stable, you can try Eset again; though I recommend you stick with MSE.

Enable Driver Verifier using the instructions in the link below:

Driver Verifier - Enable and Disable

Driver Verifier will trigger BSOD's when it finds a faulty driver. Hopefully, the dump will point to the offending driver. Upload any new dumps to us - http://www.sevenforums.com/tutorials/83172-dump-files-upload-seven-forums.html

I also found some outdated drivers on your system. Win 7 does not like obsolete drivers. They can and do cause memory corruption and crashes.

AsIO.sys Mon Dec 17 04:10:20 2007
DamewareMini.sys Sun Mar 16 14:41:51 2008
dwvkbd.sys Wed Apr 11 17:23:28 2007
ehdrv.sys Thu Apr 09 09:01:29 2009 -

ESet Smart Security driver system driver file.
epfwwfpr.sys Thu Apr 09 08:42:42 2009 - ESET Personal Firewall driver is a driver file belonging to ESET Smart Security.

Update these drivers. The drivers dated 2007 and 2008 are very obsolete. Uninstalling Eset will take care of the Eset drivers.

How To Find Drivers:
- I have listed links to most of the drivers in the code box below. Please use the links there to see what info I've found about those drivers.
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

- - The most common drivers are listed on this page: Driver Reference
- - Driver manufacturer links are on this page: Drivers and Downloads

If you need help with the drivers, please post.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 34, {50830, 8df6fa80, 8df6f660, 82cdd94b}

Probably caused by : hardware ( nt!CcAcquireByteRangeForWrite+610 )

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

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

CACHE_MANAGER (34)
    See the comment for FAT_FILE_SYSTEM (0x23)
Arguments:
Arg1: 00050830
Arg2: 8df6fa80
Arg3: 8df6f660
Arg4: 82cdd94b

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


EXCEPTION_RECORD:  8df6fa80 -- (.exr 0xffffffff8df6fa80)
ExceptionAddress: 82cdd94b (nt!CcAcquireByteRangeForWrite+0x00000610)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000001
   Parameter[1]: 0b9ad8b3
Attempt to write to address 0b9ad8b3

CONTEXT:  8df6f660 -- (.cxr 0xffffffff8df6f660)
eax=859fb9e0 ebx=86b1c438 ecx=00000001 edx=00001000 esi=8df6fc04 edi=00000000
eip=82cdd94b esp=8df6fb48 ebp=8df6fbd0 iopl=0         nv up ei ng nz na pe cy
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010287
nt!CcAcquireByteRangeForWrite+0x610:
82cdd94b 008b7b14e984    add     byte ptr [ebx-7B16EB85h],cl ds:0023:0b9ad8b3=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  00000001

EXCEPTION_PARAMETER2:  0b9ad8b3

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82da7718
Unable to read MiSystemVaType memory at 82d87160
 0b9ad8b3 

FOLLOWUP_IP: 
nt!CcAcquireByteRangeForWrite+610
82cdd94b 008b7b14e984    add     byte ptr [ebx-7B16EB85h],cl

FAULTING_IP: 
nt!CcAcquireByteRangeForWrite+610
82cdd94b 008b7b14e984    add     byte ptr [ebx-7B16EB85h],cl

BUGCHECK_STR:  0x34

MISALIGNED_IP: 
nt!CcAcquireByteRangeForWrite+610
82cdd94b 008b7b14e984    add     byte ptr [ebx-7B16EB85h],cl

LAST_CONTROL_TRANSFER:  from 82cce94f to 82cdd94b

STACK_TEXT:  
8df6fbd0 82cce94f 86b1c438 00000000 00000000 nt!CcAcquireByteRangeForWrite+0x610
8df6fc70 82cd78a3 86e2dad8 00000000 00000001 nt!CcFlushCache+0x244
8df6fca8 82cdfee6 8df6fcc4 a6cc0d5e 85782528 nt!CcWriteBehind+0x105
8df6fd00 82cacf3b 85782528 00000000 85798d48 nt!CcWorkerThread+0x164
8df6fd50 82e4d6bb 00000000 a6cc0dce 00000000 nt!ExpWorkerThread+0x10d
8df6fd90 82cff0f9 82cace2e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!CcAcquireByteRangeForWrite+610

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  .cxr 0xffffffff8df6f660 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {2efa9a87, 2, 1, 82ccaa01}

*** WARNING: Unable to verify timestamp for tdrpm251.sys
*** ERROR: Module load completed but symbols could not be loaded for tdrpm251.sys
*** WARNING: Unable to verify timestamp for eamon.sys
*** ERROR: Module load completed but symbols could not be loaded for eamon.sys
Probably caused by : hardware ( tdrpm251+9fce )

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

1: 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: 2efa9a87, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, 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: 82ccaa01, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82d7e718
Unable to read MiSystemVaType memory at 82d5e160
 2efa9a87 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiWaitForInPageComplete+6e3
82ccaa01 0888460e0f84    or      byte ptr [eax-7BF0F1BAh],cl

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  9d45f1d4 -- (.trap 0xffffffff9d45f1d4)
ErrCode = 00000002
eax=aaeb8c41 ebx=86eb2cc8 ecx=84a6de68 edx=00000000 esi=84a6de60 edi=00000000
eip=82ccaa01 esp=9d45f248 ebp=9d45f2a0 iopl=0         nv up ei pl nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010202
nt!MiWaitForInPageComplete+0x6e3:
82ccaa01 0888460e0f84    or      byte ptr [eax-7BF0F1BAh],cl ds:0023:2efa9a87=??
Resetting default scope

MISALIGNED_IP: 
nt!MiWaitForInPageComplete+6e3
82ccaa01 0888460e0f84    or      byte ptr [eax-7BF0F1BAh],cl

LAST_CONTROL_TRANSFER:  from 82ccaa01 to 82c5c82b

STACK_TEXT:  
9d45f1d4 82ccaa01 badb0d00 00000000 0000058b nt!KiTrap0E+0x2cf
9d45f2a0 82cc20e5 86eb2d5c 9d45f2f8 82d4a4c0 nt!MiWaitForInPageComplete+0x6e3
9d45f334 82c9de5f 82d4a4c0 d0f88000 86eb2cc8 nt!MiIssueHardFault+0x3b2
9d45f3b8 82c77ea9 00000000 d0f88000 00000000 nt!MmAccessFault+0x2656
9d45f4c4 82ca7c29 d0f88000 00001000 00000000 nt!MmCheckCachedPageStates+0x3f0
9d45f4fc 82ca6caa 00000000 00000001 d0f88000 nt!CcMapAndRead+0xbf
9d45f574 82e6118e 86e9a008 9d45f5b8 00000078 nt!CcPinFileData+0x2dd
9d45f5e8 8bcb958e 86eb4400 00000000 00000078 nt!CcPinRead+0xc6
9d45f610 8bcb1002 88667e28 8cda6d78 02a88000 Ntfs!NtfsPinStream+0xae
9d45f6bc 8bcb55eb 88667e28 00000000 39a88000 Ntfs!NtOfsPutData+0x37c
9d45f738 8bcb235e 88667e28 aaec9808 b043b450 Ntfs!NtfsWriteFcbUsnRecordToJournal+0xb2
9d45f794 8bcb5a01 88667e28 aaec9808 aaec98f8 Ntfs!NtfsWriteUsnJournalChanges+0x1a8
9d45f7a8 8bcbcab4 88667e28 1681428c 00000014 Ntfs!NtfsCheckpointCurrentTransaction+0x1b
9d45f83c 8bcbaefc 88667e28 880c7a00 87bcb888 Ntfs!NtfsSetEndOfFileInfo+0x72b
9d45f8bc 8bc2732b 88667e28 87bcb888 16814398 Ntfs!NtfsCommonSetInformation+0x78d
9d45f928 82c524bc 8699e020 87bcb888 87bcb888 Ntfs!NtfsFsdSetInformation+0x107
9d45f940 8bb7620c 87a281f0 87bcb888 00000000 nt!IofCallDriver+0x63
9d45f964 8bb763cb 9d45f984 87a281f0 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
9d45f99c 82c524bc 87a281f0 87bcb888 8c214600 fltmgr!FltpDispatch+0xc5
9d45f9b4 8c21cfce 8c23db9c 87a281f0 87bcb888 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
9d45fa48 8bb7620c 87cf39b0 87bcb888 00000000 tdrpm251+0x9fce
9d45fa6c 8bb763cb 9d45fa8c 87cf39b0 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2aa
9d45faa4 82c524bc 87cf39b0 87bcb888 87bcbb80 fltmgr!FltpDispatch+0xc5
9d45fabc 92cee087 880c7a00 87c37020 00000000 nt!IofCallDriver+0x63
9d45fad0 82c524bc 87c37020 87bcb888 87c37020 eamon+0x5087
9d45fae8 82e0023b 00000000 87a23030 82040000 nt!IofCallDriver+0x63
9d45fb20 82e9bfbf 9d45fc48 9d45fcdc 87a23030 nt!FsRtlSetFileSize+0x98
9d45fb68 82e397eb 880c7a00 9d45fbb0 00000004 nt!MiCreateDataFileMap+0x81
9d45fc9c 82e46ed1 9d45fcf0 000f0007 00000000 nt!MmCreateSection+0x654
9d45fd10 82c5944a 04f7efcc 000f0007 00000000 nt!NtCreateSection+0x16e
9d45fd10 77a564f4 04f7efcc 000f0007 00000000 nt!KiFastCallEntry+0x12a
04f7efb0 00000000 00000000 00000000 00000000 0x77a564f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tdrpm251+9fce
8c21cfce ??              ???

SYMBOL_STACK_INDEX:  14

SYMBOL_NAME:  tdrpm251+9fce

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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


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


Loading Dump File [C:\Users\Owner\Downloads\A-Rar\081510-32229-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c55000 PsLoadedModuleList = 0x82d9d810
Debug session time: Sat Aug 14 23:21:58.682 2010 (GMT-4)
System Uptime: 1 days 6:53:37.462
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, 2, 8, 0}

Probably caused by : tcpip.sys ( tcpip!IppInspectLocalDatagramsOut+101 )

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

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

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
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 kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000000, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000008, value 0 = read operation, 1 = write operation
Arg4: 00000000, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82dbd718
Unable to read MiSystemVaType memory at 82d9d160
 00000000 

CURRENT_IRQL:  2

FAULTING_IP: 
+5b79952f00dfdf74
00000000 ??              ???

PROCESS_NAME:  ekrn.exe

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

TRAP_FRAME:  b4b23830 -- (.trap 0xffffffffb4b23830)
ErrCode = 00000010
eax=8651d500 ebx=00000000 ecx=0000fffd edx=00001001 esi=00000001 edi=86e8e848
eip=00000000 esp=b4b238a4 ebp=b4b238f4 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
00000000 ??              ???
Resetting default scope

LAST_CONTROL_TRANSFER:  from 00000000 to 82c9b82b

FAILED_INSTRUCTION_ADDRESS: 
+5b79952f00dfdf74
00000000 ??              ???

STACK_TEXT:  
b4b23830 00000000 badb0d00 00001001 b4b2379c nt!KiTrap0E+0x2cf
WARNING: Frame IP not in any known module. Following frames may be wrong.
b4b238a0 86e8e848 00000da1 00000000 00000000 0x0
b4b238f4 8c09c9c7 00000006 00000002 00003bc5 0x86e8e848
b4b2395c 8c0a3304 00000000 865770a4 8651d5f0 tcpip!IppInspectLocalDatagramsOut+0x101
b4b23a24 8c0a3635 00000000 00000007 8c115d98 tcpip!IppSendDatagramsCommon+0x5a8
b4b23a44 8c0833a8 86511740 b4b23a5c b4b23bc4 tcpip!IpNlpSendDatagrams+0x4b
b4b23ad0 8c083339 86511740 b4b23bc4 87e150b8 tcpip!IppSlowSendDatagram+0x31
b4b23b30 8c0866c4 86511740 00000001 b4b23bc4 tcpip!IpNlpFastSendDatagram+0xefd
b4b23c80 8c08a555 859b8700 00000000 00000003 tcpip!TcpTcbSend+0x78b
b4b23ca0 8c0883e9 859b8700 86f45458 00000000 tcpip!TcpEnqueueTcbSendOlmNotifySendComplete+0x157
b4b23d00 8c08a8e6 859b8700 9f267170 00000000 tcpip!TcpEnqueueTcbSend+0x3ca
b4b23d1c 82cc511e 9f267144 00000000 ffffffff tcpip!TcpTlConnectionSendCalloutRoutine+0x17
b4b23d1c 82cc5215 9f267144 00000000 ffffffff nt!KiSwapKernelStackAndExit+0x15a
9f2670a8 00000000 00000000 00000000 00000000 nt!KiSwitchKernelStackAndCallout+0x31


STACK_COMMAND:  kb

FOLLOWUP_IP: 
tcpip!IppInspectLocalDatagramsOut+101
8c09c9c7 50              push    eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  tcpip!IppInspectLocalDatagramsOut+101

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c15a3db

FAILURE_BUCKET_ID:  0xD1_CODE_AV_NULL_IP_tcpip!IppInspectLocalDatagramsOut+101

BUCKET_ID:  0xD1_CODE_AV_NULL_IP_tcpip!IppInspectLocalDatagramsOut+101

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

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 82eba989, a806faec, 0}

Probably caused by : hardware ( nt!AlpcpDispatchNewMessage+177 )

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

2: 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: 82eba989, The address that the exception occurred at
Arg3: a806faec, 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!AlpcpDispatchNewMessage+177
82eba989 868e0000008b    xchg    cl,byte ptr [esi-75000000h]

TRAP_FRAME:  a806faec -- (.trap 0xffffffffa806faec)
ErrCode = 00000002
eax=858f4ae0 ebx=87213658 ecx=85bd2d04 edx=85bd2c40 esi=a806fc37 edi=d8b3b998
eip=82eba989 esp=a806fb60 ebp=a806fb88 iopl=0         nv up ei pl nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010206
nt!AlpcpDispatchNewMessage+0x177:
82eba989 868e0000008b    xchg    cl,byte ptr [esi-75000000h] ds:0023:3306fc37=??
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  SearchIndexer.

CURRENT_IRQL:  0

MISALIGNED_IP: 
nt!AlpcpDispatchNewMessage+177
82eba989 868e0000008b    xchg    cl,byte ptr [esi-75000000h]

LAST_CONTROL_TRANSFER:  from 82e90e7b to 82eba989

STACK_TEXT:  
a806fb88 82e90e7b 8339b7f1 87213658 87213658 nt!AlpcpDispatchNewMessage+0x177
a806fc10 82eb0ccc a806fc38 02aa1730 02a5ecd4 nt!AlpcpSendMessage+0x653
a806fca0 82eba203 87213658 00020000 02aa1730 nt!AlpcpProcessSynchronousRequest+0x243
a806fd0c 82c8844a 00000fd4 00020000 02aa1730 nt!NtAlpcSendWaitReceivePort+0xd0
a806fd0c 776a64f4 00000fd4 00020000 02aa1730 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
04dff0c4 00000000 00000000 00000000 00000000 0x776a64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!AlpcpDispatchNewMessage+177
82eba989 868e0000008b    xchg    cl,byte ptr [esi-75000000h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!AlpcpDispatchNewMessage+177

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: hardware

FAILURE_BUCKET_ID:  IP_MISALIGNED

BUCKET_ID:  IP_MISALIGNED

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

 

[mannyi]

WOW Thank you for you help seems like I have a lot of work to do,
I did talk to eset support and did and update, since the PC is part of a network there for I can't install the MSE, as for the driver I'll try to update all of them and then see what happaned.

Thx

Manny

 

[CarlTR6]

You are very welcome. Troubleshooting hardware problems is often laborious and a process of elimination. Perhaps simply updating the obsolete drivers will solve your problem.

Maybe the updated Eset driver will work for you. Generally speaking, third party firewalls cause trouble with Win 7. My suggestion would be to uninstall Eset and turn on Windows firewall while you are troubleshooting. However, you can certainly try running with the new driver.

Good luck and keep us updated.