TLDR: I got BSOD but I got 2 stop codes or no Blue Screen at all (the PC just froze and restart after a while). 2 Stop Codes being SYSTEM_THREAD_EXCEPTION_NOT_HANDLED and MEMORY_MANAGEMENT. One of the three (one of the 2 codes or no Blue Screens) happens when Win 10 Crashes. Log from "WhoCrashed" at the end of post.
In case the whole story will help: I played Dark Souls 1 Item Randomizer mod for a week without problem (while recording and streaming), then a few days ago I started to get my first total system crash without a BSOD, my Dark Souls monitor froze and another monitor just goes black. After a while the computer reboots.
Next day I continue my run, after around 1.5 hours, BSOD happened with stop code of SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. The following few days I continues to experience BSOD with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED except sometimes the stop code will be MEMORY_MANAGEMENT without any file names after it.
Then I realize the very first day I experience the crash was right after my GTX 1070 driver updated from 390.65 to 390.77. So I thought maybe it messed up my stuff. So I rolled back to 390.65. And I got another MEMORY_MANAGEMENT BSOD without streaming and playing Dark Souls, I was playing Xcom 1 this time.
I thought maybe the rollback was not doing properly (the control panel window stopped responding after I confirmed rollback, but it still showed my version is back to 390.65 in both GF Experience and control panel), I used Display Driver Uninstaller to completely uninstall the driver in safe mode, and then reinstall it. I also did SFC scan with "Windows Resource Protection found corrupt files but was unable to fix some of them" result, and then did a DISM which said I had no problem whatsoever. And then I did a SFCfix which said they repaired everything. I also ran a memory test (which requires you to restart the PC?) and it said nothing is wrong with my RAM.
And...... I just get another BSOD with MEMORY_MANAGEMENT stop code. At first I thought it only happens with I pick up items in Dark Souls or join a covenant, because every BSOD before that is when I "confirm something" in a game, including that Xcom 1 BSOD. But no, this time I am just fighting a boss in Dark Souls 1.
So what gives? My spec is here:
WD Blue WD10EZEX 1TB 7200rpm 64MB 3.5 Inch HDD
Samsung 960 EVO Series - 250GB PCIe NVMe - M.2 SSD
Antec NeoEco II Series NEO-ECO2-550 80Plus Bronze 550W PSU
MSI GeForce® GTX 1070 GAMING X 8GB GDDR5
Corsair VENGEANCE® LED 16GB (2 x 8GB) DDR4 3000MHz C15 - White LED
AMD RYZEN R7 1700 3.7GHz 16M L3 8 Core 16 Thread 65W AM4
Gigabyte GA-AB350M-Gaming 3 AM4 M.ATX
WIN10
WhoCrashed report showed (do not have earlier reports since I only install it after a few crashes):
On Mon 5/2/2018 12:19:09 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020518-6546-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x1A (0x41201, 0xFFFFF30000060000, 0x1, 0xFFFFD888489F2EA0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys MEMORY_MANAGEMENT
In case the whole story will help: I played Dark Souls 1 Item Randomizer mod for a week without problem (while recording and streaming), then a few days ago I started to get my first total system crash without a BSOD, my Dark Souls monitor froze and another monitor just goes black. After a while the computer reboots.
Next day I continue my run, after around 1.5 hours, BSOD happened with stop code of SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. The following few days I continues to experience BSOD with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED except sometimes the stop code will be MEMORY_MANAGEMENT without any file names after it.
Then I realize the very first day I experience the crash was right after my GTX 1070 driver updated from 390.65 to 390.77. So I thought maybe it messed up my stuff. So I rolled back to 390.65. And I got another MEMORY_MANAGEMENT BSOD without streaming and playing Dark Souls, I was playing Xcom 1 this time.
I thought maybe the rollback was not doing properly (the control panel window stopped responding after I confirmed rollback, but it still showed my version is back to 390.65 in both GF Experience and control panel), I used Display Driver Uninstaller to completely uninstall the driver in safe mode, and then reinstall it. I also did SFC scan with "Windows Resource Protection found corrupt files but was unable to fix some of them" result, and then did a DISM which said I had no problem whatsoever. And then I did a SFCfix which said they repaired everything. I also ran a memory test (which requires you to restart the PC?) and it said nothing is wrong with my RAM.
And...... I just get another BSOD with MEMORY_MANAGEMENT stop code. At first I thought it only happens with I pick up items in Dark Souls or join a covenant, because every BSOD before that is when I "confirm something" in a game, including that Xcom 1 BSOD. But no, this time I am just fighting a boss in Dark Souls 1.
So what gives? My spec is here:
WD Blue WD10EZEX 1TB 7200rpm 64MB 3.5 Inch HDD
Samsung 960 EVO Series - 250GB PCIe NVMe - M.2 SSD
Antec NeoEco II Series NEO-ECO2-550 80Plus Bronze 550W PSU
MSI GeForce® GTX 1070 GAMING X 8GB GDDR5
Corsair VENGEANCE® LED 16GB (2 x 8GB) DDR4 3000MHz C15 - White LED
AMD RYZEN R7 1700 3.7GHz 16M L3 8 Core 16 Thread 65W AM4
Gigabyte GA-AB350M-Gaming 3 AM4 M.ATX
WIN10
WhoCrashed report showed (do not have earlier reports since I only install it after a few crashes):
On Mon 5/2/2018 12:19:09 AM your computer crashed or a problem was reported
crash dump file: C:\WINDOWS\Minidump\020518-6546-01.dmp
This was probably caused by the following module: nt_wrong_symbols.sys (nt_wrong_symbols)
Bugcheck code: 0x1A (0x41201, 0xFFFFF30000060000, 0x1, 0xFFFFD888489F2EA0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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: nt_wrong_symbols.sys .
Google query: nt_wrong_symbols.sys MEMORY_MANAGEMENT
Facebook
Twitter
Instagram