Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


BSOD ntoskrnl.exe

  • Please log in to reply
1 reply to this topic

#1 DukeDui


  • Members
  • 4 posts
  • Gender:Male
  • Local time:12:42 PM

Posted 27 April 2016 - 04:06 AM


I need help with this.

The information is in the attached files.

Attached Files

BC AdBot (Login to Remove)


#2 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,091 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:10:42 PM

Posted 28 April 2016 - 02:41 PM

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

If it doesn't work for you, then please try this:  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

Can't tell much from the lone memory dump - but here's what I got:


ntoskrnl.exe (also seen as ntkrnlpa.exe, ntkrnlmp.exe, or ntkrpamp.exe) is the kernel (core) of the Windows operating system.  It is protected by security features and the Windows System File Checker.  As such, if this file was to blame, you'd be experiencing many more problems other than the occasional BSOD.

In most cases this file is blamed because another file (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own.  When this happens, ntoskrnl.exe typically finds unknown data (from the 3rd party driver) in it's memory space.  At this point the OS panics and throws a BSOD to prevent damage to the system.

More info here:  https://en.wikipedia.org/wiki/Ntoskrnl.exe


I wonder about the AsrVDrive.sys driver (belongs to the AsRock V Drive software) as it dates from 2012

A bit more info on it here:  http://www.carrona.org/drivers/driver.php?id=AsrVDrive.sys

Please uninstall it.  If you want to keep it, please install a fully compatible W10 version.


If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html



Debug session time: Wed Apr 27 05:00:36.057 2016 (UTC - 4:00)
Loading Dump File [C:\Users\john\SysnativeBSODApps\042716-15265-01.dmp]
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
System Uptime: 0 days 0:37:34.685
Probably caused by : memory_corruption ( nt!MiTryLocateWsle+266 )
BugCheck 3B, {c0000005, fffff800d74d71d6, ffffd000233dab80, 0}
Bugcheck code 0000003B
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800d74d71d6, Address of the instruction which caused the bugcheck
Arg3: ffffd000233dab80, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID:  0x3B_nt!MiTryLocateWsle
MaxSpeed:     3400
CurrentSpeed: 3408
BiosVersion = P1.20
BiosReleaseDate = 07/09/2015
SystemManufacturer = To Be Filled By O.E.M.
BaseBoardManufacturer = ASRock
SystemProductName = To Be Filled By O.E.M.
BaseBoardProduct = H170 Performance

AsrVDrive.sys               Mon Oct  1 04:21:03 2012 (5069526F)
BEDaisy.sys                 Mon Feb  8 14:24:17 2016 (56B8EB61)
NvStreamKms.sys             Fri Mar 18 17:26:05 2016 (56EC726D)
TeeDriverW8x64.sys          Thu Oct  8 14:13:00 2015 (5616B22C)
e1d65x64.sys                Tue May 19 03:44:13 2015 (555AE9CD)
iaStorA.sys                 Wed Jun  3 05:38:57 2015 (556ECB31)
intelppm.sys                Thu Oct 29 22:09:51 2015 (5632D16F)
nvhda64v.sys                Mon Sep 21 05:44:17 2015 (55FFD171)
nvlddmkm.sys                Mon Mar 21 21:44:53 2016 (56F0A395)
nvvad64v.sys                Mon Mar 14 02:27:42 2016 (56E659DE)
rzendpt.sys                 Tue Aug 11 07:13:46 2015 (55C9D8EA)
rzpmgrk.sys                 Thu Sep 17 14:42:44 2015 (55FB09A4)
rzpnk.sys                   Wed Sep 16 20:16:35 2015 (55FA0663)
rzudd.sys                   Tue Aug 11 07:13:50 2015 (55C9D8EE)



My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users