Windows 7 Blue screens at random

Manzoe

New Member
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.
 

Attachments

  • 022118-16411-01.dmp
    310.1 KB · Views: 497
  • 021118-17019-01.dmp
    312.3 KB · Views: 578
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.
 
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.
Thank you for your reply, I deleted the said files and running the sfc /scannow. I will send any future blue screen.
 
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.
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.
 
Here is the newest blue screen. Hopefully I can find the root to the problem and correct
 

Attachments

  • 042318-18704-01.dmp
    309.3 KB · Views: 484
Code:
*******************************************************************************
*                                                                             *
*                        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
Hi,
the above probable cause relates to your network driver:
athrx.sys Tue May 5 08:30:13 2015: Atheros network adapter driver
I checked your support page but there isn't a later driver. You could try simply removing the current version and installing a fresh copy.
Your support page is here:
Support For GT70 2OC | MSI Global

Please post any new dump files.
 
Thank you, Just can't understand why this keeps happening over different problems. Appreciate your assistance
 
It could be down to something else like a hardware failure.

Try running this battery of tests to see if we can find the culprit.

Run a chkdsk /r in an admin command prompt.
How to Fix Hard Drive Problems with Chkdsk in Windows 7, 8, and 10

Test your memory using memtest86

Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link above you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
Test the RAM overnight unless you see an error crop up straight away.

Check the processor over by running this tool:
Download Intel® Processor Diagnostic Tool
 
Any suggestions on how to stop these I'm really getting frustrated over the blue screens.
 

Attachments

  • 042618-19000-01.dmp
    309.3 KB · Views: 489
Here another that just happen guess it's getting worst.
 

Attachments

  • 042718-19531-01.dmp
    309.9 KB · Views: 524
Code:
*******************************************************************************
*                                                                             *
*                        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
Hi,
the above dump file can be caused by a number of things including hardware failure (usually RAM), corrupt drivers, corrupt NTFS volume and finally Anti Virus applications.
Looking through your system drivers I came across this:

SASDIFSV64.SYS Fri Jul 22 00:03:00 2011: SUPERAntiSpyware

I did ask you to remove it in a previous post, perhaps you forgot?

Can you also remove or update this:

ElRawDsk.sys Tue Oct 26 10:34:13 2010: RawDisk Driver by EldoS Corporation

If the bsod continues you need to run tests to try and determine what could be causing the issue.

Try running this battery of tests to see if we can find the culprit.

Run a chkdsk /r in an admin command prompt.
How to Fix Hard Drive Problems with Chkdsk in Windows 7, 8, and 10

Test your memory using memtest86

Windows does have a memory testing app but it can miss errors and the best app for the job is Memtest86.
If you open the link above you'll see you can run Memtest86 in two ways. You can either burn it to disk or install it onto a USB drive it's entirely up to you. You'll then need to enter the bios to change the boot order so you can boot from either the Disk or USB stick you have Memtest86 on.
Test the RAM overnight unless you see an error crop up straight away.

Check the processor over by running this tool:
Download Intel® Processor Diagnostic Tool
 
Seems to be happening more frequently. I deleted super antispyware program, ran the processor diagnostic tool, and ran sfc /scannow couldn't find any errors. I need to get a memory stick to download the Memtest86. Thought I would send these see if maybe you see something. Thank you for all your help. I will try to find someone that can fix computer if I can't figure this out.
 

Attachments

  • 050618-18720-01.dmp
    309.3 KB · Views: 506
  • 050618-19921-01.dmp
    310.5 KB · Views: 468
  • 050718-19141-01.dmp
    309.5 KB · Views: 515
Code:
*******************************************************************************
*                                                                             *
*                        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
Hi,
you could try using the windows memory diagnostic and this guide will show you how:
How to Test Your Computer’s RAM for Problems

Also can you go through your apps and basically remove anything which is either old or no longer used.
 
I am so disguisted with the computer seems to be something different all the time
 

Attachments

  • 050818-18267-01.dmp
    309.8 KB · Views: 482
  • 050818-30498-01.dmp
    311.5 KB · Views: 511
I've got to nip out but will check the dumps on return (2-3hrs)
 
Code:
*******************************************************************************
*                                                                             *
*                        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
Hi,
as i mentioned in the previous post, you need to go through your apps and drivers and remove anything no longer used or out of date.

It looks like that the trigger for the bsod is a command to register a dll: regsvr32 Unfortunately as to which app or driver causing this isn't mentioned.

Here are few likely suspects I noticed in your drivers:
TuneUpUtver64.sys Thu Sep 17 12:54:52 2009: The age alone warrants the removal but this app is linked to AVG and could be a possible cause of your issue.
AVG TuneUp | Clean & Speed Up Your PC | Free Download

XtuAcpiDriver.sys Tue Jun 28 10:05:03 2016: Intel extreme clocking app. If your using this to overclock please stop and uninstall said app.

VPN applications. It looks like you have a number of these apps installed? If so please remove anything not used or out of date.

Just keep going like that and remove anything thats out of date or no longer used.

Oh and don't forget about the RAM test mentioned previously.

Please post any new dump files
 
I deleted a lot of old programs as suggested by you, cleaned up what I thought could be deleted without causing any other problems. Thought it was going well been six days since last blue screen and I know I have to do that memory check still will get my son to do that in couple of weeks for me. What other suggestions may you have cause seems all you told me helped.
 

Attachments

  • 051418-19531-01.dmp
    309.1 KB · Views: 507
Back
Top