[问题求助] 请问这个蓝屏是不是世界之窗的BUG啊 还是... 谁帮我分析一下！ BUG, 蓝屏, 世界

苑志国

蓝屏内容是：

a problem has been detected and windows has been shut down to prevent damage to your computer  
if this is the first time you've seen this stoperror screen.restart your computer .if this screen appears again,follow these steps.  

cheak to be sure you have adequate disk space.if a driver is identified in the stop message.disable the driver or check with the manufacturer for driver updates.try changing video adapters  

check with your havdwaare vendor for any bios updates.disable bios memory options such as caching or shadowing.if you need to use safe mode to remove or disable components .restart your computer.press f8 to select advanced startup options,and then select safe mode.  

technical information :  

*** stop:0×0000008e(0×C0000005 0×8061508C 0×B15431CC 0×00000000)

beginning dump of physical memory
physical memory dump complete
Contact your system administrator or technice support group for further assistanc

苑志国

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

Loading Dump File [C:\WINDOWS\Minidump\Mini040210-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.090804-1435
Machine Name:
Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055e720
Debug session time: Fri Apr  2 11:32:46.375 2010 (UTC + 8:00)
System Uptime: 0 days 3:15:44.986
Loading Kernel Symbols
...............................................................
................................................................

Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 8061508c, b15431cc, 0}

Probably caused by : win32k.sys ( win32k!OffBitBlt+1e )

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

4: 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: 8061508c, The address that the exception occurred at
Arg3: b15431cc, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - "0x%08lx"

FAULTING_IP:
nt!ExRaiseAccessViolation+a
8061508c c3              ret

TRAP_FRAME:  b15431cc -- (.trap 0xffffffffb15431cc)
ESP EDITED! New esp=b154357c
ErrCode = 00000000
eax=b154367f ebx=bf9a660c ecx=b15436cc edx=00000000 esi=00000000 edi=00000000
eip=8061508c esp=b1543240 ebp=b154358c iopl=0         ov up ei pl nz na po nc
cs=0000  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00000a02
nt!ExRaiseAccessViolation+0xa:
8061508c c3              ret
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  TheWorld.exe

LAST_CONTROL_TRANSFER:  from 80616ac3 to 8061508c

STACK_TEXT:  
b154357c 80616ac3 b15436cc b15436cc b15435c4 nt!ExRaiseAccessViolation+0xa
b154358c bf8a5b05 00000000 b1543678 b1543670 nt!ProbeForWrite+0x4d
b15435c4 bf8a59c9 bf803313 b1543680 e61a6e90 win32k!OffBitBlt+0x1e
b154368c bf8438e8 e61a6e90 e4883bb0 e5dcde90 win32k!SpBitBlt+0x1e9
b15437dc bf8687ef b15438c4 e5f1cbc0 00000000 win32k!BLTRECORD::bBitBlt+0x725
b15438f8 8054262c 2001185f 00000240 00000073 win32k!GreMaskBlt+0x71c
b15438f8 7c92e514 2001185f 00000240 00000073 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
3540acb8 00000000 00000000 00000000 00000000 0x7c92e514


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k!OffBitBlt+1e
bf8a5b05 8b4528          mov     eax,dword ptr [ebp+28h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  win32k!OffBitBlt+1e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a8564c7

FAILURE_BUCKET_ID:  0x8E_win32k!OffBitBlt+1e

BUCKET_ID:  0x8E_win32k!OffBitBlt+1e

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

苑志国

前段时间发生过0000000A的蓝屏  因为没打开虚拟内存  所以没有记录  大家帮我看看是驱动问题还是内存问题啊？


两次用世界之窗阅览  开着迅雷蓝屏   一次是玩魔兽争霸3之人族无敌 蓝屏   以前经常遇到过  NV4_disp.dll  蓝屏