Windows 8 and 8.1 Forums


BSODs related to memory or drivers at startup

  1. #1


    Posts : 4
    Windows 8.1

    BSODs related to memory or drivers at startup


    I've been experiencing a number of different blue screens of death recently that occur just around after starting up my computer. If it's been running fine for more than a couple hours, it can go for days, but getting into that state is a hassle filled with many preceding blue screens.

    At first I thought there might be a problem with my RAM, but I ran memtest and it came out all clear. I can't see anything fishy under device manager, I don't know what to do anymore.

    Some of the blue screen messages:
    Page Fault in Non Paged Area (aswVmm.sys)
    Attempted Execute of NoExecute Memory
    Driver Verifier Detected Violation
    (there was one more I think, but can't remember, nor can I find it in my history - there was something with jraid.sys)

    The zip file I had to create with my system dumps and whatnot is attached:
    Attachment 61067

    Thanks for any help!

    Edit: Saw one other message I recognised: Driver IRQL not less or equal. Thank you.
    Last edited by MercuryHunter; 01 May 2015 at 07:26. Reason: Added in a recognised message

      My System SpecsSystem Spec

  2. #2


    Posts : 356
    Windows 8.1 Enterprise


    Hi,
    jraid.sys is a hard disk driver probably produced by Home, and your dumps mostly refer to this problem.
    Your driver is from 2009, so it would be wise to check for newer driver version on ASUS website and update other drivers as well.

    checking disk for errors also:
    Check your hard disk for errors

    Please report results/troubles/dumps
      My System SpecsSystem Spec

  3. #3


    Posts : 4
    Windows 8.1

    Updates


    Thank you! But still having problems.
    Okay, I upgraded a bunch of drivers (including that jmicron driver) and my BIOS, and still had the attempted execute of
    noexecute memory bsod a couple times - but only close to the startup of the computer, either before I could give input, or after logging, within a short while.


    I have 3HDDS - Two 3TB Sata 3 6Gbs drives - S, and T, and my main 1TB HDD split into C (250GB) and R (750GB)


    I then scanned those hard drives using Error Checking as recommended:
    C: Drive - "Your drive was successfully scanned. Windows successfully scanned the drive. No errors were found."
    R: Drive - "Your drive was successfully scanned. Windows successfully scanned the drive. No errors were found."
    S: Drive - "Your drive was successfully scanned. Windows successfully scanned the drive. No errors were found."
    T: Drive - "Your drive was successfully scanned. Windows successfully scanned the drive. No errors were found."


    What else could the problem be?


    Updated Dumps:
    Attachment 61108
      My System SpecsSystem Spec

  4. #4


    Posts : 356
    Windows 8.1 Enterprise


    Hi,
    Updating drivers, has narrowed "attack surface" down.
    last 5 out of 6 dumps are due to page fault...


    ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
    This indicates that an attempt was made to execute non-executable memory.
    None of these dumps directly points to quilty driver, which is marked in red below, just before fault occurs:


    Code:
    4: kd> kvChild-SP          RetAddr           : Args to Child                                                           : Call Site
    ffffd000`afeacc28 fffff800`fb232ee8 : 00000000`000000fc ffffe000`274c5250 80000002`8cd5b963 ffffd000`afeace70 : nt!KeBugCheckEx
    ffffd000`afeacc30 fffff800`fb283e4e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4cd28
    ffffd000`afeacc70 fffff800`fb1f8a11 : ffffd000`af040180 ffffd000`afeacd00 ffffe000`262d2880 00000000`00000000 : nt!MiRaisedIrqlFault+0x152
    ffffd000`afeaccb0 fffff800`fb1dff2f : 00000000`00000008 ffffd000`af040180 00000000`80000300 fffff800`bec00000 : nt! ?? ::FNODOBFM::`string'+0x12851
    ffffd000`afeace70 ffffe000`274c5250 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x12f (TrapFrame @ ffffd000`afeace70)
    ffffd000`afead000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffe000`274c5250
    
    4: kd> !pte 800000028cd5b963
                                               VA 800000028cd5b963
    PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00050    PDE at FFFFF6FB4000A330    PTE at FFFFF68001466AD8
    Unable to get PPE FFFFF6FB7DA00050
    WARNING: noncanonical VA, accesses will fault !
    
    // Note: VA stands for "Valid" and "Accessed" 
    
    
    
    4: kd> .trap ffffd000`afeace70
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000004
    rdx=0000000206f93000 rsi=0000000000000000 rdi=0000000000000000
    rip=ffffe000274c5250 rsp=ffffd000afead000 rbp=0000000000000000
     r8=0000000000000000  r9=0000000000000004 r10=0000000000000000
    r11=fffff800fb1e288f r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl zr na pe nc
    ffffe000`274c5250 0100            add     dword ptr [rax],eax ds:00000000`00000000=????????


    PAGE_FAULT_IN_NONPAGED_AREA
    This indicates that invalid system memory has been referenced
    Hopefully this time the guilty driver has been caught


    Code:
    10: kd> kvChild-SP          RetAddr           : Args to Child                                                           : Call Site
    ffffd001`8b71ba78 fffff803`377f805e : 00000000`00000050 ffffffff`ffffffff 00000000`00000001 ffffd001`8b71bce0 : nt!KeBugCheckEx
    ffffd001`8b71ba80 fffff803`376cb839 : 00000000`00000001 ffffe001`a2e2a040 ffffd001`8b71bce0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x1ee9e
    ffffd001`8b71bb20 fffff803`377d2f2f : 00000000`00000001 00000000`c0000001 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x769
    ffffd001`8b71bce0 fffff800`d19ce71b : fffff800`d19c46a9 00000000`80000301 fffff800`d19ac000 ffffe001`a56e1480 : nt!KiPageFault+0x12f (TrapFrame @ ffffd001`8b71bce0)
    ffffd001`8b71be78 fffff800`d19c46a9 : 00000000`80000301 fffff800`d19ac000 ffffe001`a56e1480 ffffd001`8b71bf78 : aswVmm+0x2271b
    ffffd001`8b71be80 00000000`80000301 : fffff800`d19ac000 ffffe001`a56e1480 ffffd001`8b71bf78 ffffd001`8b71bf78 : aswVmm+0x186a9
    ffffd001`8b71be88 fffff800`d19ac000 : ffffe001`a56e1480 ffffd001`8b71bf78 ffffd001`8b71bf78 fffff800`d19bcdeb : 0x80000301
    ffffd001`8b71be90 ffffe001`a56e1480 : ffffd001`8b71bf78 ffffd001`8b71bf78 fffff800`d19bcdeb ffffd001`8a72a180 : aswVmm
    ffffd001`8b71be98 ffffd001`8b71bf78 : ffffd001`8b71bf78 fffff800`d19bcdeb ffffd001`8a72a180 fffff803`377cbf33 : 0xffffe001`a56e1480
    ffffd001`8b71bea0 ffffd001`8b71bf78 : fffff800`d19bcdeb ffffd001`8a72a180 fffff803`377cbf33 ffffe001`a56e1480 : 0xffffd001`8b71bf78
    ffffd001`8b71bea8 fffff800`d19bcdeb : ffffd001`8a72a180 fffff803`377cbf33 ffffe001`a56e1480 00000000`00000003 : 0xffffd001`8b71bf78
    ffffd001`8b71beb0 ffffd001`8a72a180 : fffff803`377cbf33 ffffe001`a56e1480 00000000`00000003 ffffd001`8b71bf58 : aswVmm+0x10deb
    ffffd001`8b71beb8 fffff803`377cbf33 : ffffe001`a56e1480 00000000`00000003 ffffd001`8b71bf58 00000000`00000000 : 0xffffd001`8a72a180
    ffffd001`8b71bec0 ffffd001`8b71bff8 : 00000000`00000000 00000000`00000000 00000000`00000246 00000000`00000000 : nt!SwapContext_PatchLdtBypass+0x7
    ffffd001`8b71bf00 00000000`00000000 : 00000000`00000000 00000000`00000246 00000000`00000000 ffffe001`a56f67a0 : 0xffffd001`8b71bff8
    
    
    10: kd> .trap ffffd001`8b71bce0
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=ffffffffffffffff rbx=0000000000000000 rcx=0000000000000001
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff800d19ce71b rsp=ffffd0018b71be78 rbp=ffffd0018a754b01
     r8=000000000000044f  r9=0101010101010101 r10=000000c34b792bf8
    r11=0000000000000001 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up di pl nz ac pe nc
    aswVmm+0x2271b:
    fffff800`d19ce71b 488910          mov     qword ptr [rax],rdx ds:ffffffff`ffffffff=????????????????
    
    
    
    10: kd> lmvm aswVmm
    start             end                 module name
    fffff800`d19ac000 fffff800`d19f0000   aswVmm   T (no symbols)           
        Loaded symbol image file: aswVmm.sys
        Image path: \SystemRoot\System32\Drivers\aswVmm.sys
        Image name: aswVmm.sys
        Timestamp:        Fri Mar 20 12:57:07 2015 (550C0B13)
        CheckSum:         00047A9F
        ImageSize:        00044000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4


    The above driver belongs to Avast! antivirus and is known to produce BSOD, therefore it deserves to be removed from system at least while we track this issue down.
    During that time I would recommend to use built in Windows defender which will auto enable it self upon avast removal.
    Update windows which will in turn update windows defender.

    Please note that conventional removal might not work in some cases, therefore the safest way is to use Avast removal utility

    And of course share new results, try to reproduce BSOD
      My System SpecsSystem Spec

  5. #5


    Posts : 4
    Windows 8.1


    Okay, so I uninstalled Avast (which seems to have been good for my computer - much faster startup time), and restarted a number of times, and have also left my computer idle for some periods of time, as previously caused these BSODs, but so far nothing. If it doesn't happen again within 4 or so days, I will take it as the issue has been solved (and mark the thread so as well).

    Thank you for the help
      My System SpecsSystem Spec

  6. #6


    Posts : 356
    Windows 8.1 Enterprise


    OK, let's hope this works!
      My System SpecsSystem Spec

  7. #7


    Quote Originally Posted by Addictive Gamer View Post
    Code:
    4: kd> !pte 800000028cd5b963
                                               VA 800000028cd5b963
    PXE at FFFFF6FB7DBED000    PPE at FFFFF6FB7DA00050    PDE at FFFFF6FB4000A330    PTE at FFFFF68001466AD8
    Unable to get PPE FFFFF6FB7DA00050
    WARNING: noncanonical VA, accesses will fault !
    
    // Note: VA stands for "Valid" and "Accessed" 
    No, VA stands for Virtual Address.
      My System SpecsSystem Spec

  8. #8


    Posts : 356
    Windows 8.1 Enterprise


    Quote Originally Posted by Mysers Briggs View Post
    No, VA stands for Virtual Address.
    uff You are correct.
      My System SpecsSystem Spec

  9. #9


    Posts : 4
    Windows 8.1


    Okay, so it seems as if no further problems have come to light, leaving me to conclude that it was indeed Avast screwing everything up. Multiple restarts and idles and restarts have had no further bad effects.

    Thank you for the help Addictive Gamer
      My System SpecsSystem Spec

BSODs related to memory or drivers at startup
Related Threads
Hi guys. I've had my computer for around 4 years now and I have always had this bug that I have been unable to resolve. In the past, I had no idea what to do is the computer would just freeze up and not go to blue screen, However, since upgrading to Windows 8.1 it has been giving me a blue screen...
Hello everybody, Frustrated Windows 8 user and busy college student here. Small background on this longstanding current problem: a couple years back I had to replace most of the main components in my HP desktop due to a motherboard defect that essentially destroyed the motherboard’s ability to...
Hello. Just a prequel. I've never had a problem on Windows 7. Only after upgrading to Windows 8/8.1 over a year ago. I went back to Windows 7 just to make sure I didn't have the issue. This was several months ago. Yesterday, I just reinstalled windows 8.1 on a new SSD. I have 4x4GB (16GB)...
I have been getting some random BSOD errors the past few weeks. Most of them are related to the nvlddmkm.sys driver, according to BlueScreenView. They tend to happen if I am using Skype, playing any game, or just using Chrome. Also, they happen 8 out of 10 times if I restart, or log off of my user...
Solved Multiple BSODs everyday might be game related in BSOD Crashes and Debugging
I really need help diagnosing these BSODs. 1st off i recovered my laptop about 3 days ago to factory and it took about 10 hours then i refreshed it for another 3 hours so its all at default settings. I just started using it again today so this is the 1st time its really been on since recovery and...
Widespread memory related BSOD? in BSOD Crashes and Debugging
Hi there I have a new laptop and am trying to work out the kinks Its a new Windows 8.1 build. But seems to be causing all kinds of problems. And honestly i'm not sure where to start trying to fix it. I think its driver related but have tried updating a few drivers with varying success (as...
My CPU cooler, an Antec Khuler H2O 920, is powered by internal USB 2.0. This allows the radiator and fans to be controlled from a program inside Windows (ChillControl). The fans and radiator pump work, but I am unable to get the fans to run any faster than idle (this is important for doing anything...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook