New
#1
BSOD playing Fifa 14
BSOD when i play fifa 14. I already attached DM Log Collector zip file..can someone please check for me what is the problem ?
Thank You.
BSOD when i play fifa 14. I already attached DM Log Collector zip file..can someone please check for me what is the problem ?
Thank You.
From the dump file it seems you need to update the Intel Graphics driver
Driver Reference Table
Name Information Source
igdkmd64.sys
Intel Graphics driver
http://downloadcenter.intel.com/Default.aspx
Code:Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\Usra\Downloads\THIVHA-Fri_04_11_2014_104416_31\041114-29515-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 Machine Name: Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e51e90 Debug session time: Thu Apr 10 22:20:59.820 2014 (UTC + 6:00) System Uptime: 0 days 0:12:21.084 Loading Kernel Symbols ............................................................... ................................................................ .............................. Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 3D, {fffff80000b9be20, 0, 0, fffff88004fae4c6} *** WARNING: Unable to verify timestamp for igdkmd64.sys *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys Probably caused by : Unknown_Image ( dxgmms1!VidSchiProcessIsrCompletedPacket+46 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* INTERRUPT_EXCEPTION_NOT_HANDLED (3d) Arguments: Arg1: fffff80000b9be20 Arg2: 0000000000000000 Arg3: 0000000000000000 Arg4: fffff88004fae4c6 Debugging Details: ------------------ CONTEXT: fffff80000b9be20 -- (.cxr 0xfffff80000b9be20) rax=fffff80000b9c888 rbx=00fffa80088ab1a0 rcx=0000000000000004 rdx=000000000006a889 rsi=fffffa80088aa000 rdi=0000000000000000 rip=fffff88004fae4c6 rsp=fffff80000b9c800 rbp=fffffa8008876010 r8=0000000000000001 r9=0000000000000000 r10=0000000000000000 r11=fffffa80088aaac0 r12=000000000006a889 r13=0000000000000000 r14=0000000000000001 r15=0000000000000000 iopl=0 nv up ei ng nz ac po cy cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010297 dxgmms1!VidSchiProcessIsrCompletedPacket+0x46: fffff880`04fae4c6 837b5803 cmp dword ptr [rbx+58h],3 ds:002b:00fffa80`088ab1f8=???????? Resetting default scope CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x3D PROCESS_NAME: System CURRENT_IRQL: 9 TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0 LAST_CONTROL_TRANSFER: from fffff88004fae172 to fffff88004fae4c6 STACK_TEXT: fffff800`00b9c800 fffff880`04fae172 : fffffa80`088aa000 00000000`00000000 fffff800`00000001 fffff800`00b9c960 : dxgmms1!VidSchiProcessIsrCompletedPacket+0x46 fffff800`00b9c890 fffff880`04fadf76 : 00000000`0006a889 fffff880`05c296df fffffa80`08b69000 00000000`0006a889 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x1ea fffff800`00b9c8e0 fffff880`04eb513f : fffffa80`07957480 fffff880`05a5b51c 00000000`00000000 fffff880`05c293c8 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e fffff800`00b9c910 fffff880`05b1818e : fffffa80`03fde2f0 fffffa80`07953000 fffff880`069ac000 00000000`00000000 : dxgkrnl!DxgNotifyInterruptCB+0x83 fffff800`00b9c940 fffffa80`03fde2f0 : fffffa80`07953000 fffff880`069ac000 00000000`00000000 fffff800`00000001 : igdkmd64+0xf818e fffff800`00b9c948 fffffa80`07953000 : fffff880`069ac000 00000000`00000000 fffff800`00000001 00000000`0006a889 : 0xfffffa80`03fde2f0 fffff800`00b9c950 fffff880`069ac000 : 00000000`00000000 fffff800`00000001 00000000`0006a889 00000000`00000000 : 0xfffffa80`07953000 fffff800`00b9c958 00000000`00000000 : fffff800`00000001 00000000`0006a889 00000000`00000000 00000000`00000000 : 0xfffff880`069ac000 FOLLOWUP_IP: dxgmms1!VidSchiProcessIsrCompletedPacket+46 fffff880`04fae4c6 837b5803 cmp dword ptr [rbx+58h],3 SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: dxgmms1!VidSchiProcessIsrCompletedPacket+46 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 STACK_COMMAND: .cxr 0xfffff80000b9be20 ; kb BUCKET_ID: INVALID_KERNEL_CONTEXT MODULE_NAME: Unknown_Module Followup: MachineOwner --------- 0: kd> lmvm igdkmd64 start end module name fffff880`05a20000 fffff880`065c9620 igdkmd64 T (no symbols) Loaded symbol image file: igdkmd64.sys Image path: igdkmd64.sys Image name: igdkmd64.sys Timestamp: Sat Apr 16 00:08:20 2011 (4DA88994) CheckSum: 00BA97E5 ImageSize: 00BA9620 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Thank You ! I've updated my drivers. Hope this will works fine :)