*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa802b600000, 0, fffff8000327eb7b, 0}
Could not read faulting driver name
Probably caused by : luafv.sys ( luafv!SynchronousFsControl+1ca )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffa802b600000, 0, fffff8000327eb7b, 0}
Could not read faulting driver name
Probably caused by : luafv.sys ( luafv!SynchronousFsControl+1ca )
Followup: MachineOwner
Thank you for your reply, I deleted the said files and running the sfc /scannow. I will send any future blue screen.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 50, {fffffa802b600000, 0, fffff8000327eb7b, 0} Could not read faulting driver name Probably caused by : luafv.sys ( luafv!SynchronousFsControl+1ca ) Followup: MachineOwner
Hi,
bugcheck 50 can be caused by a number of issues including hardware (RAM), faulty system service and finally AV suites.
Looking over your system I see that Super antispyware is dated from 2011
SASDIFSV64.SYS Fri Jul 22 00:03:00 2011
Please re-install later version: SUPERAntiSpyware | Remove Malware | Remove Spyware - AntiMalware, AntiSpyware, AntiAdware!
Please look in your Start menu for command prompt, right click on it, choose properties followed by run as admin, Type:
sfc /scannow
press enter and await results
Please post any new dump files.
This problem happened to my wife's laptop. I removed the ram and cleaned the copper connections with a red ruby erassor. Presto! No more blue screens. I hope this helps.Out of nowhere I get blue screens I had it in shop to be checked they couldn't find problem could anyone look and see if they have any idea whats causing them. This is just a couple of them seems to happen at no specific time or task.
You are still blue screening?will try and let you know
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80003333f73, fffff880037b5eb8, fffff880037b5720}
*** WARNING: Unable to verify timestamp for athrx.sys
*** ERROR: Module load completed but symbols could not be loaded for athrx.sys
Probably caused by : athrx.sys ( athrx+c2fe )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a03da72e08, 0, fffff88001445ff9, 2}
Could not read faulting driver name
Probably caused by : Ntfs.sys ( Ntfs!NtfsZeroEndOfSectorNonCached+159 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {7010000, 1, 207c6a, 8}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+3c575 )
Followup: MachineOwner
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff8000325ad3c, fffff8801f40a5d0, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiInsertTimerTable+1cc )
Followup: MachineOwner