Windows 10: BSOD/crash playing games, memory error on shutdown

In this period of the latest Microsoft upgrade some of our windbg commands are not working limiting the debugging.
The unexpected shutdowns with bugcheck 1a and 139 were noted.




Code: 10/8/2017 5:35 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 109 P2: a39fcd5ad35599de P3: b3b6d9e125d88451 P4: ffffdb2ebe7e4030 P5: c P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100717-7046-01.dmp \\?\C:\Windows\Temp\WER-8765-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AB9.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AC9.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2ACA.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_109_53442b596245217bb73b8515668ac078ea2a415b_00000000_cab_14a42bb3 Analysis symbol: Rechecking for solution: 0 Report Id: be86ef82-454b-4489-8016-40e3c3809371 Report Status: 2049 Hashed bucket:10/8/2017 5:35 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 109 P2: a39fcd5ad35599de P3: b3b6d9e125d88451 P4: ffffdb2ebe7e4030 P5: c P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100717-7046-01.dmp \\?\C:\Windows\Temp\WER-8765-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AB9.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AC9.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2ACA.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_109_53442b596245217bb73b8515668ac078ea2a415b_00000000_03082ac9 Analysis symbol: Rechecking for solution: 0 Report Id: be86ef82-454b-4489-8016-40e3c3809371 Report Status: 4 Hashed bucket:10/18/2017 4:35 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 12b P2: ffffffffc00002c4 P3: c56 P4: 107ff60 P5: ffffc801c46fa000 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\101717-6015-01.dmp \\?\C:\Windows\Temp\WER-7984-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26B2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26C1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26D2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_12b_c76d26c2709a18cfa752fd3bebab11e1fdee8b_00000000_cab_104427ac Analysis symbol: Rechecking for solution: 0 Report Id: 4e5972cf-8df0-4e33-bac9-e1097f87ae73 Report Status: 2049 Hashed bucket:10/18/2017 4:35 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 12b P2: ffffffffc00002c4 P3: c56 P4: 107ff60 P5: ffffc801c46fa000 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\101717-6015-01.dmp \\?\C:\Windows\Temp\WER-7984-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26B2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26C1.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26D2.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_12b_c76d26c2709a18cfa752fd3bebab11e1fdee8b_00000000_02ec26d1 Analysis symbol: Rechecking for solution: 0 Report Id: 4e5972cf-8df0-4e33-bac9-e1097f87ae73 Report Status: 4 Hashed bucket:10/19/2017 3:44 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffff9e80a87b7470 P4: ffff9e80a87b73c8 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\101817-5812-01.dmp \\?\C:\Windows\Temp\WER-7765-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25D7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25F6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25F7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_139_7581868615cfa34c1d168d4ab02a9548ec5ef516_00000000_cab_07b2f61e Analysis symbol: Rechecking for solution: 0 Report Id: 4c057639-3fd5-4fa1-b710-ff2d58178af6 Report Status: 2049 Hashed bucket:10/19/2017 3:41 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 139 P2: 3 P3: ffff9e80a87b7470 P4: ffff9e80a87b73c8 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\101817-5812-01.dmp \\?\C:\Windows\Temp\WER-7765-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25D7.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25F6.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25F7.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_139_7581868615cfa34c1d168d4ab02a9548ec5ef516_00000000_031025f6 Analysis symbol: Rechecking for solution: 0 Report Id: 4c057639-3fd5-4fa1-b710-ff2d58178af6 Report Status: 4 Hashed bucket:10/26/2017 5:32 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 41791 P3: ffff97800aea60b0 P4: ffff9d4e80006960 P5: e1 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102517-6312-01.dmp \\?\C:\Windows\Temp\WER-7750-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2654.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2673.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2684.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_fb3ae8bf1fbd5db129facdbb93133c773dbafa4_00000000_cab_0b36e96c Analysis symbol: Rechecking for solution: 0 Report Id: bc5cc12f-a631-4cd2-81e1-134cc04a45d2 Report Status: 2049 Hashed bucket:10/26/2017 5:29 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 41791 P3: ffff97800aea60b0 P4: ffff9d4e80006960 P5: e1 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\102517-6312-01.dmp \\?\C:\Windows\Temp\WER-7750-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2654.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2673.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2684.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_fb3ae8bf1fbd5db129facdbb93133c773dbafa4_00000000_03402683 Analysis symbol: Rechecking for solution: 0 Report Id: bc5cc12f-a631-4cd2-81e1-134cc04a45d2 Report Status: 4 Hashed bucket:10/2/2017 3:33 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 41791 P3: ffffab8007ea6110 P4: ffffc2611ffffea0 P5: f5 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100117-6375-01.dmp \\?\C:\Windows\Temp\WER-6906-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2599.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2599.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25A9.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_1a_c453c1662ed534f78758ac6bc2c9936c0104dbc_00000000_cab_2ca8ef90 Analysis symbol: Rechecking for solution: 0 Report Id: ea2f3968-4dbf-46c1-a889-05b694338b0f Report Status: 2049 Hashed bucket:10/2/2017 3:32 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 1a P2: 41791 P3: ffffab8007ea6110 P4: ffffc2611ffffea0 P5: f5 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100117-6375-01.dmp \\?\C:\Windows\Temp\WER-6906-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2599.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2599.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER25A9.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_1a_c453c1662ed534f78758ac6bc2c9936c0104dbc_00000000_031c25a8 Analysis symbol: Rechecking for solution: 0 Report Id: ea2f3968-4dbf-46c1-a889-05b694338b0f Report Status: 4 Hashed bucket:10/10/2017 3:17 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff80183cdf8af P4: ffffbe81f7e06c40 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100917-6296-01.dmp \\?\C:\Windows\Temp\WER-6890-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2431.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2441.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2442.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_3b_76d4c799354dfcc811e6e287491bc2594043f8a6_00000000_cab_078ee94c Analysis symbol: Rechecking for solution: 0 Report Id: 6b3855ff-5068-4a09-a8c1-c91926843356 Report Status: 2049 Hashed bucket:10/10/2017 3:14 AM Windows Error Reporting Fault bucket , type 0 Event Name: BlueScreen Response: Not available Cab Id: 0 Problem signature: P1: 3b P2: c0000005 P3: fffff80183cdf8af P4: ffffbe81f7e06c40 P5: 0 P6: 10_0_15063 P7: 0_0 P8: 768_1 P9: P10: Attached files: \\?\C:\WINDOWS\Minidump\100917-6296-01.dmp \\?\C:\Windows\Temp\WER-6890-0.sysdata.xml \\?\C:\WINDOWS\MEMORY.DMP \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2431.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2441.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2442.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_3b_76d4c799354dfcc811e6e287491bc2594043f8a6_00000000_03082450 Analysis symbol: Rechecking for solution: 0 Report Id: 6b3855ff-5068-4a09-a8c1-c91926843356 Report Status: 4 Hashed bucket:[/quote]

 

