BSOD playing only one game


  1. Posts : 1
    Windows 10 x64
       #1

    BSOD playing only one game


    Hello,

    After having my PC in a while where nothing happened i am recently experience BSOD with the Code IRQL NOT LESS THEN EUQAL. I have Updated the most driver but it didnt FIx the Problem.
    MY PC Specc is

    Windows 10 x64
    Gigabyte Z170-HD3P BIOS Version F5
    Intel i-5 6400
    2 X Corsair DDR IV SDRAM 4096MB
    Radeon RX 470

    I Debugged the Dumpfiles but canīt figure out what the heck is going wrong

    HELP PLS! Thanks in advance
    Loading Dump File [C:\Users\Jesper\Desktop\022117-4343-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 14393 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 14393.693.amd64fre.rs1_release.161220-1747
    Machine Name:
    Kernel base = 0xfffff800`a100a000 PsLoadedModuleList = 0xfffff800`a130f060
    Debug session time: Tue Feb 21 15:08:55.657 2017 (UTC + 1:00)
    System Uptime: 0 days 17:52:07.343
    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, {28, 2, 0, fffff800a1190759}

    Probably caused by : memory_corruption

    Followup: memory_corruption
    ---------

    0: kd> !analye -v
    No export analye found
    0: kd> !analyse -v
    No export analyse found
    0: 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: 0000000000000028, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, 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: fffff800a1190759, address which referenced memory

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


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)

    SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

    SYSTEM_PRODUCT_NAME: To be filled by O.E.M.

    SYSTEM_SKU: To be filled by O.E.M.

    SYSTEM_VERSION: To be filled by O.E.M.

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: F5

    BIOS_DATE: 03/07/2016

    BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

    BASEBOARD_PRODUCT: Z170-HD3P-CF

    BASEBOARD_VERSION: x.x

    DUMP_TYPE: 2

    BUGCHECK_P1: 28

    BUGCHECK_P2: 2

    BUGCHECK_P3: 0

    BUGCHECK_P4: fffff800a1190759

    READ_ADDRESS: fffff800a13b1338: Unable to get MiVisibleState
    0000000000000028

    CURRENT_IRQL: 2

    FAULTING_IP:
    nt! ?? ::FNODOBFM::`string'+2cbc9
    fffff800`a1190759 488b4628 mov rax,qword ptr [rsi+28h]

    CPU_COUNT: 4

    CPU_MHZ: a98

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

    CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 74'00000000 (cache) 74'00000000 (init)

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: CODE_CORRUPTION

    BUGCHECK_STR: AV

    PROCESS_NAME: chrome.exe

    ANALYSIS_SESSION_HOST: DESKTOP-B9MP0Q3

    ANALYSIS_SESSION_TIME: 02-21-2017 17:32:59.0815

    ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

    TRAP_FRAME: ffff9200ce072100 -- (.trap 0xffff9200ce072100)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffe28000000028 rbx=0000000000000000 rcx=0000000000000000
    rdx=ffffe28000000028 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800a1190759 rsp=ffff9200ce072290 rbp=0000000000000000
    r8=ffff8087ed689460 r9=0000000000000001 r10=0000000fffffffff
    r11=ffffe28000000000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up ei ng nz na po nc
    nt! ?? ::FNODOBFM::`string'+0x2cbc9:
    fffff800`a1190759 488b4628 mov rax,qword ptr [rsi+28h] ds:00000000`00000028=????????????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff800a115f829 to fffff800a11546f0

    STACK_TEXT:
    ffff9200`ce071fb8 fffff800`a115f829 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    ffff9200`ce071fc0 fffff800`a115de07 : ffff8087`f5445240 ffff9200`ce0722d1 00000000`00000000 fffff800`a10db600 : nt!KiBugCheckDispatch+0x69
    ffff9200`ce072100 fffff800`a1190759 : ffff374e`9df80d4c ffffea75`3a800000 00000000`00000040 fffff800`a13523b8 : nt!KiPageFault+0x247
    ffff9200`ce072290 fffff800`a1076c9a : 00000000`00000011 ffffea00`0003f600 ffff9200`ce0726b0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x2cbc9
    ffff9200`ce072390 fffff800`a14ecd04 : 00000000`00000003 00000000`00000001 00000000`00066000 00000000`00000000 : nt!MmProbeAndLockPages+0x25a
    ffff9200`ce0724a0 fffff800`a14ec92f : 00000000`025fe600 00000000`00000010 ffff8087`ed6d6320 00000000`00000001 : nt!MmCopyVirtualMemory+0x364
    ffff9200`ce072950 fffff800`a14ec7cb : ffff8087`f568d400 00000000`025fe618 ffff9200`ce072a28 00000000`026fe9f0 : nt!MiReadWriteVirtualMemory+0x15f
    ffff9200`ce0729d0 fffff800`a115f393 : ffffea75`00000050 ffffea75`3a800000 ffffea75`3a9d4000 ffff374e`9df804ec : nt!NtReadVirtualMemory+0x1b
    ffff9200`ce072a10 00007ff8`b25d68b4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
    00000000`025fe5f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`b25d68b4


    STACK_COMMAND: kb

    CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff800a1190044 - nt! ?? ::FNODOBFM::`string'+2c4b4
    [ fa:e2 ]
    fffff800a119044a-fffff800a119044c 3 bytes - nt! ?? ::FNODOBFM::`string'+2c8ba (+0x406)
    [ 40 fb f6:00 75 ea ]
    fffff800a1190478 - nt! ?? ::FNODOBFM::`string'+2c8e8 (+0x2e)
    [ fa:e2 ]
    fffff800a11904a2-fffff800a11904a4 3 bytes - nt! ?? ::FNODOBFM::`string'+2c912 (+0x2a)
    [ 40 fb f6:00 75 ea ]
    fffff800a11904d0 - nt! ?? ::FNODOBFM::`string'+2c940 (+0x2e)
    [ fa:e2 ]
    fffff800a1190833 - nt! ?? ::FNODOBFM::`string'+2cca3 (+0x363)
    [ fa:e2 ]
    fffff800a1190847 - nt! ?? ::FNODOBFM::`string'+2ccb7 (+0x14)
    [ fa:e2 ]
    fffff800a1190920 - nt! ?? ::FNODOBFM::`string'+2cd90 (+0xd9)
    [ fa:e2 ]
    fffff800a119092a - nt! ?? ::FNODOBFM::`string'+2cd9a (+0x0a)
    [ fa:e2 ]
    fffff800a1190e8d-fffff800a1190e8f 3 bytes - nt! ?? ::FNODOBFM::`string'+2d2fd (+0x563)
    [ 40 fb f6:00 75 ea ]
    fffff800a1190eeb - nt! ?? ::FNODOBFM::`string'+2d35b (+0x5e)
    [ fa:e2 ]
    fffff800a1190f96-fffff800a1190f97 2 bytes - nt! ?? ::FNODOBFM::`string'+2d406 (+0xab)
    [ 80 f6:00 ea ]
    19 errors : !nt (fffff800a1190044-fffff800a1190f97)

    MODULE_NAME: memory_corruption

    IMAGE_NAME: memory_corruption

    FOLLOWUP_NAME: memory_corruption

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    MEMORY_CORRUPTOR: LARGE

    FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE

    BUCKET_ID: MEMORY_CORRUPTION_LARGE

    PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_LARGE

    TARGET_TIME: 2017-02-21T14:08:55.000Z

    OSBUILD: 14393

    OSSERVICEPACK: 693

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 272

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-12-21 07:50:57

    BUILDDATESTAMP_STR: 161220-1747

    BUILDLAB_STR: rs1_release

    BUILDOSVER_STR: 10.0.14393.693

    ANALYSIS_SESSION_ELAPSED_TIME: 135b

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:memory_corruption_large

    FAILURE_ID_HASH: {e29154ac-69a4-0eb8-172a-a860f73c0a3c}Attachment 122343Attachment 122344
      My Computer


  2. Posts : 926
    Windows 10 Pro
       #2

    Attention:

    Before posting a BSOD thread, please read the instructions here: Blue Screen of Death (BSOD) Posting Instructions

    If you need to add new information, please make a new post in your initial BSOD thread. Please do not make an extra new thread.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Đ Designer Media Ltd
All times are GMT -5. The time now is 16:54.
Find Us




Windows 10 Forums