Windows 10: Various BSOD Caused by ntoskrnl.exe

Hi,
I'm facing various BSOD. After I open minidump files via Bluescreenview, it's caused by Ntoskrnl.exe.

Here's the minidump files
Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Here's the screenshot of the Bluescreenview :





Please help, Thanks in advance *Smile

:)

 

Various BSOD Caused by ntoskrnl.exe

Wow slow down.

What's wrong with my PC and how to fix it?

 

Various BSOD Caused by ntoskrnl.exe

Hi,

The 5 minidumps were Bug_Check 1A, 139, 50, 0A (2).

BugCheck 139, {3, ffffd0002650f740, ffffd0002650f698, 0}

Probably caused by : ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )

BugCheck 1A, {41793, fffff6800009aee0, 19, 18}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+1ed59 )

BugCheck 50, {ffffa00032f6efc0, 0, fffff8028f2ba8ce, 2}

Probably caused by : memory_corruption

BugCheck A, {fffff6c0009940e0, 2, 0, fffff80139f9b350}

Probably caused by : memory_corruption

BugCheck 1A, {41792, fffff6bffeca6ee0, 400000000000, 0}

Probably caused by : memory_corruption ( ONE_BIT )

ntkrnlmp.exe is a Windows component which means something else drove it into Fault.

The last 1A Bug_Check is very telling.

1. Check the memory very thoroughly using the methods below.

2. Check with MSI Support, their on-line documentation and drivers, and ask in their forums

about any known issues. Update the BIOS, low level chipset drivers, and the major on-board

and separate device drivers (see driver update methods below).

BiosVersion = V1.6

BiosReleaseDate = 05/18/2010

SystemManufacturer = MSI

SystemProductName = MS-7640

BaseBoardManufacturer = MSI

BaseBoardProduct = 890FXA-GD70 (MS-7640)

BaseBoardVersion = 1.0

MSI Support

MSI Global

MSI - Downloads (BIOS and Drivers)

MSI Global

MSI - Forums

MSI Global English Forum - Index

MSI - Service

MSI USA

MSI - Live Update On-Line

MSI Global

MSI - Contacts - Set to North America - USA

MSI Global

3. As needed use ALL the other methods in the troubleshooters below.

4. If needed run Driver Verifier to see if it can indicate a CAUSE (see Driver Verifier methods

below).

======================+

Troubleshoot blue screen errors

http://windows.microsoft.com/en-us/windows-10/troubleshoot-blue-screen-errors

BCCode: 1a 0x0000001a

Remove ALL power and reseat all cards, memory, and cables (both ends when

possible) - actually remove and replace - do not just snug. Make sure the vents

are clear and that the fans are working. Even though the temp is OK do not

assume heat can't affect the video, sound or other system functions it those

get to hot. Try adding a small fan blowing into the vents as a test. (Those are

mostly for a PC not a laptop.)



Have you added any hardware lately? Have you updated any driver just before

these started? (Check Control Panel - Windows Updates to see if any drivers

were updated there about the time this started) Main likely culprits are Video

driver, other major drivers, memory, and antivirus/antispyware/security products

could be at fault as well as drive issues.

BCCode: 1a 0x0000001a <-- read this link

MEMORY_MANAGEMENT



Bug Check 0x1A: MEMORY_MANAGEMENT <-- read this link

Bug Check 0x1A MEMORY_MANAGEMENT
====================================================

This utility makes it easy to see which versions are loaded : Run DriverView - set


VIEW to Hide Microsoft drivers - update those without Dump in their names (

and BIOS and chipset).

DriverView - Free - utility displays the list of all device drivers currently loaded

on your system. For each driver in the list, additional useful information is

displayed: load address of the driver, description, version, product name,

company that created the driver, and more.

http://www.nirsoft.net/utils/driverview.html



For Drivers check System Maker as fallbacks and Device Maker's which are the

most current. Control Panel - Device Manager - Display Adapter - write down

the make and complete model of your video adapter - double click - Driver's

tab - write down the version info. Now click UPdate Driver (this may not do

anything as MS is far behind certifying drivers) - then Right Click - Uninstall -

