Random BSOD during startup, mostly points to ntoskrnl.exe+748c0

anchan · 30 Jun 2015

Hello!

I have problems with random BSODs during Windows startup - they appear after the welcome screen, when the desktop is loading. They have been present for over a year, so I have decided to format my laptop and install everything again. Unfortunately, after this operation the bluescreens started to appear more often, even during the boot process, which leads to the windows repair tool starting if I do not select to continue booting. The tool can not repair anything. Most of the crash dumps point to the ntoskrnl.exe+748c0.

I have already run memtest86 two times. First time did 70 passes on the 10th test and the second time did 5 passes on the deafult settings. Both test did not return any errors. CrystalDiskInfo shows my disk health as good condition. Two passes with sfc /scannow did not find anything wrong with my system files.

Attachment 364409

Thank you very much for your help!
Attachment 364410

Arc · 30 Jun 2015

Hi anchan.

Test your RAM modules for possible errors.

How to Test and Diagnose RAM Issues with Memtest86+

Run memtest86+ for at least 8 consecutive passes.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

Let us know the result. A camera snap of the memtest86+ screen before closing the program will be nice.
________________________________________________________

Code:

BugCheck 4E, {2, 1c2c51, 25f5ff, 1}

Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+8d )

Followup: MachineOwner
---------

Code:

BugCheck A, {fffff6800001e298, 0, 0, fffff80002edd8d2}

Probably caused by : memory_corruption ( nt!MiUpdateWsle+122 )

Followup: MachineOwner
---------

anchan · 30 Jun 2015

Hi! Thank you for your reply.

I have run the test for 12 hours and 8 passes, no errors have been found.
Attachment 364445

Arc · 30 Jun 2015

As the next step, enable Driver Verifier to monitor the drivers, because a failing driver may pass bad information to the memory which may cause memory corruption.

Driver Verifier - Enable and Disable

Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

Tip

If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.

anchan · 01 Jul 2015

I am running the Driver Verifier right now and I have severe graphic corruption on some websites and applications, for example on Steam.
Attachment 364474
I also had a bluescreen while restarting the system after enabling the DV. I am attaching the dump file, but I do not know if it will help in any way.

Arc · 01 Jul 2015

It still shows memory corruption.

Code:

BugCheck 4E, {99, 1b855c, 2, 15ef7b}

Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )

Followup: MachineOwner
---------

When a driver verifier enabled dump blames to memory corruption, then there must be something wrong there with the RAM. Can you take teh test once again, using the latest version 5 of the memtest86+?

anchan · 02 Jul 2015

I ran the test again for 11 passes, again with no errors.
Attachment 364552

I might have been not clear enough with the previous bluescreen - it has occurred after I have configured the Driver Verifier and had to reboot the system in order for it to start working.
I have also tried to reproduce the bluescreens by rebooting the system around 20 times, both on battery and plugged in, but to no avail.

Arc · 02 Jul 2015

You are using two different RAM sticks there. One Is Crucial and the other is Hynix. That is enough cause of such a failure.

Remove either one, and run the computer with the rest one. See how it goes.

RAM is always to be bought in a KIT, a set of two or more RAM sticks tested to work together. Never mix RAM.

anchan · 02 Jul 2015

Thank you for your help, I will do so. This is actually fault of the shop where I bought my laptop, since the model was sold with 4GB and the shop had an option with 8GB, which they have added themselves.