!!! Strange BSOD !!!
 

Hi everybody,

I get a BSOD when playing WOW : here is the debugging result of the minidump
file generated by this error :

It is a 0x1000008e (0xc0000005, 0xbf8b7377, 0x f793e898, 0x00000000) error
code !

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction "0x%08lx" emploie
l'adresse m moire "0x%08lx". La m moire ne peut pas tre "%s".

FAULTING_IP:
win32k!UpdateAsyncKeyState+da
bf8b7377 081f or [edi],bl

TRAP_FRAME: f791e898 -- (.trap fffffffff791e898)
ErrCode = 00000002
eax=00305cd0 ebx=00000040 ecx=85680484 edx=e236edc4 esi=00000026 edi=00305d20
eip=bf8b7377 esp=f791e90c ebp=f791e918 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
win32k!UpdateAsyncKeyState+0xda:
bf8b7377 081f or [edi],bl ds:0023:00305d20=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf8b7d35 to bf8b7377

STACK_TEXT:
f791e918 bf8b7d35 e382d440 85680484 00000004 win32k!UpdateAsyncKeyState+0xda
f791e978 bf8b8609 00000126 f7910048 00a96991 win32k!xxxKeyEvent+0x21c
f791e9ac bf873940 f791e926 00000000 00000000 win32k!xxxProcessKeyEvent+0x221
f791e9ec bf874449 e1a5c5e0 26a5c4b8 00000001
win32k!ProcessKeyboardInputWorker+0x24d
f791ea0c bf86dcb0 e1a5c4b8 8563a8e8 f791ea64 win32k!ProcessKeyboardInput+0x68
f791ea1c 804f18b8 e1a5c4b8 e1a5c4e0 00000000 win32k!InputApc+0x4e
f791ea64 804f02c1 00000000 00000000 00000000 nt!KiDeliverApc+0x124
f791ea7c 804e3b7d 804dcbe4 00000001 00000000 nt!KiSwapThread+0x64
f791eab4 bf888cc2 00000007 8565b740 00000001 nt!KeWaitForMultipleObjects+0x284
f791ed30 bf86d09c f790e4a8 00000002 f791ed54 win32k!RawInputThread+0x4f3
f791ed40 bf8010ca f790e4a8 f791ed64 0070fff4
win32k!xxxCreateSystemThreads+0x60
f791ed54 804de7ec 00000000 00000022 00000000 win32k!NtUserCallOneParam+0x23
f791ed54 7c91eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c91eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
win32k!UpdateAsyncKeyState+da
bf8b7377 081f or [edi],bl

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!UpdateAsyncKeyState+da

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

FAILURE_BUCKET_ID: 0x8E_win32k!UpdateAsyncKeyState+da

BUCKET_ID: 0x8E_win32k!UpdateAsyncKeyState+da

Followup: MachineOwner

Does anybody can help me out to analyse this and solve my problem ?

Thanks a lot !

!!! Strange BSOD !!!
 

Check your Ram with memtest or something similar. See if this is any help
http://support.microsoft.com/default...;en-us;Q310740


"micod2000" wrote in message
...
Hi everybody,

I get a BSOD when playing WOW : here is the debugging result of the
minidump
file generated by this error :

It is a 0x1000008e (0xc0000005, 0xbf8b7377, 0x f793e898, 0x00000000) error
code !

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction "0x%08lx" emploie
l'adresse m moire "0x%08lx". La m moire ne peut pas tre "%s".

FAULTING_IP:
win32k!UpdateAsyncKeyState+da
bf8b7377 081f or [edi],bl

TRAP_FRAME: f791e898 -- (.trap fffffffff791e898)
ErrCode = 00000002
eax=00305cd0 ebx=00000040 ecx=85680484 edx=e236edc4 esi=00000026
edi=00305d20
eip=bf8b7377 esp=f791e90c ebp=f791e918 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
win32k!UpdateAsyncKeyState+0xda:
bf8b7377 081f or [edi],bl ds:0023:00305d20=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf8b7d35 to bf8b7377

