Windows 10: Possible solution for Dump analysis

Discus and support Possible solution for Dump analysis in Windows 10 Installation and Upgrade to solve the problem; I understand from below analysis that Blue Coat is causing the problems, How can i fix the issue i can safe boot into networking /CMD, This package... Discussion in 'Windows 10 Installation and Upgrade' started by ankarora, Aug 25, 2020.

  1. ankarora Win User

    Possible solution for Dump analysis


    I understand from below analysis that Blue Coat is causing the problems,


    How can i fix the issue i can safe boot into networking /CMD, This package is not getting installed i have tried disabling it from MSCONFIG & STARTUP & Turnning off the Services of the same but still my machine is continous restarting with error your PC ran into problem


    Possible solution for Dump analysis 1f45aecb-d65a-41f0-be1e-a2f921dac92a?upload=true.jpg


    ============================================================================

    Microsoft R Windows Debugger Version 10.0.19041.1 X86

    Copyright c Microsoft Corporation. All rights reserved.





    Loading Dump File [G:\2018\MEMORY.DMP]

    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.



    Symbol search path is: srv*

    Executable search path is:

    Windows 10 Kernel Version 17134 MP 8 procs Free x64

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 17134.1.amd64fre.rs4_release.180410-1804

    Machine Name:

    Kernel base = 0xfffff800`cb619000 PsLoadedModuleList = 0xfffff800`cb9c5ce0

    Debug session time: Tue Aug 25 09:01:46.159 2020 UTC + 5:30

    System Uptime: 0 days 0:04:59.161

    Loading Kernel Symbols

    .Page 200003613 too large to be in the dump file.

    ..Page 200204e79 too large to be in the dump file.

    ...................................Page 200066698 too large to be in the dump file.

    .........Page 200216439 too large to be in the dump file.

    ................

    .Page 20021cee4 too large to be in the dump file.

    .....Page 2002182ad too large to be in the dump file.

    Page 200213fe8 too large to be in the dump file.

    .....Page 20000cc8e too large to be in the dump file.

    ...Page 20000cc8e too large to be in the dump file.

    Page 200211ec9 too large to be in the dump file.

    .Page 20000cc8e too large to be in the dump file.

    ...Page 20021c25a too large to be in the dump file.

    ......Page 2002182cd too large to be in the dump file.

    ...Page 200216f5e too large to be in the dump file.

    ..Page 200211d9c too large to be in the dump file.

    ...Page 20021cc03 too large to be in the dump file.

    .Page 20001e629 too large to be in the dump file.

    ....Page 20021cd9f too large to be in the dump file.

    .Page 20021cd52 too large to be in the dump file.

    ..Page 20021cd52 too large to be in the dump file.

    .Page 200216559 too large to be in the dump file.

    .Page 200216559 too large to be in the dump file.

    .Page 20021a52d too large to be in the dump file.

    .Page 20021cc7e too large to be in the dump file.

    .Page 200210d80 too large to be in the dump file.

    .Page 20021c402 too large to be in the dump file.

    .Page 20021cc7e too large to be in the dump file.

    .Page 200211cd0 too large to be in the dump file.

    .Page 200211e48 too large to be in the dump file.

    .Page 20021cc7e too large to be in the dump file.

    ..Page 200211cd0 too large to be in the dump file.

    ...Page 200210dd5 too large to be in the dump file.

    .Page 200210dd5 too large to be in the dump file.

    .Page 200216559 too large to be in the dump file.

    ..Page 200211e48 too large to be in the dump file.

    ..Page 200212cc9 too large to be in the dump file.

    ..Page 20020ab33 too large to be in the dump file.

    .

    Page 20021914c too large to be in the dump file.

    ..Page 200210d80 too large to be in the dump file.

    .Page 200214cfb too large to be in the dump file.

    .Page 200002c3f too large to be in the dump file.

    .Page 20021834e too large to be in the dump file.

    ..Page 200211d15 too large to be in the dump file.

    .Page 20021c402 too large to be in the dump file.

    .Page 20001f494 too large to be in the dump file.

    ...Page 200212cc9 too large to be in the dump file.

    .Page 20020aaf3 too large to be in the dump file.

    ..Page 2002158c4 too large to be in the dump file.

    .Page 200210de1 too large to be in the dump file.

    .Page 20021d842 too large to be in the dump file.

    .Page 2000144e2 too large to be in the dump file.

    .Page 200216559 too large to be in the dump file.

    .Page 200211e48 too large to be in the dump file.

    ..Page 200216ffc too large to be in the dump file.

    .Page 20021a787 too large to be in the dump file.

    .Page 200021bac too large to be in the dump file.

    ..Page 200211d9c too large to be in the dump file.

    .Page 200029739 too large to be in the dump file.

    .Page 20021d9c7 too large to be in the dump file.

    ..Page 200216ee9 too large to be in the dump file.

    .Page 200210d10 too large to be in the dump file.

    .Page 20003cc29 too large to be in the dump file.

    ...Page 200042b48 too large to be in the dump file.

    ......Page 200041917 too large to be in the dump file.

    .....Page 20007fc59 too large to be in the dump file.

    .Page 20021d681 too large to be in the dump file.

    ..Page 20007f086 too large to be in the dump file.

    ...............

    ..



    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

    ........

    For analysis of this file, run !analyze -v

    4: kd> !analyze -v

    *******************************************************************************

    * *

    * Bugcheck Analysis *

    * *

    *******************************************************************************



    BAD_POOL_CALLER c2

    The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.

    Arguments:

    Arg1: 000000000000009b, Attempt to allocate pool with a tag of zero. This would make the pool untrackable and worse, corrupt the existing tag tables.

    Arg2: 0000000000000200, Pool type

    Arg3: 00000000000000c0, Size of allocation in bytes

    Arg4: fffff80466bb694d, Caller's address.



    Debugging Details:

    ------------------



    Page 20021aed8 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    Page 200003236 too large to be in the dump file.



    KEY_VALUES_STRING: 1



    Key : Analysis.CPU.Sec

    Value: 4



    Key : Analysis.DebugAnalysisProvider.CPP

    Value: Create: 8007007e on DESKTOP-VD2PCVJ



    Key : Analysis.DebugData

    Value: CreateObject



    Key : Analysis.DebugModel

    Value: CreateObject



    Key : Analysis.Elapsed.Sec

    Value: 26



    Key : Analysis.Memory.CommitPeak.Mb

    Value: 72



    Key : Analysis.System

    Value: CreateObject





    BUGCHECK_CODE: c2



    BUGCHECK_P1: 9b



    BUGCHECK_P2: 200



    BUGCHECK_P3: c0



    BUGCHECK_P4: fffff80466bb694d



    BLACKBOXBSD: 1 !blackboxbsd





    BLACKBOXPNP: 1 !blackboxpnp





    PROCESS_NAME: System



    STACK_TEXT:

    Page 200003235 too large to be in the dump file.

    Page 200003235 too large to be in the dump file.

    ffffd804`8465f428 fffff800`cbe36443 : 00000000`000000c2 00000000`0000009b 00000000`00000200 00000000`000000c0 : nt!KeBugCheckEx

    ffffd804`8465f430 fffff800`cbe50ca9 : 00000000`00000280 fffff804`66bb694d 00000000`000000c0 ffffd804`8465f530 : nt!VerifierBugCheckIfAppropriate+0xdf

    ffffd804`8465f470 fffff800`cbe2bdea : 00000000`000000c0 00000000`00000020 00000000`00000280 00000000`00000000 : nt!ExAllocatePoolSanityChecks+0x59

    ffffd804`8465f4b0 fffff804`66b27c52 : 00000000`00000280 00000000`000000c0 00000000`00000000 00000000`00000000 : nt!VeAllocatePoolWithTagPriority+0x8a

    ffffd804`8465f520 fffff800`cbe2c4d7 : 00000000`00000280 00000000`00000200 00000000`000000c0 fffff800`cbe3dbe3 : VerifierExt!ExAllocatePoolWithTagPriority_internal_wrapper+0x82

    ffffd804`8465f560 fffff804`66bb694d : 00000000`000000c0 fffff68b`ad160e10 fffff68b`ad1daf90 00000000`00000070 : nt!VerifierExAllocatePoolWithTag+0x87

    ffffd804`8465f5b0 fffff804`66bd5e21 : 00000000`00000000 00000000`00000000 00000000`00000200 fffff68b`ad160e10 : Wdf01000!FxPoolAllocator+0x6d [minkernel\wdf\framework\shared\object\wdfpool.cpp @ 337]

    ffffd804`8465f600 fffff800`cab1bea9 : fffff68b`ad140de0 ffffd804`8465f749 ffff8b08`bd87de60 00000000`80000000 : Wdf01000!imp_WdfRegistryOpenKey+0x141 [minkernel\wdf\framework\shared\support\fxregistryapi.cpp @ 128]

    ffffd804`8465f6f0 fffff800`cab2b255 : 00000000`00000000 00000000`00000000 ffff8b08`bd87de60 fffff68b`ad140de0 : bcua_wfp+0xbea9

    ffffd804`8465f7b0 fffff800`cab228cc : 00000000`00000000 00000000`00000000 ffff8b08`bd839e40 fffff68b`ad160e10 : bcua_wfp+0x1b255

    ffffd804`8465f830 fffff800`cbc104c9 : 00000000`00000000 ffffd804`8465f960 ffff8b08`bd87de60 ffffffff`800019b4 : bcua_wfp+0x128cc

    ffffd804`8465f860 fffff800`cbc0efb6 : fffff800`cba80240 00000000`00000000 00000000`00000000 fffff68b`ad190fb0 : nt!IopLoadDriver+0x4bd

    ffffd804`8465fa40 fffff800`cb73eee5 : 00000000`00000000 ffffffff`800019b4 ffff8b08`bb2a23d0 ffff8b08`be1f93c0 : nt!IopLoadUnloadDriver+0x56

    ffffd804`8465fa80 fffff800`cb6b1fa7 : ffff8b08`be1f93c0 00000000`00000080 ffff8b08`bb29d040 ffff8b08`be1f93c0 : nt!ExpWorkerThread+0xf5

    ffffd804`8465fb10 fffff800`cb7caf36 : ffffc801`cd4b9180 ffff8b08`be1f93c0 fffff800`cb6b1f60 00000000`00000000 : nt!PspSystemThreadStartup+0x47

    ffffd804`8465fb60 00000000`00000000 : ffffd804`84660000 ffffd804`84659000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16





    SYMBOL_NAME: bcua_wfp+bea9



    MODULE_NAME: bcua_wfp



    IMAGE_NAME: bcua-wfp.sys



    IMAGE_VERSION: 4.10.1.23382



    STACK_COMMAND: .thread ; .cxr ; kb



    BUCKET_ID_FUNC_OFFSET: bea9



    FAILURE_BUCKET_ID: 0xc2_9b_VRF_bcua_wfp!unknown_function



    OS_VERSION: 10.0.17134.1



    BUILDLAB_STR: rs4_release



    OSPLATFORM_TYPE: x64



    OSNAME: Windows 10



    FAILURE_ID_HASH: {cda573aa-b37b-2fa6-ceb2-0097c03b909d}



    Followup: MachineOwner

    ---------



    4: kd> lmvm bcua_wfp

    Browse full module list

    start end module name

    fffff800`cab10000 fffff800`cab2e000 bcua_wfp no symbols

    Loaded symbol image file: bcua-wfp.sys

    Image path: \SystemRoot\system32\DRIVERS\bcua-wfp.sys

    Image name: bcua-wfp.sys

    Browse all global symbols functions data

    Timestamp: Fri Jun 8 03:03:09 2018 5B19A495

    CheckSum: 000284D3

    ImageSize: 0001E000

    File version: 4.10.1.23382

    Product version: 4.10.1.23382

    File flags: 0 Mask 3F

    File OS: 4 Unknown Win32

    File type: 3.6 Driver

    File date: 00000000.00000000

    Translations: 0409.04b0

    Information from resource tables:

    CompanyName: Blue Coat Systems, Inc.

    ProductName: Blue Coat Unified Agent

    InternalName: bcua-wfp.SYS

    OriginalFilename: bcua-wfp.SYS

    ProductVersion: 4.10.1.219990

    FileVersion: 4.10.1.219990

    FileDescription: BCUA WFP Filter Driver

    LegalCopyright: Copyright C 2013 Blue Coat Systems, Inc.

    :)
     
    ankarora, Aug 25, 2020
    #1
  2. Ryan Fra Win User

    BSOD Dump File Analysis

    Hi,

    Thank you for sharing the dump file. While we are checking the information you've shared, we suggest that you follow the steps on how to
    Troubleshoot blue screen.

    Please let us know the result after following the steps.
     
    Ryan Fra, Aug 25, 2020
    #2
  3. BSOD dump analysis request

    Hi,

    Thank you for posting your query in Microsoft Community.

    I can understand how frustrating it could be when things go unusual.

    I will certainly help you.

    Please provide us the following details:


    • Have you made any changes to the computer prior to this issue?

    • When exactly you get these errors?
    A blue screen error (also called a stop error) can occur if a problem causes your PC to shut down or restart unexpectedly.

    The BAD_POOL_HEADER bug check has a value of 0x00000019.

    The issue occurs because the Hdaudio.sys driver tries to process the audio information when the uninitialized internal firmware memory within the video card is set in a certain manner. The result is internal pool corruption.

    As we are analyzing the dump files, let us try the following steps as a workaround and check if it makes any difference.

    Step 1: Initially, I suggest you to start your computer in safe mode with Networking and check if the issue appears there as well. If it does not appear in safe mode with Networking place the computer in clean
    boot state to identify the culprit program running in the background creating this error.

    Safe Mode is a diagnostic mode that starts your computer in a limited state. Only the basic files and drivers necessary to run Windows are started.

    Refer the article below:

    Start your PC in safe mode in Windows 10

    http://windows.microsoft.com/en-in/windows-10/start-your-pc-in-safe-mode

    Step 2: Let us follow the steps suggested in the following article and check if it helps in resolving the issue.

    Troubleshoot blue screen errors

    http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

    Hope it helps.

    Let us know the status, we are glad to assist you further.
     
    Abdul_Malik, Aug 25, 2020
    #3
  4. BostjanVi Win User

    Possible solution for Dump analysis

    Analysis of crash dump failed

    Hello,

    I've been getting frequent system crashes ("blue screen"), and I'm trying to determine the cause. The latest crash has produced a dump, and I tried to use a Microsoft tool to analyse it; but apparently the analysis failed. Can someone help me discover the
    reason?

    Appreciate any help.

    link to result of dump analysis:

    Dropbox - Link not found

    Regards,

    BV
     
    BostjanVi, Aug 25, 2020
    #4
