I just got a Lenovo W500 with Vista Business and I have been getting some BSOD’s for the past few weeks. Most of these are 8e errors, although a few have been as follows:”The bugcheck was: 0x0000007e (0xc0000005, 0x81cc87ac, 0x91590bac, 0x915908a8)”.
I have run all the Windows updates and the Lenovo System updates to update all the drivers but I’m still getting at least one a day. I have collected the minidumps but I need some help interpretting them. Can someone assist? Here is the text from the latest.
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\Mini020909-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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.22269.x86fre.vistasp1_ldr.080917-1612
Machine Name:
Kernel base = 0x81c0e000 PsLoadedModuleList = 0x81d25c70
Debug session time: Mon Feb 9 11:02:55.529 2009 (GMT-5)
System Uptime: 0 days 2:21:49.249
Loading Kernel Symbols
………………………………………………………
……………………………………………………….
……………………………………………………….
………
Loading User Symbols
Loading unloaded module list
……….
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 81cc37ac, c727f4a8, 0}
Probably caused by : pacer.sys ( pacer!PcFilterRequestComplete+64 )
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: 81cc37ac, The address that the exception occurred at
Arg3: c727f4a8, 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!memcpy+12c
81cc37ac 89448ff8 mov dword ptr [edi+ecx*4-8],eax
TRAP_FRAME: c727f4a8 — (.trap 0xffffffffc727f4a8)
ErrCode = 00000002
eax=00000000 ebx=c727f590 ecx=00000002 edx=00000000 esi=84713cf8 edi=00000000
eip=81cc37ac esp=c727f51c ebp=c727f524 iopl=0 nv up ei ng nz ac pe cy
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010297
nt!memcpy+0x12c:
81cc37ac 89448ff8 mov dword ptr [edi+ecx*4-8],eax ds:0023:00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: OUTLOOK.EXE
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 88a16f32 to 81cc37ac
STACK_TEXT:
c727f524 88a16f32 00000000 84713cf8 00000008 nt!memcpy+0x12c
c727f54c 88a10be2 c727f590 c727f5ac 99091c10 ndis!ndisOidPostMiniportStats+0xae
c727f578 88a101bf c727f590 968c2090 99046920 ndis!ndisOidRequestComplete+0xcb
c727f5ac 90aee9b8 99091c10 c727f8d0 00000000 ndis!NdisFOidRequestComplete+0x6c
c727f5cc 88a10eaf 990466f8 c727f8d0 00000000 pacer!PcFilterRequestComplete+0x64
c727f600 88acf750 0027f614 86bff0e8 968c2090 ndis!ndisOidRequestComplete+0x398
c727f634 88acf224 86bff0e8 018c2090 00000011 ndis!ndisPreProcessOid+0x115
c727f684 88a0ff33 00bff0e8 99091c10 00000004 ndis!ndisMDoOidRequest+0x1a3
c727f6b0 88a10101 00000000 968c2090 968c2110 ndis!ndisFQueueRequestOnNext+0x22e
c727f718 90aee918 99091c10 968c2090 81fcaec0 ndis!NdisFOidRequest+0x13c
c727f738 88acf94b 990466f8 c727f8d0 99091c10 pacer!PcFilterRequest+0x80
c727f798 88a10633 00091c10 00001388 c727f8d0 ndis!ndisFDoOidRequest+0x199
c727f7d0 88ae41a5 86bff0e8 c727f8d0 99091c10 ndis!ndisQueueRequestOnTop+0x24e
c727f7f0 88a14b49 00000000 00000000 0027f8d0 ndis!ndisQuerySetMiniport+0x189
c727f960 88a12cfc 86bff0e8 860e227c 99091c10 ndis!ndisIfGetMiniportStatistics+0x1f6
c727fa2c 88a157a2 99091c10 00020106 c727fa54 ndis!ndisIfQueryObject+0x8bf
c727fa6c 88a14006 857f9ab0 9904fab0 c727fa8c ndis!ndisNsiGetInterfaceRodInformation+0x4db
c727fac8 88b49074 0027fb14 00000022 860e2000 ndis!ndisNsiGetAllInterfaceInformation+0x2bf
c727fb7c 90bce063 860e2000 579ae0eb 0000003c NETIO!NsiEnumerateObjectsAllParametersEx+0x4eb
c727fbf0 90bceea8 860e203c 00000000 860e2054 nsiproxy!NsippEnumerateObjectsAllParameters+0xeb
c727fc14 90bcef91 8618bd01 00000000 85f801c0 nsiproxy!NsippDispatchDeviceControl+0x78
c727fc2c 81cc9fb3 990b7330 8618bd58 8618bd58 nsiproxy!NsippDispatch+0x33
c727fc44 81e5a795 85f801c0 8618bd58 8618bdc8 nt!IofCallDriver+0x63
c727fc64 81e5af3a 990b7330 85f801c0 231bfd00 nt!IopSynchronousServiceTail+0x1d9
c727fd00 81e44c0d 990b7330 8618bd58 00000000 nt!IopXxxControlFile+0x6b7
c727fd34 81c65a0a 000003f0 00001dec 00000000 nt!NtDeviceIoControlFile+0x2a
c727fd34 77029a94 000003f0 00001dec 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
231bfd00 00000000 00000000 00000000 00000000 0x77029a94
STACK_COMMAND: kb
FOLLOWUP_IP:
pacer!PcFilterRequestComplete+64
90aee9b8 53 push ebx
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: pacer!PcFilterRequestComplete+64
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: pacer
IMAGE_NAME: pacer.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 47f6d426
FAILURE_BUCKET_ID: 0x8E_pacer!PcFilterRequestComplete+64
BUCKET_ID: 0x8E_pacer!PcFilterRequestComplete+64
Followup: MachineOwner
