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.

Photo

multiple BSOD Caused by Driver: ntoskrnl.exe


  • Please log in to reply
2 replies to this topic

#1 Slimey

Slimey

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:01:02 PM

Posted 27 January 2018 - 09:32 AM

Hi,

 

I know my way around computers but I am not able to find a solution so I am in need of some help figuring out what is happening here...

I have had several BSOD related to the ntoskrnl.exe driver.

I have updated all my drivers, all the windows updates, did a disk check, did a memory check and all come up empty.

 

 

Two times when the BSOD appeared I was running a video game. I could run the game before without a problem and now I have BSODs...

 

Could any of you help me track down the issue without me needing to go back to the manufacturer?

 

Thank you

 

 

 

http://speccy.piriform.com/results/HqyMziRsNboWn54ip1RTgo8

Attached Files



BC AdBot (Login to Remove)

 


#2 george144

george144

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:07:02 AM

Posted 27 January 2018 - 09:43 AM

How do you know the BSODs are related to that particular driver?



#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:02 AM

Posted 27 January 2018 - 10:02 AM

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 ntoskrnl.exe was to blame, you'd be experiencing many more problems other than the occasional BSOD.

In most cases ntoskrnl.exe was blamed because a driver (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.

If the culprit (the offending 3rd party driver) hasn't exited yet, then a BSOD analyst may be able to find traces of it in the reports/dumps.  If the culprit has exited, then the chase is on and further tests/reports will be needed to help identify what actually caused it.

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


Your UEFI/BIOS (version V22.2) dates from 2014.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and the outdated UEFI/BIOS' may be the cause of some compatibility issues).

242 Windows Update hotfixes installed.  Most systems have more than this  Please visit Windows Update and get ALL available updates (it may take several trips to get them all).
Don't worry about the specific number, it's just important that you have checked and installed any updates that were available (and didn't experience any errors).

C drive only has about 3% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

You have the TP Link wireless configuration utility installed - but no wireless is shown in the systeminfo.txt report

Please uninstall the TP Link utility.

 

MSI Afterburner (along with EVGA Precision and Riva Tuner) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!
If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.

The lone memory dump blames video.
First, please try a clean install of your video drivers using these instructions:

 

Please uninstall your video drivers and all the nVidia/AMD/Intel VIDEO (not chipset) software from your system (Settings...Apps - or appwiz.cpl)
- If uninstalling the AMD video drivers, you may also want to run the AMD Clean Uninstall utility (free from here:  http://support.amd.com/en-us/kb-articles/Pages/AMD-Clean-Uninstall-Utility.aspx )
Then use this free tool to remove any traces of the drivers:  http://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Then reboot and check Windows Update (allow it to install video drivers):  https://support.microsoft.com/en-us/help/15054/windows-7-automatically-get-recommended-drivers-updates-hardware

Test to see if this helps and post back with the results.

Then, if that works and you need the nVidia drivers - feel free to download and install the latest, W10 compatible video drivers from http://www.nvidia.com/Download/index.aspx
Then, if that works and you need the AMD drivers - feel free to download and install the latest, W10 compatible video drivers from http://support.amd.com/en-us/download
Then, if that works and you need the Intel drivers - feel free to download and install the latest, W10 compatible video drivers from http://downloadcenter.intel.com (you can also usually download these drivers from the manufacturer's website)

 

If that doesn't work, then the next step would be to try another video card.

If you don't have another video card, you may want to purchase one from a shop that'll let you return it for your money back (if it's not needed).

 

Analysis:
The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:
**************************Sat Jan 27 09:15:23.965 2018 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\012718-45765-01.dmp]
Windows 8.1 Kernel Version 9600 MP (8 procs) Free x64
Built by: 9600.18895.amd64fre.winblue_ltsb.180101-1800
System Uptime:0 days 2:23:45.688
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :dxgkrnl.sys ( dxgkrnl!DpSynchronizeExecution+af )
BugCheck 133, {0, 501, 500, 0}
BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  ACOrigins.exe
FAILURE_BUCKET_ID: 0x133_DPC_dxgkrnl!DpSynchronizeExecution
  BIOS Version                  V22.2
  BIOS Release Date             12/16/2014
  Manufacturer                  MSI
  Product Name                  MS-7693
  Baseboard Product             970 GAMING (MS-7693)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


3rd Party Drivers:
The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Sat Jan 27 09:15:23.965 2018 (UTC - 5:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
lvrs64.sys                  Mon Oct 22 22:11:24 2012 (5085FCCC)
lvuvc64.sys                 Mon Oct 22 22:12:08 2012 (5085FCF8)
xusb22.sys                  Tue Mar 18 04:18:41 2014 (53280161)
amd_sata.sys                Thu Mar 19 02:43:08 2015 (550A6FFC)
amd_xata.sys                Thu Mar 19 02:43:10 2015 (550A6FFE)
HWiNFO64A.SYS               Tue Mar 31 05:51:32 2015 (551A6E24)
Phosgene.sys                Wed Sep  2 03:28:10 2015 (55E6A50A)
e2xw8x64.sys                Tue Jan 26 18:57:45 2016 (56A807F9)
RTCore64.sys                Fri Sep 30 08:03:17 2016 (57EE5485)
rzendpt.sys                 Wed Oct 26 04:12:17 2016 (58106561)
rzudd.sys                   Wed Oct 26 04:12:19 2016 (58106563)
RTKVHD64.sys                Wed Jun 14 01:58:31 2017 (5940D087)
rzpnk.sys                   Sun Jul 16 15:12:07 2017 (596BBA87)
rzpmgrk.sys                 Tue Jul 18 17:15:21 2017 (596E7A69)
avgbuniva.sys               Mon Dec  4 10:04:10 2017 (5A2563EA)
avgbdiska.sys               Mon Dec  4 10:04:12 2017 (5A2563EC)
avgbidsdrivera.sys          Mon Dec  4 10:04:12 2017 (5A2563EC)
avgbidsha.sys               Mon Dec  4 10:04:12 2017 (5A2563EC)
avgbloga.sys                Mon Dec  4 10:04:14 2017 (5A2563EE)
nvvad64v.sys                Thu Dec 14 00:40:29 2017 (5A320ECD)
nvhda64v.sys                Fri Dec 15 03:17:43 2017 (5A338527)
avgRvrt.sys                 Tue Dec 19 13:09:14 2017 (5A3955CA)
avgArPot.sys                Tue Dec 19 13:09:16 2017 (5A3955CC)
avgSnx.sys                  Tue Dec 19 13:09:41 2017 (5A3955E5)
avgRdr2.sys                 Tue Dec 19 13:09:50 2017 (5A3955EE)
avgVmm.sys                  Tue Dec 19 13:21:43 2017 (5A3958B7)
avgStm.sys                  Tue Dec 19 13:30:47 2017 (5A395AD7)
nvlddmkm.sys                Wed Jan  3 18:39:48 2018 (5A4D69C4)
nvvadarm.sys                Wed Jan  3 18:56:49 2018 (5A4D6DC1)
avgMonFlt.sys               Tue Jan  9 15:21:28 2018 (5A552448)
avgSP.sys                   Tue Jan  9 15:21:48 2018 (5A55245C)


http://www.carrona.org/drivers/driver.php?id=MBfilt64.sys
http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys
http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
http://www.carrona.org/drivers/driver.php?id=HWiNFO64A.SYS
Phosgene.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
e2xw8x64.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=RTCore64.sys
http://www.carrona.org/drivers/driver.php?id=rzendpt.sys
http://www.carrona.org/drivers/driver.php?id=rzudd.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=rzpnk.sys
http://www.carrona.org/drivers/driver.php?id=rzpmgrk.sys
avgbuniva.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgbdiska.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgbidsdrivera.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgbidsha.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgbloga.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
avgRvrt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgArPot.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgSnx.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgRdr2.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgVmm.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgStm.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvadarm.sys
avgMonFlt.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
avgSP.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
 
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.




2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users