Regular BSOD - 0x50 - Page fault in nonpaged area

Page 1 of 3 123 LastLast

  1. Posts : 17
    Windows 7 Ultimate x64
       #1

    Regular BSOD - 0x50 - Page fault in nonpaged area


    Hi guys

    I've had a lot of problems with BSODs on my new computer. I don't know if a record of events is important for the diagnosis, but I'll go ahead and write it out, and if it's not, feel free to just skip to the attached file.

    I recently got a few pieces of new hardware - MB, CPU, GPU, RAM, PSU and UPS. When I installed them, all seemed good at first. I went through the motions of installing drivers and all that jazz, and then got around to playing with it. I think around 2 hours in was when I got the first BSOD, but it didn't happen again for the rest of the night, so I ignored it.

    A few hours later, I'm woken up by the UPS beeping. The power had gone out (a common occurrence and the reason I bought the UPS in the first place). It turned out the electrical company had screwed up well this time, and rather than a 2 minute blackout, it lasted all day. When that fact became clear, I shut down the computer (still running on battery power from the UPS) the regular way and waited for the power to come back on.

    Power comes back on. From that point on, between 2 and 10 minutes from booting up the computer, I get the same BSOD I'd gotten on the first day. I do basic hardware troubleshooting in the form of trying my RAM chips one by one, trying to run on the old graphics card, unplugging excess hard drives, and running it through the UPS vs running it plugged in directly. Nothing changes.

    So I figure it's a software issue. I'd read that virtual imaging software can cause this BSOD, so I unistalled them all. No help. I read that antivirus software can cause this as well, so I unistalled that too. Now, here's the interesting part. After uninstalling Avast, it worked good for about an hour or so. I thought it was fixed, but it went right back to crashing after that time period was over.

    I went back to hardware. The only part I hadn't swapped out (apart from the MB and CPU, which I can't) was the PSU. I dug out my old one and plugged it in, booted up, and - voila! - it didn't crash for the rest of the night. Satisfied that I'd gotten to the root of it after 6 hours of "testing" in the form of playing games, I go to sleep, leaving the computer on to see if it would still be working in the morning.

    It wasn't. I got up this morning, and the Windows welcome screen was waiting for me. Checked my minidumps, and it turns out it had been crashing and restarting itself all night while I slept. Much to my frustration, it's still doing it now as I write out this post in three sentence increments between BSODs.

    I am at an absolute loss. The only conclusion I can come to is that both PSUs got fried by the UPS when the power fluctuated, but my evidence for that is flimsy and certainly not grounds for accusing the supplier for pushing faulty hardware.

    So, dear internet people, I come to you. Is there anything in the dumped files that can give ANY sort of hint as to why this is happening? Your time is greatly appreciated.
      My Computer


  2. Posts : 17,796
    Windows 10, Home Clean Install
       #2

    Welcome
    A lot of reports, most with the same answer. The problem seems to be your Avast. Uninstall Avast, then in its place use Microsoft Security Essentials. Start with a system restore point so it will be easy to go back if the problem is not solved. Good luck

    EDIT Reading your post again, it seems you did uninstall Avast, you left a driver and it is the cause.
    aswsnx.sys
      My Computer


  3. Posts : 17
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Hi Rich

    I already uninstalled Avast. It gave me an hour-long reprieve from the BSODs, but they resumed in their normal fashion thereafter. Looks like that wasn't it.

    Edit: A ha. Could you tell me how I'd uninstall the driver? I'm a bit of a noob. :)
      My Computer


  4. Posts : 17,796
    Windows 10, Home Clean Install
       #4

    Try the uninstall tool. If that does not work, Ill tell you how to do it manucally
    avast! Uninstall Utility | Download aswClear for avast! Removal
      My Computer


  5. Posts : 17
    Windows 7 Ultimate x64
    Thread Starter
       #5

    I ran the uninstall tool. It said it was successfully removed and rebooted the system to seal the deal. I'm gonna leave the computer on for a while, and if it doesn't crash, I'll update the thread and mark it as solved.

    Thanks for the help, Rich. :)
      My Computer


  6. Posts : 17,796
    Windows 10, Home Clean Install
       #6

    Hope that you got your BSOD sorted. I think my advice will work, however.
      My Computer


  7. Posts : 17
    Windows 7 Ultimate x64
    Thread Starter
       #7

    No luck. Crashed again.

    Do you have any other ideas?
      My Computer


  8. Posts : 17,796
    Windows 10, Home Clean Install
       #8

    Give me the report, so that I could look at it.
      My Computer


  9. Posts : 17
    Windows 7 Ultimate x64
    Thread Starter
       #9

    This is what WhoCrashed had to say:


    On Fri 8/3/2012 9:35:38 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\080312-13634-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
    Bugcheck code: 0x50 (0xFFFFF8A00A566000, 0x0, 0xFFFFF8000354B079, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


    On Fri 8/3/2012 9:35:38 AM GMT your computer crashed
    crash dump file: C:\Windows\memory.dmp
    This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
    Bugcheck code: 0x50 (0xFFFFF8A00A566000, 0x0, 0xFFFFF8000354B079, 0x0)
    Error: PAGE_FAULT_IN_NONPAGED_AREA
    Bug check description: This indicates that invalid system memory has been referenced.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.



    Let me know if you need data from somewhere else.
      My Computer


  10. Posts : 17,796
    Windows 10, Home Clean Install
       #10

    I need the actual report, like you made in your first post.
      My Computer


 
Page 1 of 3 123 LastLast

  Related Discussions
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 09:29.
Find Us