Windows 7 BSOD. Started recently.

Yojimbo · Mar 30, 2015

Bluescreen would just occur out of no where. Not exactly sure what is going on. Can anyone please take a look at my crash dump log? I'm not too sure how to decipher the error. For your information, I did not install or remove any driver recently.

kemical · Mar 30, 2015

It's entirely possible. Again one of the causes for Bugcheck 50 is hardware fault. You could try running memtest86 just to be sure (although if a RAM stick is creating a bsod anyway I'd say you've got it).

kemical · Mar 30, 2015

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8805d5d938b, 0, fffff88001d24b84, 5}


Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+17986 )

Followup: MachineOwner

Hi,
some of the principle causes of the above Bugcheck are:

Bug check 0x50 usually occurs after the installation of faulty hardware or in the event of failure of installed hardware (usually related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

Another common cause is the installation of a faulty system service.

Antivirus software can also trigger this error, as can a corrupted NTFS volume.

ref:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff559023(v=vs.85).aspx

The dump file also shows that the process at the time of BSOD was avp.exe which relates to Kaspersky Anti Virus software. So you may either have some corruption on the hard disk or the Anti Virus app is causing the bsod.

To check for a corrupted volume you need to run a chkdsk. Use the guide i posted below but please make sure that, whichever way you do it, tick the boxes to find and repair broken sectors:
Link Removed

kl1.sys Tue Jun 19 14:27:15 2012: Kaspersky Unified Driver. Please try and update Kaspersky to a later version:
http://usa.kaspersky.com/downloads

You also have driver updates available for your Lenovo:
Link Removed

Post any new dump files.

Yojimbo · Mar 30, 2015

I have a Lenovo W540 and it has 4 dimm slots. 2 top layer and 2 bottom layer. Top Layer(slot 1, slot2) Bottom layer (slot 3, slot4).
What is strange is that when I place any 8gb stick (kingston KTL - TP3CL) on slot 2, the screen flickers. However, one of the 8gb stick will cause crashes with either slot 1 or slot 2. While the other one would work fine on slot 1. If I placed the stock 4gb ram that came with the laptop on slot 2, no flickering or crashes happens. When I placed both the 8gb stick on the bottom layer (slot 3, slot 4) it will work perfectly fine with no crashes and no flickers. I did a lenovo diagnostic test and it passed on everything. When I did the diagnostic test with the "supposely bad" ram on either one of the top layer, it failed on several tests. (One of the test was called moving inversion 8 bit test). So would you say it is a combination of a bad ram and the top dimm slots being busted?

kemical · Mar 30, 2015

It's entirely possible. Again one of the causes for Bugcheck 50 is hardware fault. You could try running memtest86 just to be sure (although if a RAM stick is creating a bsod anyway I'd say you've got it).

Windows 7 BSOD. Started recently.

Yojimbo

New Member

Attachments

kemical

kemical

Essential Member

Yojimbo

New Member

kemical

Essential Member

Similar threads