Page 1 of 2 12 LastLast
  1.    11 May 2017 #1
    Join Date : May 2017
    Posts : 12
    windows 10 ver 1703 ( os 15063.296 )

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


    hi

    since i have upgraded my rams to new one from 2X4 to 2X8 = 16gb ddr 3 ( asus n56jrh )

    i am getting many errors of BSOD

    1 _ i have upgraded my win from 8.1 to 10 : but not resolved

    2 _ i have deleted old windows and clean install windows 10 - enterprise : errors decreased , but not solved

    3 _ i used memtest86 and memtest86+ and windows memory diag and didnt get any error

    3 _ uesd windows scannow and checkdisk to repair : but erros not solved

    4 _ now i have disabled windows driver verifier but again didnt help to resolve it

    5 _ used Dism /Online /Cleanup-Image /RestoreHealth and didnt dolved problem


    i have update all drivers by DriverMax and DriverPack-17-Online_369305223.1493746835

    i was suspicious to my intel 4600 graphic so i have uninstalled it , first day didnt get BSOD but now getting errors


    my MEMORY.DMP is large to upload to here and zipped to 100 mb but still is large

    but it is my mini dumps


    Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.



    and this one is ms info

    Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.


    On Thu 5/11/2017 6:32:36 AM your computer crashed

    crash dump file: C:\Windows\Minidump\051117-22609-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
    Bugcheck code: 0x1A (0x41792, 0xFFFFF3816ACAA158, 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. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 5/11/2017 6:32:36 AM your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x1A (0x41792, 0xFFFFF3816ACAA158, 0x100000000000000, 0x0)
    Error: MEMORY_MANAGEMENT
    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. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



    On Thu 5/11/2017 4:40:53 AM your computer crashed
    crash dump file: C:\Windows\Minidump\051117-23265-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x16C310)
    Bugcheck code: 0x1A (0x41792, 0xFFFFD7010C4B4158, 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. This problem might also be caused because of overheating (thermal issue).
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
    Last edited by javadth1; 13 May 2017 at 11:08.
      My ComputerSystem Spec
  2.    13 May 2017 #2
    Join Date : Nov 2015
    Posts : 2,860
    64bit Win 10 Pro ver 1709 Build 16299.64

    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.
      My ComputersSystem Spec
  3.    13 May 2017 #3
    Join Date : May 2017
    Posts : 12
    windows 10 ver 1703 ( os 15063.296 )
    Thread Starter

    Quote Originally Posted by philc43 View Post
    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
      My ComputerSystem Spec
  4.    14 May 2017 #4
    Join Date : Nov 2015
    Posts : 2,860
    64bit Win 10 Pro ver 1709 Build 16299.64

    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.
      My ComputersSystem Spec
  5.    14 May 2017 #5
    Join Date : May 2017
    Posts : 12
    windows 10 ver 1703 ( os 15063.296 )
    Thread Starter

    Quote Originally Posted by philc43 View Post
    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. 
    
    
      My ComputerSystem Spec
  6.    14 May 2017 #6
    Join Date : Nov 2015
    Posts : 2,860
    64bit Win 10 Pro ver 1709 Build 16299.64

    Quote Originally Posted by javadth1 View Post
    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.
      My ComputersSystem Spec
  7.    14 May 2017 #7
    Join Date : May 2017
    Posts : 12
    windows 10 ver 1703 ( os 15063.296 )
    Thread Starter

    Quote Originally Posted by philc43 View Post
    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
      My ComputerSystem Spec
  8.    14 May 2017 #8
    Join Date : Nov 2015
    Posts : 2,860
    64bit Win 10 Pro ver 1709 Build 16299.64

    Try the test with this version:



    skrnl.exe (nt+0x16C310) - ntkrnlmp.exe (nt!KeBugCheckEx+0x0) Diagnostic Test skrnl.exe (nt+0x16C310) - ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
     RAM TEST

    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   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.
      My ComputersSystem Spec
  9.    14 May 2017 #9
    Join Date : May 2017
    Posts : 12
    windows 10 ver 1703 ( os 15063.296 )
    Thread Starter

    final report again with memtest
    by pic
    Code:
    http://up.upinja.com/ykr2y.jpg
    by html

    Code:
    https://1drv.ms/u/s!AuV35THT-jT2hmLrWutA5pq3r4wb
    additional reports

    Code:
    http://up.upinja.com/ua7pr.jpg
    http://up.upinja.com/6zd5e.jpg
    http://up.upinja.com/w49uj.jpg
    http://up.upinja.com/2ftmv.jpg
    http://up.upinja.com/sbhbz.jpg
    http://up.upinja.com/mh1nv.jpg
    http://up.upinja.com/hszxw.jpg
    http://up.upinja.com/6rid0.jpg
    http://up.upinja.com/5hbvr.jpg
    http://up.upinja.com/asb45.jpg

    Code:
    Last 10 Errors 
    [Data Error] Test: 7, CPU: 4, Address: 2E45301DC, Expected: FEFFFFFF, Actual: FFFFFFFF
    [Data Error] Test: 4, CPU: 0, Address: 2DE86415C, Expected: F7F7F7F7, Actual: F6F7F7F7
    [Data Error] Test: 7, CPU: 2, Address: 2E00EC1DC, Expected: FFFFFF7F, Actual: FEFFFF7F
    [Data Error] Test: 7, CPU: 2, Address: 2E028815C, Expected: FFFFFF7F, Actual: FEFFFF7F
    [Data Error] Test: 7, CPU: 2, Address: 2E02CC1DC, Expected: FFFFFF7F, Actual: FEFFFF7F
    [Data Error] Test: 7, CPU: 2, Address: 2E03101DC, Expected: FFFFFF7F, Actual: FEFFFF7F
    [Data Error] Test: 7, CPU: 2, Address: 2E035415C, Expected: FFFFFF7F, Actual: FEFFFF7F
    [Data Error] Test: 7, CPU: 2, Address: 2E039815C, Expected: FFFFFF7F, Actual: FEFFFF7F
    [Data Error] Test: 7, CPU: 2, Address: 2E04201DC, Expected: FFFFFF7F, Actual: FEFFFF7F
    [Data Error] Test: 7, CPU: 2, Address: 2E04A815C, Expected: FFFFFF7F, Actual: FEFFFF7F
    Last edited by javadth1; 14 May 2017 at 13:35.
      My ComputerSystem Spec
  10.    14 May 2017 #10
    Join Date : Nov 2015
    Posts : 2,860
    64bit Win 10 Pro ver 1709 Build 16299.64

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

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
ntkrnlmp.exe
63127 here is my batch of files... i have been fighting with BSOD's for about a month after building my computer this is the last one that i can't seem to fix. it keeps happening once a day or so and is really irritating me as i have put in hours...
BSOD Crashes and Debugging
Bsod ntkrnlmp.exe
Hi, hoping someone can help me narrow down the exact cause of this blue screen. I believe it is something related to the drivers. When plugging in a video camera drop box displayed a message, after clicking okay this blue screen appeared and the...
BSOD Crashes and Debugging
Kmode_exception_not_handled - ntkrnlmp.exe
ok so i have had this BSOD a few times now and have been trying to fix it ever since. i ran who crashed after ever blue screen and same problem comes up (the title) i have no idea what is causing this and have been reading online to find an answer...
BSOD Crashes and Debugging
BSOD because of ntkrnlmp.exe
Hi, my computer keeps on crashing when playing games and WhoCrashed says the problem is to do with ntkrnlmp.exe. I ran the verifier and the dmp and msinfo are below. dmp: Dropbox - 122215-31218-01.dmp msinfo: Dropbox - msinfo.nfo speccy:...
BSOD Crashes and Debugging
BSOD - ntkrnlmp.exe
Experiencing what appears to be random BSOD events. This has been going on for some time now. I've recently switched from Windows 7 to 10, but the problem followed. Bug check points to ntkrnlmp.exe. An internet search has left...
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 22:26.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums