Welcome
What were you doing at the time of crash? BSOD Index STOP 0x0000004E: PFN_LIST_CORRUPT Usual causes: Device driver, memory
BSOD Analyze Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 4E, {99, 1cdaf7, 0, 1ceaf7}
Probably caused by : memory_corruption ( nt!MiBadShareCount+4c )
Followup: MachineOwner
---------
7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PFN_LIST_CORRUPT (4e)
Typically caused by drivers passing bad memory descriptor lists (ie: calling
MmUnlockPages twice with the same list, etc). If a kernel debugger is
available get the stack trace.
Arguments:
Arg1: 0000000000000099, A PTE or PFN is corrupt
Arg2: 00000000001cdaf7, page frame number
Arg3: 0000000000000000, current page state
Arg4: 00000000001ceaf7, 0
Debugging Details:
------------------ Run memtest+86 preferably overnight for 8 passes:
RAM - Test with Memtest86+ BSOD Index 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
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff8a20947eda0, 0, fffff8000314eb3a, 5}
Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!CmpKcbCacheLookup+22a )
Followup: MachineOwner
--------- Do what the quote below asks you to: 
Quote: Originally Posted by
writhziden
Use
Advanced Boot Options to select Repair Your Computer and get to the
System Recovery Options. Then select the command prompt. Do the following:
chkdsk /r c:
chkdsk /r d:
chkdsk /r e:
chkdsk /r f:
.etc until you get the message that the volume could not be opened for direct access. For any drives that do not give the message:
"Windows has checked the file system and found no problems"
run chkdsk again as above. In other words, if it says:
"Windows has made corrections to the file system"
after running the disk check, run the disk check again.
Run the system file checker to repair windows files:
SFC /SCANNOW Command - System File Checker Checking your Msinfo32 file I see that your windows build is 7600 = Non-SP1 Please download and install all updates from windows updates including SP1 which has many patches and fixes. I see no antivirus on your computer or probably I missed it. What antivirus are you using? Get an update for your BIOS version as well.
AMI | American Megatrends Inc. : Support
Keep us posted.