skrnl.exe (nt+0x16C310) - ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

The BSOD posting instructions are there for a reason. The zip log created will contain many more files than the mini-dumps and they can all help in troubleshooting so it is much better to do as we instruct in the header and post them.

philc43 said:

The BSOD posting instructions are there for a reason. The zip log created will contain many more files than the mini-dumps and they can all help in troubleshooting so it is much better to do as we instruct in the header and post them.

if you check this file it is included what ever you need

Code:

https://drive.google.com/file/d/0By2bF4_O_j5AQXNDWEhYcW1lVlU/view?usp=sharing

mirror :

Code:

https://www.dropbox.com/s/5ldxkafixbymcya/DESKTOP-EAP4OL8-Sat_05_13_2017_201027_99.zip?dl=0

other mirror :

Code:

https://1drv.ms/u/s!AuV35THT-jT2hmAD7Q5DzzJ5M3x3

Many thanks for the additional files. Unfortunately debugging the creators update is problematic at the moment so I can't do a full analysis. For example if you look at your drivers.txt file you will see the dates are all over the place so I can't tell which are correct. Memory corruption is suggested as you already know but if you have run the memtest diagnostic correctly and let it run for around 10 passes (overnight or longer) with no errors then there is a not a lot more I can suggest.

philc43 said:

Many thanks for the additional files. Unfortunately debugging the creators update is problematic at the moment so I can't do a full analysis. For example if you look at your drivers.txt file you will see the dates are all over the place so I can't tell which are correct. Memory corruption is suggested as you already know but if you have run the memtest diagnostic correctly and let it run for around 10 passes (overnight or longer) with no errors then there is a not a lot more I can suggest.

i ran memtest for 2 hour and memtest+ for 1 pass and windows memory diag

none of them shows any error

but i am getting BSOD Closer and closer

it is fun because for example i just open ORBIT downloader and set a file for download and after 2 hours BSOD happened

Code:

On Sun 5/14/2017 8:06:17  AM your computer crashed
crash dump file:  C:\Windows\Minidump\051417-26109-01.dmp
uptime: 02:00:47
This was probably  caused by the following module: ntoskrnl.exe (nt+0x16C310) 
Bugcheck code: 0x1A  (0x41793, 0xFFFFCD013FB39FF8, 0x2, 0x1)
Error: MEMORY_MANAGEMENT
file path:  C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &  System
Bug check description: This indicates that a severe memory management  error occurred.
This might be a case of memory corruption. More often memory  corruption happens because of software errors in buggy drivers, not because of  faulty RAM modules. 
The crash took place in the Windows kernel. Possibly  this problem is caused by another driver that cannot be identified at this time.  



On  Sun 5/14/2017 5:34:26 AM your computer crashed
crash dump file:  C:\Windows\Minidump\051417-27218-01.dmp
uptime: 01:01:06
This was probably  caused by the following module: ntoskrnl.exe (nt+0x16C310) 
Bugcheck code: 0x1A  (0x41792, 0xFFFFFE00DCE90158, 0x100000000000000, 0x0)
Error: MEMORY_MANAGEMENT
file path:  C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &  System
Bug check description: This indicates that a severe memory management  error occurred.
This might be a case of memory corruption. More often memory  corruption happens because of software errors in buggy drivers, not because of  faulty RAM modules. 
The crash took place in the Windows kernel. Possibly  this problem is caused by another driver that cannot be identified at this time.  



On  Sun 5/14/2017 4:32:57 AM your computer crashed
crash dump file:  C:\Windows\Minidump\051417-26562-01.dmp
uptime: 00:14:30
This was probably  caused by the following module: ntoskrnl.exe (nt+0x16C310) 
Bugcheck code: 0x1A  (0x41792, 0xFFFFF380EDEAE158, 0x100000000000000, 0x0)
Error: MEMORY_MANAGEMENT
file path:  C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &  System
Bug check description: This indicates that a severe memory management  error occurred.
This might be a case of memory corruption. More often memory  corruption happens because of software errors in buggy drivers, not because of  faulty RAM modules. 
The crash took place in the Windows kernel. Possibly  this problem is caused by another driver that cannot be identified at this time.  



On  Sun 5/14/2017 4:16:48 AM your computer crashed
crash dump file:  C:\Windows\Minidump\051417-32281-01.dmp
uptime: 01:03:14
This was probably  caused by the following module: ntoskrnl.exe (nt+0x16C310) 
Bugcheck code: 0x34  (0x5122A, 0xFFFFE48144762328, 0xFFFFE48144761B60, 0xFFFFF80148E8A169)
Error:  CACHE_MANAGER
file path:  C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &  System
Bug check description: This indicates that a problem occurred in the  file system's cache manager.
This might be a case of memory corruption. More  often memory corruption happens because of software errors in buggy drivers, not  because of faulty RAM modules. 
The crash took place in the Windows kernel.  Possibly this problem is caused by another driver that cannot be identified at  this time. 



On Sun 5/14/2017 2:15:13 AM your computer  crashed
crash dump file:  C:\Windows\Minidump\051417-25968-01.dmp
uptime: 00:43:26
This was probably  caused by the following module: ntoskrnl.exe (nt+0x16C310) 
Bugcheck code: 0x109  (0xA3A00563A2083573, 0x0, 0xBFB97382BDB042A0, 0x101)
Error: CRITICAL_STRUCTURE_CORRUPTION
file path:  C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &  System
Bug check description: This indicates that the kernel has detected  critical kernel code or data corruption.
This might be a case of memory  corruption. More often memory corruption happens because of software errors in  buggy drivers, not because of faulty RAM modules. 
The crash took place in  the Windows kernel. Possibly this problem is caused by another driver that  cannot be identified at this time. 

javadth1 said:

i ran memtest for 2 hour and memtest+ for 1 pass and windows memory diag

none of them shows any error

In that case you definitely need to run memtest86+ again for at least an overnight period to get to a full 8-10 passes.

philc43 said:

In that case you definitely need to run memtest86+ again for at least an overnight period to get to a full 8-10 passes.

i connect a bootable memtest flash and then suddenly my pc again caused MEMORY_MANAGEMENT and then restarted and its boot with memtest86+

this is the results

Code:

http://uupload.ir/files/mza9_photo_2017-05-14_16-37-12.jpg
http://uupload.ir/files/h92_photo_2017-05-14_16-37-18.jpg
http://uupload.ir/files/romn_photo_2017-05-14_16-37-20.jpg

Try the test with this version:

Diagnostic Test

 RAM TEST

Run MemTest86+ to analyse your RAM. 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.

Looks like your RAM is faulty - try removing one of the sticks and seeing if it makes a difference, then swap and test again.