BSOD when attempting to log in or shortly after logging in


  1. Raevion
    Posts : 4
    64-bit Windows 7 Professional
       New #1

    BSOD when attempting to log in or shortly after logging in


    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.
    Last edited by Raevion; 07 Jun 2012 at 18:28. Reason: Updating dump files
      My Computer
    Quote Quote

  3. yowanvista
    Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       New #2

    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
    Code:
    *******************************************************************************
*                                                                             *
*                        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
      My Computer
    Quote Quote

  4. Raevion
    Posts : 4
    64-bit Windows 7 Professional
    Thread Starter
       New #3

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

  6. yowanvista
    Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       New #4

    Raevion said:
    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.
      My Computer
    Quote Quote

  7. Raevion
    Posts : 4
    64-bit Windows 7 Professional
    Thread Starter
       New #5

    Updated the dump files in the first post.
      My Computer
    Quote Quote

  8. yowanvista
    Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       New #6

    STOP 0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

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

    Run those tools/tests:
    RAM - Test with Memtest86+ (At least 7 passes)
    SFC /SCANNOW Command - System File Checker
    Disk Check

    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.
      My Computer
    Quote Quote

  10. Raevion
    Posts : 4
    64-bit Windows 7 Professional
    Thread Starter
       New #7

    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.
      My Computer
    Quote Quote

  11. yowanvista
    Posts : 8,383
    Windows 10 Pro x64, Arch Linux
       New #8

    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.
      My Computer
    Quote Quote

 

  Related Discussions
As the title states, I'm experiencing frequent BSODing (this is sudden, I've never had BSOD issues with Windows 7 before) shortly after logging on to my user profile. I don't know if the problem is affecting other profiles or not, but I'm currently logged on in Safe Mode with networking, and...
BSOD shortly after logging in.
in BSOD Help and Support

Hi everyone, I just registered after browsing for a solution to my problem, so this is my last resort before finding someone more experienced to deal with this in person. After I log in I have about 15 seconds before my monitor starts to flicker and freeze, followed by the BSOD and system...
BSOD shortly after logging in
in BSOD Help and Support

I'm pretty sure it's a driver issue, ignore the old DMP files this issue has only occurred today. I also got a weird anti-virus message saying that svchost.exe was a virus but that isn't possible as far as I know being that svchost is a system file. I ran a full system scan regardless and nothing...
BSOD shortly after logon
in BSOD Help and Support

I am experiencing an occasional BSOD when booting the computer. This occurs shortly after logging on. A BSOD will flash very quickly so I can't really tell what's written. Then the system will reboot spontaneously, and then works fine thereafter. My previous installation (Win XP sp3 x86) also had a...
BSOD on log in or shortly afterwards
in BSOD Help and Support

Hi there, Suddenly today, and to the best of my knowledge without adding any new programs/hardware, windows began crashing to the BSOD. It usually happens about 1 minute after logging in although sometimes it is immediate and very rarely I can use the computer for about 20 minutes. I don't know...
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

 © Designer Media Ltd
All times are GMT -5. The time now is 03:57.
Find Us