It is recommended to use driver sweeper when installing graphics drivers, it has resolved issue before.
Your Zip files are not complete, follow the
Blue Screen of Death (BSOD) Posting Instructions
When posting a new crash dump, include all System File Collection and health reports. They contain valuable information that we can use to find the cause of the crashes
Re-set your BIOS to defaults, this is not a good time to be changing any settings, it just complicates the trouble shooting.
Can you post your specs, this will help diagnose your system hardware.
Use these links to find your system specs.
Speccy Free System information Utility
System Info - See Your System Specs
Attachment 191434
Run memtest86+ to test your RAM, windows RAM test is not that good.
RAM - Test with Memtest86+
Run it with all RAM cards installed and for a minimum of 7 full passes, best to run overnight.
D/L CPUZ and post a snip of the CPU, Mainboard, Memory, and SPD tabs.
For posting the information , enter 'Snipping tool' in the Start button > Search box, hit enter. Select the area you want to post and save to a convenient place.
How to Post a Screenshot in Seven Forums
Your last crash is 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
This indicates that invalid system memory has been referenced.
Cause:
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.
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ffe9eaf2, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8b8d128c, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
READ_ADDRESS: GetPointerFromAddress: unable to read from 81dab718
Unable to read MiSystemVaType memory at 81d8b160
ffe9eaf2
FAULTING_IP:
Ntfs!NtfsAcquireScbForLazyWrite+13
8b8d128c 83780801 cmp dword ptr [eax+8],1
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: 8c90bbf8 -- (.trap 0xffffffff8c90bbf8)
ErrCode = 00000000
eax=ffe9eaea ebx=00000000 ecx=81dac100 edx=00000000 esi=9ca02d78 edi=870a4450
eip=8b8d128c esp=8c90bc6c ebp=8c90bc78 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
Ntfs!NtfsAcquireScbForLazyWrite+0x13:
8b8d128c 83780801 cmp dword ptr [eax+8],1 ds:0023:ffe9eaf2=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from 81c895f8 to 81cc88e3
STACK_TEXT:
8c90bbe0 81c895f8 00000000 ffe9eaf2 00000000 nt!MmAccessFault+0x106
8c90bbe0 8b8d128c 00000000 ffe9eaf2 00000000 nt!KiTrap0E+0xdc
8c90bc78 81cdbe5d 9ca02d78 00000001 870a4450 Ntfs!NtfsAcquireScbForLazyWrite+0x13
8c90bca8 81ce3ed6 8c90bcc4 8101399b 847382e0 nt!CcWriteBehind+0x6cf
8c90bd00 81cb0f2b 847382e0 00000000 8472f798 nt!CcWorkerThread+0x164
8c90bd50 81e5166d 00000000 8101390b 00000000 nt!ExpWorkerThread+0x10d
8c90bd90 81d030d9 81cb0e1e 00000000 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs!NtfsAcquireScbForLazyWrite+13
8b8d128c 83780801 cmp dword ptr [eax+8],1
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: Ntfs!NtfsAcquireScbForLazyWrite+13
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Ntfs
IMAGE_NAME: Ntfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf45
FAILURE_BUCKET_ID: 0x50_Ntfs!NtfsAcquireScbForLazyWrite+13
BUCKET_ID: 0x50_Ntfs!NtfsAcquireScbForLazyWrite+13
Followup: MachineOwner
---------
The other crashes:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffc07, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 8c4d4629, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
MODULE_NAME: Ntfs
.............................................................................................................................
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8583e01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b41e2000, High order 32-bits of the MCi_STATUS value.
Arg4: 00000135, Low order 32-bits of the MCi_STATUS value.
MODULE_NAME: hardware
............................................................................................................................
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8594d01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b6004000, High order 32-bits of the MCi_STATUS value.
Arg4: 67000135, Low order 32-bits of the MCi_STATUS value.
MODULE_NAME: hardware
.................................................................................................................................
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 850bd008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8d84b4da, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
MODULE_NAME: atikmpag
.................................................................................................................................
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: ff000004, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 81e60aa6, If non-zero, the instruction address which referenced the bad memory address.
Arg4: 00000002, (reserved)
MODULE_NAME: nt
....................................................................................................................................
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 00000000, Machine Check Exception
Arg2: 8603201c, Address of the WHEA_ERROR_RECORD structure.
Arg3: b4002000, High order 32-bits of the MCi_STATUS value.
Arg4: c5000135, Low order 32-bits of the MCi_STATUS value.
MODULE_NAME: hardware
This is a hardware issue, please fill in your system specs so we can proceed.
Driver list:
Code:
1: kd> lmntsm
start end module name
99400000 9940a000 ALSysIO ALSysIO.sys Sun Jul 10 08:27:36 2011 (4E18F1F8)
8b7a7000 8b7b0000 amdxata amdxata.sys Wed May 20 01:57:35 2009 (4A12F30F)
8199d000 819d4000 dump_nvstor32 dump_nvstor32.sys Wed Jul 01 08:17:14 2009 (4A4AAB0A)
8e1f5000 8e1f9fa0 jswpslwf jswpslwf.sys Thu May 15 18:28:43 2008 (482C105B)
90229000 9026d700 nvmf6232 nvmf6232.sys Fri May 01 03:45:40 2009 (49F9FFE4)
8b704000 8b729000 nvstor nvstor.sys Wed May 20 14:44:09 2009 (4A13A6B9)
8b770000 8b7a7000 nvstor32 nvstor32.sys Wed Jul 01 08:17:14 2009 (4A4AAB0A)
8bd89000 8bd92000 scmndisp scmndisp.sys Wed Jan 17 17:25:59 2007 (45ADEBA7)
994b9000 994c3000 secdrv secdrv.SYS Wed Sep 13 21:18:32 2006 (45080528)
8bdda000 8bde2000 spldr spldr.sys Tue May 12 00:13:47 2009 (4A084EBB)
994f1000 9955b000 spsys spsys.sys Tue May 12 00:37:10 2009 (4A085436)
Your drivers are mostly old versions.
Go to your motherboard website and update all your drivers.
Do not use the CD that came with your motherboard, they are old.