multiple BSODS after reinstalling windows on different disks

[karmigo]

EDIT: it was processor fault, after replacing CPU everything work fine, thanks everyone for help.

Hi,

I am getting BSODs:

- system thread exception not handled
- attempt to write read only memory
- DPC Watchdog Violation
- irql not less or equal

I have reinstalled windows 10 and still get this error. I have tried different SSD and HDD disk. So I suppose it is hardware fault.


Ram was checked with mem test and there was no issue, GPU tried on different pc and no issue Motherboard was returned to me from warranty as fixed.

Could this be CPU (ryzen 1700) fault? I have not checked it in any way. Is there way to determine what is causing the issue?

 

[Colif]

Can you follow option one here
and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD

that creates a file in c windows/minidump after the next BSOD
copy that file to documents
upload the copy from documents to a cloud server and share the link here and someone with right software to read them will help you fix it

do you have the latest BIOS?

 

[karmigo]

Hi,
Thanks for help. There are dump files:
https://uploadfiles.io/fuvnb - memory dump

https://uploadfiles.io/nkf70 - mini dump
https://uploadfiles.io/itaxl - mini dump
https://uploadfiles.io/9yodm - mini dump

It looks like I do not have the latest bios. I have:
bios ver: E7A33AMS.160
bios build date: 09/20/2017
while on msi bios website latest version is 7A33v1B relased on 03/20/2018

 

[Colif]

those could all be memory errors and a new BIOS might be all you need so try updating and see. I will ask someone to look at the dump files.

 

[incorrector]

indeed,seems memory errors,but try another sata cable if BIOS update didn't fix the issue

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://pste.eu/p/PZw4.html

File: 050118-3718-01.dmp (Apr 28 2018 - 05:09:00)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: memory_corruption (Process: amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.0_none_36d3ccc3ddfd1ec)
Uptime: 0 Day(s), 0 Hour(s), 10 Min(s), and 27 Sec(s)

File: 042818-4750-01.dmp (Apr 28 2018 - 04:22:29)
BugCheck: [SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007E)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 45 Sec(s)

