Random shutdowns

[powersafevh57]

I get daily random shutdowns.
"windows has recovered from an unexpected shutdown"
I have beeen updating everything I can find but am in the dark.
Suggestions please. Files attached.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057

Additional information about the problem:
BCCode: 50
BCP1: FFFFFA803BF1B793
BCP2: 0000000000000000
BCP3: FFFFF88001071071
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Files that help describe the problem:
C:\Windows\Minidump\102912-23446-01.dmp
C:\Users\living room\AppData\Local\Temp\WER-42635-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[koolkat77]

Welcome

Your .dmp's come with various bug checks. Their usual causes are....

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA  
Usual causes:  Defective hardware (particularly memory - but not just RAM), 
Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {fffffa803bf1b793, 0, fffff88001071071, 2}
[I]Could not read faulting driver name[/I]
Probably caused by : memory_corruption
============================================================================
STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA  
Usual causes:  Defective hardware (particularly memory - but not just RAM), 
Faulty system service, Antivirus,  Device driver, NTFS corruption, BIOS
BugCheck 50, {ffffffff90909090, 1, fffff80002b40076, 5}
[I]Could not read faulting driver name[/I]
Probably caused by : memory_corruption
============================================================================
STOP 0x00000024: NTFS_FILE_SYSTEM  
Usual causes:  Disk corruption, insufficient physical memory, Device driver, 
Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
BugCheck 24, {1904fb, fffff8800624eea8, fffff8800624e700, fffff80002cf8079}
Probably caused by : memory_corruption
============================================================================
STOP 0x00000024: NTFS_FILE_SYSTEM  
Usual causes:  Disk corruption, insufficient physical memory, Device driver, 
Indexing, Resident antivirus, backup, defrag programs, Disk/Drive failing/failure
BugCheck 24, {1904fb, fffff88005f13258, fffff88005f12ab0, fffff8800130e95d}
Probably caused by : Ntfs.sys ( Ntfs! ?? ::NNGAKEGL::`string'+157e7 )
============================================================================
STOP 0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
Usual causes:  Device driver
BugCheck D1, {fffff800048bc3a1, 2, 8, fffff800048bc3a1}
Probably caused by : ntkrnlmp.exe ( nt!KiPageFault+260 )

So we'll start with simple things first;

Please uninstall ESET antivirus. It does contribute in BSODs.,replace with free MSE. You can see that bug check 50 and 24 have antivirus listed in their usual causes.

[FONT="Verdana"]Start Menu\Programs\ESET	Public:Start Menu\Programs\ESET	Public
Start Menu\Programs\ESET\ESET Smart Security	Public:Start Menu\Programs\ESET\ESET Smart Security	Public[/FONT]

• Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Recommended antivirus program for Windows 7 based on stability compared to others:-

• Microsoft Security Essentials - Free Antivirus for Windows
• Malwarebytes - The Free version
• http://www.sevenforums.com/system-security/206705-good-free-system-security-combination.html

Run a full scan with both (separately) once downloaded, installed and updated.

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

Upload a screenshot of your hard disk using crystal disk info:

• CrystalDiskInfo - Software - Crystal Dew World
• http://www.sevenforums.com/tutorials/9733-screenshots-files-upload-post-seven-forums.html

Run Disk Check on your hard disk for file system errors and bad sectors on it:

• http://www.sevenforums.com/tutorials/433-disk-check.html

Report back if your system is stable or not.​

Then go ahead with testing the ram sticks:
Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html
• Guide to using Memtest86+ - Geeks to Go Forums

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.
Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.
If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
3. Test the next stick of RAM (stick #2) in the next motherboard slot.
If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

Let us know the results and further BSODs if any