Please find the memory dumps and post a one drive or drop box share link into the thread.

%SystemRoot%\MEMORY.DMP
or
C:\Windows\MEMORY.DMP

Use file explorer > this PC > local C: drive > right upper corner search enter each of the above to find results.

 

I zipped them to reduce upload/download time.
MEMORY.DMP: Dropbox - MEMORY.zip

I also uploaded a zip of my Minidump folder:
Dropbox - Minidump.zip

 

The important command was not able to be ran on the memory dump.
We will have to wait for more mini dumps.
The bugchecks for the mini dumps have been:
1A
3B
12B
109
139
RAM has not yet been tested.
Whenever you have a new BSOD please post a new zip into the thread.

 

Have you finished all HDD tests on your partitions / hard drives?

 

Another update since it's been 2 days...

The crashes have continued to happen, but no more BSOD so far. It still just goes into that weird state where the computer is still on and working, but I just can't re-launch the game that crashed.

I ran a memtest86+ for most of the day today just to make sure that's covered. It completed 4 passes with no problems.

I still need to do the chkdsk /r on one of the drives (the 3TB), which is going to take almost all day which is why I haven't done it yet. However, all drives/partitions have been done with HD Tune and screenshots are spread throughout the thread.

Next time it gets into that state, I have a few things I want to look at. I'm not sure why I haven't tried this, but I should make sure all drives are actually accessible at that point. I've already tried restarting Explorer in this state, as well as closing a bunch of background programs. I should probably try restarting whatever launcher for the game (steam or blizzard)...any other things I should try when in the broken state?

