Question

Locked

BSOD 0x8e errors in Vista

By orfjmc ·
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 0xffffffffc727f4a
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_I 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_COMMAN 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_I 0x8E_pacer!PcFilterRequestComplete+64

BUCKET_I 0x8E_pacer!PcFilterRequestComplete+64

Followup: MachineOwner

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

This may help

by Jacky Howe In reply to BSOD 0x8e errors in Vista

I would have suggested sfc /scannow to repair it but unfortunatly you are on a Notebook.

pacer.sys is a part of Windows Vista.
Default location: %WinDir%\System32\drivers\pacer.sys

Useful information about: pacer.sys

Description: QoS Packet Scheduler


Click Start, and then click Control Panel.

In Classic View, click Network and Sharing Center.

Untick the box to disable QoS Packet Scheduler and then click OK.

<i>Keep us informed as to your progress if you require further assistance.</i>

Collapse -

re: thuis may help

by orfjmc In reply to This may help

Thanks for the info. I'll make that change and see if it helps.
I'm not sure the issue is directly related to pacer.sys as I am getting a variety of different messages. Most of them are 0x8e errors but the file the debugger says is causiong the problem is usually different. I am pasting two more of these below. One points to ndis.sys and one points to Win32k.sys. I will say that I have recived several of these messages pointing to win32k.sys.


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


Loading Dump File [C:\Windows\Minidump\Mini020809-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 = 0x81c03000 PsLoadedModuleList = 0x81d1ac70
Debug session time: Sun Feb 8 18:56:28.642 2009 (GMT-5)
System Uptime: 0 days 23:51:34.430
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..
Loading User Symbols
Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 81cb87ac, b611fbac, b611f8a8}

Probably caused by : ndis.sys ( ndis!ndisOidPostMiniportStats+ae )

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

1: kd> !analyze -v
*******************************************************************************
* *
* 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: 81cb87ac, The address that the exception occurred at
Arg3: b611fbac, Exception Record Address
Arg4: b611f8a8, 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!memcpy+12c
81cb87ac 89448ff8 mov dword ptr [edi+ecx*4-8],eax

