hello: bluescreen DSOD on login win10 1909 -DISABLE AMD VGA SOLVE PROB


  1. Posts : 1
    wındows 10 1909
       #1

    hello: bluescreen DSOD on login win10 1909 -DISABLE AMD VGA SOLVE PROB


    hello: bluescreen DSOD on login win10 1909 -DISABLE AMD VGA OR DISABLE VIRTUALITY LIKE VHD OR SANDBOX
    BSOD GOAWAY


    Code:
    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\---------\Desktop\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
    
    
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 10 Kernel Version 18362 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff805`66800000 PsLoadedModuleList = 0xfffff805`66c48150
    Debug session time: Wed Mar 18 22:22:23.803 2020 (UTC + 3:00)
    System Uptime: 0 days 0:06:13.531
    Loading Kernel Symbols
    .......................................Page 200128c7f too large to be in the dump file.
    Page 200128c7e too large to be in the dump file.
    ........................
    ................................................................
    ................................................................
    ....
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 00000000`01152018).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ......
    For analysis of this file, run !analyze -v
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    APC_INDEX_MISMATCH (1)
    This is a kernel internal error. The most common reason to see this
    bugcheck is when a filesystem or a driver has a mismatched number of
    calls to disable and re-enable APCs. The key data item is the
    Thread->CombinedApcDisable field. This consists of two separate 16-bit
    fields, the SpecialApcDisable and the KernelApcDisable. A negative value
    of either indicates that a driver has disabled special or normal APCs
    (respectively) without re-enabling them; a positive value indicates that
    a driver has enabled special or normal APCs (respectively) too many times.
    Arguments:
    Arg1: 00007ffa9097ca04, Address of system call function or worker routine
    Arg2: 0000000000000000, Thread->ApcStateIndex
    Arg3: 00000000ffffffff, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
    Arg4: ffffa4809ed8eb80, Call type (0 - system call, 1 - worker routine)
    
    Debugging Details:
    ------------------
    
    
    KEY_VALUES_STRING: 1
    
    
    PROCESSES_ANALYSIS: 1
    
    SERVICE_ANALYSIS: 1
    
    STACKHASH_ANALYSIS: 1
    
    TIMELINE_ANALYSIS: 1
    
    
    DUMP_CLASS: 1
    
    DUMP_QUALIFIER: 401
    
    BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202
    
    SYSTEM_MANUFACTURER:  SAMSUNG ELECTRONICS CO., LTD.
    
    SYSTEM_PRODUCT_NAME:  350V5C/351V5C/3540VC/3440VC
    
    SYSTEM_SKU:  P08ABE.011.CP
    
    SYSTEM_VERSION:  P08ABE.011.CP
    
    BIOS_VENDOR:  American Megatrends Inc.
    
    BIOS_VERSION:  P08ABE
    
    BIOS_DATE:  02/23/2013
    
    BASEBOARD_MANUFACTURER:  SAMSUNG ELECTRONICS CO., LTD.
    
    BASEBOARD_PRODUCT:  NP350V5C-S0JTR
    
    BASEBOARD_VERSION:  BOARD REVISION 00
    
    DUMP_TYPE:  1
    
    BUGCHECK_P1: 7ffa9097ca04
    
    BUGCHECK_P2: 0
    
    BUGCHECK_P3: ffffffff
    
    BUGCHECK_P4: ffffa4809ed8eb80
    
    FAULTING_IP: 
    +0
    00007ffa`9097ca04 ??              ???
    
    CPU_COUNT: 4
    
    CPU_MHZ: a22
    
    CPU_VENDOR:  GenuineIntel
    
    CPU_FAMILY: 6
    
    CPU_MODEL: 3a
    
    CPU_STEPPING: 9
    
    CPU_MICROCODE: 6,3a,9,0 (F,M,S,R)  SIG: 20'00000000 (cache) 20'00000000 (init)
    
    BLACKBOXBSD: 1 (!blackboxbsd)
    
    
    BLACKBOXNTFS: 1 (!blackboxntfs)
    
    
    BLACKBOXWINLOGON: 1
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    BUGCHECK_STR:  0x1
    
    PROCESS_NAME:  Steam.exe
    
    CURRENT_IRQL:  0
    
    ANALYSIS_SESSION_HOST:  DESKTOP-9AU5H3U
    
    ANALYSIS_SESSION_TIME:  03-18-2020 23:25:06.0007
    
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffff805669d41e9 to fffff805669c2380
    
    STACK_TEXT:  
    ffffa480`9ed8e948 fffff805`669d41e9 : 00000000`00000001 00007ffa`9097ca04 00000000`00000000 00000000`ffffffff : nt!KeBugCheckEx
    ffffa480`9ed8e950 fffff805`669d4093 : 00000000`00000000 00000000`00000001 00000000`014ef38c ffffa480`9ed8eb80 : nt!KiBugCheckDispatch+0x69
    ffffa480`9ed8ea90 00007ffa`9097ca04 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x1fe
    00000000`00b4e478 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`9097ca04
    
    
    THREAD_SHA1_HASH_MOD_FUNC:  1b1fd012b2a510c586295e696f84a9476c8f91e5
    
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6a054393ae1713fef08345a54701ed3a92fa10c6
    
    THREAD_SHA1_HASH_MOD:  2a7ca9d3ab5386d53fea7498e1d81b9c4a4c036b
    
    FOLLOWUP_IP: 
    nt!KiSystemServiceExitPico+1fe
    fffff805`669d4093 4883ec50        sub     rsp,50h
    
    FAULT_INSTR_CODE:  50ec8348
    
    SYMBOL_STACK_INDEX:  2
    
    SYMBOL_NAME:  nt!KiSystemServiceExitPico+1fe
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nt
    
    IMAGE_NAME:  ntkrnlmp.exe
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  0
    
    STACK_COMMAND:  .thread ; .cxr ; kb
    
    BUCKET_ID_FUNC_OFFSET:  1fe
    
    FAILURE_BUCKET_ID:  0x1_SysCallNum_4a_nt!KiSystemServiceExitPico
    
    BUCKET_ID:  0x1_SysCallNum_4a_nt!KiSystemServiceExitPico
    
    PRIMARY_PROBLEM_CLASS:  0x1_SysCallNum_4a_nt!KiSystemServiceExitPico
    
    TARGET_TIME:  2020-03-18T19:22:23.000Z
    
    OSBUILD:  18362
    
    OSSERVICEPACK:  0
    
    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:  unknown_date
    
    BUILDDATESTAMP_STR:  190318-1202
    
    BUILDLAB_STR:  19h1_release
    
    BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202
    
    ANALYSIS_SESSION_ELAPSED_TIME:  5006
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x1_syscallnum_4a_nt!kisystemserviceexitpico
    
    FAILURE_ID_HASH:  {0a11deae-715f-8dfb-4637-78b71080853b}
    
    Followup:     MachineOwner
    ---------
    Last edited by Brink; 18 Mar 2020 at 15:47. Reason: code box
      My Computer


  2. Posts : 1,260
    Windows 8.1 Enterprise x64
       #2
      My Computer


  3. Posts : 392
    W10
       #3

    In the past I had 2 issues with my Samsung laptop:
    - Windows Updates not installing
    - Issues with the AMD video driver

    Turns out the Windows Update issues where caused by Samsung (I found info on this on the web)
    And the AMD driver problem was because it was modified by someone to be signed by Intel - which rendered the AMD version unworkable. This renderred the system useless for gaming.


    As such, I wiped the computer and clean installed W10.
    I also got another laptop - so I stopped gaming on the Samsung

    But the Samsung has been my "test" machine eversince - working quite well with nearly every Fast Ring Insider build that I've installed on it. Just recently (in the last 2 or 3 builds) I've started getting an AMD video driver error - but it can easily be dismissed through the error dialog box.

    In short, I suggest making a disk image of the current installation (just in case you want to go back) and then do a clean install of W10 using the Microsoft Media Creation Tool to install W10 (without the Samsung stuff that it has now).

    Good luck!
      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 08:11.
Find Us




Windows 10 Forums