BSOD Crash ntoskrnl.exe+16C388

lincolnsixecho · Aug 26, 2015

Hello,

I'm getting the same BSOD every few minutes on the computer. This limits me to using the web browser and not doing anything that's hard on the computer. I reformatted, upgraded to windows 10. I have 8gb ram. I even swapped the ram into different slots. Drivers are up to date. I ordered new ram chips and they should come tomorrow (hoping that's the true fix). Any help on this would be appreciated!

082615-7765-01.dmp 8/26/2015 10:03:00 PM MEMORY_MANAGEMENT 0x0000001a 00000000`00061941 00000000`20710818 00000000`0000000d ffffd000`abb34c40 ntoskrnl.exe ntoskrnl.exe+14dd00 x64 ntoskrnl.exe+14dd00 C:\WINDOWS\Minidump\082615-7765-01.dmp 8 15 10240 293,872 8/26/2015 10:03:41 PM

ntoskrnl.exe ntoskrnl.exe+16c388 fffff803`d4e89000 fffff803`d56db000 0x00852000 0x55c9bcb6 8/11/2015 4:13:26 AM

http://

popatim · Aug 27, 2015

You didn't bother testing the ram before ordering new ones?
Luckily the 0x0000001a error is usually caused by ram though it could be a timing or voltage issue; improperly set int the bios.

johnbl · Aug 27, 2015

here is your error code:
0x61946
The MDL being created is flawed. This almost always means the driver calling MmProbeAndLockPages is at fault. Typically the driver is attempting to create a Write MDL when it is being asked to process a paging Read.

I would:
update the BIOS, or if already current, reset it to defaults. Boot and run memtest off its own image. If it work as expected (no errors)
boot into windows, change them memory dump type from minidump to kernel memory dump. https://www.sophos.com/en-us/support/knowledgebase/111474.aspx

run cmd.exe as an admin then run
verifier.exe /standard /all
reboot and hope windows finds a bad driver. If it does it will bugcheck your machine and name the driver in the memory dump.
put the memory dump on a server and post a link.
the kernel memory dump will be located at c:\windows\memory.dmp
you my also put up your mini memory dumps from c:\windows\minidump directory.
(sometimes it is very clear which driver caused the problem even from a minidump)

Search

BSOD Crash ntoskrnl.exe+16C388

lincolnsixecho

Reputable

popatim

Titan

johnbl

Polypheme

TRENDING THREADS

Latest posts

Moderators online

Share this page