!!! BSOD most often when playing WOW !!!

[micod2000]

Hi everybody,

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

The exact error code is 0x1000008e (0xc0000005, 0xbf8b7377, 0x f793e898,
0x00000000) and i found nothing on the net about it !!!

Recently it happened while surfing on the net ...

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

Summary of my system :

- Win XP PRO SP2
- AMD Athlon XP 3200+
- 2x512 MO DDR PC3200
- MSI K7N2 DELTA2 Platinum (NFORCE2 Gigabit)
- 2x250 GB HITACHI DESKSTAR 7K250 in a RAID 0 configuration (NVRAID)
- ASUS V8460 ULTRA DELUXE (GeForce 4 Ti4600)


I already checked every piece of my hardware :
- 24H of MEMTEST86+ for the RAM : nothing
- 24H of prime95 torture test : nothing
- MB seems physically OK

2 doubts : my videocard is pretty old and i wonder if my RAID 0 array is OK ...

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

Thanks a lot !

 

[WinDoWsMoNoPoLy]

Update your video drivers at the nvidia website. There was a similar error with nVidia cards in WC3TFT. Updating the drivers fixed that. Sadly, i have no idea how to read minidumps

Also, i have never even heard of that model of video card and being as WoW runs with D3D or OpenGL it may not be able to handle it. But still, update your drivers search the Blizzard Forums for this such error. Read the WoW game box for the minimum system requirements and then compare to your video card. Check to see if the video card fan is running along with all the other fans.

I would just wait for someone to tell you what your minidump says as it will pinpoint the problem.

 

[howard_hopkinso]

Hello and welcome to Techspot.

Go HERE and follow the instructions.

If that doesn`t help. Zip 5 or 6 of your latest minidumps together and attach them here.

Regards Howard :wave: :wave:

 

[Spike]

quite simply, it says there's a DRIVER_FAULT in win32k.sys

It's difficult to make a definitive diagnosis from only one minidump though.

 

[micod2000]

Hi,

Here are my zipped 4 minidump files ... I have only four of these files because my paging file was not on C: drive untill a few weeks ago ...

Very big thanks for helping me out ! :grinthumb

 

[howard_hopkinso]

1 minidump crashes at ntoskrnl.exe. This is the Windows bootup kernel file. It has a bugcheck of CD.

3 minidumps crash at win32k.sys. This is the Windows Multi-User Win32 Driver. They have a bugcheck of 8E.

0x000000CD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION

The driver allocated n bytes of memory from the special pool. Subsequently, the system referenced more than n bytes from this pool. This usually indicates a system-driver synchronization problem.

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

Check that all your drivers are upto date, including your chipset drivers.

Check for any bios upgrades that may be available.

Regards Howard

 

[micod2000]

All my drivers and BIOS are up to date ... Sorry for the first minidump file : it was normally issued when running verifier.exe on a faulty driver ... in my case it was aspi32.sys because i installed ADAPTEC ASPI layer in order to rip CD's using AUDIOGRABBER from my DVD drive : i solved the problem so i deleted the ASPI layer because it was generating error messages in the event viewer.

Do you have another suggestions to my problem ?

 

[howard_hopkinso]

Did you run the tests in the link I gave you? If so, what were the results?

This is only a suggestion and may or may not help. Maybe try doing a Windows repair as per this thread HERE.

Regards Howard

 

[micod2000]

- RAM tested with MEMTEST86+ : nothing
- chkdsk ran and Drive Fitness Test on my 2 HITACHI drives : nothing
- Page file resetted : did not help ...

I will test with a 1GB kit of KINGSTON HyperX memory from my father system to see if it's better.

I will get also a new AGP video card : ASUS AX800XL 256MB and let you know if it helps. My actual GPU is at 57°C idle !!!

Otherwise, i have no lead !

NOTE : Why does the result of windbg on the minidump i posted at the beginning of this post pinpoint something around the keyboard ? Does something with my keyboard is wrong ?

 

[WinDoWsMoNoPoLy]

What Service Pack are you using? I have had an issue with a game before after updating to SP2 where it would seemingly randomly crash usually around 30 minutes of play. I went back to SP1 which i still am using and it never did it again. You could try going to a different SP.

 

[cpc2004]

Hi Micod2000,

Your version of nVidia Display card driver and daemon tools have known software problem. Install nVidia Display Card Driver 78.xx and un-install daemon tool.