STACK_TEXT:
f791e918 bf8b7d35 e382d440 85680484 00000004
win32k!UpdateAsyncKeyState+0xda
f791e978 bf8b8609 00000126 f7910048 00a96991 win32k!xxxKeyEvent+0x21c
f791e9ac bf873940 f791e926 00000000 00000000
win32k!xxxProcessKeyEvent+0x221
f791e9ec bf874449 e1a5c5e0 26a5c4b8 00000001
win32k!ProcessKeyboardInputWorker+0x24d
f791ea0c bf86dcb0 e1a5c4b8 8563a8e8 f791ea64
win32k!ProcessKeyboardInput+0x68
f791ea1c 804f18b8 e1a5c4b8 e1a5c4e0 00000000 win32k!InputApc+0x4e
f791ea64 804f02c1 00000000 00000000 00000000 nt!KiDeliverApc+0x124
f791ea7c 804e3b7d 804dcbe4 00000001 00000000 nt!KiSwapThread+0x64
f791eab4 bf888cc2 00000007 8565b740 00000001
nt!KeWaitForMultipleObjects+0x284
f791ed30 bf86d09c f790e4a8 00000002 f791ed54 win32k!RawInputThread+0x4f3
f791ed40 bf8010ca f790e4a8 f791ed64 0070fff4
win32k!xxxCreateSystemThreads+0x60
f791ed54 804de7ec 00000000 00000022 00000000
win32k!NtUserCallOneParam+0x23
f791ed54 7c91eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c91eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
win32k!UpdateAsyncKeyState+da
bf8b7377 081f or [edi],bl

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!UpdateAsyncKeyState+da

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

FAILURE_BUCKET_ID: 0x8E_win32k!UpdateAsyncKeyState+da

BUCKET_ID: 0x8E_win32k!UpdateAsyncKeyState+da

Followup: MachineOwner

Does anybody can help me out to analyse this and solve my problem ?

Thanks a lot !

!!! Strange BSOD !!!
 

Hi,

To be precise i posted here because i am working on this issue for a while
now accross different forums and i checked every piece of my hardware : 24H
running memtest86+ did not return any error for example; resetting the paging
file did not do anything either. For the software part i ran verifier.exe :
nothing. It's a very strange BSOD because it can happens 3 times a day
sometimes and then nothing for a week.

WOW is unplayable : BSOD after 5 minutes in the better case and i get this
error sometimes while surfing on the web.

BSOD expert wanted ...

Thanks.

"Rich Barry" wrote:

Check your Ram with memtest or something similar. See if this is any help
http://support.microsoft.com/default...;en-us;Q310740


"micod2000" wrote in message
...
Hi everybody,

I get a BSOD when playing WOW : here is the debugging result of the
minidump
file generated by this error :

It is a 0x1000008e (0xc0000005, 0xbf8b7377, 0x f793e898, 0x00000000) error
code !

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - L'instruction "0x%08lx" emploie
l'adresse m moire "0x%08lx". La m moire ne peut pas tre "%s".

FAULTING_IP:
win32k!UpdateAsyncKeyState+da
bf8b7377 081f or [edi],bl

TRAP_FRAME: f791e898 -- (.trap fffffffff791e898)
ErrCode = 00000002
eax=00305cd0 ebx=00000040 ecx=85680484 edx=e236edc4 esi=00000026
edi=00305d20
eip=bf8b7377 esp=f791e90c ebp=f791e918 iopl=0 nv up ei pl nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010212
win32k!UpdateAsyncKeyState+0xda:
bf8b7377 081f or [edi],bl ds:0023:00305d20=??
Resetting default scope

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

LAST_CONTROL_TRANSFER: from bf8b7d35 to bf8b7377

