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

Discus and support skrnl.exe (nt+0x16C310) - ntkrnlmp.exe (nt!KeBugCheckEx+0x0) in Windows 10 BSOD Crashes and Debugging to solve the problem; 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... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by javadth1, May 10, 2017.

  1. javadth1 Win User

    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.

    :)
     
    javadth1, May 10, 2017
    #1

  2. ntkrnlmp.exe (nt!KeBugCheckEx+0x0) and ntoskrnl.exe (nt+0x142480) Errors

    060717-6203-01.dmp
     
    JaceHolton, May 10, 2017
    #2
  3. ntkrnlmp.exe (nt!KeBugCheckEx+0x0) and ntoskrnl.exe (nt+0x142480) Errors

    I performed the sfc /scannow and the error message returned "Windows Resource Protection did not find any integrity violations"
     
    JaceHolton, May 10, 2017
    #3
  4. philc43 Win User

    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, May 12, 2017
    #4
  5. javadth1 Win User
    if you check this file it is included what ever you need



    Code: DESKTOP-EAP4OL8-Sat_05_13_2017_201027_99.zip mirror :

    Code: Dropbox - DESKTOP-EAP4OL8-Sat_05_13_2017_201027_99.zip other mirror :

    Code: https://1drv.ms/u/s!AuV35THT-jT2hmAD7Q5DzzJ5M3x3[/quote]
     
    javadth1, May 12, 2017
    #5
  6. philc43 Win User
    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, May 13, 2017
    #6
  7. javadth1 Win User
    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. [/quote]
     
    javadth1, May 13, 2017
    #7
  8. philc43 Win User

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

    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, May 13, 2017
    #8
  9. javadth1 Win User
    javadth1, May 13, 2017
    #9
  10. philc43 Win User
    Try the test with this version:




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

    skrnl.exe (nt+0x16C310) - ntkrnlmp.exe (nt!KeBugCheckEx+0x0) [​IMG]
    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums


    skrnl.exe (nt+0x16C310) - ntkrnlmp.exe (nt!KeBugCheckEx+0x0) [​IMG]
    Note
    skrnl.exe (nt+0x16C310) - ntkrnlmp.exe (nt!KeBugCheckEx+0x0) [​IMG]


    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.
     
    philc43, May 13, 2017
    #10
  11. javadth1 Win User
    final report again with memtest
    by pic
    Code: http://up.upinja.com/ykr2y.jpg[/quote] by html

    Code: https://1drv.ms/u/s!AuV35THT-jT2hmLrWutA5pq3r4wb[/quote] 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[/quote]
    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 [/quote]
     
    javadth1, May 13, 2017
    #11
  12. philc43 Win User
    Looks like your RAM is faulty - try removing one of the sticks and seeing if it makes a difference, then swap and test again.
     
    philc43, May 13, 2017
    #12
  13. javadth1 Win User

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

    few days ago i tried to change rams and move them but i after that laptop didnt run

    repair man told this chipset damaged and changed it with new one so i dont want to again Manipulate it
    Code: http://up.upinja.com/ak8j4.jpg[/quote]
    without manually changing rams how can know which ram is damaged ?
    -------

    new reports by memtest86+ 5.01

    Code: http://up.upinja.com/mrv6s.jpg http://up.upinja.com/n0dy5.jpg http://up.upinja.com/jqkgk.jpg[/quote]
     
    javadth1, May 13, 2017
    #13
  14. philc43 Win User
    I think manually removing one at a time is the only way to be sure. It is possible you may not have used an earth wrist strap and you could have caused a static discharge when handling the RAM previously.
     
    philc43, May 13, 2017
    #14
  15. javadth1 Win User
    my laptop battery is out of use
    and on that time charger was connected when i disconnect the one of rams
     
    javadth1, May 14, 2017
    #15
Thema:

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

Loading...
  1. skrnl.exe (nt+0x16C310) - ntkrnlmp.exe (nt!KeBugCheckEx+0x0) - Similar Threads - skrnl exe nt+0x16C310

  2. .exe

    in Windows 10 Network and Sharing
    .exe: So i was not able to run Amd.exe . To do so i went to regedit and under Hkey class root .exe i changed the value .exe to “%1” %* but the mistake i made was i did not gave a space after “%1”. So after i restarted my pc i am anot able to open any .exe files i tried...
  3. ntldr. ....exe?

    in Windows 10 Network and Sharing
    ntldr. ....exe?: Soooooooo, I've heard of a file called ntldr. If you delete it, nothing seems to happen while Windows is running, but if you try to reboot, it just says: ntldr is missing Press Ctrl-Alt-Del to restart Firstly, what is the file extension for ntldr, and secondly, what...
  4. .exe Files

    in Windows 10 Network and Sharing
    .exe Files: I can't seem to find where my .exe files are and when i went online to find them they were listed in tools but i don't have a tools access seemingly trying to figure it out for a game i play...
  5. exe file

    in Windows 10 Installation and Upgrade
    exe file: exe file is not working on windows 10 https://answers.microsoft.com/en-us/windows/forum/all/exe-file/7e708774-b56c-4846-8036-2e683879ecd7
  6. NT SERVICE\TrustedInstaller is missing

    in AntiVirus, Firewalls and System Security
    NT SERVICE\TrustedInstaller is missing: TrustedInstaller is missing when i try to give TrustedInstaller back the ownership of WindowsApps Folder in program files. What I did: 1. I gave myself the ownership of WindowsApps folder in program files through its advanced security settings. 2. Then after I had done...
  7. Exe error

    in Windows 10 BSOD Crashes and Debugging
    Exe error: what does this mean and how i can fix this? (the instruction at 0x00000000759059A0 referenced memory at 0x00000000759059A0. the required data was not placed into memory because of an I/O error status of 0xc000009c....
  8. BSOD ntkrnlmp.exe (nt!KeBugCheckEx+0x0)

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntkrnlmp.exe (nt!KeBugCheckEx+0x0): Please help me identify what is causing my computer to randomly restart. System Information (local) Computer name: MONSTER Windows version: Windows 10 , 10.0, build: 15063 Windows dir: C:\Windows Hardware: MS-7A58, MSI, Z270 XPOWER GAMING TITANIUM (MS-7A58) CPU:...
  9. Rundll32.exe Problem

    in Windows 10 Performance & Maintenance
    Rundll32.exe Problem: Hi Everybody as the title shows i want to completely block Windows Host Processes (Rundll32.exe) from being executed and i am very consistent to do so *sarc because its swallowing my cpu all the time *Mad and im sure that its not a virus it just a droll and useless windows...
  10. Qurious question regarding NT

    in Windows 10 Support
    Qurious question regarding NT: Hey there, a mate of mine asked me this question and truly speaking I do not know the answer, therefore I am putting it to you guys for help. What version of NT would Win 10 be, this statement being based on the past facts that Windows XP was based on NT version 4 etc. So...
Tags: