Page 1 of 2 12 LastLast

  1. Posts : 5
    Windows 10

    Infrequent BSoD BAD_POOL_CALLER

    Hi, I built my PC 12 days ago. I have two issues left after doing everything I knew until now.

    One is a BSoD/crash BAD_POOL_CALLER that happens ... sometimes. 5 days ago, 3 days ago and yesterday. One was while I was watching a low-res video in my browser and another was while playing a fairly taxing game (for my GPU anyway).
    The other issue I still have is a similarly infrequent screen flicker. Sometimes it happens thrice a minute and sometimes I don't see it at all for an hour. This one doesn't seem to be particularly tied to the load of my system either... I don't know if this one is connected to the BSoD, but I wanted to provide the info in case it is.

    I still have hopes that both of these are driver issues/conflicts, and I would like to request your help with this. I included the minidumps that came with the 3 BSoDs in question.
    Oh, and I already ran memtest86 over my RAM for a couple hours and nothing turned up there. My BIOS is also up to date.

    I included the zip collected by v2 log collector and I also separately included the minidumps created by the BSoDs in question(didn't know if they'd be in the bunch).

    If it really is a hardware issue, it'd be cool to know what causes the problem so I can send only the part that causes issues back and not all of them :/
      My Computer

  2. Posts : 1,495
    Windows 8.1 Enterprise x64

    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    Loading Dump File [C:\091719-8406-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       SRV*
    Symbol search path is: SRV*
    Executable search path is: 
    Windows 10 Kernel Version 18362 MP (12 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 18362.1.amd64fre.19h1_release.190318-1202
    Machine Name:
    Kernel base = 0xfffff803`71c00000 PsLoadedModuleList = 0xfffff803`720475b0
    Debug session time: Tue Sep 17 14:03:20.032 2019 (UTC + 2:00)
    System Uptime: 0 days 0:12:43.739
    Loading Kernel Symbols
    Loading User Symbols
    Loading unloaded module list
    For analysis of this file, run !analyze -v
    9: kd> !analyze
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    Use !analyze -v to get detailed debugging information.
    BugCheck C2, {99, ffffe704ce0474d8, 0, 0}
    *** WARNING: Unable to verify timestamp for mwac.sys
    Probably caused by : NETIO.SYS ( NETIO!NetioFreeMdl+28225 )
    Followup:     MachineOwner
    9: kd> !analyze -v
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    The current thread is making a bad pool request.  Typically this is at a bad IRQL level or double freeing the same allocation, etc.
    Arg1: 0000000000000099, Attempt to free pool with invalid address  (or corruption in pool header)
    Arg2: ffffe704ce0474d8, Address being freed
    Arg3: 0000000000000000, 0
    Arg4: 0000000000000000, 0
    Debugging Details:
    BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202
    SYSTEM_PRODUCT_NAME:  To Be Filled By O.E.M.
    SYSTEM_SKU:  To Be Filled By O.E.M.
    SYSTEM_VERSION:  To Be Filled By O.E.M.
    BIOS_VENDOR:  American Megatrends Inc.
    BIOS_VERSION:  P3.50
    BIOS_DATE:  07/18/2019
    DUMP_TYPE:  2
    BUGCHECK_P1: 99
    BUGCHECK_P2: ffffe704ce0474d8
    BUGCHECK_P3: 0
    BUGCHECK_P4: 0
    fffff803`748b9685 90              nop
    BUGCHECK_STR:  0xc2_99
    CPU_COUNT: c
    CPU_MHZ: d42
    CPU_VENDOR:  AuthenticAMD
    CPU_FAMILY: 17
    CPU_MODEL: 8
    BLACKBOXBSD: 1 (!blackboxbsd)
    BLACKBOXNTFS: 1 (!blackboxntfs)
    PROCESS_NAME:  MBAMService.exe
    ANALYSIS_SESSION_TIME:  09-18-2019 22:10:03.0572
    ANALYSIS_VERSION: 10.0.18362.1 amd64fre
    LAST_CONTROL_TRANSFER:  from fffff8037256e6e3 to fffff80371dc10a0
    fffffe89`7dd71f38 fffff803`7256e6e3 : 00000000`000000c2 00000000`00000099 ffffe704`ce0474d8 00000000`00000000 : nt!KeBugCheckEx
    fffffe89`7dd71f40 fffff803`71f29391 : ffffe704`ce0474d8 00000000`00000cd0 00000000`00000075 00000000`00000000 : nt!VerifierBugCheckIfAppropriate+0xdf
    fffffe89`7dd71f80 fffff803`71dfa9d1 : ffffe704`bc010000 00000000`fffff803 ffffe704`ce0474d8 00000000`74707070 : nt!VerifierFreeTrackedPool+0x41
    fffffe89`7dd71fc0 fffff803`71f6e0a9 : ffffe704`c6b493d0 00000000`00000000 00000000`00000000 01000000`00100000 : nt!ExFreeHeapPool+0x1b4e91
    fffffe89`7dd720e0 fffff803`748b9685 : ffffe704`ce3142e0 00000000`00000001 ffffe704`cb6ab7c0 01000000`00100000 : nt!ExFreePool+0x9
    fffffe89`7dd72110 fffff803`7f88f390 : ffffe704`ce314460 ffffe704`c232e150 ffffe704`c6b493d0 00000000`00000000 : NETIO!NetioFreeMdl+0x28225
    fffffe89`7dd72140 fffff803`7f88c400 : ffffe704`c2319390 ffffe704`d33ead61 00000000`00000000 00000000`00000000 : wanarp!FlpCompleteNdisNetBufferListChain+0x2f50
    fffffe89`7dd72180 fffff803`748951e6 : ffffe704`d33ead61 00000000`00000000 ffffe704`ce3142e0 00000000`00000000 : wanarp!FlpReturnNetBufferListChain+0x90
    fffffe89`7dd721b0 fffff803`74fa5642 : fffffe89`7dd724a0 00000000`00000001 00000000`00000000 ffffe704`d332d9c0 : NETIO!NetioDereferenceNetBufferList+0xb6
    fffffe89`7dd721f0 fffff803`74fa5484 : ffffe704`c7ae1080 fffffe89`7dd724a0 fffffe89`7dd724a0 ffffe704`bf532a00 : tcpip!IppInspectInjectReceiveEx+0x1b2
    fffffe89`7dd72240 fffff803`75127ac5 : ffffe704`ce3142e0 ffffe704`cf7f2b10 fffffe89`7dd6d000 fffff803`71c6a168 : tcpip!IppInspectInjectReceive+0x24
    fffffe89`7dd722a0 fffff803`71c69ff8 : fffffe89`7dd724a0 ffffe704`bf532ae0 00000000`00000003 fffff803`748a6545 : fwpkclnt!FwppInjectionStackCallout+0x115
    fffffe89`7dd72330 fffff803`71c69f6d : fffff803`751279b0 fffffe89`7dd724a0 ffffe704`bf5ff6d0 ffffe704`cf7f2b10 : nt!KeExpandKernelStackAndCalloutInternal+0x78
    fffffe89`7dd723a0 fffff803`751294c4 : 00000000`00000001 fffff803`75111b43 00000000`00000000 fffff803`7dc89d20 : nt!KeExpandKernelStackAndCalloutEx+0x1d
    fffffe89`7dd723e0 fffff803`7512919c : 00000000`00000000 fffffe89`7dd72519 00000000`00000001 ffffe704`d332d9c0 : fwpkclnt!NetioExpandKernelStackAndCallout+0x58
    fffffe89`7dd72420 fffff803`7dc88e7f : ffffe704`c6b493d0 00000000`00000000 ffffe704`ce314400 ffffe704`c232e150 : fwpkclnt!FwpsInjectTransportReceiveAsync0+0x2fc
    fffffe89`7dd72560 ffffe704`c6b493d0 : 00000000`00000000 ffffe704`ce314400 ffffe704`c232e150 ffffe704`c2320002 : mwac+0x8e7f
    fffffe89`7dd72568 00000000`00000000 : ffffe704`ce314400 ffffe704`c232e150 ffffe704`c2320002 00000000`00000001 : 0xffffe704`c6b493d0
    THREAD_SHA1_HASH_MOD_FUNC:  f9f0ac8c70473c26efc84d8e91a110830497823b
    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6eaf6d103f1f13894505e3dea94545b79db3aa7f
    THREAD_SHA1_HASH_MOD:  61459616305fcd79d954d6c062dbc69247abc9df
    fffff803`748b9685 90              nop
    FAULT_INSTR_CODE:  7defe990
    SYMBOL_NAME:  NETIO!NetioFreeMdl+28225
    FOLLOWUP_NAME:  MachineOwner
    IMAGE_VERSION:  10.0.18362.10036
    STACK_COMMAND:  .thread ; .cxr ; kb
    FAILURE_BUCKET_ID:  0xc2_99_NETIO!NetioFreeMdl
    BUCKET_ID:  0xc2_99_NETIO!NetioFreeMdl
    PRIMARY_PROBLEM_CLASS:  0xc2_99_NETIO!NetioFreeMdl
    TARGET_TIME:  2019-09-17T12:03:20.000Z
    OSBUILD:  18362
    SUITE_MASK:  272
    OSNAME:  Windows 10
    OSEDITION:  Windows 10 WinNt TerminalServer SingleUserTS
    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
    FAILURE_ID_HASH_STRING:  km:0xc2_99_netio!netiofreemdl
    FAILURE_ID_HASH:  {2def513e-002b-95b4-9931-f6ae0e497574}
    Followup:     MachineOwner
    9: kd> .load pde
     PDE v11.3 - Copyright 2017 Andrew Richards
    9: kd> !dpx
    Start memory scan  : 0xfffffe897dd71f38 ($csp)
    End memory scan    : 0xfffffe897dd73000 (Kernel Stack Base)
                   rsp : 0xfffffe897dd71f38 : 0xfffff8037256e6e3 : nt!VerifierBugCheckIfAppropriate+0xdf
    0xfffffe897dd71f38 : 0xfffff8037256e6e3 : nt!VerifierBugCheckIfAppropriate+0xdf
    0xfffffe897dd71f78 : 0xfffff80371f29391 : nt!VerifierFreeTrackedPool+0x41
    0xfffffe897dd71fe8 : 0xfffff80371c45e97 : nt!ExFreeHeapPool+0x357
    0xfffffe897dd72018 : 0xfffff8037489137f : NETIO!WfpNblInfoDestroyIfUnused+0x11f
    0xfffffe897dd72048 : 0xfffff80371cfa54d : nt!IoFreeMdl+0x5d
    0xfffffe897dd72058 : 0xfffff80375124474 : fwpkclnt!FwppSetPacketInfo+0x88
    *** WARNING: Unable to verify timestamp for mwac.sys
    0xfffffe897dd720d8 : 0xfffff80371f6e0a9 : nt!ExFreePool+0x9
    0xfffffe897dd72178 : 0xfffff8037f88c400 : wanarp!FlpReturnNetBufferListChain+0x90
    0xfffffe897dd721a8 : 0xfffff803748951e6 : NETIO!NetioDereferenceNetBufferList+0xb6
    0xfffffe897dd721d8 : 0xfffff80375111598 : fwpkclnt!FwppNetBufferListEventNotify+0x108
    0xfffffe897dd721e0 : 0xfffff8037501f2e0 : tcpip!Ipv4Global
    0xfffffe897dd721e8 : 0xfffff80374fa5642 : tcpip!IppInspectInjectReceiveEx+0x1b2
    0xfffffe897dd72228 : 0xfffff803751279b0 : fwpkclnt!FwppInjectionStackCallout
    0xfffffe897dd72238 : 0xfffff80374fa5484 : tcpip!IppInspectInjectReceive+0x24
    0xfffffe897dd72268 : 0xfffff80371c6b700 : nt!KeQueryCurrentStackInformationEx+0x60
    0xfffffe897dd72290 : 0xfffff80374fa5460 : tcpip!IppInspectInjectReceive
    0xfffffe897dd72298 : 0xfffff80375127ac5 : fwpkclnt!FwppInjectionStackCallout+0x115
    0xfffffe897dd722b8 : 0xfffff80371c6a168 : nt!KiExpandKernelStackAndCalloutSwitchStack+0x108
    0xfffffe897dd722e0 : 0xfffff80374e95740 : tcpip!WfppTaggedContextInit
    0xfffffe897dd72310 : 0xfffff803751279b0 : fwpkclnt!FwppInjectionStackCallout
    0xfffffe897dd72320 : 0xfffff803751279b0 : fwpkclnt!FwppInjectionStackCallout
    0xfffffe897dd72328 : 0xfffff80371c69ff8 : nt!KeExpandKernelStackAndCalloutInternal+0x78
    0xfffffe897dd72348 : 0xfffff803748a6545 : NETIO!NetioInitializeNetBufferListContextPrimitive+0x15
    0xfffffe897dd72398 : 0xfffff80371c69f6d : nt!KeExpandKernelStackAndCalloutEx+0x1d
    0xfffffe897dd723a0 : 0xfffff803751279b0 : fwpkclnt!FwppInjectionStackCallout
    0xfffffe897dd723c8 : 0xfffff8037512737b : fwpkclnt!FwppInjectPrologue+0x13b
    0xfffffe897dd723d8 : 0xfffff803751294c4 : fwpkclnt!NetioExpandKernelStackAndCallout+0x58
    0xfffffe897dd723e8 : 0xfffff80375111b43 : fwpkclnt!FwpsIPSecGetPacketListSecurityInformation+0x53
    0xfffffe897dd72408 : 0xfffff80374f7e26b : tcpip!WfpAleReleaseAsyncCompletionLocalContext+0x2b
    0xfffffe897dd72418 : 0xfffff8037512919c : fwpkclnt!FwpsInjectTransportReceiveAsync0+0x2fc
    0xfffffe897dd72468 : 0xfffff80374f86117 : tcpip!WfpAleCompleteOperation+0x1b7
    0xfffffe897dd72488 : 0xffffe704bd0a14a0 : 0xfffff80374ea0c70 : tcpip!InetInspectCreateEndpoint
    0xfffffe897dd72498 : 0xfffff80375123263 : fwpkclnt!FwppAllocateNetioCloneNetBufferList+0x193
    0xfffffe897dd724a8 : 0xffffe704bd0a14a0 : 0xfffff80374ea0c70 : tcpip!InetInspectCreateEndpoint
    0xfffffe897dd725b8 : 0xfffff80371c33926 : nt!RtlpHpLfhSlotAllocate+0x126
    0xfffffe897dd727c8 : 0xfffff80371f533a9 : nt!_guard_retpoline_exit_indirect_rax+0x9
    0xfffffe897dd72818 : 0xfffff80371c31f39 : nt!IofCallDriver+0x59
    0xfffffe897dd72858 : 0xfffff803721e8345 : nt!IopSynchronousServiceTail+0x1a5
    0xfffffe897dd728a8 : 0xfffff80371c324fe : nt!IopVerifierExAllocatePoolWithQuota+0xfe
    0xfffffe897dd728f8 : 0xfffff803721e8150 : nt!IopXxxControlFile+0xc10
    0xfffffe897dd72a18 : 0xfffff803721e7526 : nt!NtDeviceIoControlFile+0x56
    0xfffffe897dd72a78 : 0xfffff803721f1fab : nt!NtWaitForSingleObject+0x12b
    0xfffffe897dd72a80 : 0xfffff803721e74d0 : nt!NtDeviceIoControlFile
    0xfffffe897dd72a88 : 0xfffff80371dd2918 : nt!KiSystemServiceCopyEnd+0x28
    0xfffffe897dd72af0 : 0xfffff8037221b720 : nt!NtOpenProcess
    0xfffffe897dd72af8 : 0xfffff80371dd2918 : nt!KiSystemServiceCopyEnd+0x28
    0xfffffe897dd72b00 : 0xffffe704c7ae1080 :  Trap @ fffffe897dd72b00
    9: kd> !poolval ffffe704ce0474d8
    fffff803721723b8: Unable to get MiVisibleState
    Unable to get NonPagedPoolStart
    Unable to get NonPagedPoolEnd
    Unable to get PagedPoolStart
    Unable to get PagedPoolEnd
    Pool page ffffe704ce0474d8 region is Unknown
    Validating Pool headers for pool page: ffffe704ce0474d8
    Pool page [ ffffe704ce047000 ] is INVALID.
    Analyzing linked list...
    [ ffffe704ce047000 --> ffffe704ce047820 (size = 0x820 bytes)]: Corrupt region
    Scanning for single bit errors...
    None found
    9: kd> !address ffffe704ce0474d8
    Mapping user range ...
    ERROR: !address: extension exception 0x80004005.
        "ExtRemoteTyped::Set from type and offset"
    9: kd> lmvm mwac
    Browse full module list
    start             end                 module name
    fffff803`7dc80000 fffff803`7dca5000   mwac     T (no symbols)           
        Loaded symbol image file: mwac.sys
        Image path: \SystemRoot\system32\DRIVERS\mwac.sys
        Image name: mwac.sys
        Browse all global symbols  functions  data
        Timestamp:        Mon Jul  1 15:35:24 2019 (5D1A0C1C)
        CheckSum:         0002A1EC
        ImageSize:        00025000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    The only way I can see is reinstalling this Malware-Bytes Anti-Malware, and if that doesn't help, removing the program completely. Alternatively, use Driver Verifier (Enable and Disable Driver Verifier in Windows 10)
      My Computer

  3. Posts : 39,994
    windows 10 professional version 1607 build 14393.969 64 bit

    The logs were in a foreign language and could not be scanned or read.

    Please use English as the default language and upload a new V2:
    Change Display Language in Windows 10
      My Computer

  4. Posts : 5
    Windows 10
    Thread Starter

    The logs were in a foreign language and could not be scanned or read.
    sorry about that. Kinda forgot I even set it to german. Here's a new one.
      My Computer

  5. Posts : 546

    IEatLouis said:
    sorry about that. Kinda forgot I even set it to german. Here's a new one.
    I see there is no transcript-elevated.txt in the zip file you posted - are you getting an error (red text) in the second window? If so, could you please let me know what that error message is? A screenshot or copy-pasting it would be great.
      My Computer

  6. Posts : 39,994
    windows 10 professional version 1607 build 14393.969 64 bit

    1) The logs displayed 3 different bugchecks including:
    Attempt to reset the display driver and recover from timeout failed.

    2) In case there is no error message or code please uninstall Bitdefender using the applicable uninstall tool and then upload a new V2.

    Uninstall Bitdefender

    3) Turn off Windows fast startup:
    Turn On or Off Fast Startup in Windows 10

    4) Uninstall iobit using their uninstall tool:
    COMPLETELY remove IOBit - IObit.Com Forums

    5) Uninstall and reinstall:
    RGB Fusion 3.19.0905.1 GIGABYTE

    6) Run HD Tune (free version) (all drives)
    HD Tune website
    Post images into the thread for results on these tabs:
    a) Health
    b) Benchmark
    c) Full error scan

    7) Run Sea Tools for Windows
    long generic test
    Post an image of the test result into the thread
    SeaTools for Windows |

    How to use SeaTools for Windows | Seagate Support US

    8) Open administrative command prompt and type or copy and paste:
    9) sfc /scannow
    10) dism /online /cleanup-image /scanhealth
    11) dism /online /cleanup-image /restorehealth
    12) sfc /scannow
    13) chkdsk /scan
    14) wmic recoveros set autoreboot = false
    15) wmic recoveros set DebugInfoType = 7
    16) bcdedit /enum {badmemory}

    17) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    18) Uninstall everything AMD using Display driver uninstaller and install new drivers from the the AMD website.

    19) On the AMD web site be sure the "clean install" box is checked and only install the graphics driver.

    Official Display Driver Uninstaller DDU Download

    Display Driver Uninstaller Download version (or newer version if available)

    Display Driver Uninstaller: How to use - Windows 7 Help Forums
      My Computer

  7. Posts : 5
    Windows 10
    Thread Starter

    Here's a new v2log, I checked that the file name you mentioned is in there this time.

    Both of my drives were completely green in the HD Tune error scan. Here is the benchmark of my m.2 boot drive, and of my 2nd drive that is the boot drive of my laptop. And the health tab of that 2nd drive. The health tab of my main m.2 drive was just empty. Both of my drives were completely green in the error scan.
    I included the stats of the 2nd drive but really I don't think it matters since nothing vital for my system is on it.

    here is the stuff from the cmd prompt
    Microsoft Windows [Version 10.0.18362.356]
    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\Users\Administrator>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection found corrupt files and successfully repaired them.
    For online repairs, details are included in the CBS log file located at
    windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
    repairs, details are included in the log file provided by the /OFFLOGFILE flag.

    C:\Users\Administrator>dism /online /cleanup-image /scanhealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.356

    [==========================100.0%==========================] No component store corruption detected.
    The operation completed successfully.

    C:\Users\Administrator>dism /online /cleanup-image /restorehealth

    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

    Image Version: 10.0.18362.356

    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.

    C:\Users\Administrator>sfc /scannow

    Beginning system scan. This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.

    Windows Resource Protection did not find any integrity violations.

    C:\Users\Administrator>chkdisk /scan
    'chkdisk' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Users\Administrator>chkdsk /scan
    The type of the file system is NTFS.

    Stage 1: Examining basic file system structure ...
    381440 file records processed.
    File verification completed.
    9014 large file records processed.
    0 bad file records processed.

    Stage 2: Examining file name linkage ...
    287 reparse records processed.
    524368 index entries processed.
    Index verification completed.
    0 unindexed files scanned.
    0 unindexed files recovered to lost and found.
    287 reparse records processed.

    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.
    71465 data files processed.
    CHKDSK is verifying Usn Journal...
    40844064 USN bytes processed.
    Usn Journal verification completed.

    Windows has scanned the file system and found no problems.
    No further action is required.

    499446783 KB total disk space.
    73214344 KB in 289959 files.
    186008 KB in 71466 indexes.
    0 KB in bad sectors.
    506407 KB in use by the system.
    65536 KB occupied by the log file.
    425540024 KB available on disk.

    4096 bytes in each allocation unit.
    124861695 total allocation units on disk.
    106385006 allocation units available on disk.

    C:\Users\Administrator>wmic recoveros set autoreboot = false
    Updating property(s) of '\\DESKTOP-M534IB5\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition4"'
    Property(s) update successful.

    C:\Users\Administrator>wmic recoveros set debuginfotype = 7
    Updating property(s) of '\\DESKTOP-M534IB5\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Pro|C:\\Windows|\\Device\\Harddisk1\\Partition4"'
    Property(s) update successful.

    C:\Users\Administrator> bcedit /enum {badmemory}
    'bcedit' is not recognized as an internal or external command,
    operable program or batch file.

    C:\Users\Administrator> bcdedit /enum {badmemory}

    RAM Defects
    identifier {badmemory}

      My Computer

  8. Posts : 39,994
    windows 10 professional version 1607 build 14393.969 64 bit

    Windows Resource Protection found corrupt files and successfully repaired them.

    Please post images of all test results: full error scans, etc.

    When available post results for Sea Tool long generic on ST500L.

    Run HD Sentinel: (free or trial edition)
    Hard Disk Sentinel - HDD health and temperature monitoring
    Hard Disk Sentinel - HDD health and temperature monitoring
    Post images of each of these tabs into the thread:
    Overview tab
    Disk performance

    During the troubleshooting process please perform steps #2 and #4 in post #6.
      My Computer

  9. Posts : 5
    Windows 10
    Thread Starter

    so here you go. the error scans of both my drives, all the stuff you asked for.
    However, for step 2 of post 6, I did not uninstall bitdefender to make a new v2 just like I didn't back then. I just went into it and disabled all the protection and stuff while the v2log was made. I hope that's fine. uninstalling and reinstalling bitdefender seems like a big hassle :/
      My Computer

  10. Posts : 39,994
    windows 10 professional version 1607 build 14393.969 64 bit

    Recheck the drive with HD sentinel.
    If there are transfer errors swap drive cables to see if it makes any difference.

    Hard disk case: communication errors

    The last dump file was on 9/17.
    The last unexpected shutdown/restart was on 9/19.

    Unexpected shutdowns/restarts are recorded when:
    a) the end user uses power off
    b) BSOD
    c) temperature / malfunctioning hardware

    Please indicate whether there was or was not a manual power off yesterday.
      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 10:02.
Find Us

Windows 10 Forums