É a falha do meu IRQL_NOT_LESS_OR_EQUAL Bugcheck do Firefox ou falha do Flash Player?

2

Espero que este seja o lugar certo para postar isso. Parece que sempre que vejo vídeos online no Firefox, recebo um BSOD. É um IRQL_NOT_LESS_OR_EQUAL BSOD. Eu corri windbg para analisar por minidump no modo detalhado e é isso que me deu.

As linhas em que estou preocupado são:

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

Parece que o Bugcheck foi iniciado pelo Firefox. Mas o site usa o Flash para mostrar o vídeo. É culpa do Firefox ou Flash? Ou poderia ser uma memória defeituosa? No rastreamento de pilha, parece haver algumas chamadas de função relacionadas a gráficos, como NtGdiCreateCompatibleBitmap . Isso significa alguma coisa? Muito obrigado pela sua ajuda.

E esse é o resultado inteiro de windbg :

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


{blah, blah, blah, loading symbols, etc.}
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
..........
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {805d7000, 0, 1, 82c8bd8e}

Probably caused by : win32k.sys ( win32k!PALLOCMEM+29 )

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*                                                                             *
*                        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: 805d7000, memory referenced
Arg2: 00000000, 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: 82c8bd8e, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from 82db6718
Unable to read MiSystemVaType memory at 82d96160
 805d7000 

CURRENT_IRQL:  0

FAULTING_IP: 
nt!KiXMMIZeroPagesNoSave+6
82c8bd8e 0f2b01          movntps xmmword ptr [ecx],xmm0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

TRAP_FRAME:  c8223b1c -- (.trap 0xffffffffc8223b1c)
ErrCode = 00000002
eax=00000000 ebx=001fdac8 ecx=000096b2 edx=00000000 esi=fb402000 edi=fb5da000
eip=82c8ce85 esp=c8223b90 ebp=c8223ba8 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!memset+0x45:
82c8ce85 f3ab            rep stos dword ptr es:[edi]
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82c8bd8e to 82c9482b

STACK_TEXT:  
c8223908 82c8bd8e badb0d00 00000040 c8223928 nt!KiTrap0E+0x2cf
c82239a0 82d00ca3 00000000 d4e10c80 00000002 nt!KiXMMIZeroPagesNoSave+0x6
c82239b8 82cdc92c 00000000 fb5da000 c07daed0 nt!MiZeroPhysicalPage+0xa4
c82239f8 82cde999 00000001 fb5da000 c8223b1c nt!MiResolveDemandZeroFault+0x158
c8223a78 82cd4d76 fb5da000 00000000 8e6a2d70 nt!MiDispatchFault+0x659
c8223b04 82c94638 00000001 fb5da000 00000000 nt!MmAccessFault+0x157c
c8223b04 82c8ce85 00000001 fb5da000 00000000 nt!KiTrap0E+0xdc
c8223b90 9c659d18 fb402000 00000000 001fdac8 nt!memset+0x45
c8223ba8 9c66dbae 001fdac8 35316847 c8223c58 win32k!PALLOCMEM+0x29
c8223bc4 9c6830bf 001fdac8 00000005 00000001 win32k!AllocateObject+0x98
c8223c24 9c657b57 00000f04 00000000 00000000 win32k!SURFMEM::bCreateDIB+0x261
c8223c90 9c657661 00000000 00000006 01080030 win32k!hsurfCreateCompatibleSurface+0x2a8
c8223d0c 9c6576f3 ffb92748 000003c1 0000021f win32k!GreCreateCompatibleBitmap+0x1cd
c8223d20 82c9144a 24012070 000003c1 0000021f win32k!NtGdiCreateCompatibleBitmap+0x19
c8223d20 776f64f4 24012070 000003c1 0000021f nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0031edbc 00000000 00000000 00000000 00000000 0x776f64f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!PALLOCMEM+29
9c659d18 83c40c          add     esp,0Ch

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  win32k!PALLOCMEM+29

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c425a

FAILURE_BUCKET_ID:  0xA_win32k!PALLOCMEM+29

BUCKET_ID:  0xA_win32k!PALLOCMEM+29

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

0: kd> .trap 0xffffffffc8223b1c
ErrCode = 00000002
eax=00000000 ebx=001fdac8 ecx=000096b2 edx=00000000 esi=fb402000 edi=fb5da000
eip=82c8ce85 esp=c8223b90 ebp=c8223ba8 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!memset+0x45:
82c8ce85 f3ab            rep stos dword ptr es:[edi]
    
por Chris Laplante 17.09.2010 / 01:56

1 resposta

3

É provável que seja algum tipo de incompatibilidade entre o Flash e o driver da placa gráfica, pois os próprios aplicativos não podem causar BSoDs. Tente atualizar seus drivers gráficos e Flash. Você pode querer experimentar o BlueScreenView também.

    
por 17.09.2010 / 02:49