Sudden BSoD While Playing an Online Game, Error 0x50

Sudden BSoD while playing an online game in my 2 year old laptop. Then after the computer restarts and prompted to choose to run the windows normally or repair. After choosing the run normally, I got BSoD again. Not sure if it is really one since I don't see the error code. Then the computer restarts. Then, prompted again and chose run normally and it happened again. For the third time, now the Windows started normally.

Hi errorwin7.

The zip contains one crash dump only ......

Code:

BugCheck C000021A, {fffff8a0078043d0, 0, ffffffffc0000001, 10768}

----- ETW minidump data unavailable-----
Probably caused by : ntkrnlmp.exe ( nt!ExpSystemErrorHandler2+5e1 )

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

So I strongly support what errorwin7 suggested.

errorwin7 said:

This error 0x50 can have multiple causes : hardware (memory), Antiviruses, HDD problems. Try use Last good Known Configuration with F8 key pressing while you log in. After you log in then check Hardware drivers, antivirus, HDD chkdsk /f /r options....

For any next BSOD, Post it following the Blue Screen of Death (BSOD) Posting Instructions.

No new BSOD is there.

From the next time, dont change the original post. Update data in your subsequent post only.

If you have Windows Update KB2670838 installed, uninstall it.
Remove an update - Microsoft Windows Help

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff881a2b637c0, 0, fffff880082e7185, 5}

*** WARNING: Unable to verify timestamp for igdpmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for igdpmd64.sys

Could not read faulting driver name
Probably caused by : igdpmd64.sys ( igdpmd64+a9185 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff881a2b637c0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff880082e7185, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800040c2100
GetUlongFromAddress: unable to read from fffff800040c21c0
 fffff881a2b637c0 Nonpaged pool

FAULTING_IP: 
igdpmd64+a9185
fffff880`082e7185 8b0401          mov     eax,dword ptr [rcx+rax]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

TRAP_FRAME:  fffff8800bd4cae0 -- (.trap 0xfffff8800bd4cae0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff88008dc35c0 rbx=0000000000000000 rcx=0000000199da0200
rdx=fffffa800ca907c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880082e7185 rsp=fffff8800bd4cc70 rbp=fffffa800ca907c0
 r8=0000000000000000  r9=fffff8800bd4cca0 r10=fffffa800ae3a3a0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
igdpmd64+0xa9185:
fffff880`082e7185 8b0401          mov     eax,dword ptr [rcx+rax] ds:fffff881`a2b637c0=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003f075a3 to fffff80003e8ab80

STACK_TEXT:  
fffff880`0bd4c978 fffff800`03f075a3 : 00000000`00000050 fffff881`a2b637c0 00000000`00000000 fffff880`0bd4cae0 : nt!KeBugCheckEx
fffff880`0bd4c980 fffff800`03e88cae : 00000000`00000000 fffff881`a2b637c0 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`0bd4cae0 fffff880`082e7185 : 00000000`00000001 00000000`00000000 00000000`00000020 fffffa80`0cd60300 : nt!KiPageFault+0x16e
fffff880`0bd4cc70 00000000`00000001 : 00000000`00000000 00000000`00000020 fffffa80`0cd60300 fffffa80`0ae3a3a0 : igdpmd64+0xa9185
fffff880`0bd4cc78 00000000`00000000 : 00000000`00000020 fffffa80`0cd60300 fffffa80`0ae3a3a0 fffff880`082e7bde : 0x1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
igdpmd64+a9185
fffff880`082e7185 8b0401          mov     eax,dword ptr [rcx+rax]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  igdpmd64+a9185

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: igdpmd64

IMAGE_NAME:  igdpmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4e4152eb

FAILURE_BUCKET_ID:  X64_0x50_igdpmd64+a9185

BUCKET_ID:  X64_0x50_igdpmd64+a9185

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x50_igdpmd64+a9185

FAILURE_ID_HASH:  {fe72fd6b-76c5-73e0-f365-f9187c9a803e}

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

0: kd> lmvm igdpmd64
start             end                 module name
fffff880`0823e000 fffff880`08df65c0   igdpmd64 T (no symbols)           
    Loaded symbol image file: igdpmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdpmd64.sys
    Image name: igdpmd64.sys
    Timestamp:        Tue Aug 09 21:01:55 2011 (4E4152EB)
    CheckSum:         00BB861A
    ImageSize:        00BB85C0
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

You can, but you may not.