Thema:

Possible solution for Dump analysis

Loading...
  1. Possible solution for Dump analysis - Similar Threads - Possible solution Dump

  2. BSOD Dump Analysis

    in Windows 10 BSOD Crashes and Debugging
    BSOD Dump Analysis: After applying the latest patches I started getting blue screen errors. I could reboot just fine for a day or so. Now I can only boot into safe mode. I have tried the usual repair scenarios in the troubleshooting but nothing is working. the error is...
  3. Mini Dump Analysis Help Request

    in Windows 10 BSOD Crashes and Debugging
    Mini Dump Analysis Help Request: Long story short after many issues with BSOD, I did a fresh install of windows to try and get a fresh slate. I was hoping it was some driver issue that would resolve by itself. Unfortunately, I am getting the same error on the fresh install different hard drive is being used...
  4. Mini Dump Analysis PLEASE!

    in Windows 10 BSOD Crashes and Debugging
    Mini Dump Analysis PLEASE!: Hello Microsoft Community, I have a DELL Laptop that is dumping... the mother board has been replaced a few times, but I don't want it replaced again if the motherboard and its components are not the issue. Wondering if someone could do a stack dump analysis for me ......
  5. Possible OneDrive solution?

    in Windows 10 Ask Insider
    Possible OneDrive solution?: Hello, all! I'll cut right to the chase. Got a new SSHD, reinstalled Windows to it, been through this process a few times, yadda yadda yadda. HOWEVER during the installation process (because I have been through this process a few times now), I sped my way through the...
  6. Dump File Analysis

    in Windows 10 Installation and Upgrade
    Dump File Analysis: Hi there, After continuously getting BSOD over the last few weeks and have tried to resolve the matter with no luck - I was wondering if someone could look at my dump files and see if they can see problem I am having? Files Here:...
  7. BSOD dump file analysis

    in Windows 10 BSOD Crashes and Debugging
    BSOD dump file analysis: Hi, I wondered if anyone would be able to analyse this dmp file: https://drive.google.com/open?id=1w2SEOPFcekqZ0KF0agtSftysZPj5t_rL It crashed with an event 1001 error: The computer has rebooted from a bugcheck. The bugcheck was: 0x000000ef 0xffffbb8f0fac1400,...
  8. Dump file MSInfo32 Analysis of Windows 10

    in Windows 10 BSOD Crashes and Debugging
    Dump file MSInfo32 Analysis of Windows 10: Need help on a recently upgraded computer from Windows 7 to Windows 10 due to Microsoft's end of support. Since I upgraded, however, I'm running into an annoying sporadic reboot issue. The computer in question will spontaneously restart every 30 minutes to 2 hours with...
  9. Dump File analysis

    in Windows 10 Installation and Upgrade
    Dump File analysis: Never done this before, hoping someone can help with the .dmp file from this computer. https://1drv.ms/u/s!AoJ3iNIXnNFug0JmZ1EmOWVXAPJ6?e=T01B95 Thank you, SWD https://answers.microsoft.com/en-us/windows/forum/all/dump-file-analysis/0ee05ab5-2c01-4846-98a0-82bb7039aa29
  10. Need help with BSOD / Crash Dump analysis

    in Windows 10 Drivers and Hardware
    Need help with BSOD / Crash Dump analysis: Hello, I get intermittent (lately 1 or 2 times per week) BSODs on my windows 10 desktop. I need someone to analyze the DMP files for me so I can narrow down the driver and hopefully solve the problem. I just performed the driver verifier procedure (as directed here) and...