Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD while idling, error 0x00000050


11 Jan 2013   #1

Windows 7 64bit
 
 
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 System SpecsSystem Spec
.

12 Jan 2013   #2

 

Are you using an Offset voltage?
My System SpecsSystem Spec
12 Jan 2013   #3

Windows 7 64bit
 
 

Yes, it is set to auto in the BIOS.
My System SpecsSystem Spec
.


12 Jan 2013   #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 System SpecsSystem Spec
12 Jan 2013   #5

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

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   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 System SpecsSystem Spec
12 Jan 2013   #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 System SpecsSystem Spec
12 Jan 2013   #7

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

@ OP. Please let us know if our suggestions have worked.
My System SpecsSystem Spec
12 Jan 2013   #8

Windows 7 64bit
 
 

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 Windows 7? 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 System SpecsSystem Spec
12 Jan 2013   #9

 

Quote   Quote: Originally Posted by ivo09 View Post
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 System SpecsSystem Spec
21 Jan 2013   #10

Windows 7 64bit
 
 

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 System SpecsSystem Spec
Reply

 BSOD while idling, error 0x00000050




Thread Tools



Similar help and support threads for2: BSOD while idling, error 0x00000050
Thread Forum
BSOD usualy when idling, error 0x0000001e BSOD Help and Support
BSOD error 0x0000000a while idling BSOD Help and Support
Solved BSOD when idling, can't remember error code BSOD Help and Support
BSOD after idling, error 0x1000007e driver atikmdag.sys BSOD Help and Support
BSOD error 0x00000050 BSOD Help and Support
BSOD while playing game or idling , error 0x0000000(a)/(4e)/(50)/(7f) BSOD Help and Support
Solved Computer on and idling and get bsod, previously was error 0x9F BSOD Help and Support

Our Sites

Site Links

About Us

Find 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 07:43 AM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33