Here are some things that I've noticed that might or might not be related (though probably not?). It generally only happens on the first boot of the day. Also on the first boot of the day, the windows 'press a key to actually see your login' splash lags a bit in the animation when it's going away, but not on subsequent boots. It also seems to happen more often when I've had a browser open, although I generally do browsing before gaming so it also falls into first boot of the day territory.

 

Had another BSOD with stop message KMODE_EXCEPTION_NOT_HANDLED (0x1e) and after it rebooted, my wireless didn't connect automatically; had to toggle wifi off and on. Is that a coincidence (b/c hal.dll is the one blamed in the dump file) or a potential cause? I had this same model of wireless card in my old computer and it would not connect automatically sometimes as well.

Wireless card is the tp-link TL-WDN4800. I've just updated drives for it using the Atheros driver for AR938x since it's the same chipset and that's actually what's printed in Device Manager.

 

Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 complete passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.

Make a photo of the result and post it.

Addition:
If errors show up you can stop the test, remove all sticks but 1 and test this single stick in each slot for 8 passes or until errors show, switch sticks and repeat.
If errors show up and you see them a lot later, no problem, the errors don't affect the test.

 

Ran MemTest86+ for over 8 passes, no errors. Have gotten 2 more blue screens with even more stop messages, both playing Destiny 2. Interestingly, one of the crashes happened during the same cutscene as a previous one but with a different stop message and a slightly different place in the cutscene.

This latest crash went into the broken state briefly first. It actually blue screened when I tried to access my third hard drive. I heard it spin up (WD Blacks are loud), saw the files inside, then BSOD. Could have just been delayed from the crash though since it was only about 30 seconds between. I'm first going to try to turn off Windows power saving putting that drive to sleep, and if I continue to have crashes I'll unplug that drive. EDIT: turns out Hard Disk is already set to never turn off...I could have sworn I heard/felt it spin up

 

Please uninstall everything of Nvidia using Display Driver Uninstaller and install new drivers from Nvidia. Be sure the clean install box is checked and only install the Graphics driver and the PhysX driver, you can use this tutorial for the installation part *Arrow NVIDIA Drivers - Avoid Problems - Windows 7 Help Forums

 

I unplugged my third hard drive that wasn't in use and re installed Nvidia drivers. It did still crash (no BSOD), but it was after 3 hours rather than 1. I did notice some frame drops occasionally after an hour or so of playing Destiny 2, more than I'd expect and have gotten in the past.

I'm not sure what else to check atm...I might try and install one of my crash-prone games onto the third hard drive. It's possible that heat is an issue for my second drive; during HD Tune tests, both HDDs were hovering around 55C and I know that my case temperature does rise after hours of gameplay. It would make since that unplugging my third drive would delay the issue since they are in a drive bay next to each other, but doesn't make sense that it would be fine for even longer play sessions after a reboot...

I was monitoring temperatures and they were within reason; CPU maxing at 55C and GPU maxing at 73C. GPU was hovering around 65 near the beginning, and rose slowly over the course of the play session.

 

I've had a few more BSODs, however when I went to create the usual dm log, I noticed it say there were no minidumps. My computer did recently update to Fall Creators, and I don't have the 'Disable automatic deletion of memory dumps when disk space is low' ticked, but the drive isn't even half full.

Anyways, I'm going to try some more troubleshooting steps and wanted to run them by the thread before actually doing them:
- Re-seat graphics card and memory. Already done today, will be doing a test (aka, normal nightly gaming) to see if it crashes.
- Move a crash-prone game to third hard drive and unplug current
- Swap out my 1080 for my old 750TI I still have lying around
- Buy a single 16GB DDR4 RAM stick and use that in a different slot. Unfortunately my cooler covers one of the memory slots, so I can have a max of 3 sticks. If nothing else, I'm upgrading to 32GB of RAM =P Probably last test b/c it involves spending money
- Reinstall Windows

Anyone have a suggested order I should attempt these in? I'm thinking next step is probably either install on third drive and unplug second, or swap graphics cards

 

Re: memory. This is what the manual for your board shows:











16GB is probably the max DIMM you can have in a single slot.

 

@Ztruker Memory is now in that configuration. Before they were both in the DIMMB slots.

Had another blue screen after ~20 mins on Divinity: Original Sin 2, then played for another hour and half no problem...I think reinstalling things on third hard drive and removing second is my next move.

I also haven't said this so far this thread, but thank you all for helping me through this troubleshooting. It's so strange how it seems to be pointing to everything, but every test run comes back with no problems...