BSOD on startup of PC (page_fault_error?)

[cav]

Hi, so i've been having this problem with my PC recently where i'll boot it up, it will go into desktop, quickly bsod (it was too fast fro me to read but I caught a glimpse of PAGE_FAULT...), restart my PC, boot back into desktop and then everything will be fine (i'll get the "windows has recovered from an unexpected crash error" but nothing bad happens afterwords)

my pc specs are as follows:
CPU: AMD FX-6360 @ 3.9 GHz
GPU: Gigabyte GeForce GTX 660
RAM: 8GB DDR3 1333 (4*2)
HDD: Western Digital Blue 1TB
MOBO: ASUS M5A97 r2.0
OS: Windows 7 Home Premium 64-Bit
PSU: 460W coolermaster elite atx12v

 

[koolkat77]

Start by testing RAM.

Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\USER\Downloads\Compressed\JUSTIN-Wed_10_08_2014__82644_26\100814-17581-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0301c000 PsLoadedModuleList = 0xfffff800`0325f890
Debug session time: Wed Oct  8 21:19:19.892 2014 (UTC + 6:00)
System Uptime: 0 days 0:00:56.733
Loading Kernel Symbols
...............................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff6efffffff80, 0, fffff800030ae401, 5}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiDispatchFault+d1 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffff6efffffff80, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff800030ae401, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000005, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800032c9100
GetUlongFromAddress: unable to read from fffff800032c91c0
 fffff6efffffff80 Nonpaged pool

FAULTING_IP: 
nt!MiDispatchFault+d1
fffff800`030ae401 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  taskhost.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006e4b7f0 -- (.trap 0xfffff88006e4b7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8009aaa060 rbx=0000000000000000 rcx=000000000444f000
rdx=0000000004410000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8000337b862 rsp=fffff88006e4b980 rbp=fffff88006e4bb60
 r8=0000000000000000  r9=000000000003f000 r10=fffffa80067e0660
r11=000000000012019f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!NtReadFile+0x142:
fffff800`0337b862 0fb602          movzx   eax,byte ptr [rdx] ds:00000000`04410000=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000310e5b3 to fffff80003091bc0

STACK_TEXT:  
fffff880`06e4b288 fffff800`0310e5b3 : 00000000`00000050 fffff6ef`ffffff80 00000000`00000000 fffff880`06e4b3f0 : nt!KeBugCheckEx
fffff880`06e4b290 fffff800`0308fcee : 00000000`00000000 fffff6ef`ffffff80 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x43801
fffff880`06e4b3f0 fffff800`030ae401 : fffffa80`09f2d010 00000000`00000000 fffffa80`098d6c70 fffff8a0`0364fa10 : nt!KiPageFault+0x16e
fffff880`06e4b580 fffff800`0309e179 : fffff8a0`0364fa10 00000000`04410000 fffff8a0`0364fbb0 fffff8a0`00000000 : nt!MiDispatchFault+0xd1
fffff880`06e4b690 fffff800`0308fcee : 00000000`00000000 00000000`04410000 fffffa80`078d9800 fffffa80`09c31240 : nt!MmAccessFault+0x359
fffff880`06e4b7f0 fffff800`0337b862 : fffffa80`09c31200 fffffa80`00000001 fffffa80`067e0660 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`06e4b980 fffff800`03090e53 : fffff880`06e4bb60 00000000`0000042d 00000000`00000000 00000000`00000000 : nt!NtReadFile+0x142
fffff880`06e4ba70 00000000`7769131a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`024fcc68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7769131a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiDispatchFault+d1
fffff800`030ae401 4b8b1c1c        mov     rbx,qword ptr [r12+r11]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiDispatchFault+d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  531590fb

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

BUCKET_ID:  X64_0x50_nt!MiDispatchFault+d1

Followup: MachineOwner
---------

Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

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.

   Information

Errors are sometimes found after 8 passes.

   Tip

Memtest should be done overnight.

 

[cav]

I have ran memtest86 for 11 hours (started at midnight ended at 11:20) and have had 0 errors.

I was told that the asus utility suite 2 might be giving me driver issues. A while ago, I had uninstalled it due to its poor performance, but it still left some .sys files. Should I delete these files in safe mode?
Here are the names of the files:
Image path: \SystemRoot\SysWow64\drivers\AsUpIO.sys
Image path: \SystemRoot\SysWow64\drivers\AsIO.sys
Image path: \SystemRoot\SysWow64\drivers\AiChargerPlus.sys