Windows 10: BSOD Video_memory_managment_internal

Discus and support BSOD Video_memory_managment_internal in Windows 10 BSOD Crashes and Debugging to solve the problem; the laptop was on sleep when I turned it on the next day it gave me that crash .. the only thing that was open when it was on was a movie on gom player... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by CMBADR, May 1, 2016.

  1. CMBADR Win User

    BSOD Video_memory_managment_internal


    the laptop was on sleep when I turned it on the next day it gave me that crash .. the only thing that was open when it was on was a movie on gom player that was paused

    :)
     
    CMBADR, May 1, 2016
    #1

  2. Driver Verifier BSOD diagnosis opinions?

    Thank you very much for looking at this.

    I followed the directions for uninstalling the drivers, and attempted to install new ones that I

    downloaded from my motherboard maker, ASUS.
    Unfortunately, they don't provide audio drivers for anything past Win 7 64 bit, but even though I'm running Win 10, I tried them. The computer would still crash when I ran driver verifier at startup and I had
    to use a restore point.

    When I checked which drivers were installed, however, it seemed to still be reverting to the original ones that initially caused the problem. So, I did some research on my own and used the Windows Show or Hide Updates program to make sure VIA wasn't auto-updating,
    but the issues persisted. So, as a last resort, I simply went to device manager and updated the audio drivers to Win 10 provided by Microsoft, but I'm still getting the driver verifier crash before the system starts. My computer is presently in this state.
    As long as I don't use driver verifier, it doesn't crash at startup, but I bet it will after normal sustained use.

    The new dump files are here from the trials above. I'm curious if they're all still pointing to the audio driver, and if so/not,
    what other steps you might recommend?
     
    BSOD Monster, May 1, 2016
    #2
  3. Driver Verifier BSOD diagnosis opinions?

    I used the link provided and selected the option that says the BSOD occurred while using my PC. The link suggests checking for updates and disconnecting hardware. My software is already up to date, and rather than disconnecting random hardware, I was under
    the impression from that by uploading the dump files from the Driver Verifier program that from

    this post
    , there might be some clues as to what specific driver is causing the crashes. Is that possible to determine?
     
    BSOD Monster, May 1, 2016
    #3
  4. axe0 New Member

    BSOD Video_memory_managment_internal

    Please remove / disable items from the startup in taskmanager
    These programs could interfere with the boot process giving you trouble and increase the boot time.

    Please remove these programs so they won't cause any trouble while troubleshooting
    Code: Start Menu\Programs\ReviverSoft\Driver Reviver Public:Start Menu\Programs\ReviverSoft\Driver Reviver Public Start Menu\Programs\ReviverSoft\PC Reviver Public:Start Menu\Programs\ReviverSoft\PC Reviver Public[/quote] It is recommended that you revert back the changes they made using a restore point prior the use of them.

    If you have switchable GPUs configured, please make sure you're using only 1 GPU.

    Unfortunately no specific display driver has been named, this makes it a little more difficult to find out which GPU is causing issues but that is also why we need to make sure your laptop is only using either of the GPUs. After you've configured your system to use only 1 GPU try to replicate the crash with each of the GPUs to see if there is any difference.

    You've had a 0x10E which is a video memory management internal error, which is why I focus this post mostly on finding out which of the GPUs was used at the moment of the crash.

    Analysis:
    Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) The video memory manager encountered a condition that it can't recover from. By crashing, the video memory manager is attempting to get enough information into the minidump such that somebody can pinpoint what lead to this condition. Arguments: Arg1: 0000000000000017, Unexpected system command failure. Arg2: ffffe00063c00000 Arg3: 0000000000000000 Arg4: ffffffffc00002b6 Debugging Details: ------------------ SYSTEM_SKU: Default string SYSTEM_VERSION: REV:1.0 BIOS_DATE: 01/07/2016 BASEBOARD_PRODUCT: MS-1794 BASEBOARD_VERSION: REV:0.A BUGCHECK_P1: 17 BUGCHECK_P2: ffffe00063c00000 BUGCHECK_P3: 0 BUGCHECK_P4: ffffffffc00002b6 BUGCHECK_STR: 0x10e_17 CPU_COUNT: 8 CPU_MHZ: a20 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 5e CPU_STEPPING: 3 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 10.0.10240.9 amd64fre LAST_CONTROL_TRANSFER: from fffff800c05e3e1d to fffff800f3fd3760 STACK_TEXT: ffffd000`cdb57958 fffff800`c05e3e1d : 00000000`0000010e 00000000`00000017 ffffe000`63c00000 00000000`00000000 : nt!KeBugCheckEx ffffd000`cdb57960 fffff800`c2c18952 : ffffe000`63c00000 ffffe000`62190e38 ffffe000`63c00000 ffffe000`62190e38 : watchdog!WdLogEvent5_WdCriticalError+0xcd ffffd000`cdb579a0 fffff800`c17243d8 : ffffe000`628af530 ffffd000`2ad18600 ffffe000`62183b80 ffffe000`63c00000 : dxgmms2!VIDMM_GLOBAL::RestoreFromPurge+0x15ad2 ffffd000`cdb57a20 fffff800`c16ee4e0 : 00000000`00000000 ffffe000`6217d010 ffffd000`2ad186b0 fffff800`c1741600 : dxgkrnl!ADAPTER_RENDER::RestoreFromPurgeSegments+0x5c ffffd000`cdb57a50 fffff800`c1706632 : ffffe000`61101190 ffffe000`61101c28 fffff800`c1741600 00000000`00000000 : dxgkrnl!DXGADAPTER::ReleaseCoreSync+0xa0 ffffd000`cdb57a80 fffff800`c1741726 : ffffe000`61101190 00000000`00000000 00000000`00000000 ffffe000`6a005100 : dxgkrnl!DxgkReleaseAdapterCoreSync+0x12 ffffd000`cdb57ab0 fffff800`f3f74895 : ffffe000`61101b18 ffffe000`612ed800 00000000`00000080 fffff800`c1741640 : dxgkrnl!DpiPowerArbiterThread+0xe6 ffffd000`cdb57b10 fffff800`f3fd8906 : ffffd000`cc9b0180 ffffe000`612ed800 fffff800`f3f74854 ffffd000`cdcc71e0 : nt!PspSystemThreadStartup+0x41 ffffd000`cdb57b60 00000000`00000000 : ffffd000`cdb58000 ffffd000`cdb51000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 STACK_COMMAND: kb FOLLOWUP_IP: dxgmms2!VIDMM_GLOBAL::RestoreFromPurge+15ad2 fffff800`c2c18952 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: dxgmms2!VIDMM_GLOBAL::RestoreFromPurge+15ad2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: dxgmms2 IMAGE_NAME: dxgmms2.sys DEBUG_FLR_IMAGE_TIMESTAMP: 56cd4793 IMAGE_VERSION: 10.0.10586.162 BUCKET_ID_FUNC_OFFSET: 15ad2 FAILURE_BUCKET_ID: 0x10e_17_dxgmms2!VIDMM_GLOBAL::RestoreFromPurge BUCKET_ID: 0x10e_17_dxgmms2!VIDMM_GLOBAL::RestoreFromPurge PRIMARY_PROBLEM_CLASS: 0x10e_17_dxgmms2!VIDMM_GLOBAL::RestoreFromPurge ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x10e_17_dxgmms2!vidmm_global::restorefrompurge FAILURE_ID_HASH: {080c4a7e-6c7f-a390-e7c9-ccc78d5fe562} Followup: MachineOwner --------- [SMBIOS Data Tables v3.0] [DMI Version - 0] [2.0 Calling Convention - No] [Table Size - 4244 bytes] [OEM Strings (Type 11) - Length 5 - Handle 0000h] Number of Strings 5 1 2 $BIOSE1110000000000000000 3 4 5 [BIOS Information (Type 0) - Length 24 - Handle 0001h] Vendor American Megatrends Inc. BIOS Version E1794IMS.10C BIOS Starting Address Segment f000 BIOS Release Date 01/07/2016 BIOS ROM Size 600000 BIOS Characteristics 07: - PCI Supported 11: - Upgradeable FLASH BIOS 12: - BIOS Shadowing Supported 15: - CD-Boot Supported 16: - Selectable Boot Supported 19: - EDD Supported 23: - 1.2MB Floppy Supported 24: - 720KB Floppy Supported 25: - 2.88MB Floppy Supported 26: - Print Screen Device Supported 27: - Keyboard Services Supported 28: - Serial Services Supported 29: - Printer Services Supported 32: - BIOS Vendor Reserved BIOS Characteristic Extensions 00: - ACPI Supported 01: - USB Legacy Supported 08: - BIOS Boot Specification Supported 10: - Specification Reserved 11: - Specification Reserved BIOS Major Revision 1 BIOS Minor Revision 12 EC Firmware Major Revision 255 EC Firmware Minor Revision 255 [System Information (Type 1) - Length 27 - Handle 0002h] Manufacturer Micro-Star International Co., Ltd. Product Name GE72 6QF Version REV:1.0 Serial Number 9S7179441015ZG1000034 UUID 00000000-0000-0000-0000-000000000000 Wakeup Type Power Switch SKUNumber Default string Family [BaseBoard Information (Type 2) - Length 15 - Handle 0003h] Manufacturer Micro-Star International Co., Ltd. Product MS-1794 Version REV:0.A Serial Number BSS-0123456789 Asset Tag Feature Flags 09h -924964544: - (null) -924964496: - (null) Location Default string Chassis Handle 0004h Board Type 0ah - Processor/Memory Module Number of Child Handles 0 [System Enclosure (Type 3) - Length 22 - Handle 0004h] Manufacturer Micro-Star International Co., Ltd. Chassis Type Notebook Version Default string Serial Number Asset Tag Number Bootup State Safe Power Supply State Safe Thermal State Safe Security Status None OEM Defined 0 Height 0U Number of Power Cords 1 Number of Contained Elements 0 Contained Element Size 3 [Onboard Devices Information (Type 10) - Length 6 - Handle 0022h] Number of Devices 1 01: Type Video [enabled] 01: Description To Be Filled By O.E.M. [System Configuration Options (Type 12) - Length 5 - Handle 0023h] [Cache Information (Type 7) - Length 19 - Handle 003eh] Socket Designation L1 Cache Cache Configuration 0180h - WB Enabled Int NonSocketed L1 Maximum Cache Size 0080h - 128K Installed Size 0080h - 128K Supported SRAM Type 0020h - Synchronous Current SRAM Type 0020h - Synchronous Cache Speed 0ns Error Correction Type ParitySingle-Bit ECC System Cache Type Data Associativity 8-way Set-Associative [Cache Information (Type 7) - Length 19 - Handle 003fh] Socket Designation L1 Cache Cache Configuration 0180h - WB Enabled Int NonSocketed L1 Maximum Cache Size 0080h - 128K Installed Size 0080h - 128K Supported SRAM Type 0020h - Synchronous Current SRAM Type 0020h - Synchronous Cache Speed 0ns Error Correction Type ParitySingle-Bit ECC System Cache Type Instruction Associativity 8-way Set-Associative [Cache Information (Type 7) - Length 19 - Handle 0040h] Socket Designation L2 Cache Cache Configuration 0181h - WB Enabled Int NonSocketed L2 Maximum Cache Size 0400h - 1024K Installed Size 0400h - 1024K Supported SRAM Type 0020h - Synchronous Current SRAM Type 0020h - Synchronous Cache Speed 0ns Error Correction Type Multi-Bit ECC System Cache Type Unified Associativity 4-way Set-Associative [Cache Information (Type 7) - Length 19 - Handle 0041h] Socket Designation L3 Cache Cache Configuration 0182h - WB Enabled Int NonSocketed L3 Maximum Cache Size 1800h - 6144K Installed Size 1800h - 6144K Supported SRAM Type 0020h - Synchronous Current SRAM Type 0020h - Synchronous Cache Speed 0ns Error Correction Type Specification Reserved System Cache Type Unified Associativity Specification Reserved [Processor Information (Type 4) - Length 48 - Handle 0042h] Socket Designation U3E1 Processor Type Central Processor Processor Family c6h - Specification Reserved Processor Manufacturer Intel(R) Corporation Processor ID e3060500fffbebbf Processor Version Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Processor Voltage 8bh - 1.1V External Clock 100MHz Max Speed 3500MHz Current Speed 3100MHz Status Enabled Populated Processor Upgrade Other L1 Cache Handle 003fh L2 Cache Handle 0040h L3 Cache Handle 0041h Serial Number Asset Tag Number Part Number To Be Filled By O.E.M. [Physical Memory Array (Type 16) - Length 23 - Handle 0043h] Location 03h - SystemBoard/Motherboard Use 03h - System Memory Memory Error Correction 03h - None Maximum Capacity 67108864KB Memory Error Inf Handle [Not Provided] Number of Memory Devices 4 [Memory Device (Type 17) - Length 40 - Handle 0044h] Physical Memory Array Handle 0043h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 8192MB Form Factor 0dh - SODIMM Device Set [None] Device Locator ChannelA-DIMM0 Bank Locator BANK 0 Memory Type 1ah - Specification Reserved Type Detail 0080h - Synchronous Speed 2133MHz Manufacturer Samsung Serial Number Asset Tag Number Part Number M471A1K43BB0-CPB [Memory Device (Type 17) - Length 40 - Handle 0045h] Physical Memory Array Handle 0043h Memory Error Info Handle [Not Provided] Total Width 0 bits Data Width 0 bits Size [Not Populated] Form Factor 02h - Unknown Device Set [None] Device Locator ChannelA-DIMM1 Bank Locator BANK 1 Memory Type 02h - Unknown Type Detail 0000h - Speed 0MHz Manufacturer [String Not Specified] Serial Number [String Not Specified] Asset Tag Number [String Not Specified] Part Number [String Not Specified] [Memory Device (Type 17) - Length 40 - Handle 0046h] Physical Memory Array Handle 0043h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 8192MB Form Factor 0dh - SODIMM Device Set [None] Device Locator ChannelB-DIMM0 Bank Locator BANK 2 Memory Type 1ah - Specification Reserved Type Detail 0080h - Synchronous Speed 2133MHz Manufacturer Samsung Serial Number Asset Tag Number Part Number M471A1K43BB0-CPB [Memory Device (Type 17) - Length 40 - Handle 0047h] Physical Memory Array Handle 0043h Memory Error Info Handle [Not Provided] Total Width 0 bits Data Width 0 bits Size [Not Populated] Form Factor 02h - Unknown Device Set [None] Device Locator ChannelB-DIMM1 Bank Locator BANK 3 Memory Type 02h - Unknown Type Detail 0000h - Speed 0MHz Manufacturer [String Not Specified] Serial Number [String Not Specified] Asset Tag Number [String Not Specified] Part Number [String Not Specified] [Memory Array Mapped Address (Type 19) - Length 31 - Handle 0048h] Starting Address 00000000h Ending Address 00ffffffh Memory Array Handle 0043h Partition Width 02 [Memory Device Mapped Address (Type 20) - Length 35 - Handle 004ah] Starting Address 00000000h Ending Address 007fffffh Memory Device Handle 0044h Mem Array Mapped Adr Handle 0048h Partition Row Position [Unknown] Interleave Position 01 Interleave Data Depth 02 [Memory Device Mapped Address (Type 20) - Length 35 - Handle 004bh] Starting Address 00800000h Ending Address 00ffffffh Memory Device Handle 0046h Mem Array Mapped Adr Handle 0048h Partition Row Position [Unknown] Interleave Position 02 Interleave Data Depth 02 Machine ID Information [From Smbios 3.0, DMIVersion 0, Size=4244] BiosMajorRelease = 1 BiosMinorRelease = 12 BiosVendor = American Megatrends Inc. BiosVersion = E1794IMS.10C BiosReleaseDate = 01/07/2016 SystemManufacturer = Micro-Star International Co., Ltd. SystemProductName = GE72 6QF SystemFamily = SystemVersion = REV:1.0 SystemSKU = Default string BaseBoardManufacturer = Micro-Star International Co., Ltd. BaseBoardProduct = MS-1794 BaseBoardVersion = REV:0.A CPUID: "Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz" MaxSpeed: 2600 CurrentSpeed: 2592 GetPointerFromAddress: unable to read from fffff800f4210200 THREAD ffffe000612ed800 Cid 0004.01b8 Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 5 Not impersonating GetUlongFromAddress: unable to read from fffff800f415ffa8 Owning Process ffffe0005c0da680 Image: System Attached Process N/A Image: N/A fffff78000000000: Unable to get shared data Wait Start TickCount 11739110 Context Switch Count 953 IdealProcessor: 5 ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address dxgkrnl!DpiPowerArbiterThread (0xfffff800c1741640) Stack Init ffffd000cdb57b90 Current ffffd000cdb57420 Base ffffd000cdb58000 Limit ffffd000cdb51000 Call 0 Priority 14 BasePriority 8 UnusualBoost 5 ForegroundBoost 0 IoPriority 2 PagePriority 5 Child-SP RetAddr : Args to Child : Call Site ffffd000`cdb57958 fffff800`c05e3e1d : 00000000`0000010e 00000000`00000017 ffffe000`63c00000 00000000`00000000 : nt!KeBugCheckEx ffffd000`cdb57960 fffff800`c2c18952 : ffffe000`63c00000 ffffe000`62190e38 ffffe000`63c00000 ffffe000`62190e38 : watchdog!WdLogEvent5_WdCriticalError+0xcd ffffd000`cdb579a0 fffff800`c17243d8 : ffffe000`628af530 ffffd000`2ad18600 ffffe000`62183b80 ffffe000`63c00000 : dxgmms2!VIDMM_GLOBAL::RestoreFromPurge+0x15ad2 ffffd000`cdb57a20 fffff800`c16ee4e0 : 00000000`00000000 ffffe000`6217d010 ffffd000`2ad186b0 fffff800`c1741600 : dxgkrnl!ADAPTER_RENDER::RestoreFromPurgeSegments+0x5c ffffd000`cdb57a50 fffff800`c1706632 : ffffe000`61101190 ffffe000`61101c28 fffff800`c1741600 00000000`00000000 : dxgkrnl!DXGADAPTER::ReleaseCoreSync+0xa0 ffffd000`cdb57a80 fffff800`c1741726 : ffffe000`61101190 00000000`00000000 00000000`00000000 ffffe000`6a005100 : dxgkrnl!DxgkReleaseAdapterCoreSync+0x12 ffffd000`cdb57ab0 fffff800`f3f74895 : ffffe000`61101b18 ffffe000`612ed800 00000000`00000080 fffff800`c1741640 : dxgkrnl!DpiPowerArbiterThread+0xe6 ffffd000`cdb57b10 fffff800`f3fd8906 : ffffd000`cc9b0180 ffffe000`612ed800 fffff800`f3f74854 ffffd000`cdcc71e0 : nt!PspSystemThreadStartup+0x41 ffffd000`cdb57b60 00000000`00000000 : ffffd000`cdb58000 ffffd000`cdb51000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16 Bugcheck code 0000010E Arguments 00000000`00000017 ffffe000`63c00000 00000000`00000000 ffffffff`c00002b6 Debug session time: Mon May 2 13:18:26.885 2016 (UTC + 2:00) System Uptime: 2 days 2:57:03.594[/quote]
     
    axe0, May 1, 2016
    #4
  5. CMBADR Win User
    I have an Nvidia card and an intel default one how can I make sure only one is working? and Driver reviver and PC reviver I chose for them not to open on startup before that problem happened .. I also checked in task manager as you said and didn't find them open in the startup tab
     
    CMBADR, May 6, 2016
    #5
  6. axe0 New Member
    You've understood me wrong about those programs, I asked that you remove these programs + I asked to cleanup your startup programs. You can use Ccleaner to remove startup items.
    Attachment 78577

    Normally with Nividia you have software in which it is configurable, at least that is what I've seen so far with laptops using Nvidia GPUs
     
    axe0, Apr 5, 2018
    #6
