Windows 10: RANDOM STOPCODE - ntoskrnl.exe+16bfd0.

Discus and support RANDOM STOPCODE - ntoskrnl.exe+16bfd0. in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, getting random bluescreens with above error, I have just built the pc basically all new hardware - I have run memtest86 which was weird one failed... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by elodsne, Jul 31, 2017.

  1. elodsne Win User

    RANDOM STOPCODE - ntoskrnl.exe+16bfd0.


    Hi, getting random bluescreens with above error, I have just built the pc basically all new hardware - I have run memtest86 which was weird one failed and 3 passes. So does that mean the DDR4 RAM is faulty? I had unplugged all other hard drives and swapped over GPU. Did a clean install of windows and still the problem occurs.

    I have spoken to Microsoft and the said clear CMOS which I have done and if that fails speak to MSI regarding this error but no luck so far. I hoping someone with the knowledge more then me can advised would be grateful thanks in advanced.

    P.S. I don't have a bluescreen in safemode.

    .

    :)
     
    elodsne, Jul 31, 2017
    #1

  2. Lots of BSOD's

    PS: after my previous/last replie i had 3 more BSOD's:

    seems like there are a lot of random once...

    MEMORY_MANAGEMENT win32kbase.sys

    MEMORY_MANAGEMENT ntoskrnl.exe

    ntoskrnl.exe
     
    florian de graef, Jul 31, 2017
    #2
  3. RichardW_ Win User
    Surface 4 Pro BSOD

    I am having trouble with blue screens, I am attaching the contents a some mini dumps from blue screen view

    My symptoms are very random, and affects excel, outlook and the pdf reader, I'm starting to point to a ram situation.

    I have ran a system restore to an earlier date, and updated all the drivers

    --------------

    ==================================================

    Dump File : 071817-19453-01.dmp

    Crash Time : 7/18/2017 8:02:50 AM

    Bug Check String : BAD_POOL_CALLER

    Bug Check Code : 0x000000c2

    Parameter 1 : 00000000`00000007

    Parameter 2 : 00000000`00000000

    Parameter 3 : 00000000`00000000

    Parameter 4 : ffffc10d`65595f38

    Caused By Driver : fwpkclnt.sys

    Caused By Address : fwpkclnt.sys+1ca5

    File Description :

    Product Name :

    Company :

    File Version :

    Processor : x64

    Crash Address : ntoskrnl.exe+16bfd0

    Stack Address 1 :

    Stack Address 2 :

    Stack Address 3 :

    Computer Name :

    Full Path : C:\WINDOWS\Minidump\071817-19453-01.dmp

    Processors Count : 4

    Major Version : 15

    Minor Version : 15063

    Dump File Size : 196,684

    Dump File Time : 7/18/2017 8:04:07 AM

    ==================================================

    ==================================================

    Dump File : 071417-9734-01.dmp

    Crash Time : 7/14/2017 9:11:02 PM

    Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL

    Bug Check Code : 0x000000d1

    Parameter 1 : 00000000`0000000a

    Parameter 2 : 00000000`00000002

    Parameter 3 : 00000000`00000000

    Parameter 4 : fffff80b`0bcccd58

    Caused By Driver : tcpip.sys

    Caused By Address : tcpip.sys+cd58

    File Description :

    Product Name :

    Company :

    File Version :

    Processor : x64

    Crash Address : ntoskrnl.exe+16bfd0

    Stack Address 1 :

    Stack Address 2 :

    Stack Address 3 :

    Computer Name :

    Full Path : C:\WINDOWS\Minidump\071417-9734-01.dmp

    Processors Count : 4

    Major Version : 15

    Minor Version : 15063

    Dump File Size : 570,844

    Dump File Time : 7/14/2017 9:12:45 PM

    ==================================================

    ==================================================

    Dump File : 070417-11859-01.dmp

    Crash Time : 7/4/2017 8:08:06 AM

    Bug Check String : DRIVER_IRQL_NOT_LESS_OR_EQUAL

    Bug Check Code : 0x000000d1

    Parameter 1 : 00000000`00000008

    Parameter 2 : 00000000`00000002

    Parameter 3 : 00000000`00000000

    Parameter 4 : fffff807`3fa54f6c

    Caused By Driver : hal.dll

    Caused By Address : hal.dll+1c9f4

    File Description :

    Product Name :

    Company :

    File Version :

    Processor : x64

    Crash Address : ntoskrnl.exe+16bfd0

    Stack Address 1 :

    Stack Address 2 :

    Stack Address 3 :

    Computer Name :

    Full Path : C:\WINDOWS\Minidump\070417-11859-01.dmp

    Processors Count : 4

    Major Version : 15

    Minor Version : 15063

    Dump File Size : 566,636

    Dump File Time : 7/4/2017 8:09:41 AM

    ==================================================

    ==================================================

    Dump File : 062817-8781-01.dmp

    Crash Time : 6/28/2017 8:47:06 AM

    Bug Check String : BAD_POOL_CALLER

    Bug Check Code : 0x000000c2

    Parameter 1 : 00000000`00000007

    Parameter 2 : 00000000`00000000

    Parameter 3 : 00000000`00000000

    Parameter 4 : ffff978f`c2f82ab8

    Caused By Driver : fwpkclnt.sys

    Caused By Address : fwpkclnt.sys+1ca5

    File Description :

    Product Name :

    Company :

    File Version :

    Processor : x64

    Crash Address : ntoskrnl.exe+16bfd0

    Stack Address 1 :

    Stack Address 2 :

    Stack Address 3 :

    Computer Name :

    Full Path : C:\WINDOWS\Minidump\062817-8781-01.dmp

    Processors Count : 4

    Major Version : 15

    Minor Version : 15063

    Dump File Size : 571,060

    Dump File Time : 6/28/2017 8:51:29 AM

    ==================================================

    ***Post moved by the moderator to the appropriate forum category.***
     
    RichardW_, Jul 31, 2017
    #3
  4. elodsne Win User

    RANDOM STOPCODE - ntoskrnl.exe+16bfd0.

    I done a GPU Stress test no problems however prime95 shows up this error

    "Prime 95 ERROR:rounding was 0.5 less than 0.4 and hardware failure "

    Any ideas

    Many Thanks
     
    elodsne, Jul 31, 2017
    #4
  5. Hi,
    theres only one bsod dump which shows memory_corruption at one point:

    Code: 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED (1.08.2017 13:04:02) [Windows 10] CAUSED BY: memory_corruption NTFS.sys [6.07.1994] * NT File System Driver (Windows System File) PROCESS: svchost.exe Usual causes: Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS[/quote]
    After reading your memtest results, the tests also failed:

    Code: Report Date 2017-07-31 22:45:51 Generated by MemTest86 V7.4 Free (64-bit) Result FAIL [/quote] Test # Tests Passed Errors Test 0 [Address test, walking ones, 1 CPU] 4/4 (100%) 0 Test 1 [Address test, own address, 1 CPU] 4/4 (100%) 0 Test 2 [Address test, own address] 4/4 (100%) 0 Test 3 [Moving inversions, ones & zeroes] 4/4 (100%) 0 Test 4 [Moving inversions, 8-bit pattern] 4/4 (100%) 0 Test 5 [Moving inversions, random pattern] 4/4 (100%) 0 Test 6 [Block move, 64-byte blocks] 3/4 (75%) 2 Test 7 [Moving inversions, 32-bit pattern] 4/4 (100%) 0 Test 8 [Random number sequence] 3/4 (75%) 1 Test 9 [Modulo 20, ones & zeros] 4/4 (100%) 0 Test 10 [Bit fade test, 2 patterns, 1 CPU] 4/4 (100%) 0 Test 13 [Hammer test] 4/4 (100%) 0 Last 10 Errors [Data Error] Test: 8, CPU: 8, Address: 11CC41DFC, Expected: 23BC2E84, Actual: 23B82E84 [Data Error] Test: 6, CPU: 8, Address: 11F9225D8, Expected: 00000000, Actual: 00040000 [Data Error] Test: 6, CPU: 8, Address: 11D9225F8, Expected: 00000000, Actual: 00040000
     
    BSODHunter, Jul 31, 2017
    #5
  6. To verify I recommend running Memtest V5.01 too:




    RANDOM STOPCODE - ntoskrnl.exe+16bfd0. [​IMG]
    Diagnostic Test
    RANDOM STOPCODE - ntoskrnl.exe+16bfd0. [​IMG]
    RAM TEST

    RANDOM STOPCODE - ntoskrnl.exe+16bfd0. [​IMG]
    Run MemTest86+ - Test RAM - Windows 10 Forums


    RANDOM STOPCODE - ntoskrnl.exe+16bfd0. [​IMG]



    RANDOM STOPCODE - ntoskrnl.exe+16bfd0. [​IMG]
    Note MemTest86+ V5.01 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.

    More Info here: https://answers.microsoft.com/en-us/...f-ecc7b7ff6461


    Make a photo of the result and post it.
     
    BSODHunter, Jul 31, 2017
    #6
  7. elodsne Win User
    Test has been running 5 mins found 3 errors .. Does this mean ram is at fault will post details after complete.
     
    elodsne, Jul 31, 2017
    #7
  8. RANDOM STOPCODE - ntoskrnl.exe+16bfd0.

    Yes the RAM is gone...
     
    BSODHunter, Jul 31, 2017
    #8
  9. elodsne Win User
    Make that 38 errors and counting, Corsair RAM DDR4 out the window just ordered myself a new lot should be here tomorrow.
     
    elodsne, Jul 31, 2017
    #9
  10. zbook New Member
    There were operating system corruption problems reported in the event log.
    When you have properly functioning ram see if you can fix the operating system problem by:
    1) opening administrative command prompt and type or copy and paste:
    2) sfc /scannow
    3) dism /online /cleanup-image /checkhealth
    4) dism /online /cleanup-image /scanhealth
    5) dism /online /cleanup-image /restorehealth
    6) in case the above steps are unable to complete plan an in place upgrade repair using a windows 10 iso:
    Download Windows 10
    7) Repair Install Windows 10 with an In-place Upgrade Windows 10 Installation Upgrade Tutorials

    Code: Event[312]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2017-07-31T19:44:33.551 Event ID: 1121 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-NHBIA96 Description: The following file necessary for Windows start-up was corrupt: c:\windows\system32\drivers\tcpip.sys[/quote] Code: Event[386]: Log Name: System Source: Microsoft-Windows-StartupRepair Date: 2017-07-31T19:52:09.201 Event ID: 1121 Task: N/A Level: Information Opcode: Info Keyword: N/A User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-NHBIA96 Description: The following file necessary for Windows start-up was corrupt: c:\windows\system32\drivers\spaceport.sys[/quote] Code: Start-up Repair failed.[/quote] Code: Event[599]: Log Name: System Source: Microsoft-Windows-WindowsUpdateClient Date: 2017-08-01T12:16:05.622 Event ID: 20 Task: Windows Update Agent Level: Error Opcode: Installation Keyword: Installation,Failure User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: DESKTOP-NHBIA96 Description: Installation Failure: Windows failed to install the following update with error 0x80070103: Advanced Micro Devices, Inc driver update for AMD SMBus.[/quote] Code: Event[49]: Log Name: System Source: Service Control Manager Date: 2017-07-31T19:38:45.771 Event ID: 7023 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: WIN-7IUN9R4SKTO Description: The iphlpsvc service terminated with the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.[/quote]
     
    zbook, Aug 1, 2017
    #10
  11. file system and os corruption could caused by defective memory so the first step should be replacing the RAM
     
    BSODHunter, Aug 1, 2017
    #11
  12. elodsne Win User
    Ended up running the memetest over night had 381 errors so RAM is dud.. I got a replacement delivered this morning did a test found no errors then did a clean install of windows 10 pro, touch wood all seems ok. Now to RMA this RAM. Great help from BSODHUNTER and zbook for the advice given. I will post back in couple of days with an update. *Wink
     
    elodsne, Aug 1, 2017
    #12
  13. elodsne Win User

    RANDOM STOPCODE - ntoskrnl.exe+16bfd0.

    Shes 's back *Sad KERNAL_SERCURITY_CHECK_FAILURE been running fine until now no idea why have had new ram. Any advice would be kindly appreciated.

    Thank you. *Sad
     
    elodsne, Aug 4, 2017
    #13
  14. zbook New Member
    There was no definitive misbehaving driver in the mini dump.
    When you did the clean install did you delete partitions, format the drive, make it an unallocated drive and then reinstall windows 10 using a bootable windows 10 iso?
    The event log reported a bad block on the drive.



    1) Check the RAM Memtest86+ making 8 or more passes.
    Make sure that at least 8 passes are made as anything less has too high an incidence of false negatives.
    A false negative is getting a pass when in reality the RAM is faulty.
    The more passes the better.
    When testing is complete use a camera or smart phone camera to take a picture and post the image into the thread.

    2) When the memory testing has completed run HD Tune on your drive.
    check the health,scan for errors, no quick scan but full scanrun a benchmark.It may take some time, but please take the time you need to perform it properly.When above is done please make screenshots of the followingthe health,the error scan,the benchmark incl. followingtransfer rate,access time,burst rate,cpu usage.Take Screenshot in Windows 10 Windows 10 General Tips Tutorials

    3) Run Sea tools for windows on your drive using SMART, short and long generic tests:

    How to use SeaTools for Windows
    http://www.seagate.com/support/downl...ls-win-master/
    How to use SeaTools for Windows
    http://www.seagate.com/support/downloads/seatools/

    Use the Microsoft snipping tool to make images of the test results and post into the thread.

    4) open administrative command prompt and type or copy and paste:
    5) sfc /scannow
    6) dism /online /cleanup-image /restorehealth

    When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

    7) To ensure that there are no improper bios settings please reset the bios.

    How to Clear Your Computers CMOS to Reset BIOS Settings:
    How to Clear Your Computers CMOS to Reset BIOS Settings

    3 Ways to Reset Your BIOS - wikiHow:
    3 Ways to Reset Your BIOS - wikiHow

    8) open administrative command prompt and type or copy and paste:
    chkdsk /x /f /r (this may take many hours to run so plan to run it overnight)

    It will display something similar to this:
    Microsoft Windows [Version 10.0.15063]
    (c) 2017 Microsoft Corporation. All rights reserved.


    C:\Windows\system32>chkdsk /x /f /r
    The type of the file system is NTFS.
    Cannot lock current drive.


    Chkdsk cannot run because the volume is in use by another
    process. Would you like to schedule this volume to be
    checked the next time the system restarts? (Y/N)

    Type: Y

    And reboot to run chkdsk /x /f /r



    Event ID 157 Ntdebugging Blog

    Code: BugCheck 139, {3, ffff828201be0730, ffff828201be0688, 0}*** WARNING: Unable to verify timestamp for win32kfull.sys*** ERROR: Module load completed but symbols could not be loaded for win32kfull.sys*** WARNING: Unable to verify timestamp for win32k.sys*** ERROR: Module load completed but symbols could not be loaded for win32k.sysProbably caused by : memory_corruption[/quote] Code: Disk 4 has been surprise removed[/quote] Code: Disk 5 has been surprise removed.[/quote] Code: The device, \Device\Harddisk4\DR6, has a bad block.[/quote]
     
    zbook, Aug 4, 2017
    #14
  15. elodsne Win User
    Have been runningmemtest for a several of hours now no errors, also have changed my hard drive as HD tune pro found problem with one of my drives. Hoping this cures the dreaded blue screen. Thanks again.
     
    elodsne, Aug 4, 2017
    #15
