Windows 8 and 8.1 Forums


BSOD Win 8.1 x64 (ntoskrnl.exe)

  1. #11


    4040 Jyllinge Denmark
    Posts : 18
    Windows 8.1 Pro Professional 6.02.9200 (64-bit)

    Driver Verifier


    I installed the Intel Management Engine program from the Clevo website as you suggested. I have used the opportunity of (carrona.org) to run the Driver Verifier and came up with the result of BSOD - all happened after windows was started!
    I restarted windows program throughout the three times..dump files in the zip folder.
    Attachment 50886

    Thanks

      My System SpecsSystem Spec

  2. #12


    4040 Jyllinge Denmark
    Posts : 18
    Windows 8.1 Pro Professional 6.02.9200 (64-bit)

    Verifier drivers NOT provided by Microsoft (BSOD) igdkmd64


    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\091214-9296-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    Machine Name:
    Kernel base = 0xfffff803`1a485000 PsLoadedModuleList = 0xfffff803`1a74f350
    Debug session time: Fri Sep 12 09:45:20.195 2014 (UTC + 2:00)
    System Uptime: 0 days 0:08:19.959
    Loading Kernel Symbols
    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    ..............................................................
    ................................................................
    ...................
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 116, {ffffe0019ed942a0, fffff8016d4fb0d0, ffffffffc0000001, 3}

    Unable to load image \SystemRoot\system32\DRIVERS\igdkmd64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    Probably caused by : igdkmd64.sys ( igdkmd64+c0d0 )

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

    7: kd> !analyse -v
    No export analyse found
    7: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: ffffe0019ed942a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8016d4fb0d0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000003, Optional internal context dependent data.

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


    FAULTING_IP:
    igdkmd64+c0d0
    fffff801`6d4fb0d0 48895c2410 mov qword ptr [rsp+10h],rbx

    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

    CUSTOMER_CRASH_COUNT: 1

    BUGCHECK_STR: 0x116

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    STACK_TEXT:
    ffffd000`32e90788 fffff801`6d1cbfac : 00000000`00000116 ffffe001`9ed942a0 fffff801`6d4fb0d0 ffffffff`c0000001 : nt!KeBugCheckEx
    ffffd000`32e90790 fffff801`6d1bf3a2 : fffff801`6d4fb0d0 ffffe001`9865f540 ffffe001`9865f600 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    ffffd000`32e907d0 fffff801`6d1cb8b2 : ffffe001`9ed901a0 00000000`00000087 ffffe001`9ed942a0 00000000`00000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x152
    ffffd000`32e90820 fffff801`6d277644 : ffffe001`9ed942a0 ffffd000`32e908c9 00000000`00000000 00000000`00000000 : dxgkrnl!TdrIsRecoveryRequired+0x1be
    ffffd000`32e90850 fffff801`6d2aa3fa : 00000000`00000008 ffffd000`32e90950 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x3e4
    ffffd000`32e90930 fffff801`6d263ba8 : ffffffff`ff676980 00000000`00000000 ffffd000`32e90ac0 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x1868a
    ffffd000`32e909c0 fffff801`6d29ed4a : ffffe001`9cfa2000 ffffe001`9cfa2000 ffffe001`9dc67a20 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x448
    ffffd000`32e90b70 fffff801`6d29ed1d : ffffe001`9cfa2000 00000000`00000080 ffffe001`9cfdd880 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
    ffffd000`32e90bc0 fffff803`1a55e514 : fffff803`1a7d2a00 ffffe001`9cfdd880 ffffd000`32e90c90 fffff803`1a5dc07d : dxgmms1!VidSchiWorkerThread+0x8d
    ffffd000`32e90c00 fffff803`1a5df2c6 : fffff803`1a76b180 ffffe001`9cfdd880 fffff803`1a7d2a00 ffffc001`7524abe0 : nt!PspSystemThreadStartup+0x58
    ffffd000`32e90c60 00000000`00000000 : ffffd000`32e91000 ffffd000`32e8b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    igdkmd64+c0d0
    fffff801`6d4fb0d0 48895c2410 mov qword ptr [rsp+10h],rbx

    SYMBOL_NAME: igdkmd64+c0d0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: igdkmd64

    IMAGE_NAME: igdkmd64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 53e8f12b

    FAILURE_BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys

    BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x116_vrf_image_igdkmd64.sys

    FAILURE_ID_HASH: {3e1b97eb-0b23-2ef6-99fb-38dcc07b5a62}

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

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

    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: ffffe0019ed942a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8016d4fb0d0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000003, Optional internal context dependent data.

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


    FAULTING_IP:
    igdkmd64+c0d0
    fffff801`6d4fb0d0 48895c2410 mov qword ptr [rsp+10h],rbx

    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

    CUSTOMER_CRASH_COUNT: 1

    BUGCHECK_STR: 0x116

    PROCESS_NAME: System

    CURRENT_IRQL: 0

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    STACK_TEXT:
    ffffd000`32e90788 fffff801`6d1cbfac : 00000000`00000116 ffffe001`9ed942a0 fffff801`6d4fb0d0 ffffffff`c0000001 : nt!KeBugCheckEx
    ffffd000`32e90790 fffff801`6d1bf3a2 : fffff801`6d4fb0d0 ffffe001`9865f540 ffffe001`9865f600 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    ffffd000`32e907d0 fffff801`6d1cb8b2 : ffffe001`9ed901a0 00000000`00000087 ffffe001`9ed942a0 00000000`00000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x152
    ffffd000`32e90820 fffff801`6d277644 : ffffe001`9ed942a0 ffffd000`32e908c9 00000000`00000000 00000000`00000000 : dxgkrnl!TdrIsRecoveryRequired+0x1be
    ffffd000`32e90850 fffff801`6d2aa3fa : 00000000`00000008 ffffd000`32e90950 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x3e4
    ffffd000`32e90930 fffff801`6d263ba8 : ffffffff`ff676980 00000000`00000000 ffffd000`32e90ac0 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x1868a
    ffffd000`32e909c0 fffff801`6d29ed4a : ffffe001`9cfa2000 ffffe001`9cfa2000 ffffe001`9dc67a20 ffffe001`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x448
    ffffd000`32e90b70 fffff801`6d29ed1d : ffffe001`9cfa2000 00000000`00000080 ffffe001`9cfdd880 ffffe001`00000000 : dxgmms1!VidSchiRun_PriorityTable+0x2a
    ffffd000`32e90bc0 fffff803`1a55e514 : fffff803`1a7d2a00 ffffe001`9cfdd880 ffffd000`32e90c90 fffff803`1a5dc07d : dxgmms1!VidSchiWorkerThread+0x8d
    ffffd000`32e90c00 fffff803`1a5df2c6 : fffff803`1a76b180 ffffe001`9cfdd880 fffff803`1a7d2a00 ffffc001`7524abe0 : nt!PspSystemThreadStartup+0x58
    ffffd000`32e90c60 00000000`00000000 : ffffd000`32e91000 ffffd000`32e8b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    igdkmd64+c0d0
    fffff801`6d4fb0d0 48895c2410 mov qword ptr [rsp+10h],rbx

    SYMBOL_NAME: igdkmd64+c0d0

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: igdkmd64

    IMAGE_NAME: igdkmd64.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 53e8f12b

    FAILURE_BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys

    BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x116_vrf_image_igdkmd64.sys

    FAILURE_ID_HASH: {3e1b97eb-0b23-2ef6-99fb-38dcc07b5a62}

    Followup: MachineOwner
    ---------
      My System SpecsSystem Spec

  3. #13


    4040 Jyllinge Denmark
    Posts : 18
    Windows 8.1 Pro Professional 6.02.9200 (64-bit)


    This is my first WinDbg Analysis Report!

    This should be one of 'three dump files with the latest BSOD

    Sir
      My System SpecsSystem Spec

  4. #14


    4040 Jyllinge Denmark
    Posts : 18
    Windows 8.1 Pro Professional 6.02.9200 (64-bit)

    BSOD in windows 8.1 due to intel graphics driver


    igdkmd64 sys is the Intel Graphics Kernel Mode Driver for Microsoft Windows 8, Windows 7, Windows Vista and Windows XP 64-bit operating systems.

    exactly BSOD ONLY happens when I watch Flash Player videos on various websites, YouTube, etc.
    Last edited by Alex Jones; 15 Sep 2014 at 16:56.
      My System SpecsSystem Spec

  5. #15


    4040 Jyllinge Denmark
    Posts : 18
    Windows 8.1 Pro Professional 6.02.9200 (64-bit)

    "Intel Generic drivers vs Computer manufacturer Drivers"


    Intel staff proposes: You can download the driver for your graphics controller from the following link: Intelо Driver Update Utility In case our driver does not work properly in your system, please install the driver from your system manufacturer.
    Several issues regarding Intel igdkmd64.sys recent BSODs this summer..
    https://communities.intel.com/message/238389#238389

    I will have to visit CLEVO website to obtain the proper graphic driver If - due to the present intel igdkmd64 graphic driver causes additional errors BSODs

    clean install Windows does it work? As I have previously installed on this Clevo: Win.7x64 Ultimate and Win.8x64 pro all ended up having the same result as current BSODs regularly having Win 8.1x64 pro installed running with integrated Intel HD 4600 graphics.

    BSODs regularly quite odd that happens to brand new machines
    hugely frustrating!

    Thanks again Sir for the Support
    Last edited by Alex Jones; 15 Sep 2014 at 17:48.
      My System SpecsSystem Spec

  6. #16


    Posts : 5,139
    Win8.1Pro - Finally!!!


    Nice work with the debugging report!
    But only 1 memory dump in the uploaded files

    On systems with dual graphics adapters (mostly laptops), often the laptop manufacturer will modify the drivers so that they'll work nicely together (and to make them work with the proprietary switching software). As such I only recommend using the video drivers from the laptop manufacturer's website.

    More suggestions on STOP 0x116 errors here: Video TDR Timeout - 0x116 + 0x117 - Sysnative Forums
    Also, please monitor your temps with this free utility: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting

    Please ensure that you turn Driver Verifier off. To do this, open up verifier.exe and select "Delete existing settings", then click on "Finish" and reboot the system for the changes to take effect.

    Ensure that you have the latest updates for Flash Player from Download a free trial or buy Adobe products | Adobe downloads

    A clean install is a valid troubleshooting tool. If you install windows clean, using different installation media or different OS versions - and you still experience BSOD's - then it's most likely that this is a hardware problem (rather than a software/driver problem). A clean install includes ALL available Windows Updates, and verifying that Device Manager has no problem devices. There may be updates available from the manufacturer's website, but those should be chosen carefully - to avoid introducing something that may actually cause a BSOD. The point here is to make the installation as close to the way that Microsoft intended it as is possible.

    Just FYI - here's how I do BSOD analysis':
    - first I rule out 3rd party drivers (over 90% of BSOD's are due to this)
    - then I rule out hardware (less than 10% of BSOD's are due to this)
    - then I look at Windows problems (less than 1% of BSOD's are due to this - as long as Windows Updates are fully up to date).
      My System SpecsSystem Spec

  7. #17


    4040 Jyllinge Denmark
    Posts : 18
    Windows 8.1 Pro Professional 6.02.9200 (64-bit)

    win32k.sys


    Microsoft (R) Windows Debugger Version 6.3.9600.17237 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Windows\Minidump\091614-7218-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available


    ************* Symbol Path validation summary **************
    Response Time (ms) Location
    Deferred SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    Machine Name:
    Kernel base = 0xfffff802`b1e0b000 PsLoadedModuleList = 0xfffff802`b20d5350
    Debug session time: Tue Sep 16 10:02:07.842 2014 (UTC + 2:00)
    System Uptime: 0 days 0:39:34.517
    Loading Kernel Symbols
    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    ..............................................................
    ................................................................
    .................
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {ffffa000752afa40, e, 1, fffff802b259c619}

    Probably caused by : win32k.sys ( win32k!memcpy+a5 )

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

    4: kd> !analyze -v
    *******************************************************************************
    * *
    * 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: ffffa000752afa40, memory referenced
    Arg2: 000000000000000e, IRQL
    Arg3: 0000000000000001, 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: fffff802b259c619, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff802b215f138
    unable to get nt!MmNonPagedPoolStart
    unable to get nt!MmSizeOfNonPagedPoolInBytes
    ffffa000752afa40

    CURRENT_IRQL: e

    FAULTING_IP:
    hal!HalPerformEndOfInterrupt+9
    fffff802`b259c619 4883c428 add rsp,28h

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: AV

    PROCESS_NAME: casinogame.exe

    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre

    TRAP_FRAME: ffffd000214e3800 -- (.trap 0xffffd000214e3800)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffd00053dcbfb8 rbx=0000000000000000 rcx=0000000000000000
    rdx=ffffd00021048770 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff802b259c619 rsp=ffffd000214e3990 rbp=ffffd000214e3a40
    r8=0000000000001000 r9=ffffd00021048770 r10=ffffd00017fffaf0
    r11=ffffd000214e3df0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up di pl zr na po nc
    hal!HalPerformEndOfInterrupt+0x9:
    fffff802`b259c619 4883c428 add rsp,28h
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff802b1f6a7e9 to fffff802b1f5eca0

    STACK_TEXT:
    ffffd000`214e36b8 fffff802`b1f6a7e9 : 00000000`0000000a ffffa000`752afa40 00000000`0000000e 00000000`00000001 : nt!KeBugCheckEx
    ffffd000`214e36c0 fffff802`b1f6903a : 00000000`00000001 ffffd000`214e3d50 00000000`00000000 ffffd000`214e3800 : nt!KiBugCheckDispatch+0x69
    ffffd000`214e3800 fffff802`b259c619 : 00000000`0000630c fffff802`b1ea25c9 fffffa80`04e1b3f0 fffff960`0028c845 : nt!KiPageFault+0x23a
    ffffd000`214e3990 fffff802`b1f6500c : 00000000`00000000 00000000`00000000 00000010`00000000 00000008`00000000 : hal!HalPerformEndOfInterrupt+0x9
    ffffd000`214e39c0 fffff960`001d3d25 : fffff960`001ba440 00000000`fffff000 ffffd000`00000000 00000000`00000000 : nt!KiIpiInterrupt+0x10c
    ffffd000`214e3b58 fffff960`001ba440 : 00000000`fffff000 ffffd000`00000000 00000000`00000000 00000000`00000000 : win32k!memcpy+0xa5
    ffffd000`214e3b60 fffff960`0020157a : ffffd000`214e42f0 ffffd000`214e4330 00000000`00000000 00000000`00000000 : win32k!vSrcCopyS32D32Identity+0x64
    ffffd000`214e3b90 fffff960`00200de4 : fffff901`401f28d0 ffffd000`214e4444 ffffd000`214e4444 00000000`00000000 : win32k!BltLnkRect+0x442
    ffffd000`214e4230 fffff960`001fef52 : fffff901`4000ac58 00000000`00000000 0000ffff`ffffde01 fffff901`46d59000 : win32k!BltLnk+0x434
    ffffd000`214e45f0 fffff960`0019c3a6 : fffff901`400bce30 fffff901`400bce30 fffff901`400bce30 fffff901`40130a70 : win32k!EngBitBlt+0x2a2
    ffffd000`214e4760 fffff802`b1f6a4b3 : 00000000`04051033 00000000`00000000 00000000`00000000 fffff901`435dd010 : win32k!NtGdiBitBltInternal+0xefd
    ffffd000`214e4a90 00000000`772f5a4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`0008e4e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x772f5a4a


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    win32k!memcpy+a5
    fffff960`001d3d25 f30f6f4c0a10 movdqu xmm1,xmmword ptr [rdx+rcx+10h]

    SYMBOL_STACK_INDEX: 5

    SYMBOL_NAME: win32k!memcpy+a5

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: win32k

    IMAGE_NAME: win32k.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 53fbb825

    IMAGE_VERSION: 6.3.9600.17286

    BUCKET_ID_FUNC_OFFSET: a5

    FAILURE_BUCKET_ID: AV_win32k!memcpy

    BUCKET_ID: AV_win32k!memcpy

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:av_win32k!memcpy

    FAILURE_ID_HASH: {cfc39bd0-2ccf-05d1-bd02-fa40feecda07}

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

    4: kd> .trap 0xffffd000214e3800
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffd00053dcbfb8 rbx=0000000000000000 rcx=0000000000000000
    rdx=ffffd00021048770 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff802b259c619 rsp=ffffd000214e3990 rbp=ffffd000214e3a40
    r8=0000000000001000 r9=ffffd00021048770 r10=ffffd00017fffaf0
    r11=ffffd000214e3df0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up di pl zr na po nc
    hal!HalPerformEndOfInterrupt+0x9:
    fffff802`b259c619 4883c428 add rsp,28h
      My System SpecsSystem Spec

  8. #18


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I didn't get much from this BSOD. Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum): Blue Screen of Death (BSOD) Posting Instructions Please use Option 1 as it provides Event Viewer logs.
      My System SpecsSystem Spec

  9. #19


    4040 Jyllinge Denmark
    Posts : 18
    Windows 8.1 Pro Professional 6.02.9200 (64-bit)
      My System SpecsSystem Spec

  10. #20


    Posts : 5,139
    Win8.1Pro - Finally!!!


    I saw several of the diagnostics that I suggest in your MSINFO32.
    Have you run all of these ( Hardware Diagnostics )?
    If so, what were the results?
    Also, please let us know which tests you've run and which you haven't run.

    Have you run Driver Verifier? If not, then please do so using these instructions: Driver Verifier Settings

    While not a particularly accurate diagnostic tool, I find that those memory dumps with few 3rd party drivers (like yours) will generally be a hardware problem (or could even be a Windows problem).
    In this case, it "feels" like a hardware problem to me - again, not a real accurate tool.

    As this is a laptop, it's usually easier to work on possible Windows problems first (as hardware problems aren't real easy to fix on a laptop). This presumes that you haven't found anything with the hardware diagnostics.
    Also, please monitor your system's temperatures with this free tool: HWMonitor CPUID - System & hardware benchmark, monitoring, reporting
    If you're already using it, please let us know what the temperatures are.

    As fixing Windows, please start with this:
    Then please run the following DISM commands to see if there's any problems with the system (from an elevated (Run as administrator) Command Prompt). Press Enter after each one:
    Code:
    Dism /Online /Cleanup-Image /ScanHealth
    Code:
    Dism /Online /Cleanup-Image /CheckHealth
    Code:
    Dism /Online /Cleanup-Image /RestoreHealth
    FYI - I have repaired systems using the last command even though problems weren't found with the first 2 - so I suggest running them all.

    From this article: Repair a Windows Image

    You can also run sfc.exe /scannow from an elevated (Run as administrator) Command Prompt to check for further corruption.
    If this doesn't help, I'd next suggest a Refresh of the system.
    And, if able, then I'd suggest a RESET (which will wipe everything out!).

    Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.

    The drivers that are struckout don't have updates available (AFAIK).
    DO NOT delete them, just leave them be.



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Tue Sep 16 13:08:25.473 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091614-7609-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:12:38.780
    Probably caused by :memory_corruption ( nt!MmZeroPageThread+66a )
    BugCheck A, {fffffd67ffffffe0, 2, 1, fffff803891c012a}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
    Arguments: 
    Arg1: fffffd67ffffffe0, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff803891c012a, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_nt!MmZeroPageThread
    CPUID:        "Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2394
      BIOS Version                  1.00.05
      BIOS Release Date             08/07/2013
      Manufacturer                  Notebook                        
      Product Name                  W65_W670SZ                      
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 16 12:55:16.268 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091614-7250-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 8:06:05.154
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :win32k.sys ( win32k+4383c )
    BugCheck A, {4000000, 2, 1, fffff8003c717682}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
    Arguments: 
    Arg1: 0000000004000000, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, 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: fffff8003c717682, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  casinogame.exe
    FAILURE_BUCKET_ID: AV_win32k+4383c
    CPUID:        "Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2394
      BIOS Version                  1.00.05
      BIOS Release Date             08/07/2013
      Manufacturer                  Notebook                        
      Product Name                  W65_W670SZ                      
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep 16 04:02:07.842 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091614-7218-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:39:34.517
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by :win32k.sys ( win32k+70d25 )
    BugCheck A, {ffffa000752afa40, e, 1, fffff802b259c619}
    BugCheck Info: IRQL_NOT_LESS_OR_EQUAL (a)
    Arguments: 
    Arg1: ffffa000752afa40, memory referenced
    Arg2: 000000000000000e, IRQL
    Arg3: 0000000000000001, 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: fffff802b259c619, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  casinogame.exe
    FAILURE_BUCKET_ID: AV_win32k+70d25
    CPUID:        "Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2394
      BIOS Version                  1.00.05
      BIOS Release Date             08/07/2013
      Manufacturer                  Notebook                        
      Product Name                  W65_W670SZ                      
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep 12 14:18:24.174 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091214-11093-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 10:32:32.886
    Probably caused by :ntkrnlmp.exe ( nt!IopProcessWorkItem+76 )
    BugCheck C4, {9400b, fffff8012f295ba0, ffffe0018e2d2630, ffffe0018e2d2688}
    BugCheck Info: DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    DRIVER_VERIFIER_DETECTED_VIOLATION (c4)
    Arguments: 
    Arg1: 000000000009400b, ID of the 'WlanTimedLinkQuality' rule that was violated.
    Arg2: fffff8012f295ba0, A pointer to the string describing the violated rule condition.
    Arg3: ffffe0018e2d2630, Address of internal rule state (second argument to !ruleinfo).
    Arg4: ffffe0018e2d2688, Address of supplemental states (third argument to !ruleinfo).
    BUGCHECK_STR:  0xc4_WlanTimedLinkQuality_XDV
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0xc4_WlanTimedLinkQuality_XDV_VRF_nt!IopProcessWorkItem
    CPUID:        "Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2394
      BIOS Version                  1.00.05
      BIOS Release Date             08/07/2013
      Manufacturer                  Notebook                        
      Product Name                  W65_W670SZ                      
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep 12 03:45:20.195 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091214-9296-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:08:19.959
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    Probably caused by :igdkmd64.sys ( igdkmd64+c0d0 )
    BugCheck 116, {ffffe0019ed942a0, fffff8016d4fb0d0, ffffffffc0000001, 3}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: ffffe0019ed942a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8016d4fb0d0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000003, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys
    CPUID:        "Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2394
      BIOS Version                  1.00.05
      BIOS Release Date             08/07/2013
      Manufacturer                  Notebook                        
      Product Name                  W65_W670SZ                      
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Sep 12 03:36:33.953 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091214-11484-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 0:08:36.665
    *** WARNING: Unable to verify timestamp for igdkmd64.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd64.sys
    Probably caused by :igdkmd64.sys ( igdkmd64+c0d0 )
    BugCheck 116, {ffffe000285d64d0, fffff801cb2940d0, ffffffffc0000001, 3}
    BugCheck Info: VIDEO_TDR_FAILURE (116)
    Arguments: 
    Arg1: ffffe000285d64d0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff801cb2940d0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000003, Optional internal context dependent data.
    BUGCHECK_STR:  0x116
    DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x116_VRF_IMAGE_igdkmd64.sys
    CPUID:        "Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2394
      BIOS Version                  1.00.05
      BIOS Release Date             08/07/2013
      Manufacturer                  Notebook                        
      Product Name                  W65_W670SZ                      
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Sep  9 22:20:55.443 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\091014-7171-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
    System Uptime:0 days 3:11:01.120
    Probably caused by :ntkrnlmp.exe ( nt!KiPageFault+23a )
    BugCheck D1, {fffff801a97069b0, e, 8, fffff801a97069b0}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: fffff801a97069b0, memory referenced
    Arg2: 000000000000000e, IRQL
    Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
    Arg4: fffff801a97069b0, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: AV_CODE_AV_BAD_IP_nt!KiPageFault
    CPUID:        "Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz"
    MaxSpeed:     2400
    CurrentSpeed: 2394
      BIOS Version                  1.00.05
      BIOS Release Date             08/07/2013
      Manufacturer                  Notebook                        
      Product Name                  W65_W670SZ                      
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    3rd Party Drivers:
    The following is for information purposes only.
    Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.
    Code:
    **************************Tue Sep 16 13:08:25.473 2014 (UTC - 4:00)**************************
    AirplaneModeHid.sys         Thu Jun 27 17:28:59 2013 (51CCAE9B)
    RtsBaStor.sys               Thu Jul 11 23:41:18 2013 (51DF7ADE)
    ETD.sys                     Tue Aug  6 02:18:47 2013 (52009547)
    [DEL]intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
    [/DEL]TeeDriverx64.sys            Thu Sep  5 14:02:18 2013 (5228C72A)
    
    
    iaStorA.sys                 Mon Oct 28 17:15:26 2013 (526ED3EE)
    [DEL]dump_iaStorA.sys            Mon Oct 28 17:15:26 2013 (526ED3EE)
    [/DEL]viahduaa.sys                Tue Oct 29 03:10:03 2013 (526F5F4B)
    athrx.sys                   Mon Dec 23 23:12:48 2013 (52B909C0)
    iwdbus.sys                  Thu Mar 13 17:59:14 2014 (53222A32)
    Rt630x64.sys                Tue Jun 17 07:56:46 2014 (53A02CFE)
    HWiNFO64A.SYS               Wed Aug  6 17:59:34 2014 (53E2A546)
    igdkmd64.sys                Mon Aug 11 12:36:59 2014 (53E8F12B)
    
    http://www.carrona.org/drivers/driver.php?id=AirplaneModeHid.sys
    http://www.carrona.org/drivers/driver.php?id=RtsBaStor.sys
    http://www.carrona.org/drivers/driver.php?id=ETD.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=viahduaa.sys
    http://www.carrona.org/drivers/driver.php?id=athrx.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
      My System SpecsSystem Spec

Page 2 of 3 FirstFirst 123 LastLast
BSOD Win 8.1 x64 (ntoskrnl.exe)
Related Threads
Solved BSOD, Ntoskrnl. in BSOD Crashes and Debugging
Hi guys, My laptop crashes showing this BSOD, sometimes it is so frequent may reach 5 times/day sometimes the day passes clearly http://www.sevenforums.com/images/smilies/biggrin.gif Sometimes during browsing and working on it, sometimes when I leave it free/on lockscreen !!...
ntoskrnl.exe BSOD in BSOD Crashes and Debugging
Hi everyone! So I recently bought a new laptop within the last month or so. Its the new line of Asus ROG gaming. i7, 12 GB RAM, GTX 860, Windows 8.1, 1 TB HDD. I've been getting BSODs after playing games such as Batman Arkham Orgins and Borderlands 2. During the game, everything runs smoothly at...
BSOD - (hal.dll - ntoskrnl.exe, etc) in BSOD Crashes and Debugging
Sincerely, my English is not very good (Spanish). Apologies, thank you very much. I've had blue screens, very consistently, I've noticed that when using the Spotify program. is more common. They are the only ones who can help. Under the last minidump. thank you in advance.
Solved BSOD with ntoskrnl.exe in BSOD Crashes and Debugging
Hi! :) For a couple of weeks now I'm using Windows 8.1 (upgraded from a Win 8 installation). Everything went fine until yesterday when I got my first BSOD on Win 8.1. Today it happened again. The causes seem to be the same but I hope for your analysis and help! Thanks in advance :)
BSOD on ntoskrnl.exe in BSOD Crashes and Debugging
Hi, I'm getting frequent blue screens which apparently occur from ntoskrnl.exe. Please see attached zip file from SF Diagnostic Tool Thanks in advance
BSOD - Ntoskrnl.exe in BSOD Crashes and Debugging
Hi, I have been experiencing shutdowns which I am not sure of the reason behind. I have hibernate and sleep disabled. The computer crashes andshutdown on its own. This is only happening when getting into sleep mode. It will never happen If I am working on the laptop no matter for how long. I...
Solved Ntoskrnl.exe bsod in BSOD Crashes and Debugging
Hello, i have a Problem with my Lenovo S205 in irregular times. In the attachment have I add my Minidump. I hope somebody can help me. I doesnt understand the dump Thanks
Eight Forums Android App Eight Forums IOS App Follow us on Facebook