Thema:

BSOD Video_memory_managment_internal

Loading...
  1. BSOD Video_memory_managment_internal - Similar Threads - BSOD Video_memory_managment_internal

  2. BSOD when launching VALORANT

    in Windows 10 Gaming
    BSOD when launching VALORANT: Out of the blue I started getting a BSOD when launching VALORANT, only started today as I was still able to play yesterday.It gave me the PAGE_FAULT_IN_NONPAGED_AREA error.I have already tried running sfc/scannow and chkdisk, reinstalled VALORANT and Riot Vanguard but to no...
  3. BSOD when launching VALORANT

    in Windows 10 Software and Apps
    BSOD when launching VALORANT: Out of the blue I started getting a BSOD when launching VALORANT, only started today as I was still able to play yesterday.It gave me the PAGE_FAULT_IN_NONPAGED_AREA error.I have already tried running sfc/scannow and chkdisk, reinstalled VALORANT and Riot Vanguard but to no...
  4. I need help fixing my BSOD bootloop in my laptop, it occured after updating the latest...

    in Windows 10 Gaming
    I need help fixing my BSOD bootloop in my laptop, it occured after updating the latest...: This type or errors are being displayed. https://answers.microsoft.com/en-us/windows/forum/all/i-need-help-fixing-my-bsod-bootloop-in-my-laptop/b7d9ce41-f5a0-4199-883e-cd864f0288d6
  5. I need help fixing my BSOD bootloop in my laptop, it occured after updating the latest...

    in Windows 10 Software and Apps
    I need help fixing my BSOD bootloop in my laptop, it occured after updating the latest...: This type or errors are being displayed. https://answers.microsoft.com/en-us/windows/forum/all/i-need-help-fixing-my-bsod-bootloop-in-my-laptop/b7d9ce41-f5a0-4199-883e-cd864f0288d6
  6. BSOD IRQL_NOT_LESS_OR_EQUAL - Can anyone help me analyze the minidump?

    in Windows 10 Gaming
    BSOD IRQL_NOT_LESS_OR_EQUAL - Can anyone help me analyze the minidump?: Hi there,Can anyone help me analyze what's causing an issue with a PC.Here's the minidump.Thank you.******************************************************************************** ** Bugcheck Analysis **...
  7. BSOD IRQL_NOT_LESS_OR_EQUAL - Can anyone help me analyze the minidump?

    in Windows 10 Software and Apps
    BSOD IRQL_NOT_LESS_OR_EQUAL - Can anyone help me analyze the minidump?: Hi there,Can anyone help me analyze what's causing an issue with a PC.Here's the minidump.Thank you.******************************************************************************** ** Bugcheck Analysis **...
  8. BSOD IRQL_NOT_LESS_OR_EQUAL - Can anyone help me analyze the minidump?

    in Windows 10 BSOD Crashes and Debugging
    BSOD IRQL_NOT_LESS_OR_EQUAL - Can anyone help me analyze the minidump?: Hi there,Can anyone help me analyze what's causing an issue with a PC.Here's the minidump.Thank you.******************************************************************************** ** Bugcheck Analysis **...
  9. BSOD issue BugcheckCode 268435582

    in Windows 10 Gaming
    BSOD issue BugcheckCode 268435582: Hi,I've gotten two BSODs within a very short time frame. Apparently some RAM/driver issue.Here are the minidump files: MinidumpI ran the Windows memory diagnostic tool and it came back "The Windows Memory Diagnostic tested the computer's memory and detected no errors"Can...
  10. BSOD issue BugcheckCode 268435582

    in Windows 10 Software and Apps
    BSOD issue BugcheckCode 268435582: Hi,I've gotten two BSODs within a very short time frame. Apparently some RAM/driver issue.Here are the minidump files: MinidumpI ran the Windows memory diagnostic tool and it came back "The Windows Memory Diagnostic tested the computer's memory and detected no errors"Can...