BSOD while idling, error 0x00000050

Page 1 of 2 12 LastLast

  1. Posts : 4
    Windows 7 64bit
       #1

    BSOD while idling, error 0x00000050


    Hi all,

    I recently put together a new system and have been plagued by the BSOD.

    My specs:

    Asus P8Z77-V
    I5 3570K @ 4.4 w/ Hyper 212 Evo
    G.Skill 8GB (4x2) DDR3 1866
    2TB 7400RPM Seagate Barracuda
    Gigabyte GTX 670 WF3
    Rosewill 1000W PSU
    Win 7 64bit


    I will get a BSOD randomly, but it usually involves the PC being at idle. The only time I was actually in front of the PC when one happened was when I was watching a movie. Otherwise it always happens when I am away and the pc is just idling, doing nothing. Bug check code code is 0x00000050, caused by driver= ntoskrnl.exe, and it says 'PAGE_FAULT_IN_NONPAGED_AREA'.

    I ran a dskchk and Seagate tools to check my hdd and it came back ok. Then I ran memtest86 for about 4 passes and I also ran another memory test and got no errors from either. I suspect it is my graphics card. Can a graphics card cause this type of crash? I have the newest nvidia drivers. The card doesn't crash when under load. I can run Heaven DX11 fine. Is there another way to test it?


    PLEASE help me! Im tearing my hair out. I can't understand what is causing my system to crash while it isn't under load. I hope I haven't missed any important information. Dump files attached. Thanks in advance to anyone who responds.
      My Computer


  2. Posts : 1,476
       #2

    Are you using an Offset voltage?
      My Computer


  3. Posts : 4
    Windows 7 64bit
    Thread Starter
       #3

    Yes, it is set to auto in the BIOS.
      My Computer


  4. Posts : 1,476
       #4

    Oh no, that's not good. Auto is the worst setting for Offset when overclocking because it makes the voltage way higher than it needs to be. I recommend setting it manually. I can help with that, but you can also just experiment by starting at +0.005V and then work from there. Note: your Load-Line Calibration setting should also be set to about Medium. I wouldn't go higher than the High setting because this results in higher temperatures for the Voltage Regulator Module, and that can make stability harder to achieve.

    Anyway, the C-states called C3 and C6 must be disabled when using an Offset voltage because having them enabled usually results in instability like this while idling or while there's only a light load.

    On a side note, I also recommend disabling CPU Spread Spectrum. If it's enabled or set to Auto, then you might notice your Bus Speed in CPU-Z showing lower than 100 MHz (like 99.8 MHz). Disabling Spread Spectrum fixes that.
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #5

    Hi

    Avast is causing the BSOD for you. Uninstall it for the time being.

    Microsoft Security Essentials.

    Recommended from a strict BSOD perspective, compatibility & stability compared to other antiviruses/internet security software. It is free and lightweight:-
       Warning
    Do not start the free trial of Malware Bytes; remember to deselect that option when prompted.

    Run a full scan with both (separately) once downloaded, installed and updated.

    Make sure windows is up-to-date.

    Install all updates including Service Pack 1:

    Let us know the results and further BSOD-s if any.

    BSOD Report
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 50, {fffff8a010d66000, 0, fffff80003390439, 0}
    
    *** WARNING: Unable to verify timestamp for aswSnx.SYS
    *** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
    
    Could not read faulting driver name
    Probably caused by : aswSnx.SYS ( aswSnx+24fca )
    
    Followup: MachineOwner
    ---------
      My Computer


  6. Posts : 1,476
       #6

    I guess it could be Avast, but in my experience with using an Offset voltage, disabling C3 and C6 completely eliminates idle BSODs and idle lock-ups (as well as low-load BSODs and lock-ups). The reason this works is that disabling C3 and C6 results in a slightly higher idle voltage (and low-load voltage) so that it's no longer too low in order to maintain stability while idling or under light loads.
      My Computer


  7. Posts : 15,026
    Windows 10 Home 64Bit
       #7

    @ OP. Please let us know if our suggestions have worked.
      My Computer


  8. Posts : 4
    Windows 7 64bit
    Thread Starter
       #8

    Thank you for taking the time to respond :)

    @TwoCables

    Ok, I have followed your instructions and set the offset voltage to .005 and I will stress test for stability. I am not 100% sure what all the settings for overclocking do so I set most on AUTO. What does Load Line Calibration and PLL Over Volgate do and what should they be set to?

    @koolkat77

    Does Avast have an issue with Win7? I have used Avast on my older Vista PC (which this one replaced) for about 4 years now and never had one BSOD. I will follow your instructions to uninstall Avast and install MS Security Essentials. Does this mean I can never use Avast in the future?



    Since my BSOD are random and usually happen at idle, I will leave my PC at idle for long periods of time. I will report in a couple of days if I have not gotten any BSOD, or sooner if I do
      My Computer


  9. Posts : 1,476
       #9

    ivo09 said:
    Thank you for taking the time to respond :)

    @TwoCables

    Ok, I have followed your instructions and set the offset voltage to .005 and I will stress test for stability. I am not 100% sure what all the settings for overclocking do so I set most on AUTO. What does Load Line Calibration and PLL Over Volgate do and what should they be set to?
    Load-Line Calibration controls how much vDroop there is. VDroop is where the voltage droops down under full load, but this can't be seen with an offset voltage because the voltage sits very low while idling.

    Internal PLL Overvoltage is only needed if Windows isn't starting after using a higher multiplier. However, of course, it's not the first thing to look at if Windows isn't starting because it could be something else - like maybe the core voltage being too low or something.

    Anyway, the +0.005V offset recommendation is more or less a starting point. You'll have to experiment from there.
      My Computer


  10. Posts : 4
    Windows 7 64bit
    Thread Starter
       #10

    Hi guys just to give you an update. I took your suggestions but I believe the problem was actually caused by Max Payne 3. It seems like many people have reported the same problem. I installed the update and haven't had a bsod *knocks on wood* in over a week. I want to report that I also reinstalled Avast and it seems to be running great.

    Thanks for all your help!
      My Computer


 
Page 1 of 2 12 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 06:53.
Find Us