REBOOT this will refresh the driver stack.

Repeat that for Network - Network Card (NIC), Wifi, Sound, Mouse and Keyboard

if 3rd party with their own software and drivers and any other major device drivers

you have.

Now go to System Maker's site (Dell, HP, Toshiba as examples) (as rollback) and

then Device Maker's site (Realtek, Intel, Nvidia, ATI as examples) and get their

latest versions. (Look for BIOS, Chipset, and software updates at System Maker's

site while there.)

Download - SAVE - go to where you put them - Right Click - RUN AD ADMIN -

REBOOT after each installation.

Always check in Device Manager - Drivers tab to be sure the version you are

installing actually shows up. This is because some drivers rollback before the

latest is installed (sound drivers particularly do this) so install a driver - reboot

- check to be sure it is installed and repeat as needed.

Repeat at Device Makers - BTW at Device Makers DO NOT RUN THEIR SCANNER -

heck manually by model.

Manually look at manufacturer's sites for drivers - and Device Maker's sites.

http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

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

Memory tests do not catch all errors such as mismatched memory (possible even

for sticks that appear to be identical) and when faster memory is placed in system

behind slower memory. So it is best to also swap sticks in and out to check for

those even if all memory tests fail to show a problem.

To test RAM check here - let it run 4+ hours or so. <-- best method

www.memtest.org

MemTestX86 - Test RAM With

https://www.windowsphoneinfo.com/threads/memtest86-test-ram.2010/

For the Windows Memory Diagnostic Tool.

Type in Cortana's search box -> Windows Memory Diagnostics

at top of list - click it. in Windows 8/8.1/10 the name is "Windows Memory

Diagnostic".



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

After doing ALL the updates you can, and if the issue continues, then run

DriverVerifier. (Remember to use the Windows 8/8.1 methods posted at the

top of the original reply above.)

Driver Verifier can help find some BSOD issues :

Using Driver Verifier to identify issues with Windows drivers for advanced users

http://support.microsoft.com/kb/244617

How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10

are essemtially the same).

http://www.winvistaclub.com/t79.html

Using Driver Verifier

http://msdn.microsoft.com/en-us/library/ff554113(v=VS.85).aspx

How to use Windows Driver Verifier Manager to Troubleshoot & Identify Driver

Issues



Driver Verifier

http://www.techsupportforum.com/2110308-post3.html

Using Driver Verifier

http://www.faultwire.com/solutions/using_driver_verifier.php

You can disable Driver Verifier

http://support.microsoft.com/kb/244617

WINKEY + X - RUN - type in -> verifier /reset hit enter to disable

Use BlueScreenView to see if there is a driver specified in the error message.

Also check with MyEventViewer at the time of the BlueScreen.

If DriverVerifier creates a minidump upload it and post the link here so we can analyze it.

Hope this helps.

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

Rob Brown -
Microsoft MVP <- profile - Windows Experience : Bicycle - Mark Twain said it right.

 

Attachment 61672

here's the log generated by DM Log Creator

 

Diagnostic Test

RAM TEST


Run MemTest86+ - Test RAM - Windows 10 Forums



Note



MemTest86+ needs to be run for at least 8 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.
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck A, {fffff6a00038b7f8, 2, 0, fffff8025e0efa62} Probably caused by : memory_corruption ( nt!MiAgeWorkingSet+302 ) Followup: MachineOwner[/quote]

 

Thanks for the reply!
But booting into memtest86+ stuck at "Loading mt86plus....ready"
what should I do now?

nvm, now memtest86+ is up and running, will post back after tests are done

 

Here's the test results from memtest86+

Ram A slot 1 -> 10 passes = no errors
Ram B slot 1 -> 10 passes = 55 errors
Ram B slot 2 -> 11 passses = 292 errors
Ram A slot 2 ->11 passes = no errors

So it's positive that ram B is bad, right?
Now I'm running on the latest combination (Ram A slot 2) without a problem in more than 10 hours.

Will wait a few more days before I mark this as solved, thanks!

 

RAM B is the bad one yes, remove/replace it.