BSOD when attempting to log in or shortly after logging in

[Raevion]

I built my first computer almost two weeks ago, and it worked just fine for a while, but now it repeatedly gives me a blue screen whenever I try to log in. Sometimes it happens after I type in my password and press enter, sometimes while I'm typing it, and sometimes when I just hover the mouse pointer over my user icon.

I attempted the System Health Report like the BSOD thread instructed, but that generates an error:
The system cannot find the path specified.

64-bit Windows Professional
Full retail version
System age and date of OS installation is 12 days.

Any help I can get is greatly appreciated.

EDIT: Updated the dump files.

 

[yowanvista]

Your BSODs were triggered by a2service.exe, part of Emsisoft Antimalware. Remove this application and check if you still experience those BSODs.

Update your Ideazon ZBoard/Ideazon Fang MM USB HID driver, the current version is obsolete & incompatible with Windows 7.
http://steelseries.com/support/downloads

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: fffffae00a9cc718, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002cfb761, address which referenced memory

WRITE_ADDRESS:  fffffae00a9cc718 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`02cfb761 48893cc2        mov     qword ptr [rdx+rax*8],rdi

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  a2service.exe

TRAP_FRAME:  fffff88002bc0660 -- (.trap 0xfffff88002bc0660)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000c015398e2 rbx=0000000000000000 rcx=0000000000000007
rdx=fffffa8000000008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002cfb761 rsp=fffff88002bc07f0 rbp=000000000000007b
 r8=0000000000000000  r9=0000000000000000 r10=fffffa800c901358
r11=fffff80002e4ee80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiUnlinkFreeOrZeroedPage+0x181:
fffff800`02cfb761 48893cc2        mov     qword ptr [rdx+rax*8],rdi ds:0840:fffffae0`0a9cc718=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002cdb769 to fffff80002cdc1c0

STACK_TEXT:  
fffff880`02bc0518 fffff800`02cdb769 : 00000000`0000000a fffffae0`0a9cc718 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02bc0520 fffff800`02cda3e0 : fffffa80`46503241 fffff880`00000000 fffffa80`00000000 fffffa80`0a9caf10 : nt!KiBugCheckDispatch+0x69
fffff880`02bc0660 fffff800`02cfb761 : fffffa80`0ffdfdb0 00000000`0757f800 00000000`07d00020 00000000`00000000 : nt!KiPageFault+0x260
fffff880`02bc07f0 fffff800`02cfff98 : fffff880`02bc08c0 00000000`003898fb fffffa80`0a9caf10 00000000`00000070 : nt!MiUnlinkFreeOrZeroedPage+0x181
fffff880`02bc0860 fffff800`02ce9634 : 00000000`00000000 00000000`00000002 00000000`00000000 ffffffff`ffffffff : nt!MiRemoveAnyPage+0x1d8
fffff880`02bc0980 fffff800`02cda2ee : 00000000`00000001 00000000`7ed0e000 fffff880`02bc0a01 00000000`00100048 : nt!MmAccessFault+0x1224
fffff880`02bc0ae0 00000000`75709b60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`0757f86c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75709b60


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiUnlinkFreeOrZeroedPage+181
fffff800`02cfb761 48893cc2        mov     qword ptr [rdx+rax*8],rdi

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!MiUnlinkFreeOrZeroedPage+181

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4f76721c

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181

BUCKET_ID:  X64_0xA_nt!MiUnlinkFreeOrZeroedPage+181

 

[Raevion]

I have just done both of those, but the BSODs still happen like before.

 

[yowanvista]

I have just done both of those, but the BSODs still happen like before.

Upload a new attachment with new dumps and we'll have a look at any new causes.

 

[Raevion]

Updated the dump files in the first post.

 

[yowanvista]

STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Usual causes: Defective hardware, Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

Run those tools/tests:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html (At least 7 passes)
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
http://www.sevenforums.com/tutorials/433-disk-check.html

Update your Lan/Router/Wireless driver. The driver WPN111vx.sys belongs to a wide range of Wireless hardware such as Netgear or Atheros devices.

Enable Driver Verifier, it'll help us to identify any faulty drivers.
Driver Verifier - Enable and Disable

Note: Your computer may not be functional in Normal Mode if faulting drivers are detected during this phase, you may need to use Safemode with Networking.

 

[Raevion]

Before I report how your suggestions worked out, I tried something with my motherboard. It's an Asus Sabertooth X79, and one of its features is a MemOK button. I held it down for three seconds to activate it, and since then, my computer has been working fine. That said, I'm not ready to consider this problem resolved- I find it hard to believe that a press of a button was all I needed to do. It also suggests that the problem was related to my RAM.

Moving on to the suggestions:

I am having trouble getting Memtest to work from a USB. I tried changing the priority in BIOS so that the USB drive would boot first, but it hasn't automatically started running like the tutorial said it would. Is there something else I need to do to make it work, or should I try it from a CD instead?

The sfc /scannow command reported that "Windows Resource Protection did not find any integrity violations."

Disk Check reported that no problems were found on both my SSD and my HDD.

My wireless adapter is up to date.

Driver Verifier is enabled now.

 

[yowanvista]

Before I report how your suggestions worked out, I tried something with my motherboard. It's an Asus Sabertooth X79, and one of its features is a MemOK button. I held it down for three seconds to activate it, and since then, my computer has been working fine. That said, I'm not ready to consider this problem resolved- I find it hard to believe that a press of a button was all I needed to do. It also suggests that the problem was related to my RAM.

Yes, that could possibly be the fix here considering that the RAM was the culprit.

I am having trouble getting Memtest to work from a USB. I tried changing the priority in BIOS so that the USB drive would boot first, but it hasn't automatically started running like the tutorial said it would. Is there something else I need to do to make it work, or should I try it from a CD instead?

Nope, it should boot from the USB disk without any issues unless the memtest86+ image wasn't properly written to the USB disk.

Continue to monitor your PC & upload any new dumps.