We’ve been having a lot of storms in the area lately and I don’t have a surge protector or UPS, so I immediately close out WoW and shut down when things sound bad outside and this has lead to a Memory Management BSOD.
Microsoft (R) Windows Debugger Version 10.0.18317.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022619-6156-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 17134 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff801`d1004000 PsLoadedModuleList = 0xfffff801`d13b2150
Debug session time: Tue Feb 26 19:12:10.670 2019 (UTC - 6:00)
System Uptime: 0 days 2:33:22.672
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`d11ae0c0 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff8187`06c4f660=000000000000001a
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000003453, The subtype of the bugcheck.
Arg2: ffff868acd998080
Arg3: 0000000000139a10
Arg4: 0000000000000003
Debugging Details:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804
SYSTEM_MANUFACTURER: System manufacturer
SYSTEM_PRODUCT_NAME: System Product Name
SYSTEM_SKU: SKU
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 0606
BIOS_DATE: 12/12/2017
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: PRIME Z370-A
BASEBOARD_VERSION: Rev X.0x
DUMP_TYPE: 2
BUGCHECK_P1: 3453
BUGCHECK_P2: ffff868acd998080
BUGCHECK_P3: 139a10
BUGCHECK_P4: 3
BUGCHECK_STR: 0x1a_3453
CPU_COUNT: c
CPU_MHZ: c78
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: a
CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 84'00000000 (cache) 84'00000000 (init)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: Battle.net.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-DBK2GPL
ANALYSIS_SESSION_TIME: 02-26-2019 20:39:17.0901
ANALYSIS_VERSION: 10.0.18317.1001 amd64fre
LAST_CONTROL_TRANSFER: from fffff801d11fc29c to fffff801d11ae0c0
STACK_TEXT:
ffff8187`06c4f658 fffff801`d11fc29c : 00000000`0000001a 00000000`00003453 ffff868a`cd998080 00000000`00139a10 : nt!KeBugCheckEx
ffff8187`06c4f660 fffff801`d1574e8f : ffff868a`cd998080 00000000`00000000 00000000`00000000 ffff868a`cd998640 : nt!MiDeleteFinalPageTables+0xfd358
ffff8187`06c4f710 fffff801`d10fcbcf : ffff868a`cd998080 00000000`00000000 ffff868a`cc7d0080 ffff868a`6e497350 : nt!MmDeleteProcessAddressSpace+0x5f
ffff8187`06c4f760 fffff801`d1502c00 : 00000000`00000000 ffff868a`cd998050 00000000`00000000 00000000`00000000 : nt!PspProcessDelete+0x13f
ffff8187`06c4f7f0 fffff801`d10990a6 : 00000000`00000000 00000000`00000000 00000000`00000000 ffff868a`cd998080 : nt!ObpRemoveObjectRoutine+0x80
ffff8187`06c4f850 fffff801`d14f85d9 : 00000000`ffff8006 ffff868a`c2edbf20 ffff868a`c2edbf20 ffff868a`cd998050 : nt!ObfDereferenceObjectWithTag+0xc6
ffff8187`06c4f890 fffff801`d158b1f5 : 00000000`01f85b5c ffff868a`cadde280 00000000`00000001 00000000`00000080 : nt!ObCloseHandleTableEntry+0x259
ffff8187`06c4f9d0 fffff801`d15578d9 : 00000000`00000000 00000000`40010004 ffff868a`cbf9b878 ffffffff`ffffff01 : nt!ExSweepHandleTable+0xc5
ffff8187`06c4fa80 fffff801`d14ab331 : ffffffff`ffffffff ffff868a`cbf9b580 ffffffff`00000000 ffff868a`00000000 : nt!ObKillProcess+0x35
ffff8187`06c4fab0 fffff801`d14b9d8c : ffff868a`cbf9b580 ffffa682`e0d48990 ffff8187`06c4fcc8 00000000`00000000 : nt!PspRundownSingleProcess+0x121
ffff8187`06c4fb30 fffff801`d159e843 : 00000000`40010004 00000000`00000001 00000000`00664000 00000000`00000000 : nt!PspExitThread+0x5ac
ffff8187`06c4fc30 fffff801`d109e390 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSchedulerApcTerminate+0x33
ffff8187`06c4fc70 fffff801`d11b2170 : 00000000`0000000a ffff8187`06c4fd00 00000000`00000000 00000000`00000000 : nt!KiDeliverApc+0x3a0
ffff8187`06c4fd00 fffff801`d11be7ea : ffff868a`cc7d0080 00000000`00000000 00000000`00000020 ffff868a`cc2cc150 : nt!KiInitiateUserApc+0x70
ffff8187`06c4fe40 00007ffd`74e3e690 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
00000000`09c3f8e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`74e3e690
THREAD_SHA1_HASH_MOD_FUNC: 9d5af0ebd06843cf176ac2a72bb10130e43a97a3
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 46cb8b5512dd137b2e210a460d3a79ba65f046bc
THREAD_SHA1_HASH_MOD: 38bc5fec3f0409c265cf5c87da6f8f8859d0711c
FOLLOWUP_IP:
nt!MiDeleteFinalPageTables+fd358
fffff801`d11fc29c cc int 3
FAULT_INSTR_CODE: 6483cccc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!MiDeleteFinalPageTables+fd358
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5c5a45ab
IMAGE_VERSION: 10.0.17134.590
STACK_COMMAND: .thread ; .cxr ; kb
IMAGE_NAME: memory_corruption
BUCKET_ID_FUNC_OFFSET: fd358
FAILURE_BUCKET_ID: 0x1a_3453_nt!MiDeleteFinalPageTables
BUCKET_ID: 0x1a_3453_nt!MiDeleteFinalPageTables
PRIMARY_PROBLEM_CLASS: 0x1a_3453_nt!MiDeleteFinalPageTables
TARGET_TIME: 2019-02-27T01:12:10.000Z
OSBUILD: 17134
OSSERVICEPACK: 590
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2019-02-05 20:25:47
BUILDDATESTAMP_STR: 180410-1804
BUILDLAB_STR: rs4_release
BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804
ANALYSIS_SESSION_ELAPSED_TIME: 1574
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1a_3453_nt!mideletefinalpagetables
FAILURE_ID_HASH: {5341b5a0-5b02-2da1-51b3-df124a48f6f9}
Followup: MachineOwner
---------
Looks like the battle.net app was corrupted. You might need to uninstall the battle.net app and reinstall.
The fastest way (I know) to shut the computer down.
ctrl+alt+del then click the power button at the lower right of the screen, then click shut down. It will then close all running programs, and shut down.
I’m not sure if it was corruption or on their side. I had posted my DMP file to some computer guys and they said that battle.net was at fault, and not my hardware and thought I’d report it.
Is shutting down from the start down menu any different from your mothod?
I would start with updating windows to be current.
Also post a dxdiag
DxDiag
1.Press Windows Key + R.
2.Type DxDiag and press Enter.
3.In the DxDiag window, click Save All Information.
4.Name the file “dxdiag” and click Save
5.Open the txt file above select all, copy and paste to this thread.
You can include the DXDIAG in a reply to the forum post. Place it between rows of ticks (`) for formatting:
```
Like this.
```
If it will not allow you to post the whole thing post it on pastebin.com just post the last section of the link see the highlight section below .
Hey, Jaoel! Based on the dump files, the issue points to kernel, driver, or memory pools (paged pool/nonpaged pool) based crashes. Just the process (Battle.net) is what was opened when the crash occurred. Likely what is happening is when the Blizzard Application opens it calls a specific driver or kernel that is causing those crashes.
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
It’s hard to diagnose blue screens specifically without testing. This could be due to the network drivers on the system. A clean install for the network drivers may help. There was an issue earlier with Malwarebytes where disabling the Web Protection or a full uninstall resolved the NETIO.SYS blue screen crashes.
Blue screens are not supported as the cause for blue screens are due to kernel, driver, or hardware issues. Was the system reviewed by local technicians or the system manufacturer?
With discretion or with a local technician, it can help to try just one RAM stick at a time for Memory Corruption issues. It looks like there’s 16GB on here, which might be 2x8GB or 4x4GB. Does it crash only with specific RAM?
Hopefully this is informative and may give some more troubleshooting to try! Bluescreens are troublesome issues to run into. It is recommended to contact a local technician or possibly external hardware communities for help reading those dump files more clearly
I did a memtest and got 3 passes, so it’s not the memory.
The DMP files were looked at by people on Microsoft forums.
I updated my graphics drivers because I was on a stable release and hadn’t needed to update in a few months. I also turned off razer stats at @northernlite’s suggestion.
I also posted everything to microsoft forums and they are saying it most likely has something to do with the latest windows update since it’s been happening in the past 2 weeks. They’ve seen a lot of people complain MEMORY MANAGEMENT errors recently. Also, someone in my guild got the same BSOD error last night in a similar circumstance. His computer was on idle and then he came back and immediate BSOD, same message.
If it’s not the latest windows update, then the only thing left to do is stress test drivers over two days and see if I can find the culprit.
I just wanted to post here to see that if it maybe was on your end, then I could help others by reporting it. And even then, I’m sure others are having the same problem and are looking around wondering what the heck it is and hopefully they stumble upon this thread, lol.
Appreciate the update, Jaoel! After some search, it does appear the latest updates after February 20th have had increase Memory Management reports with Windows. Thanks for bring this to our attention!
There has not been a consistent report of this with Battle.net and Bluescreens, but we will continue to monitor for any issues! It does appear from some external resources reverting the February 20th update has helped some folks out, unfortunately none specifically calling the specific updates.
Hopefully, the troubleshooting with Microsoft and the drivers will lead to a solid resolution. Feel free let us know if it does help!
