This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
From what I can see this case here is identical to my problem:
Back to my case, shorter version:
Last weeks I have had regular BSOD, where one ended in not being able to reboot so I had to reinstall Windows 10 to make it work again. It's really getting to bug me and cost me alot of hours trying to find the error.
Lately the BSOD are all MEMORY_MANAGEMENT but before I removed a faulty disk drive two weeks ago, the message/problem varied from BSOD to BSOD. To me it looked random.
I have probably had some 30+ BSOD now so roughly eash second lately. I need to fix this.
I have installed and done disk checks for all drives looking for problems or corrupted sectors, I had one disk with some corruption on it this has been physically removed. I have done all the RAM checks I can find, and every one tells me there is nothing wrong with the ram. I have also done extensive testing of RAM from some benchmarking suites I downloaded, also under stress the RAM will not fail. Same for disks, have tested and done ekstra read and write tests suits to find errors - but all disks are 100% top shape every software tool tells me. So why does the system crash?
When I reboot it all works great again, nothing lost. The only pattern I find for the crashes are using lots of RAM, I usually have a lot of Google Chrome browser tabs open - this is the only thing I can guess takes any resources.
I installed WhoCrashed, so hoperfully this can help. Also crashes are back on a fresh installed Windows 10 system aswell strangely enough.
Are there some tools I can use to test, do you require any other info than the dump below?
Thanks in advance.
Kim Steinhaug
System Information (local)
Computer name: DESKTOP-SEK6JSC
Windows version: Windows 10 , 10.0, version 1809, build: 17763
Windows dir: C:\WINDOWS
Hardware: MS-7737, MSI, Big Bang-XPower II (MS-7737)
CPU: GenuineIntel Intel(R) Core(TM) i7-3970X CPU @ 3.50GHz Intel8664, level: 6
12 logical processors, active mask: 4095
RAM: 68627722240 bytes (63,9GB)
Crash Dump Analysis
Crash dumps are enabled on your computer.
Crash dump directories:
C:\WINDOWS
C:\WINDOWS\Minidump
On Tue 15.10.2019 13.48.00 your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\MEMORY.DMP
This was probably caused by the following module: hardware.sys (hardware)
Bugcheck code: 0x1A (0x41792, 0xFFFF923FFDE9D660, 0x10000000000, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred. A corrupted PTE has been detected.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: hardware.sys .
Google query: hardware.sys MEMORY_MANAGEMENT
Conclusion
One crash dump has been found and analyzed. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:
If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.
Read the topic general suggestions for troubleshooting system crashes for more information.
Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
At the moment I have 8 RAM slots, and when plugging RAM into 2 of the slots system will generate a BSOD, so I am using the other 6 slots at the moment without any problems. I have not done extensive checks if it's the slots that are problem or if it's the two last RAM bricks that are the problem but right now system is running with 48GB ram and slots 3 and 4 not in use.
So definately problem was either RAM bricks or one of the slots.
Seems noone has interest in debugging this or look into it more than ask me to do more, which is the easy answer anyway... :(
After removing most RAM bricks I havnt had a BSOD since last time I posted, so the error must be in the RAM somehow. Today I start adding bricks back and see when it breaks.
So problem solved: RAM.
I had a quick glance at the WinDBG tool and descided it was pretty advanced and I lack basic understanding on how Windows works under the hood. That being said, anyone know if using this tool (or try using it) is worth my while? Will I learn anything from trying other than spend probabøy a good portion of time on trying.
Maby there are some classic "1.2.3" receipts for finding what the problem is if so I will have a go, if not Ill wait and see if anyone else comfortable with using the tool willl give me some feedback from the crashdump.
My latest theory is that there could be heat problems somewhere, so that in a rare occurence this heat results in memory corruption, and hence the BSOD. The machine has to be some years old and have been running in overclocked mode 24/7 for atleast 3 years straight now - does this matter at all? I feel like taking care of my baby a little, vacuum and rinse not to say add new cooling stuff for the processor.
Ok, I see there are some people around that have theese problems so hopefully some sort of knowledge has exist on what it could be?
BSOF, HOW OFTEN DOES IT HAPPEND:
Probably a daily thing last week, however I have lost all the crashdumps since the one I uploaded as I updated windows settings to save crashdumps into "%SystemRoot%\Minidump". After this change every BSOD ended in 0% freeze on the creation of the crashdump. I have now changed it back to "%SystemRoot%\MEMORY.DMP" so atleast I get the latest crashdump and can add them here.
Also if machine is on and in standby doing nothing, there will probably occur a BSOD within 12 hours even when the machine is doing nothing.
Stresstesting RAM and CPU:
Using "Intel(R) Extreme Tuning Utility" I have several times stresstested both RAM and CPU without any problems at all, same as windows tools requested for checkups of RAM. Every check I do always gives me 100% all in order results, I have never had a BSOD during any stresstest or benchmark either.
How did latest BSOD happend?
I was working in Visual Code when it popped up a notification in the lower right that an extension had crashed, when I clicked the restart extension (or some restart related name in the notification for the crashed extension) - the BSOD instantly appeared. Obviously there were some sort of relation here.
System behaviour before a BSOD
I can usually tell when BSOD is about to happend, usually a Chrome tab will crash so that I need to reload it. That is - when this happends, I usually reboot the system instead to avoid the BSOD. From VisualStudio Code the same behaviour is noticed by an extension crashing, seen by a notification popping up giving me the option to restart the extensions - which will usually result in a BSOD. Here aswell, best to reboot.
I would be very happy if anyone could check the crashdump file(s) i posted, or give me some tips for what I could try doing to avoid the BSOD.
Kim Steinhaug
Thank you for taking time to look into this. I have found such a dumpfile in windows folder, however named MEMORY.DMP and at 2,3GB so I am zipping it down now and will upload it as you requested.
I just had a BSOD now, and this came like lightning from a blue sky. When the machine rebooted (stuck on the 0% in BSOD) I now am faced with a shell that lists loads of drives and mappings. Never saw this before. However, "exit" and enter in the shell the machine boots normally and all is fine again. From what I see the CPU is sold as 3500 hertz but is clocked at 4000 - I will turn this down in BIOS to default. Maby it's time to refresh the cooling pasta and reattach the CPU - the machine is some years old so I guess some maintenance is due. I have installed more software that monitors CPU temperatures now. Regarding the SHELL that appears now in every reboot - could this have something to do with me installing KALI linux in windows10? ( https://www.microsoft.com/nb-no/p/kali-linux/9pkr34tncv07?rtc=1&SilentAuth=1&wa=wsignin1.0&activetab=pivot:overviewtab )
Crashdump file and picture of the new boot shell thingie:
https://1drv.ms/u/s!Aub1F-H72d2towFU2UKD7b7C0foL?e=sgbcdK
I did some analyzing with WinDBG, in case you do not need to download the above file:
The commands done from windbg are devided with "********** ********** **********" lines, and the commands that were used are:
1- load the dump file
2- !analyze -v
3- !blackboxbsd
4- !blackboxpnp
5- lmvm hardware
Microsoft (R) Windows Debugger Version 10.0.19494.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff806`51c0d000 PsLoadedModuleList = 0xfffff806`52028690
Debug session time: Tue Oct 15 12:48:00.573 2019 (UTC + 1:00)
System Uptime: 0 days 12:59:05.351
Loading Kernel Symbols
.....................................Page 20018e590 too large to be in the dump file.
Page 20018e58f too large to be in the dump file.
..........................
................................................................
..................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`013ce018). Type ".hh dbgerr001" for details
Loading unloaded module list
...............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`51dc1050 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffbb03`45c13ec0=000000000000001a
********** ********** **********9: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041792, A corrupt PTE has been detected. Parameter 2 contains the address of
the PTE. Parameters 3/4 contain the low/high parts of the PTE.
Arg2: ffff923ffde9d660
Arg3: 0000010000000000
Arg4: 0000000000000000
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 40
Key : Analysis.Memory.CommitPeak.Mb
Value: 67
Key : Analysis.System
Value: CreateObject
BUGCHECK_CODE: 1a
BUGCHECK_P1: 41792
BUGCHECK_P2: ffff923ffde9d660
BUGCHECK_P3: 10000000000
BUGCHECK_P4: 0
MEMORY_CORRUPTOR: ONE_BIT
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
PROCESS_NAME: git.exe
STACK_TEXT:
ffffbb03`45c13eb8 fffff806`51e210ad : 00000000`0000001a 00000000`00041792 ffff923f`fde9d660 00000100`00000000 : nt!KeBugCheckEx
ffffbb03`45c13ec0 fffff806`51cb5637 : ffffbb03`45c14059 00000100`00000000 0000007f`fffffff8 00000000`00000000 : nt!MiDeleteVa+0x1660dd
ffffbb03`45c13fd0 fffff806`51cb5a2a : ffffbb03`45c144f0 ffff9249`00000000 ffffbb03`00000000 0a000007`00000000 : nt!MiWalkPageTablesRecursively+0x2c7
ffffbb03`45c140c0 fffff806`51cb5a2a : ffffbb03`45c144f0 00000000`00000000 ffffbb03`00000001 8a000006`00000000 : nt!MiWalkPageTablesRecursively+0x6ba
ffffbb03`45c141b0 fffff806`51cb5a2a : ffffbb03`45c144f0 00000000`00000000 ffffbb03`00000002 ffff9249`00000000 : nt!MiWalkPageTablesRecursively+0x6ba
ffffbb03`45c142a0 fffff806`51cb4eea : ffffbb03`45c144f0 00000000`00000000 00000000`00000003 ffffe50f`00000000 : nt!MiWalkPageTablesRecursively+0x6ba
ffffbb03`45c14390 fffff806`51cb77fd : ffffbb03`45c144f0 fffff806`00000001 ffffe50f`00000000 00000000`00000000 : nt!MiWalkPageTables+0x1ea
ffffbb03`45c14480 fffff806`51cb8355 : 00000000`00000000 ffffe50f`2e2df8b0 ffffbb03`00000001 00000000`00000000 : nt!MiDeletePagablePteRange+0x1dd
ffffbb03`45c146c0 fffff806`52254411 : fffff806`5204a940 00000000`00000000 ffffe50f`395b7500 ffffe50f`228e7300 : nt!MiDeleteVad+0x7c5
ffffbb03`45c14830 fffff806`52253ff8 : ffffe50f`395b7500 ffffe50f`228e7300 ffffe50f`207f6080 00000000`00000000 : nt!MiUnmapVad+0x49
ffffbb03`45c14860 fffff806`52211267 : ffffe50f`395b76e0 ffffe50f`395b76e0 ffffe50f`395b7500 ffffe50f`228e7300 : nt!MiCleanVad+0x30
ffffbb03`45c14890 fffff806`522865bd : ffffffff`00000000 ffffffff`ffffffff ffffbb03`45c14b01 ffffe50f`2e2df540 : nt!MmCleanProcessAddressSpace+0x113
ffffbb03`45c14910 fffff806`52265f28 : ffffe50f`2e2df540 ffff9403`b4567060 ffffbb03`45c14b80 00000000`00000000 : nt!PspRundownSingleProcess+0x129
ffffbb03`45c14990 fffff806`5229338b : 00000000`00000000 ffffbb03`45c14b01 00000000`013cf000 ffffe50f`207f6080 : nt!PspExitThread+0x5c8
ffffbb03`45c14a90 fffff806`51dd2308 : ffffe50f`000035d4 ffffe50f`207f6080 ffffe50f`2e2df540 00000000`00000000 : nt!NtTerminateProcess+0xeb
ffffbb03`45c14b00 00007ffb`d5f1fce4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000000`015f79a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`d5f1fce4
SYMBOL_NAME: ONE_BIT
MODULE_NAME: hardware
IMAGE_NAME: memory_corruption
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
OS_VERSION: 10.0.17763.1
BUILDLAB_STR: rs5_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e3faf315-c3d0-81db-819a-6c43d23c63a7}
Followup: MachineOwner
---------********** ********** **********9: kd> !blackboxbsdVersion: 168Product type: 1Auto advanced boot: FALSEAdvanced boot menu timeout: 30
Last boot succeeded: TRUE
Last boot shutdown: FALSE
Sleep in progrees: FALSE
Power button timestamp: 0
System running: TRUE
Connected standby in progress: FALSE
User shutdown in progress: FALSE
System shutdown in progress: FALSE
Sleep in progress: 0
Connected standby scenario instance id: 0
Connected standby entry reason: 0
Connected standby exit reason: 0
System sleep transitions to on: 0
Last reference time: 0x1d5834795f2cf11
Last reference time checksum: 0xc022d55d
Last update boot id: 50
Boot attempt count: 1
Last boot checkpoint: TRUE
Checksum: 0x14
Last boot id: 50
Last successful shutdown boot id: 49
Last reported abnormal shutdown boot id: 49
Error info boot id: 0
Error info repeat count: 0
Error info other error count: 0
Error info code: 0
Error info other error count: 0
Power button last press time: 0
Power button cumulative press count: 0
Power button last press boot id: 0
Power button last power watchdog stage: 0
Power button watchdog armed: FALSE
Power button shutdown in progress: FALSE
Power button last release time: 0
Power button cumulative release count: 0
Power button last release boot id: 0
Power button error count: 0
Power button current connected standby phase: 0
Power button transition latest checkpoint id: 0
Power button transition latest checkpoint type: 0
Power button transition latest checkpoint sequence number: 0********** ********** **********9: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 132156056154020539
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : SWD\RADIO\{03B0EFCE-DACA-4A92-99DD-7B422BE00B46}
VetoString :
********** ********** **********9: kd> lmvm hardware
Browse full module list
start end module name
Hi Kim
I am Vijay, an Independent Advisor. I am assuming you are able to get into your computer. If not, please let me know.
A. Let me know the make and model of your computer.
B. To know what exactly is causing the crashes, I need to analyze minidumps generated by crashes with WinDBG. WinDBG is the only tool which can do end to end complete analysis of ..dmp files generated by BSOD (Blue screen of death).
Go to C:\Windows\Minidump
Zip the contents of the folder corresponding to date and time of your crashes.
Upload the content to Onedrive or any other file sharing site for me to locate the problem.
If you don't get minidump files in above folder, you will need to enable minidump generation. If you need help to generate Minidump - http://answers.microsoft.com/en-us/windows/wiki...
HOW TO UPLOAD TO ONEDRIVE