Thema:

RANDOM STOPCODE - ntoskrnl.exe+16bfd0.

Loading...
  1. RANDOM STOPCODE - ntoskrnl.exe+16bfd0. - Similar Threads - RANDOM STOPCODE ntoskrnl

  2. ntoskrnl Random Blue Screens

    in Windows 10 Gaming
    ntoskrnl Random Blue Screens: Minidumps from crashes provided here: https://1drv.ms/u/s!AgaXUUEKKwTvigGTCO59apS-Bfz9?e=VE1yOISince building my new system and installing Windows 11, my system experiences odd crashes during normal use. I've collected the dump files in the link above.OS: Windows 11...
  3. ntoskrnl Random Blue Screens

    in Windows 10 Software and Apps
    ntoskrnl Random Blue Screens: Minidumps from crashes provided here: https://1drv.ms/u/s!AgaXUUEKKwTvigGTCO59apS-Bfz9?e=VE1yOISince building my new system and installing Windows 11, my system experiences odd crashes during normal use. I've collected the dump files in the link above.OS: Windows 11...
  4. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: KUKutter_UKFirstly, I would like to say that I am posting this again because after having an instant reply from an 'Andrew', and posting my dmp files as requested on July 24th I haven't heard anything back since! I have responded a couple of times but nothing is happening to...
  5. BSOD Minidump shows page_faul ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD Minidump shows page_faul ntoskrnl..exe: Hi there, My new machine around 8 months old now runs perfectly most of the time. Uptime 3 - 6 weeks at a time. NO issues at all - I am a heavy PC user: Gaming, Audio Work and some 3D modelling, so my machine goes through its paces.Every now and then on boot, I get the error...
  6. Random BSOD ntoskrnl, ntkrnlmp executables

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD ntoskrnl, ntkrnlmp executables: I have a Lenovo laptop with the following specs: Intel Core i7-8550U 4C / 8T, 1.8 / 4.0GHz, 8MB Integrated Intel UHD Graphics 620 Intel SoC Platform 16GB Soldered DDR4-2400 512GB SSD M.2 2280 PCIe NVMe 13.9" UHD 3840x2160 IPS 300nits Glossy I started getting random...
  7. BSOD ntoskrnl..exe

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe: My computer has crashed a few times often when i play games. I bought more ram because i thought that it was the issue but it didn't help. It did work a few days but then the crashes came back. After that i fixed the BSOD´s by lowering the graphics and the resolution on the...
  8. BSOD ntoskrnl..exe+1b35e0

    in Windows 10 BSOD Crashes and Debugging
    BSOD ntoskrnl..exe+1b35e0: Help. Getting 4-5 of these a day. Running latest Windows 10 Pro, Xibo signboard, Docker with Xibo server. Always the same 'Caused By Address'. Put in new memory, ran memory test, no errors, all drivers up to date. Change disk type to AHCA, made sure windows driver was...
  9. Random BSODs (ntoskrnl,memory_management)

    in Windows 10 BSOD Crashes and Debugging
    Random BSODs (ntoskrnl,memory_management): Hello, first timer here. Long story short, after i updated to windows 10 from 8.1 i started experiencing some randomly BSODs. So i downloaded the ISO and made a clean install.Immidiatelly after my newly formated pc i installed Avast,mozilla and Asrock's Suite to check for...
  10. Random BSOD CRITICAL_STRUCTURE_CORRUPTION or NTOSKRNL

    in Windows 10 BSOD Crashes and Debugging
    Random BSOD CRITICAL_STRUCTURE_CORRUPTION or NTOSKRNL: Hi there! And thank you in advance for your help! AORUS-X7-DT-V6-30_10_2017__01924,84.zip Some time ago I started getting idle BSODs after reverting to an older System Image everything was fine until the creators update kicked in. Now I am getting random BSODs (not only...
Tags: