Windows 10: Got a BSOD probably by skype

Discus and support Got a BSOD probably by skype in Windows 10 BSOD Crashes and Debugging to solve the problem; Was playing a game window mode, and had Skype opened, did an alt+tab on it and got a BSOD. Is it a software problem with Skype? Driver? Faulty RAM?... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by EduardRuben, Apr 8, 2020.

  1. EDUARDRUBEN
    EduardRuben Win User

    Got a BSOD probably by skype


    Was playing a game window mode, and had Skype opened, did an alt+tab on it and got a BSOD.

    Is it a software problem with Skype? Driver? Faulty RAM?


    Any help is appreciated.


    This is from WinDbg:



    MEMORY_MANAGEMENT 1a
    # Any other values for parameter 1 must be individually examined.
    Arguments:
    Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
    contains the address of the PFN for the corrupted page table page.
    On a 32 bit OS, parameter 2 contains a pointer to the number of used
    PTEs, and parameter 3 contains the number of used PTEs.
    Arg2: ffff9a000361cf80
    Arg3: 0000000000000003
    Arg4: 0000000000000004

    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: System manufacturer

    SYSTEM_PRODUCT_NAME: System Product Name

    SYSTEM_SKU: SKU

    SYSTEM_VERSION: System Version

    BIOS_VENDOR: American Megatrends Inc.

    BIOS_VERSION: 1302

    BIOS_DATE: 03/15/2018

    BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

    BASEBOARD_PRODUCT: PRIME Z270-A

    BASEBOARD_VERSION: Rev 1.xx

    DUMP_TYPE: 1

    BUGCHECK_P1: 41790

    BUGCHECK_P2: ffff9a000361cf80

    BUGCHECK_P3: 3

    BUGCHECK_P4: 4

    BUGCHECK_STR: 0x1a_41790

    CPU_COUNT: 8

    CPU_MHZ: 1068

    CPU_VENDOR: GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 9e

    CPU_STEPPING: 9

    CPU_MICROCODE: 6,9e,9,0 F,M,S,R SIG: 8E'00000000 cache 8E'00000000 init

    BLACKBOXBSD: 1 !blackboxbsd


    BLACKBOXNTFS: 1 !blackboxntfs


    BLACKBOXPNP: 1 !blackboxpnp


    BLACKBOXWINLOGON: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    PROCESS_NAME: Skype.exe

    CURRENT_IRQL: 2

    ANALYSIS_SESSION_HOST: DESKTOP-4UTFG8P

    ANALYSIS_SESSION_TIME: 04-08-2020 12:06:24.0742

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    LAST_CONTROL_TRANSFER: from fffff8007fa38538 to fffff8007f9c2360

    STACK_TEXT:
    fffff403`37029b68 fffff800`7fa38538 : 00000000`0000001a 00000000`00041790 ffff9a00`0361cf80 00000000`00000003 : nt!KeBugCheckEx
    fffff403`37029b70 fffff800`7f8e8517 : 00000000`00000003 fffff403`3702a2c0 fffff403`3702a2c0 fffff403`3702a210 : nt!MiDeletePteRun+0x188a88
    fffff403`37029d90 fffff800`7f8e4032 : ffff870c`c048e9c0 ffffd580`0000d000 00000000`00004000 00000000`00000000 : nt!MiDeleteVaTail+0x77
    fffff403`37029dc0 fffff800`7f8e41c1 : fffff403`3702a210 ffffd5ea`c0000060 00000000`00000000 0a000001`209a8867 : nt!MiWalkPageTablesRecursively+0x512
    fffff403`37029e80 fffff800`7f8e41c1 : fffff403`3702a210 ffffd5ea`f5600000 00000000`00000000 0a000004`34928867 : nt!MiWalkPageTablesRecursively+0x6a1
    fffff403`37029f40 fffff800`7f8e41c1 : fffff403`3702a210 ffffd5ea`f57ab000 ffffd5ea`00000000 8a000003`fad27867 : nt!MiWalkPageTablesRecursively+0x6a1
    fffff403`3702a000 fffff800`7f8e394c : fffff403`3702a210 ffffd5ea`f57abd58 fffff403`00000000 fffff403`3702a189 : nt!MiWalkPageTablesRecursively+0x6a1
    fffff403`3702a0c0 fffff800`7f8e1db8 : fffff403`3702a210 00000000`00000002 00000000`00000001 00000000`00000000 : nt!MiWalkPageTables+0x36c
    fffff403`3702a1c0 fffff800`7f8eff10 : ffffffff`ffffffff ffff870c`c048e838 fffff403`00000001 00000000`00000000 : nt!MiDeletePagablePteRange+0x268
    fffff403`3702a560 fffff800`7fe7979d : ffff870c`c44f5080 ffff870c`c44f5080 ffff870c`c6f02580 ffff870c`c048e830 : nt!MiDeleteVad+0x860
    fffff403`3702a720 fffff800`7fe884d0 : ffff870c`c6f02580 ffff870c`be0cd9d0 ffff870c`c44f5080 00000000`00000000 : nt!MiUnmapVad+0x49
    fffff403`3702a750 fffff800`7fe87a3f : ffff870c`c6f04100 ffff870c`c6f04100 ffff870c`c048e4c0 fffff800`7fc6a440 : nt!MiCleanVad+0x30
    fffff403`3702a780 fffff800`7fdde469 : ffffffff`00000000 ffffffff`ffffffff fffff403`3702aa01 ffff870c`c048e4c0 : nt!MmCleanProcessAddressSpace+0x137
    fffff403`3702a800 fffff800`7fed1473 : ffff870c`c048e4c0 ffff9e05`c80d0060 fffff403`3702aa80 00000000`00000000 : nt!PspRundownSingleProcess+0x139
    fffff403`3702a880 fffff800`7fe6fd2b : 00000000`00000000 fffff403`3702aa01 00000000`0a1d8000 ffff870c`c44f5080 : nt!PspExitThread+0x60b
    fffff403`3702a990 fffff800`7f9d414e : ffff870c`000051f8 ffff870c`c44f5080 ffff870c`c048e4c0 00000000`00000000 : nt!NtTerminateProcess+0xeb
    fffff403`3702aa00 00000000`771f1cbc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x2b9
    00000000`0068ea08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x771f1cbc


    THREAD_SHA1_HASH_MOD_FUNC: b79b463ae9ce57a8c77ea389a67e316ec989b8c2

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 173dde7c8ee223699c1eda06b2f2dc09532aa33d

    THREAD_SHA1_HASH_MOD: aaa5a324bf1bd3082ad2b464ee2ed2f6d50e564c

    FOLLOWUP_IP:
    nt!MiDeletePteRun+188a88
    fffff800`7fa38538 cc int 3

    FAULT_INSTR_CODE: 4d8d48cc

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: nt!MiDeletePteRun+188a88

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 0

    STACK_COMMAND: .thread ; .cxr ; kb

    IMAGE_NAME: memory_corruption

    BUCKET_ID_FUNC_OFFSET: 188a88

    FAILURE_BUCKET_ID: 0x1a_41790_nt!MiDeletePteRun

    BUCKET_ID: 0x1a_41790_nt!MiDeletePteRun

    PRIMARY_PROBLEM_CLASS: 0x1a_41790_nt!MiDeletePteRun

    TARGET_TIME: 2020-04-08T10:55:04.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: 2b81

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x1a_41790_nt!mideletepterun

    FAILURE_ID_HASH: {27ce5d5a-97b1-faf0-183f-c86809269d56}

    Followup: MachineOwner

    :)
     
    EduardRuben, Apr 8, 2020
    #1
  2. THEDIVINEHAIRBAND
    thedivinehairband Win User

    Skype?

    As this is a now quite established messenger system of sorts perhaps a Skype feature for people skype names so perhaps some real time problem solving/discussions could be mounted?
    Just a wee suggestion.
    What does everyone else think?
     
    thedivinehairband, Apr 8, 2020
    #2
  3. DEEPIKA GOWDA
    Deepika Gowda Win User
    skype doesn't closing even after clicking "Quit skype"

    Hi Ashok,

    Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

    I understand the inconvenience that you are unable to close Skype app on your computer, we will help you with this issue.

    I suggest you to uninstall and re-install the latest version of Skype on your device and check.

    Method 1: Remove the earlier versions of the Skype and then install the latest version.

    Step 1: Uninstall Skype from the Start Screen:


    • On the Start screen, type
      Skype      .

    • From the list select Skype and right click on it.

    • You will get different options on the screen .Select
      Uninstall.
    Step 2: You can also uninstall a program from the Control Panel:


    • Press Windows + x key to open a task list from the bottom left corner of the screen.

    • Select Control Panel. Click on
      Programs      .

    • Select Programs and Features.

    • Double click on Skype and follow the onscreen instructions.


    Refer the below link to download the Skype app for the devices:

    Download Skype | Free calls | Chat app



    Hope this information is helpful. Kindly update with the status of this issue, we will be happy to assist you better.
     
    Deepika Gowda, Apr 8, 2020
    #3
  4. DEEPIKA GOWDA
    Deepika Gowda Win User

    Got a BSOD probably by skype

    Skype Microphone echo only on 1 Win Pc

    Hi,

    Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

    Do let us know the troubleshooting steps that you have tried to resolve the issue?

    As the issue persists with the Skype app, I suggest you to try the below if not yet tried and check if it helps:

    • Try to log-in to Skype using different account on the same computer, access the microphone and check if the issue persists.
    • Try to log-in to Skype account on different computer using this account, access the microphone and check.

    Also try the below if the issue still persists.

    Step 1: I suggest you to run the Windows app troubleshooter to check if the issue persists.

    Refer: Run the troubleshooter for Windows apps

    If issue still persists,

    Step 2: Uninstall and re-install Skype from Windows Store.

    You can also uninstall Skype app from the Control Panel:


    • Press Windows + x key to open a task list from the bottom left corner of the screen.

    • Select Control Panel.

    • Select Programs and Features.

    • Right click on Skype
      and select uninstall and follow the onscreen instructions.

    Steps to Install Skype app:
    Log-in with administrator account, open
    Windows Store, search for Skype app and download latest version.

    Hope it helps. Reply to the post with an updated status of this issue, we will be happy to help you further.
     
    Deepika Gowda, Apr 8, 2020
    #4
Thema:

Got a BSOD probably by skype

Loading...

  1. Got a BSOD probably by skype - Similar Threads - Got BSOD probably

  2. BSOD Errors probably related to SSD

    in Windows 10 Gaming
    BSOD Errors probably related to SSD: Have experienced twice a BSOD in during the evening, both time i can find hints that SSD driver? could be involved. Please help understangind the dump files and finding and fixing the cuase of this error. Copying content from one of the crash dumps:************ Preparing the...

  3. Random bsod probably after sleep

    in Windows 10 BSOD Crashes and Debugging
    Random bsod probably after sleep: Hello !MoboAB350M-D3HF52G biosWindows 10 proBsodINTERNAL_POWER_ERRORntoskrnl.exe ntoskrnl.exe+56a875 fffff804`3cc00000 fffff804`3dc46000 0x01046000 0xc103e0da 12.08.2072 22:47:38 What can cause problem?Already run sfc/scannow chkdsk dism and etc.Here is the link to minidump...

  4. Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD

    in Windows 10 Gaming
    Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD: This is my first experience with this specific BSOD. I have not manually updated any drivers recently so I'm not quite sure of the issue, although it could be related to the NVIDIA display drivers I installed approx 1 month ago.Microsoft R Windows Debugger Version...

  5. Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD

    in Windows 10 Software and Apps
    Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD: This is my first experience with this specific BSOD. I have not manually updated any drivers recently so I'm not quite sure of the issue, although it could be related to the NVIDIA display drivers I installed approx 1 month ago.Microsoft R Windows Debugger Version...

  6. Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD

    in Windows 10 BSOD Crashes and Debugging
    Probable cause of "CRITICAL_STRUCTURE_CORRUPTION" BSOD: This is my first experience with this specific BSOD. I have not manually updated any drivers recently so I'm not quite sure of the issue, although it could be related to the NVIDIA display drivers I installed approx 1 month ago.Microsoft R Windows Debugger Version...

  7. Problem with BSOD probably a driver

    in Windows 10 Drivers and Hardware
    Problem with BSOD probably a driver: Since about 3-4 weeks I have been getting BSOD's almost every time I start up my system. They vary in message but most of them are things like MEMORY_MANAGEMENT or ISQL or some others I can't remember. Using a blue screen viewer I have come to the conclusion that it is always...

  8. bsod probably caused by a driver

    in Windows 10 BSOD Crashes and Debugging
    bsod probably caused by a driver: i was getting bsod error's for a few days so today i decided to run driver verifier and i got a bsod with driver verifier detected violation error, i viewed the minidump file and this issue is apparently being caused by "SteamStreamingMicrophone.sys" driver, how can i fix...

  9. I probably got a virus from a proxy..

    in Windows 10 BSOD Crashes and Debugging
    I probably got a virus from a proxy..: I had to unblock a blocked site in my country, didn't want to pay for a vpn so I just searched up for a proxy on the web. After 2 hours, the games I play got slower. I had around 200 FPS in minecraft on max settings, now I get 30 to 20 fps on low settings. Also I got my pc...

  10. BSOD Probably caused by : memory_corruption

    in Windows 10 BSOD Crashes and Debugging
    BSOD Probably caused by : memory_corruption: Hi, My computer frequently has BSOD. I have used windbg to analyze 800mb dump file as attached bellow: please help , thank you! Microsoft (R) Windows Debugger Version 10.0.17763.1 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File...