Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


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

30 Jun 2015   #1
anchan

Windows 7 Home Premium x64
 
 
Random BSOD during startup, mostly points to ntoskrnl.exe+748c0

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


My System SpecsSystem Spec
.
30 Jun 2015   #2
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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
---------
My System SpecsSystem Spec
30 Jun 2015   #3
anchan

Windows 7 Home Premium x64
 
 

Hi! Thank you for your reply.

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

30 Jun 2015   #4
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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   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   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   Tip

Let us know the results, with the subsequent crash dumps, if any.
My System SpecsSystem Spec
01 Jul 2015   #5
anchan

Windows 7 Home Premium x64
 
 

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.
My System SpecsSystem Spec
01 Jul 2015   #6
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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+?
My System SpecsSystem Spec
02 Jul 2015   #7
anchan

Windows 7 Home Premium x64
 
 

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.
My System SpecsSystem Spec
02 Jul 2015   #8
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Insider Preview 64-bit
 
 

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.
My System SpecsSystem Spec
02 Jul 2015   #9
anchan

Windows 7 Home Premium x64
 
 

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.
My System SpecsSystem Spec
Reply

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




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD random most times ntoskrnl.exe+748c0 and ntoskrnl.exe+74ec0
BSOD random, probably under heavy load situations. I dont know how to do. DM log collector file attached many thanks
BSOD Help and Support
BSOD was weekly, now daily, ntoskrnl.exe+748c0
I have had a persistent problem with BSODs for several months with this laptop. Reloaded system from the factory Windows system files on drive Q about 3 months ago. Really didn't help. Problem is getting more frequent, was maybe once a week, now getting closer to daily. Been doing battery pull...
BSOD Help and Support
page_fault_in_nonpaged_are bsod error ntoskrnl.exe+748c0
can u delete this
BSOD Help and Support
BSoD caused by address "ntoskrnl.exe+748c0" (maybe related to Youtube?
I'm sorry to bother you, but I've been having a few crashes lately & I was wondering if you might be able to point me to the cause. (I apologize in advance if the below is too wordy or /way/ too much information, I'm just trying to give you a complete picture.) The issues started a few...
BSOD Help and Support
BSOD ntoskrnl.exe+748c0 - while running "Bluestacks"
Hello, I've tried for months on troubleshooting this BSOD, i've read other similar BSODs and used the same fixes if they pertain to my situation. I've also tried disabling virtual memory. Even after my upgrade on hard drive and RAM, the problem still occurs. I'm no BSOD expert and now i've...
BSOD Help and Support
Frequent BSOD, seems random, WinDbg points to ntoskrnl.exe
Frequent BSOD in VirtualBox guest Windows 7 Ultimate x64, seems random, WinDbg points to ntoskrnl.exe Attached please find SF_Diagnostic_Tool results. Thanks a lot for your help!
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 12:46.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App