STACK_TEXT:
f791e918 bf8b7d35 e382d440 85680484 00000004
win32k!UpdateAsyncKeyState+0xda
f791e978 bf8b8609 00000126 f7910048 00a96991 win32k!xxxKeyEvent+0x21c
f791e9ac bf873940 f791e926 00000000 00000000
win32k!xxxProcessKeyEvent+0x221
f791e9ec bf874449 e1a5c5e0 26a5c4b8 00000001
win32k!ProcessKeyboardInputWorker+0x24d
f791ea0c bf86dcb0 e1a5c4b8 8563a8e8 f791ea64
win32k!ProcessKeyboardInput+0x68
f791ea1c 804f18b8 e1a5c4b8 e1a5c4e0 00000000 win32k!InputApc+0x4e
f791ea64 804f02c1 00000000 00000000 00000000 nt!KiDeliverApc+0x124
f791ea7c 804e3b7d 804dcbe4 00000001 00000000 nt!KiSwapThread+0x64
f791eab4 bf888cc2 00000007 8565b740 00000001
nt!KeWaitForMultipleObjects+0x284
f791ed30 bf86d09c f790e4a8 00000002 f791ed54 win32k!RawInputThread+0x4f3
f791ed40 bf8010ca f790e4a8 f791ed64 0070fff4
win32k!xxxCreateSystemThreads+0x60
f791ed54 804de7ec 00000000 00000022 00000000
win32k!NtUserCallOneParam+0x23
f791ed54 7c91eb94 00000000 00000022 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
00000000 00000000 00000000 00000000 00000000 0x7c91eb94


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
win32k!UpdateAsyncKeyState+da
bf8b7377 081f or [edi],bl

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: win32k!UpdateAsyncKeyState+da

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 43446a58

FAILURE_BUCKET_ID: 0x8E_win32k!UpdateAsyncKeyState+da

BUCKET_ID: 0x8E_win32k!UpdateAsyncKeyState+da

Followup: MachineOwner

Does anybody can help me out to analyse this and solve my problem ?

Thanks a lot !

!!! Strange BSOD !!!
 

micod2000 wrote:
Hi,

To be precise i posted here because i am working on this issue for a while
now accross different forums and i checked every piece of my hardware : 24H
running memtest86+ did not return any error for example; resetting the paging
file did not do anything either. For the software part i ran verifier.exe :
nothing. It's a very strange BSOD because it can happens 3 times a day
sometimes and then nothing for a week.

WOW is unplayable : BSOD after 5 minutes in the better case and i get this
error sometimes while surfing on the web.

BSOD expert wanted ...

Thanks.

Ya gotta include what you've done if you dont want people to suggest
steps you've already taken.

It is also important to include your complete system specififations.

Since we're dealing with a game, What version of directx, windows
version, and service pack revision.

You may wish to upgrade the BIOS as well.

I once had a problem like yours, took me weeks to conclude the video
card was overheating under load.

!!! Strange BSOD !!!
 

Memory Dumps generally occur when there is a resource shortage in your
system. There are several things you will want to do and to check
for.
1. you can put a band-aid on the problem by disabling your error
logging. This isn't actually a fix for the actual cause, but will
alleviate the symptoms. To disable error logging, go to Control
PanelSystemAdvanced TabError Reportingcheck off
Disable Error Reporting
2.Run through your Start-up list via msconfig and disable unneeded
applications from starting up each time your system starts up. A good
reference for figuring out what you need and don't need in the list is
found at www.sysinfo.org
3.Run a scan for Spyware. I recommend using the online scan at
www.ewido.net for your initial scan and then get a program like
Ad-Aware for your regular maintenance.
4.Run msinfo32 and check to see what your computer is using for memory
and such. This can give you a good idea of what shape your system is
in.
5.Make sure your system is managing your Virtual Memory, and that is
isn't set to an unusably small size. Do this by going Control
PanelSystem AdvancedUnder the performance
area,SettingsAdvancedunder Virtual Mamory area,
Changecheck off System Managed Size.


Hope this helps a bit

!!! Strange BSOD !!!
 

Oops...I had missed that one.
:(


When you say it happens sometimes when you're surfing the, what more
specifically are you surfing. Is it heavy with graphics, or movies,
or anything like that? Does it happen right away, or does it sort of
build up to it? I agree that it is starting to sound like a heat
problem. I've seen this sort of thing from video cards, overclocked
RAM, and even from processors that had air bubbles in the heatsink
compound so they didn't cool evenly.
More info is definitely needed on this.
Have you checked your system temp after the lockups at all? May also
give a decent clue