Random BSODs

Page 1 of 3 123 LastLast

  1. Posts : 11
    Win 10
       #1

    Random BSODs


    Been having BSODs at random for about a year. Usually about 2 per week, but can go a month without 1. I've tried running driver verifier, memtest for 8 hours. I've stress tested each component for 4 hours with no faults. I've done a clean install of Windows 2 times. Issues still persisted. Most BSODs are IRQL_NOT_LESS_OR_EQUAL
    System otherwise performs normally.



    V2 file here: DESKTOP-0ECERG1-(2019-09-26_13-56-17).zip - Google Drive
      My Computer


  2. Posts : 13,961
    Windows 10 Pro X64 21H1 19043.1503
       #2

    The 9:22 11:16AM dump shows a problem with <strong>nvlddmkm.sys</strong>.<br>
    Code:
    fffff805`4f2aa688 &nbsp;fffff805`586cd874Unable to load image <strong>nvlddmkm.sys</strong>, Win32 error 0n2<br>
    *** WARNING: Unable to verify timestamp for <strong>nvlddmkm.sys</strong><br>
    &nbsp;nvlddmkm+0xfd874
    There is a new version available:

    Version: 436.30 WHQL
    Release Date: 2019.9.10

    Remove and install latest Nvidia drivers:

    Get the latest driver for your Nvidia card here: NVIDIA Driver Downloads
    Completely uninstall the current Nvidia display drivers using Display Driver Uninstaller (DDU) from WagnardMobile here: Official Download Here. Do this in Safe Mode.

    Then do a custom install of only the Nvidia Graphics and PhysX driver.
    See if that gets rid of the problem.

    Several of the dumps show memory corruption or single bit memory corruption so you need to make time to test your RAM.

    ===================================================
    Up through DDR3, follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums
    DDR4, follow this tutorial: MemTest86 v8.1 Free Memory Testing Tool Review

    Both of these are diagnostic tools designed to test Random Access Memory (RAM) for faults. They will verify that:
    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    They run from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ and Memtest86 need to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM. The new version of Memtest86 only allows 4 passes for the free version so run it twice, back to back.

    If you are asked to run MemTest86+ or Memtest86 by a Ten Forums member make sure you run the full 8 (or 4+4) passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    Both of these diagnostics has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ or 4+4 passes of Memtest86 is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run it overnight, starting just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.
      My Computers


  3. Posts : 11
    Win 10
    Thread Starter
       #3

    I tried editing the post to state I have tried DDU before and it hasn't helped, but the edit button is no longer there. I ran it again and updated to v436.15 (The download for 436.30 is currently broken) I only install the drivers and PhysX each time I update.

    Did 10.5 hours/11 full passes of Memtest. Showed 0 errors results here: Memtest.png - Google Drive

    After making this post I noticed you recommended Memtest86+ for DDR3. It was my understanding that it was no longer updating. Viewing the changelog the last update was only providing preliminary support for my CPU.

    I will update whenever the next BSOD happens unless there is another test to run.
      My Computer


  4. Posts : 13,961
    Windows 10 Pro X64 21H1 19043.1503
       #4

    We've had many people run Memtest86+ with DDR3 RAM with good results (by that I mean it has at times detected bad ram), so unless you are dead set against running it for some reason I would say go ahead and run it for the specified 8 passes and lets see what happens.

    It may not find anything but then again it may. It would be annoying to say the least to spend a lot of time trying other thing to then come back and eventually decide RAM was the culprit, especially when it's so easy to check.

    If you rather, you can try running Driver Verifier and see if that shakes out any bad drivers.

    Enable and Disable Driver Verifier in Windows 10

    Following the instructions in the above link will check for problems in all non-Microsoft drivers.

    What we're looking for is a verifier generated BSOD with a mini dump that will tell us what driver caused it. If you get a BSOD, rerun the V2 log collector as soon as possible and upload the resulting zip file. Also see if there is a new C:\Windows \MEMORY.DMP file. If there is, copy it to another location then zip it an upload to a file sharing site like OneDrive and post a link to it here.

    To check if verifier is active, open a Command Prompt and enter:

    verifier /querysettings

    If not active it will respond with

    Verifier Flags: 0x00000000

    Standard Flags:

    [ ] 0x00000001 Special pool.
    [ ] 0x00000002 Force IRQL checking.
    [ ] 0x00000008 Pool tracking.
    [ ] 0x00000010 I/O verification.
    [ ] 0x00000020 Deadlock detection.
    [ ] 0x00000080 DMA checking.
    [ ] 0x00000100 Security checks.
    [ ] 0x00000800 Miscellaneous checks.
    [ ] 0x00020000 DDI compliance checking.

    Additional Flags:

    [ ] 0x00000004 Randomized low resources simulation.
    [ ] 0x00000200 Force pending I/O requests.
    [ ] 0x00000400 IRP logging.
    [ ] 0x00002000 Invariant MDL checking for stack.
    [ ] 0x00004000 Invariant MDL checking for driver.
    [ ] 0x00008000 Power framework delay fuzzing.
    [ ] 0x00010000 Port/miniport interface checking.
    [ ] 0x00040000 Systematic low resources simulation.
    [ ] 0x00080000 DDI compliance checking (additional).
    [ ] 0x00200000 NDIS/WIFI verification.
    [ ] 0x00800000 Kernel synchronization delay fuzzing.
    [ ] 0x01000000 VM switch verification.
    [ ] 0x02000000 Code integrity checks.

    [X] Indicates flag is enabled.

    Boot Mode:

    Persistent

    Rules:

    All rules are using default settings

    Verified Drivers:

    None
      My Computers


  5. Posts : 11
    Win 10
    Thread Starter
       #5

    I'll run Memtest86+ overnight tonight then. I have tried running driver verifier for a day before disabling. It actually didn't BSOD for that day. I have also tried SFC and other Windows-related repair commands.

    I noticed in the post it said to not enable driver verifier for longer than 48 hours, but what is the recommended time? I'll have to try it again on a day where I don't need as much power on my PC.
      My Computer


  6. Posts : 13,961
    Windows 10 Pro X64 21H1 19043.1503
       #6

    There is no good reason for the 48 hour limit that I can see other than it does slow the system down, But if you don't get a BSOD in that time it's unlikely a longer run will generate one unless the workload changes or the hardware being exercised changes.

    What other hardware do you have connected to the PC?

    I see you have MSI Afterburner installed. Are you doing any overclocking? If you are, please set everything back to nominal and run that way for awhile.
      My Computers



  7. Posts : 11
    Win 10
    Thread Starter
       #7

    Well I had another BSOD last night. Didn't have driver verifier running though. I've already uninstalled and reinstalled my network drivers. New V2 is here just in case: DESKTOP-0ECERG1-(2019-09-28_08-28-18).zip - Google Drive

    I ran Memtest86+ for 9 hours. It only ended up doing 3.5 passes due to multithreading not being enabled. I can try forcing it and rerunning tonight. Result here: MemtestPlus.png - Google Drive

    I only have mouse keyboard, speakers, and headphones connected. No other external devices; no extra internal PCIe cards or anything either besides the GPU.

    The only thing I use Afterburner for is to set a more aggressive fan curve. My card just doesn't overclock well compared to the additional heat generated. I've also had BSODs while Afterburner was disabled. BSODs can happen while system is idle too. Probably not related to the GPU. I also ran Furmark and OCCT tests. Nothing caused any abnormal behavior/crashes.

    Thank you for the help by the way. I've been trying to fix it myself for a year and I'm just out of ideas.
      My Computer


  8. Posts : 13,961
    Windows 10 Pro X64 21H1 19043.1503
       #8

    This one is different from the previous dumps.

    FAILED_INSTRUCTION_ADDRESS:
    ndis!NdisSendNetBufferLists+5b
    fffff806`7beabfeb c5 ???
    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffff8067beabfeb, The address that the exception occurred at
    Arg3: ffff828529aad258, Parameter 0 of the exception
    Arg4: fffff8067cabf930, Parameter 1 of the exception
    CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
    fffff8067beabfeb - ndis!NdisSendNetBufferLists+5b

    So this appears to be network driver related. You said you already uninstalled and reinstalled your network drivers. Dump shows that you have:

    0: kd> lmvm rt640x64
    Browse full module list
    start end module name
    fffff806`85b30000 fffff806`85c4c000 rt640x64 T (no symbols)
    Loaded symbol image file: rt640x64.sys
    Image path: rt640x64.sys
    Image name: rt640x64.sys
    Browse all global symbols functions data
    Timestamp: Mon Jul 1 03:38:21 2019 (5D19B86D)
    CheckSum: 0011FC69
    ImageSize: 0011C000
    Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
    That looks the same as the latest available from the MSI Support For H87-G43 site:

    Realtek PCI-E Ethernet Drivers
    Version
    10.35.0510.2019
    Release Date
    2019-07-30
    File Size
    10.56 MB
    The one thing all the dumps have in common is this:

    MODULE_NAME: memory_corruption
    IMAGE_NAME: memory_corruption
    FOLLOWUP_NAME: memory_corruption
    DEBUG_FLR_IMAGE_TIMESTAMP: 0
    MEMORY_CORRUPTOR: ONE_BIT

    Instead of running memtest86+, try removing 1/2 of your RAM and running that way for awhile. That will still leave you with 8GB which should be okay. If you get another BSOD then swap removed and installed RAM and test for another while.

    I'm going to see if I can get one of the other BSOD guys to take a look at this as well. I don't see anything in the event viewer logs that is any help and nothing in the dumps other than an indication of a possible network driver problem and since you already have the latest and have uninstalled and reinstalled it, and clean installed Win 10 twice I'm not sure where to go next. Fresh eyes may help.
      My Computers


  9. Posts : 40,002
    windows 10 professional version 1607 build 14393.969 64 bit
       #9

    1) For BSOD the computer has been creating mini dumps.
    There were no memory dumps created.
    Please modify the settings to create memory dump files (see below)

    2) The RAM modules are mismatched.
    They are in pairs.
    a) Please check to see if the modules are or are not on the Qualified Vendor List (QVL).
    b) When were each pair installed?
    As Ztrucker commented test the RAM in pairs.
    For each pair run Memtest86 version 5.01 for 8 or more passes.
    The paired RAM modules should be tested in the same DIMM.
    Then evaluate the computer stability / instability while using the paired RAM.
    Do BSOD only happen with one pair or with both pair using the same DIMM?
    If necessary the testing can be performed in other DIMM.
    MSI motherboard testing is done by process of elimination or by swap.

    3) Make sure that there is no over clocking while troubleshooting.

    4) Sometimes there are problems in the bios that produce BSOD.

    The BIOS: Version/Date American Megatrends Inc. V2.10, 5/9/2015

    5) Please check to see if this is the most up to date version.

    6) Open the website for the computer or motherboard manufacturer to view the drivers and post a URL or hyperlink into the thread.

    7) To ensure that there are no improper bios settings please reset the bios.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computerís CMOS to Reset BIOS Settings
    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow


    8) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

    a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

    b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

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

    18) 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

    19) Run memtest86+ version 5.01 for at least 8 passes.
    Memtest86+ - Advanced Memory Diagnostic Tool
    This may take hours so plan to run it overnight.

    a) Please make sure you use the Memtest86+ version 5.01 with the link below.
    Memtest86+ - Advanced Memory Diagnostic Tool

    The testing is done not by time but by passes.
    The more passes the better the testing conditions.
    There are a significant number of false negatives if fewer than 8 passes are made.
    A false negative is a test pass when there is malfunctioning RAM.
    There is 8 GB of RAM (matched pairs) on the computer.
    Memtest86+ version 5.01 testing takes approximately 1 - 2 hours /GB RAM
    Just 1 error is a fail and you can abort testing.
    Then test 1 RAM module at a time in the same DIMM each for 8 or more passes.

    b) When Memtest86+ version 5.01 has completed 8 or more passes use a camera or smart phone camera to take a picture and post an image into the thread.
    https://answers.microsoft.com/en-us/...f-ecc7b7ff6461
    MemTest86+ - Test RAM



    Bugcheck code 0000000A
    Debug session time: Sun Sep 22 13:11:43.574 2019 (UTC - 5:00)
    Dislpayed:
    Code:
    nvlddmkm.sys Wed Jul 17 16:04:33 2019 (5D2F8D61)


    Bugcheck code 000000D1
    Debug session time: Thu Sep 19 23:42:40.679 2019 (UTC - 5:00)
    Displayed:
    Code:
    rt640x64.sys Fri May 24 03:47:02 2019 (5CE7AF86)

    Code:
    8/27/2019 3:33 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1000007e&#x000d;&#x000a;P2: ffffffffc0000005&#x000d;&#x000a;P3: fffff8067e606cdf&#x000d;&#x000a;P4: ffffa30e302ae728&#x000d;&#x000a;P5: fffff806772bf930&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\082719-5109-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6640-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28F5.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2923.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2933.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1000007e_e4fa6f78817b2f83755890ea7af6ef782eb83c85_00000000_cab_a4840596-89ba-4772-88f3-c8b641361200&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 6e495477-825a-4fef-92b9-6bfc05206e0f&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    8/27/2019 3:33 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1000007e&#x000d;&#x000a;P2: ffffffffc0000005&#x000d;&#x000a;P3: fffff8067e606cdf&#x000d;&#x000a;P4: ffffa30e302ae728&#x000d;&#x000a;P5: fffff806772bf930&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\082719-5109-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6640-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28F5.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2923.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2933.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1000007e_e4fa6f78817b2f83755890ea7af6ef782eb83c85_00000000_a4840596-89ba-4772-88f3-c8b641361200&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 6e495477-825a-4fef-92b9-6bfc05206e0f&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/6/2019 1:47 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1e&#x000d;&#x000a;P2: ffffffff80000004&#x000d;&#x000a;P3: fffff8075612a66c&#x000d;&#x000a;P4: 1&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\090519-7484-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-9000-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER349C.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34AD.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34EA.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER351A.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_65dfefb176adb6bede03ef188623a1d9fa7c7_00000000_cab_95a87447-cbe5-4f8b-8a71-fc8e6532a8e6&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: be0d365f-de13-4699-949d-07b8d4394f6c&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/6/2019 1:47 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1e&#x000d;&#x000a;P2: ffffffff80000004&#x000d;&#x000a;P3: fffff8075612a66c&#x000d;&#x000a;P4: 1&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\090519-7484-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-9000-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER349C.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34AD.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34EA.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER351A.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_65dfefb176adb6bede03ef188623a1d9fa7c7_00000000_95a87447-cbe5-4f8b-8a71-fc8e6532a8e6&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: be0d365f-de13-4699-949d-07b8d4394f6c&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    8/23/2019 8:10 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1e&#x000d;&#x000a;P2: ffffffffc000001d&#x000d;&#x000a;P3: fffff8017701207c&#x000d;&#x000a;P4: fffff8017218f400&#x000d;&#x000a;P5: ffffaf0fd80f9000&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\082319-4718-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6234-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2923.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2933.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2961.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2962.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_d3a29289c1aead1c79695dd588b6f3aaf39c41_00000000_cab_2e9624cd-03af-45ab-9168-3cf89bd391fc&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: e42850e3-3cd0-486d-ae27-2e6e036b00bb&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    8/23/2019 8:10 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1e&#x000d;&#x000a;P2: ffffffffc000001d&#x000d;&#x000a;P3: fffff8017701207c&#x000d;&#x000a;P4: fffff8017218f400&#x000d;&#x000a;P5: ffffaf0fd80f9000&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\082319-4718-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6234-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2923.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2933.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2961.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2962.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_d3a29289c1aead1c79695dd588b6f3aaf39c41_00000000_2e9624cd-03af-45ab-9168-3cf89bd391fc&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: e42850e3-3cd0-486d-ae27-2e6e036b00bb&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    8/23/2019 6:50 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1e&#x000d;&#x000a;P2: ffffffffc000001d&#x000d;&#x000a;P3: fffff805638671b4&#x000d;&#x000a;P4: ffffb281548f0140&#x000d;&#x000a;P5: fffff805706d&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\082319-5250-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6812-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29DE.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29EF.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A0D.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A1E.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1e_ce1c2d909c69d5c8a1316aa8cb98e876783319_00000000_cab_647a956f-3b94-4cf5-b739-843563b65056&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: dfeb6371-711b-4aac-8ea4-5d7c546d57e5&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    8/23/2019 6:50 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 1e&#x000d;&#x000a;P2: ffffffffc000001d&#x000d;&#x000a;P3: fffff805638671b4&#x000d;&#x000a;P4: ffffb281548f0140&#x000d;&#x000a;P5: fffff805706d&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\082319-5250-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6812-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29DE.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29EF.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A0D.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2A1E.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1e_ce1c2d909c69d5c8a1316aa8cb98e876783319_00000000_647a956f-3b94-4cf5-b739-843563b65056&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: dfeb6371-711b-4aac-8ea4-5d7c546d57e5&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/7/2019 12:39 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 3b&#x000d;&#x000a;P2: c0000005&#x000d;&#x000a;P3: fffff80181605663&#x000d;&#x000a;P4: ffffcd01170d8930&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\090619-4750-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6843-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34DB.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34EB.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3519.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER352A.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_2de58652ddb05279457f4b2b865e83028455d87_00000000_cab_85f16e90-989e-4d3c-826b-6d09dc418ddb&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 6e6ce2fb-3730-42e3-95cb-bede1cc719ea&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/7/2019 12:39 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 3b&#x000d;&#x000a;P2: c0000005&#x000d;&#x000a;P3: fffff80181605663&#x000d;&#x000a;P4: ffffcd01170d8930&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\090619-4750-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6843-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34DB.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER34EB.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3519.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER352A.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_2de58652ddb05279457f4b2b865e83028455d87_00000000_85f16e90-989e-4d3c-826b-6d09dc418ddb&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 6e6ce2fb-3730-42e3-95cb-bede1cc719ea&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/7/2019 10:46 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 50&#x000d;&#x000a;P2: ffffbad6e0da38d0&#x000d;&#x000a;P3: 0&#x000d;&#x000a;P4: ffffbad6e0718976&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\090719-5125-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6640-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35C5.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35D6.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35F4.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3605.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_50_58ffd17e77a683ef26fc6f452e309aa542c692ab_00000000_cab_35425652-8002-4c7f-9767-957ef724677c&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 1d24024d-8af8-4307-b736-f48fe619e640&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/7/2019 10:46 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: 50&#x000d;&#x000a;P2: ffffbad6e0da38d0&#x000d;&#x000a;P3: 0&#x000d;&#x000a;P4: ffffbad6e0718976&#x000d;&#x000a;P5: 0&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\090719-5125-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6640-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35C5.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35D6.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER35F4.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER3605.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_50_58ffd17e77a683ef26fc6f452e309aa542c692ab_00000000_35425652-8002-4c7f-9767-957ef724677c&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 1d24024d-8af8-4307-b736-f48fe619e640&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    7/30/2019 6:52 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: a&#x000d;&#x000a;P2: ffffa21e2fce8198&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: fffff8004503d152&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\073019-5140-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-7296-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B94.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BA4.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BC3.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C12.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_a0e933897812c9276f44b4eaa0a4c0e9467a48_00000000_cab_1032e531-8826-400a-b3d0-84f2f084a249&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 2ab29515-34b7-4e4f-9515-779b7e6cc1f5&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    7/30/2019 6:52 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: a&#x000d;&#x000a;P2: ffffa21e2fce8198&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: fffff8004503d152&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\073019-5140-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-7296-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B94.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BA4.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BC3.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2C12.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_a0e933897812c9276f44b4eaa0a4c0e9467a48_00000000_1032e531-8826-400a-b3d0-84f2f084a249&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 2ab29515-34b7-4e4f-9515-779b7e6cc1f5&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/22/2019 6:16 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: a&#x000d;&#x000a;P2: ffffb78000000368&#x000d;&#x000a;P3: ff&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: fffff8054a115875&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\092219-5156-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6718-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2961.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2972.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2990.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29A1.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_76bc768436854cf6933f943faee9e9abf7351_00000000_cab_ea9a8fe4-5603-46df-a6b8-2038f7977e00&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 6534b238-a282-4856-8ec6-2f78d85f3bc6&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/22/2019 6:16 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: a&#x000d;&#x000a;P2: ffffb78000000368&#x000d;&#x000a;P3: ff&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: fffff8054a115875&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\092219-5156-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6718-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2961.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2972.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2990.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER29A1.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_76bc768436854cf6933f943faee9e9abf7351_00000000_ea9a8fe4-5603-46df-a6b8-2038f7977e00&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 6534b238-a282-4856-8ec6-2f78d85f3bc6&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/26/2019 5:46 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: a&#x000d;&#x000a;P2: ffffffffffffff93&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 1&#x000d;&#x000a;P5: fffff80473a9aa11&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\092619-4734-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6796-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2952.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2962.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2971.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2982.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_a_9dba7c71755ac3b547acbbdebc660a37b53fd1b_00000000_cab_229a6697-9c80-42b1-b4cc-8e5d11756118&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 4843e77e-263a-4d6c-aba4-b5b132bd0808&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/26/2019 5:46 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: a&#x000d;&#x000a;P2: ffffffffffffff93&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 1&#x000d;&#x000a;P5: fffff80473a9aa11&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\092619-4734-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6796-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2952.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2962.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2971.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2982.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a_9dba7c71755ac3b547acbbdebc660a37b53fd1b_00000000_229a6697-9c80-42b1-b4cc-8e5d11756118&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 4843e77e-263a-4d6c-aba4-b5b132bd0808&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    6/10/2019 8:38 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: d1&#x000d;&#x000a;P2: 38423eb46d88&#x000d;&#x000a;P3: 9&#x000d;&#x000a;P4: 1&#x000d;&#x000a;P5: fffff80324c1cb2b&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\061019-5000-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6531-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B55.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B56.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B65.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B85.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_96eb2480b7e1e2bf7c56aaeb6b33021b3ee103c_00000000_cab_2b0e8390-ad2b-4749-8464-ed4f1c0c2ba4&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: f83991fc-5234-4abd-b633-5d86efa6bb39&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    6/10/2019 8:38 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: d1&#x000d;&#x000a;P2: 38423eb46d88&#x000d;&#x000a;P3: 9&#x000d;&#x000a;P4: 1&#x000d;&#x000a;P5: fffff80324c1cb2b&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\061019-5000-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6531-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B55.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B56.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B65.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B85.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_96eb2480b7e1e2bf7c56aaeb6b33021b3ee103c_00000000_2b0e8390-ad2b-4749-8464-ed4f1c0c2ba4&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: f83991fc-5234-4abd-b633-5d86efa6bb39&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/20/2019 10:41 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: d1&#x000d;&#x000a;P2: 3d83569f&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: fffff8072744f21a&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\092019-4453-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6531-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E5.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2904.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2914.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_fc85e81063b41ef739ad6b1c73925f0657a22a1_00000000_cab_eb44196b-8b44-4c20-b608-32309c5e3754&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: fb6fd1b7-d4c2-4a9a-af6d-abb62294a840&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/20/2019 10:41 PM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: d1&#x000d;&#x000a;P2: 3d83569f&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: fffff8072744f21a&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\092019-4453-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6531-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E4.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E5.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2904.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2914.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_fc85e81063b41ef739ad6b1c73925f0657a22a1_00000000_eb44196b-8b44-4c20-b608-32309c5e3754&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: fb6fd1b7-d4c2-4a9a-af6d-abb62294a840&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/20/2019 4:43 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: d1&#x000d;&#x000a;P2: ffff808be74bb368&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 1&#x000d;&#x000a;P5: fffff8016243581e&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\091919-5187-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6343-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B36.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B47.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B75.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B85.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_e82d24dd3feca05aae9d3dfb128529161254e_00000000_cab_f8573508-1314-4d66-b0e1-33cdbc9183df&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 2589d1ef-5f64-4e22-bcf3-e559e8bba268&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    9/20/2019 4:43 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: d1&#x000d;&#x000a;P2: ffff808be74bb368&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 1&#x000d;&#x000a;P5: fffff8016243581e&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\091919-5187-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6343-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B36.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B47.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B75.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B85.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_e82d24dd3feca05aae9d3dfb128529161254e_00000000_f8573508-1314-4d66-b0e1-33cdbc9183df&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 2589d1ef-5f64-4e22-bcf3-e559e8bba268&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    8/14/2019 5:23 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: d1&#x000d;&#x000a;P2: ffffc80fb12072d8&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: fffff80413cb5c70&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\081319-5406-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6968-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B07.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B18.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B55.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B85.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_d1_b347181ed6410dbeb2a1b75a3629fa9e66b2c91_00000000_cab_00b4c287-895a-4870-b731-76a250b81a38&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 0629b2c4-8e87-4986-8a02-c7fd6f6b0505&#x000d;&#x000a;Report Status: 2049&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    8/14/2019 5:23 AM	Windows Error Reporting	Fault bucket , type 0&#x000d;&#x000a;Event Name: BlueScreen&#x000d;&#x000a;Response: Not available&#x000d;&#x000a;Cab Id: 0&#x000d;&#x000a;&#x000d;&#x000a;Problem signature:&#x000d;&#x000a;P1: d1&#x000d;&#x000a;P2: ffffc80fb12072d8&#x000d;&#x000a;P3: 2&#x000d;&#x000a;P4: 0&#x000d;&#x000a;P5: fffff80413cb5c70&#x000d;&#x000a;P6: 10_0_18362&#x000d;&#x000a;P7: 0_0&#x000d;&#x000a;P8: 768_1&#x000d;&#x000a;P9: &#x000d;&#x000a;P10: &#x000d;&#x000a;&#x000d;&#x000a;Attached files:&#x000d;&#x000a;\\?\C:\WINDOWS\Minidump\081319-5406-01.dmp&#x000d;&#x000a;\\?\C:\WINDOWS\TEMP\WER-6968-0.sysdata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B07.tmp.WERInternalMetadata.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B18.tmp.xml&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B55.tmp.csv&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B85.tmp.txt&#x000d;&#x000a;&#x000d;&#x000a;These files may be available here:&#x000d;&#x000a;\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_d1_b347181ed6410dbeb2a1b75a3629fa9e66b2c91_00000000_00b4c287-895a-4870-b731-76a250b81a38&#x000d;&#x000a;&#x000d;&#x000a;Analysis symbol: &#x000d;&#x000a;Rechecking for solution: 0&#x000d;&#x000a;Report Id: 0629b2c4-8e87-4986-8a02-c7fd6f6b0505&#x000d;&#x000a;Report Status: 4&#x000d;&#x000a;Hashed bucket: &#x000d;&#x000a;Cab Guid: 0
    Last edited by zbook; 28 Sep 2019 at 14:17.
      My Computer


  10. Posts : 11
    Win 10
    Thread Starter
       #10

    1) Was set to small dumps instead of automatic. I changed it.

    2) 99% certain this is actually the issue. *GBRL is not supported by the motherboard while *GBXL is. I checked the timings and subtimings before installing so as far as I could tell it was just the heatspreader. There were no issues in the PC I pulled *GBRL from and the BSODs started about 3-4 weeks after installing. The fact that it didn't indicate mismatch initially made me think it was a different problem.

    3) No OC

    4) That is the most recent BIOS and I have restored it to default settings

    6) Drivers are up to date. Website here: Support For H87-G43 | Motherboard - The world leader in motherboard design | MSI Global

    9)
    Code:
    Windows PowerShell
    Copyright (C) Microsoft Corporation. All rights reserved.
    
    Try the new cross-platform PowerShell https://aka.ms/pscore6
    
    PS C:\WINDOWS\system32> 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.
    PS C:\WINDOWS\system32> 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.
    PS C:\WINDOWS\system32> 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.
    PS C:\WINDOWS\system32> 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.
    PS C:\WINDOWS\system32> bcdedit --% /enum {badmemory}
    
    RAM Defects
    -----------
    identifier              {badmemory}
    PS C:\WINDOWS\system32>

    19) Will run Memtest again tonight on the RL sticks. Though as I said in an earlier post 86+ doesn't fully support my processor. Should I still use this instead of the non+ version or force multithreading? Would this actually indicate that these sticks are the issue?

    Again thank you both for the help. Has been such an annoying issue for so long.
      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 21:57.
Find Us




Windows 10 Forums