1. #1

    Post Hello everyone! I am from Asia China, I have a problem with BSOD troubled

    I have read the blue screen death (BSOD) release instructions



    [ATTACH]27195[/ ATTACH]


    Operating system: Windows 10 (Build 14393), 64-bit
    Motherboard: MSI H81M-E33 (MS-7817)
    Display: Default monitor
    Universal Plug and Play display
    Processor: Intel (R) Core (TM) i3-4130 CPU @ 3.40GHz dual-core
    Memory: 4.00 GB
    Hard disk: Samsung Samsung SSD 750 EVO 120GB (120GB) Serial number: S33LNWA554312A Use time: 110 hours Temperature: 42 ℃ Seagate ST3500413AS (500GB) Serial number: 5VM0XZB Use time: 6448 hours Temperature: 43 ℃
    Graphics: iDisplay (Microsoft Corporation - WDDM v1.1) (40 MB)
    NVIDIA GeForce GTX 960
    Sound card: NVIDIA high fidelity audio
    Realtek High Definition Audio
    NIC: Realtek PCIe GBE Series Controller # 3 MAC Address: 4C-CC-6A-D0-EA-32 IP Address: 192.168.2.101
    Outside network IP:
    IE version: 11.1480.14393.0
    Flash version: 26.0.0.137
    Boot time: August 31, 2017 12:47:55 system has been running: 22 hours 48 minutes 1 second
    Last Leave: 2017 August 02 18:16:27
    System installation date: July 14, 2017 23:41:31

    The computer is brand new, except for memory and mechanical hard drives

    My colleague analysis says you need to uninstall

    IDisplay
    mine
    Cubic computer host
    (IDisplay Thunder Cube Computer Master)

    In addition, I also used the popular Microsoft Windbg in China, so we do not have to download a simple view

    Code:
    Microsoft (R) Windows Debugger version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. all rights reserved.
    
    
    
    
    
    
    
    
    Load the dump file [C: \ Users \ Master \ Desktop \ 080317-4093-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    
    
    
    The symbol search path is: SRV * C: \ Symbols * Symbol information
    The executable search path is:
    Windows 7 Kernel Version 14393 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 14393.1480.amd64fre.rs1_release.170706-2004
    Machine Name:
    Kernel base = 0xfffff803`07a1b000 PsLoadedModuleList = 0xfffff803`07d1a040
    Debug session time: Thu Aug 3 12: 47: 27.688 2017 (UTC + 8:00)
    System Uptime: 0 days 18: 30: 48.463
    Loading Kernel Symbols
    .................................................. .............
    .................................................. ..............
    ...................................
    Loading User Symbols
    Loading unloaded module list
    ...............
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************
    
    
    
    
    Use! Analyze-v to get detailed debugging information
    
    
    
    
    BugCheck 3B, {c0000005, fffff80307e4ecc5, ffffa781777cfe20, 0}
    
    
    
    
    Probably caused by: memory_corruption
    
    
    
    
    Followup: memory_corruption
    ---------
    
    
    
    
    0: kd>! Analyze -v
    ************************************************** *****************************
    * *
    * Bugcheck Analysis *
    * *
    ************************************************** *****************************
    
    
    
    
    SYSTEM_SERVICE_EXCEPTION (3b)
    An exception happened while executing a system service routine.
    Arguments:
    Arg1: 00000000c0000005, Exception code that caused the bugcheck
    Arg2: fffff80307e4ecc5, Address of the instruction which caused the bugcheck
    Arg3: ffffa781777cfe20, Address of the context record for the exception that caused the bugcheck
    Arg4: 0000000000000000, zero.
    
    
    
    
    Debugging Details:
    ------------------
    
    
    
    
    
    
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - 0x% p
    
    
    
    
    FAULTING_IP:
    The NT RtlIsValidProcessTrustLabelSid + 1D
    Fffff803`07e4ecc5 80790102 cmp bytes ptr [rcx + 1], 2
    
    
    
    
    Context: ffffa781777cfe20 - (.cxr 0xffffa781777cfe20)
    Rax = ffff65799b7be7d9 rbx = ffffa781777d09e0 rcx = 0000020000000000
    Rdx = 0000020000000000 rsi = ffff93094ddb7340 rdi = ffff930940187060
    Rip = fffff80307e4ecc5 rsp = ffffa781777d0820 rbp = ffffa781777d08f9
    R8 = 0000000000000000 r9 = ffffa781777d08a1 r10 = 0000020000000000
    R11 = 0000000000000000 r12 = 0000000000000000 r13 = ffff930940187060
    R14 = 0000000000000000 r15 = 0000000000000001
    Iopl = 0 nv up ei pl zr na po nc
    Cs = 0010 ss = 0018 ds = 002b es = 002b fs = 0053 gs = 002b efl = 00010246
    The NT RtlIsValidProcessTrustLabelSid + 0x1d:
    Fffff803`07e4ecc5 80790102 cmp byte ptr [rcx + 1], 2 ds: 002b: 00000200`00000001 = ??
    Reset the default range
    
    
    
    
    CUSTOMER_CRASH_COUNT: 1
    
    
    
    
    DEFAULT_BUCKET_ID: CODE_CORRUPTION
    
    
    
    
    BUGCHECK_STR: 0x3B
    
    
    
    
    PROCESS_NAME: svchost.exe
    
    
    
    
    CURRENT_IRQL: 0
    
    
    
    
    LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80307e4ecc5
    
    
    
    
    STACK_TEXT:
    Lt; / RTI & RtlIsValidProcessTrustLabelSid + 0x1d
    
    
    
    
    
    
    
    
    CHKIMG_EXTENSION :! Chkimg -lo 50 -d! Nt
    Fffff80307a6d1f4-fffff80307a6d1f5 2 bytes - nt! MiCompletePrivateZeroFault + 44
        [80 f6: 00 d6]
    Fffff80307b2e2dd-fffff80307b2e2de2 bytes - nt! MiPurgeZeroList + 6d (+ 0xc10e9)
        [80 fa: 00 bc]
    Fffff80307c63387-fffff80307c63389 3 bytes - nt! ExFreePoolWithTag + 387
        [40 fb f6: 00 6b d6]
    7 wrong:! Nt (fffff80307a6d1f4-fffff80307c63389)
    
    
    
    
    MODULE_NAME: memory_corruption
    
    
    
    
    IMAGE_NAME: memory_corruption
    
    
    
    
    FOLLOWUP_NAME: memory_corruption
    
    
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    
    
    
    
    MEMORY_CORRUPTOR: Large
    
    
    
    
    STACK_COMMAND: .cxr 0xffffa781777cfe20; KB
    
    
    
    
    FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
    
    
    
    
    BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
    
    
    
    
    Follow up: memory_corruption
    ---------
    Attached Files Attached Files
    Last edited by jcgriff2; 08-05-2017 at 11:55 PM. Reason: code box


    • Ad Bot

      advertising
      Beep.

        
       

  2. #2

    Join Date
    Jul 2017
    Location
    Cambridge, UK
    Age
    58
    Posts
    65

    Re: Hello everyone! I am from Asia China, I have a problem with BSOD troubled

    Hello Lukeash,

    I have had a look at your mini-dump file but there is no indication that I can find as to which driver might be causing the crash. Memory corruption in this case is most likely caused by the driver rather than faulty RAM.

    If the computer is brand new you do not really want to be messing about inside the case because you might void your warranty. I would take it back to the store if these BSOD problems persist. If you built it yourself it is a different matter. I also notice you are using WinDivert, this usually implies that software is being illegally used and if so further help will not be given.

  3. #3

    Re: Hello everyone! I am from Asia China, I have a problem with BSOD troubled

    Thank you very much. I'm going to stay at this good forum to improve my English level

Similar Threads

  1. Replies: 0
    Last Post: 01-19-2015, 07:24 PM
  2. Replies: 0
    Last Post: 09-02-2014, 03:17 AM
  3. Cameras Spy Endangered Siberian Tiger in China
    By JMH in forum News You Can Use
    Replies: 0
    Last Post: 06-20-2012, 06:59 PM

Log in

Log in