File: 050118-3484-02.dmp (May 1 2018 - 02:25:48)
BugCheck: [IRQL_NOT_LESS_OR_EQUAL (A)]
Probably caused by: memory_corruption (Process: TrustedInstaller.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 47 Sec(s)

File: memory.dmp (May 1 2018 - 02:22:22)
BugCheck: [BAD_POOL_HEADER (19)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 10 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

its sure not drivers, you only had one loaded at time of last bsod, the LAN drivers.

never seen this crash due to an IRQ error - amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.0_none_36d3ccc3ddfd1ec - seems its tied into windows update, https://superuser.com/questions/1096947/what-is-the-servicing-stack-and-how-does-it-work

So is trustedInstaller, it is what windows uses to install all programs.

these aren't programs that normally cause bsod.

 

[karmigo]

hey,

I have updated BIOS and have now SATA cable. Unfortunately I still have the same issue.

I can start PC and sometimes it give BSOD before windows will start properly other time it would start and crash after 5 minutes. Sometimes when it start I cant open start menu other times it would open without any problem

 

[Colif]

keep uploading dump files, one of them might give us a clue.

It might be a faulty motherboard, its odd that Gardenmans program can't see the ram speed or amount of sticks installed. Those details might show now you have a newer bios. What ram do you have?

 

[karmigo]

RAM: Corsair Vengeance LPX DDR4, 2x8GB, 3200MHz, CL16

in BIOS I can set to run at 3200MHz and 2133 MHz - I get BSODs on Both setups

I have 2 ram stick, I tried running PC with each one ram stick and I still get the error.

mni dumps when 1 ram stick is used
https://ufile.io/2hklu
https://ufile.io/jttx9
https://ufile.io/xh5h0

2 ram sticks:
https://ufile.io/n8v9o
https://ufile.io/6x1k2
https://ufile.io/gomw8

in original post I have told that I had motherboard returned from warranty, they changed bios processor (I am not 100% sure it is how it is named in English) and was told that I should run SATA in AHCI mode. I am running it in AHCI mode.

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://pste.eu/p/bLjh.html

Spoiler

File: 050618-4312-01.dmp (May 6 2018 - 07:02:37)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: ntkrnlmp.exe (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 44 Sec(s)

File: 050618-4031-01.dmp (May 6 2018 - 07:17:44)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: ntkrnlmp.exe (Process: TrustedInstaller.exe)
Uptime: 0 Day(s), 0 Hour(s), 03 Min(s), and 09 Sec(s)

File: 050618-4015-01.dmp (May 6 2018 - 07:03:51)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: ntkrnlmp.exe (Process: TiWorker.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 48 Sec(s)

File: 050618-3890-01.dmp (May 6 2018 - 06:51:03)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: ntkrnlmp.exe (Process: TiWorker.exe)
Uptime: 0 Day(s), 0 Hour(s), 02 Min(s), and 05 Sec(s)

File: 050618-3484-01.dmp (May 6 2018 - 06:52:33)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: ntkrnlmp.exe (Process: TiWorker.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 02 Sec(s)

File: 050618-3343-01.dmp (May 6 2018 - 06:54:54)
BugCheck: [MEMORY_MANAGEMENT (1A)]
Probably caused by: ntkrnlmp.exe (Process: TiWorker.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 54 Sec(s)

Motherboard: https://www.msi.com/Motherboard/support/X370-KRAIT-GAMING#down-bios
A new BIOS was just released for your system. Note: Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

tiworker and trusted installer are both parts of windows installation.. TIworker = Windows Modules installer. TrustedInstaller installs all application in windows.

I mean, it could be the CPU but CPU's normally cause other errors, these are all data errors. PC isn't staying on long enough to run any checks, its crashing as soon as it just tries to install updates.

What are you using as boot drive? SSD or hdd? What brand?

Memory management errors can be drivers, ram or hdd.

You have run memtest
You have a new motherboard - BIOS update doesn't mention memory compatability but it might help
PC crashes as soon as you try to install things, so perhaps it is the HDD/SSD

 

[karmigo]

HDD: Toshiba P300 - (HDWD110UZSVA)
SSD: ADATA SU800 512GB SATA 3 (ASU800SS-512GT-C

I have memory BSODs when I use SSD.

I have tried HDD again and I don't get memory errors. When windows is running I din't get BSODS after running it for 30 minutes 2 times.

I have other issues with HDD.
- I get often BSODs when windows is starting
- I can't update windows using autoupdate due to error 0x800736ccc, running build in windows repair tool for updating did not worked
- Openning start menu take like 1 second
- I get many errors in event viewer from multiple windows apps

minidumps from HDD that i get on windows startup:
https://ufile.io/c1r50
https://ufile.io/h0k1r
https://ufile.io/6b4cc
https://ufile.io/qrll8
https://ufile.io/gbd0b

So it looks like SSD is broken and there is also other issue with PC. Could it cause memory errors on SSD?

I have tried different GPU and RAM stick while using SSD and I was still getting Memory BSODS.

I have created RMA warranty request for SSD. What do you think about windows BSODS while using HDD?

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://pste.eu/p/GKsT.html

Spoiler

File: 051118-29453-01.dmp (May 11 2018 - 15:07:56)
BugCheck: [CRITICAL_PROCESS_DIED (EF)]
Probably caused by: ntkrnlmp.exe (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 32 Sec(s)

File: 051118-25937-01.dmp (May 11 2018 - 15:57:28)
BugCheck: [PFN_LIST_CORRUPT (4E)]
Probably caused by: memory_corruption (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 27 Sec(s)

File: 051118-25484-01.dmp (May 11 2018 - 14:34:01)
BugCheck: [KERNEL_SECURITY_CHECK_FAILURE (139)]
Probably caused by: memory_corruption (Process: smss.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 31 Sec(s)

File: 051118-25140-01.dmp (May 11 2018 - 15:53:48)
BugCheck: [CRITICAL_PROCESS_DIED (EF)]
Probably caused by: ntkrnlmp.exe (Process: csrss.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 23 Sec(s)

File: 051118-24781-01.dmp (May 11 2018 - 15:11:05)
BugCheck: [SYSTEM_SERVICE_EXCEPTION (3B)]
Probably caused by: dxgkrnl.sys (Process: csrss.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 47 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[Colif]

I am going to get a 2nd opinion on this, I wonder if its the CPU itself as it is where the memory controller is

You are getting different types of BSOD on the hdd compared to SSD, they are at least more common files to see in a BSOD.
csrss.exe is the user client
smss.exe = Session manager subsystem (okay, not so usual)
svhost = service host - all processes to run on PC are associated with a host (so not very specific)

the error at 15.11pm was caused by Direct X - common cause of DX errors are GPU drivers

 

[okcnaline]

1) Perhaps update Windows?
2) Perhaps remake a Windows 10 install USB?

 

[smorizio]

try a test power supply and onboard video. see if it bsod. if your power supply not holding or rippling out it show up those memory errors in windows. look in the bios and use hardware info to check your power supply output.

 

[karmigo]

Hi,

Thanks for help so far.

BIOS / PSU - BIOS screens: https://imgur.com/a/mIS6soL

I am not sure what I should look for in BIOS for PSU.

Windows reinstalled on different disks and using different USB sticks before - not helping


GPU - I could run dx11 game for 30 minutes, tried running unreal engine demo 5 times and had no crash.

CPU - Tried running Prime95 for stress test,

test 1: memory managament error BSOD after like 20 minutes, all CPS were running at 100%
test 2: after around 20 minutes prime95 crashed
test 3: after around 20 minutes prime95 crashed
test 4: after around around 1 hour CPU 1 and 2 stopped working at 100 % and worker 4 process in prime95 also stopped working and created log in spoiler tah, other cpus still running at 100% after 6 hours

Spoiler

[May 13 10:15] Worker starting

[May 13 10:15] Beginning a continuous self-test on your computer.

[May 13 10:15] Please read stress.txt. Choose Test/Stop to end this test.

[May 13 10:15] Test 1, 52000 Lucas-Lehmer iterations of M6225921 using FMA3 FFT length 320K, Pass1=320, Pass2=1K, clm=1.

[May 13 10:24] Self-test 320K passed!

[May 13 10:24] Test 1, 3200000 Lucas-Lehmer iterations of M172031 using FMA3 FFT length 8K, Pass1=128, Pass2=64, clm=2.

[May 13 10:32] Self-test 8K passed!

[May 13 10:32] Test 1, 44000 Lucas-Lehmer iterations of M7471105 using FMA3 FFT length 384K, Pass1=384, Pass2=1K, clm=1.

[May 13 10:40] Self-test 384K passed!

[May 13 10:40] Test 1, 1800000 Lucas-Lehmer iterations of M250519 using FMA3 FFT length 12K, Pass1=256, Pass2=48, clm=1.

[May 13 10:45] Self-test 12K passed!

[May 13 10:45] Test 1, 36000 Lucas-Lehmer iterations of M8716289 using FMA3 FFT length 448K, Pass1=448, Pass2=1K, clm=2.

[May 13 10:53] Self-test 448K passed!

[May 13 10:53] Test 1, 1400000 Lucas-Lehmer iterations of M339487 using FMA3 FFT length 16K.

[May 13 10:59] Self-test 16K passed!

[May 13 10:59] Test 1, 31000 Lucas-Lehmer iterations of M9961473 using FMA3 FFT length 512K, Pass1=512, Pass2=1K, clm=1.

[May 13 11:06] Self-test 512K passed!

[May 13 11:06] Test 1, 1100000 Lucas-Lehmer iterations of M420217 using FMA3 FFT length 20K.

[May 13 11:11] Self-test 20K passed!

[May 13 11:11] Test 1, 26000 Lucas-Lehmer iterations of M12451841 using FMA3 FFT length 640K, Pass1=640, Pass2=1K, clm=1.

[May 13 11:19] Self-test 640K passed!

[May 13 11:19] Test 1, 840000 Lucas-Lehmer iterations of M501041 using FMA3 FFT length 24K, Pass1=384, Pass2=64, clm=2.

[May 13 11:24] Self-test 24K passed!

[May 13 11:24] Test 1, 21000 Lucas-Lehmer iterations of M14942209 using FMA3 FFT length 768K, Pass1=768, Pass2=1K, clm=1.

[May 13 11:31] Self-test 768K passed!

[May 13 11:31] Test 1, 720000 Lucas-Lehmer iterations of M580673 using FMA3 FFT length 28K, Pass1=448, Pass2=64, clm=2.

[May 13 11:37] Self-test 28K passed!

[May 13 11:37] Test 1, 18000 Lucas-Lehmer iterations of M17432577 using FMA3 FFT length 896K, Pass1=896, Pass2=1K, clm=1.

[May 13 11:44] FATAL ERROR: Final result was 00000000, expected: E7FEF929.

[May 13 11:44] Hardware failure detected, consult stress.txt file.

[May 13 11:44] Torture Test completed 13 tests in 1 hour, 29 minutes - 1 errors, 0 warnings.

[May 13 11:44] Worker stopped.

I have tried to run OCCT and on CPU it gave error at 15 second. Started it more times to check if till reappear but it did not.
https://imgur.com/a/vK7UvcE - album with results
https://ufile.io/ghu6y - folder in 7zip file with results

RAM:
My ram model - CMK16GX4M2B3200C16

My ram is listed on AMD site: https://www.amd.com/system/files/2017-06/am4-motherboard-memory-support-list-en_0.pdf
But on MSI site there is only model with "R" and "W" at the end: https://msi.com/Motherboard/support/X370-KRAIT-GAMING#support-test

Could ram test not detect issues with it but due to incompatibility it would be causing issues anyway?

Could the ram incompatibility issue appear after 10 months?
Would changing ram to "R" model fix this issue? Could using incompatible ram for 10 months harm CPU or motherboard?


minidumps:
https://ufile.io/i2ps6
https://ufile.io/mub5j
https://ufile.io/qzqll
https://ufile.io/hh7i1
https://ufile.io/yc3qw

 

[gardenman]

I ran the dump files through the debugger and got the following information: https://pste.eu/p/plw8.html

Spoiler

File: 051318-26468-01.dmp (May 13 2018 - 15:38:19)
BugCheck: [PFN_LIST_CORRUPT (4E)]
Probably caused by: memory_corruption (Process: drvinst.exe)
Uptime: 0 Day(s), 0 Hour(s), 07 Min(s), and 51 Sec(s)

File: 051318-25609-01.dmp (May 13 2018 - 12:59:23)
BugCheck: [CRITICAL_PROCESS_DIED (EF)]
Probably caused by: ntkrnlmp.exe (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 50 Sec(s)

File: 051318-25156-01.dmp (May 13 2018 - 12:57:54)
BugCheck: [CRITICAL_PROCESS_DIED (EF)]
Probably caused by: ntkrnlmp.exe (Process: svchost.exe)
Uptime: 0 Day(s), 0 Hour(s), 01 Min(s), and 43 Sec(s)

File: 051318-25000-01.dmp (May 13 2018 - 12:53:10)
BugCheck: [PFN_LIST_CORRUPT (4E)]
Probably caused by: memory_corruption (Process: dwm.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 24 Sec(s)

File: 051318-23250-01.dmp (May 13 2018 - 15:22:36)
BugCheck: [STATUS_SYSTEM_PROCESS_TERMINATED (C000021A)]
Probably caused by: ntkrnlmp.exe (Process: smss.exe)
Uptime: 0 Day(s), 0 Hour(s), 00 Min(s), and 52 Sec(s)

I can't help you with this. Wait for additional replies. Good luck.

 

[smorizio]

under bios enveroment screen that tell you the temp and voltages of the 3.3/5v/12v lines. make sure all of them are within atx wiki spec. also use hardware info set it to logging and sensor in the program watch the three main rail voltages.

 

[karmigo]

hi, it was processor fault, 1 week after replacing CPU everything work fine, thanks everyone for help.

 

[Colif]

One less mystery solved.

I wish AMD had software we could test CPU out with. Intel have their own diagnostic tool but AMD don't.

Only choice I know of is Prime95 - I should have suggested it as it does test CPU and ram, and may have found the broken part of CPU sooner.