TechSpot

Bluescreen a10 7870k windows 10

By ENTY22
Jan 18, 2016
Post New Reply
  1. Hey, I recently had a a10 7870k put onto my pc and now getting blue screens on a new installation of windows 10 with all the updates and now I think its linked to my drivers if you can take a look will add my dmp files in the folder also thanks for any help that can be offered.
     

    Attached Files:

  2. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Do you see any yellow (!) in the device manager? There is a USBfilter.sys driver flagged in the minidumps
     
  3. ENTY22

    ENTY22 TS Rookie Topic Starter

    I don't see any yellow (!) I did notice that raptr was not uninstalled fully the executable and some dll's remained I re-installed and then removed it and seems to be ok but as far as you see would USBfilter.sys be the culprit of the crash?
     
  4. ENTY22

    ENTY22 TS Rookie Topic Starter

    Update had a crash again something to do with nt security check I believe
     
  5. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    Any new minidumps to post?
     
  6. ENTY22

    ENTY22 TS Rookie Topic Starter

    Here it is
     

    Attached Files:

  7. Tmagic650

    Tmagic650 TS Ambassador Posts: 17,244   +234

    What is "raptr"? The latest minidump is not flagging any driver, it just hints at general Windows instability
     
  8. ENTY22

    ENTY22 TS Rookie Topic Starter

    It was part of the AMD catalyst control that seemed to cause issues it records games as you play
     
  9. ENTY22

    ENTY22 TS Rookie Topic Starter

    Do you know what could be causing the instability as it seems to me to be a driver issue that is not working with windows 10 or something I may be missing
     
  10. Cycloid Torus

    Cycloid Torus TS Evangelist Posts: 1,657   +309

  11. ENTY22

    ENTY22 TS Rookie Topic Starter

    ive just done as you said and will monitor if that was the issue behind the crash.
     
  12. ENTY22

    ENTY22 TS Rookie Topic Starter

    The latest dump file from a crash last night im not sure what exactly is the issue could use some guidance thanks.

    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is:
    Windows 10 Kernel Version 10586 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 10586.63.amd64fre.th2_release.160104-1513
    Machine Name:
    Kernel base = 0xfffff802`f1092000 PsLoadedModuleList = 0xfffff802`f1370c70
    Debug session time: Fri Jan 22 01:30:51.050 2016 (UTC + 0:00)
    System Uptime: 0 days 8:11:13.023
    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 D1, {1f80000b0037, ff, 50, 1f80000b0037}

    Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+247 )

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

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    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 kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00001f80000b0037, memory referenced
    Arg2: 00000000000000ff, IRQL
    Arg3: 0000000000000050, value 0 = read operation, 1 = write operation
    Arg4: 00001f80000b0037, address which referenced memory

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


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING: 10586.63.amd64fre.th2_release.160104-1513

    SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.

    SYSTEM_PRODUCT_NAME: G20BM

    SYSTEM_SKU: SKU

    SYSTEM_VERSION: System Version

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 0403

    BIOS_DATE: 11/05/2014

    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

    BASEBOARD_PRODUCT: G20BM

    BASEBOARD_VERSION: Rev X.0x

    DUMP_TYPE: 2

    BUGCHECK_P1: 1f80000b0037

    BUGCHECK_P2: ff

    BUGCHECK_P3: 50

    BUGCHECK_P4: 1f80000b0037

    READ_ADDRESS: fffff802f1410520: Unable to get MiVisibleState
    00001f80000b0037

    CURRENT_IRQL: 0

    FAULTING_IP:
    +0
    00001f80`000b0037 ?? ???

    PROCESS_NAME: System

    ADDITIONAL_DEBUG_TEXT: The trap occurred when interrupts are disabled on the target.

    BUGCHECK_STR: DISABLED_INTERRUPT_FAULT

    CPU_COUNT: 4

    CPU_MHZ: f32

    CPU_VENDOR: AuthenticAMD

    CPU_FAMILY: 15

    CPU_MODEL: 38

    CPU_STEPPING: 1

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    ANALYSIS_SESSION_HOST: DESKTOP-EETIJDT

    ANALYSIS_SESSION_TIME: 01-22-2016 10:08:19.0001

    ANALYSIS_VERSION: 10.0.10586.567 amd64fre

    TRAP_FRAME: ffffd0002050d970 -- (.trap 0xffffd0002050d970)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000200046
    rdx=ffffe000212760f0 rsi=0000000000000000 rdi=0000000000000000
    rip=00001f80000b0037 rsp=ffffd0002050db00 rbp=ffffd0002050dc00
    r8=0000000000000000 r9=0000000000000004 r10=0000000000000000
    r11=fffff802f11e038f r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0 nv up di ng nz na po nc
    00001f80`000b0037 ?? ???
    Resetting default scope

    LAST_CONTROL_TRANSFER: from fffff802f11df2e9 to fffff802f11d4770

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00001f80`000b0037 ?? ???

    STACK_TEXT:
    ffffd000`2050d828 fffff802`f11df2e9 : 00000000`0000000a 00001f80`000b0037 00000000`000000ff 00000000`00000050 : nt!KeBugCheckEx
    ffffd000`2050d830 fffff802`f11ddac7 : 00000000`00000000 00000000`00000000 ffffd000`204e3180 ffffd000`204e3180 : nt!KiBugCheckDispatch+0x69
    ffffd000`2050d970 00001f80`000b0037 : 00000000`00000000 00000000`00000002 ffffe000`212760f0 00000000`00000000 : nt!KiPageFault+0x247
    ffffd000`2050db00 00000000`00000000 : 00000000`00000002 ffffe000`212760f0 00000000`00000000 00000000`00000004 : 0x00001f80`000b0037


    STACK_COMMAND: kb

    THREAD_SHA1_HASH_MOD_FUNC: bf99962f16aee8a6a536cfcc5454c0cd4db15ac9

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 3fc3928ee7b2857c7b0acb22199e00ab7dceb90c

    THREAD_SHA1_HASH_MOD: 2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b

    FOLLOWUP_IP:
    nt!KiPageFault+247
    fffff802`f11ddac7 33c0 xor eax,eax

    FAULT_INSTR_CODE: ffb0c033

    SYMBOL_STACK_INDEX: 2

    SYMBOL_NAME: nt!KiPageFault+247

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME: ntkrnlmp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP: 568b1c58

    IMAGE_VERSION: 10.0.10586.63

    BUCKET_ID_FUNC_OFFSET: 247

    FAILURE_BUCKET_ID: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_nt!KiPageFault

    BUCKET_ID: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_nt!KiPageFault

    PRIMARY_PROBLEM_CLASS: DISABLED_INTERRUPT_FAULT_CODE_AV_BAD_IP_nt!KiPageFault

    TARGET_TIME: 2016-01-22T01:30:51.000Z

    OSBUILD: 10586

    OSSERVICEPACK: 0

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK: 784

    PRODUCT_TYPE: 1

    OSPLATFORM_TYPE: x64

    OSNAME: Windows 10

    OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

    OS_LOCALE:

    USER_LCID: 0

    OSBUILD_TIMESTAMP: 2016-01-05 01:28:56

    BUILDDATESTAMP_STR: 160104-1513

    BUILDLAB_STR: th2_release

    BUILDOSVER_STR: 10.0.10586.63.amd64fre.th2_release.160104-1513

    ANALYSIS_SESSION_ELAPSED_TIME: 1386

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:disabled_interrupt_fault_code_av_bad_ip_nt!kipagefault

    FAILURE_ID_HASH: {f2ab72c5-099d-9077-bfcf-ba12aa825b36}

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

Similar Topics

Add New Comment

You need to be a member to leave a comment. Join thousands of tech enthusiasts and participate.
TechSpot Account You may also...