EXCEPTION_RECOR b611fbac -- (.exr 0xffffffffb611fbac)
ExceptionAddress: 81cb87ac (nt!memcpy+0x0000012c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000000
Attempt to write to address 00000000

CONTEXT: b611f8a8 -- (.cxr 0xffffffffb611f8a
eax=00000000 ebx=b611fce8 ecx=00000002 edx=00000000 esi=85dd4d40 edi=00000000
eip=81cb87ac esp=b611fc74 ebp=b611fc7c 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:
81cb87ac 89448ff8 mov dword ptr [edi+ecx*4-8],eax ds:0023:00000000=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_I NULL_DEREFERENCE

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_PARAMETER1: 00000001

EXCEPTION_PARAMETER2: 00000000

WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d3a868
Unable to read MiSystemVaType memory at 81d1a420
00000000

FOLLOWUP_IP:
ndis!ndisOidPostMiniportStats+ae
88a08f32 83c40c add esp,0Ch

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from 88a08f32 to 81cb87ac

STACK_TEXT:
b611fc7c 88a08f32 00000000 85dd4d40 00000008 nt!memcpy+0x12c
b611fca4 88a02be2 b611fce8 b611fd04 96e477d8 ndis!ndisOidPostMiniportStats+0xae
b611fcd0 88ac1975 b611fce8 96e477d8 88a3a000 ndis!ndisOidRequestComplete+0xcb
b611fd2c 88a07f0b 00e477d8 81d05100 946a1d78 ndis!ndisFDoOidRequest+0x1c3
b611fd44 81c3b41d 846af4e8 00000000 946a1d78 ndis!ndisDoOidRequests+0x5e
b611fd7c 81dd8c72 846af4e8 bdf9d52a 00000000 nt!ExpWorkerThread+0xfd
b611fdc0 81c31a3e 81c3b320 80000000 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: ndis!ndisOidPostMiniportStats+ae

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ndis

IMAGE_NAME: ndis.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 47abba0c

STACK_COMMAN .cxr 0xffffffffb611f8a8 ; kb

FAILURE_BUCKET_I 0x7E_ndis!ndisOidPostMiniportStats+ae

BUCKET_I 0x7E_ndis!ndisOidPostMiniportStats+ae

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

1: kd> lmvm ndis
start end module name
88a00000 88b0b000 ndis (pdb symbols) c:\symbols\ndis.pdb\B8330814861C4BBCB1A651E687FF3DBF2\ndis.pdb
Loaded symbol image file: ndis.sys
Mapped memory image file: c:\symbols\ndis.sys\47ABBA0C10b000\ndis.sys
Image path: ndis.sys
Image name: ndis.sys
Timestamp: Thu Feb 07 21:10:20 2008 (47ABBA0C)
CheckSum: 00082218
ImageSize: 0010B000
File version: 6.0.6001.22110
Product version: 6.0.6001.22110
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.6 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft? Windows? Operating System
InternalName: NDIS.SYS
OriginalFilename: NDIS.SYS
ProductVersion: 6.0.6001.22110
FileVersion: 6.0.6001.22110 (vistasp1_ldr.080207-1500)
FileDescription: NDIS 6.0 wrapper driver
LegalCopyright: ? Microsoft Corporation. All rights reserved.


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


Loading Dump File [C:\Windows\Minidump\Mini020609-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 = 0x81c17000 PsLoadedModuleList = 0x81d2ec70
Debug session time: Fri Feb 6 14:47:10.319 2009 (GMT-5)
System Uptime: 0 days 4:19:39.359
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 81d04886, b99454ac, 0}

Probably caused by : win32k.sys ( win32k!Win32AllocPool+13 )

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: c0000005, The exception code that was not handled
Arg2: 81d04886, The address that the exception occurred at
Arg3: b99454ac, 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!ExAllocatePoolWithTag+4ca
81d04886 895804 mov dword ptr [eax+4],ebx

TRAP_FRAME: b99454ac -- (.trap 0xffffffffb99454ac)
ErrCode = 00000002
eax=00000000 ebx=9ba0122c ecx=90162d38 edx=00000002 esi=9ba00dc0 edi=fd2de398
eip=81d04886 esp=b9945520 ebp=b9945568 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010216
nt!ExAllocatePoolWithTag+0x4ca:
81d04886 895804 mov dword ptr [eax+4],ebx ds:0023:00000004=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_I VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: explorer.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8136347a to 81d04886

STACK_TEXT:
b9945568 8136347a 00000021 00000400 706c6147 nt!ExAllocatePoolWithTag+0x4ca
b994557c 8134abb7 00000400 706c6147 00000400 win32k!Win32AllocPool+0x13
b9945590 81366725 00000400 706c6147 38d1894a win32k!PALLOCMEM+0x18
b99455e8 81365e02 fc9db0a0 00000400 000003a4 win32k!AlphaScanLineBlend+0xf5
b994581c 8133f314 fc9db000 fe488e68 ff39ff68 win32k!EngAlphaBlend+0x329
b9945888 8133f0f2 fc9db010 fe4bc560 fe2fd010 win32k!SURFREFAPI::SURFREFAPI+0x12d
b9945924 8133fdb8 fc9db010 fe4bc560 ff39ff68 win32k!SURFREFAPI::SURFREFAPI+0x3e7
b9945984 8133fece fc9db010 fe4bc560 ff39ff68 win32k!EngNineGrid+0x6e
b99459e0 81340130 fc9db010 fe4bc560 ff39ff68 win32k!EngDrawStream+0x100
b9945a54 8133e9c6 b9945bb4 ff39ff68 fe4bc550 win32k!NtGdiDrawStreamInternal+0x245
b9945be4 8133e423 00010e6a 00000000 ff399a78 win32k!GreDrawStream+0x556
b9945d30 81c6ea0a 00010e6a 00000060 08dae890 win32k!NtGdiDrawStream+0x8c
b9945d30 77229a94 00010e6a 00000060 08dae890 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
08dae80c 00000000 00000000 00000000 00000000 0x77229a94


STACK_COMMAN kb

FOLLOWUP_IP:
win32k!Win32AllocPool+13
8136347a 5d pop ebp

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: win32k!Win32AllocPool+13

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48d1b9ef

FAILURE_BUCKET_I 0x8E_win32k!Win32AllocPool+13

BUCKET_I 0x8E_win32k!Win32AllocPool+13

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

1: kd> lmvm win32k
start end module name
81290000 81492000 win32k (pdb symbols) c:\symbols\win32k.pdb\230B5B2DCF9F4D36AEC89C0F41FE0EAA2\win32k.pdb
Loaded symbol image file: win32k.sys
Mapped memory image file: c:\symbols\win32k.sys\48D1B9EF202000\win32k.sys
Image path: win32k.sys
Image name: win32k.sys
Timestamp: Wed Sep 17 22:16:15 2008 (48D1B9EF)
CheckSum: 001F7B79
ImageSize: 00202000
File version: 6.0.6001.18145
Product version: 6.0.6001.18145
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft? Windows? Operating System
InternalName: win32k.sys
OriginalFilename: win32k.sys
ProductVersion: 6.0.6001.18145
FileVersion: 6.0.6001.18145 (vistasp1_gdr.080917-1612)
FileDescription: Multi-User Win32 Driver
LegalCopyright: ? Microsoft Corporation. All rights reserved.

Collapse -

Try this either way will run it

by Jacky Howe In reply to re: thuis may help

Test Your Computer's Memory Using Windows Vista Memory Diagnostic Tool

Using this tool will require a reboot, so keep that in mind before you launch it.

Type memory into the Run box or press the Windows Key+r, and you should see the first option will say Memory Diagnostics Tool.

A dialog will pop up asking if you want to reboot and check for problems now, or check for problems the next time you restart.

If you choose to restart now, Vista will reboot into the memory diagnostic utility:

You'll have to hold down F8 on startup to get into Safe Mode, press Esc to get to the memory checker page and press TAB and then press Enter.

Collapse -

I'll run the test thanks

by orfjmc In reply to Try this either way will ...

OK. I'll give that a shot. I did run memtest86 and it came up clean.
I'll let you know how it goes. Thanks for the help!

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums