BSOD page_fault_in_nonpaged_area Win7 and Win8

Page 9 of 9 FirstFirst ... 789

  1. Posts : 45
    Windows 8 Pro x64
    Thread Starter
       #81

    Dave76 said:
    There are a few voltage fluctuations, other than that the graphs look ok.

    Is there a reason you're running your OC with locked in CPU frequency and voltage?
    This causes a lot of stress on your CPU, most people are OC'ing with EIST enabled and Balanced Power plan.

    This let's your system idle and gives full power when needed.
    You choice, just a recommendation.

    Let us know if you have any more crashes.
    I thought disabling Speed Step was best practice for overclocking? You want a consistent voltage and don't want the extra load of the CPU having to clock back/up on-demand.

    Dave76 said:
    At this point the crashes are likely coming from your OC, 4.0GHz is pretty high for your CPU and motherboard.
    The OCCT graphs are showing fluctuating 12v and 5v power at your motherboard. This may be caused by the PSU or the motherboard.
    If you want to check into the cause of these crashes you will need to set BIOS to defaults until the cause is found.
    Once the cause is found you can OC again.

    Latest crash:
    Code:
    STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
    Usual causes:  Device driver, hardware, System service, compatibility, Remote control programs, memory, BIOS
    This is a very common bug check, not much info in the dump the help.
    PROCESS_NAME:  t6mp.exe
    FAILURE_BUCKET_ID:  0x1E_c0000096_nt!_??_::FNODOBFM::_string_
    From your System Event Logs:
    Code:
    Event[3076]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-PnP
      Date: 2012-11-18T17:59:54.346
      Event ID: 219
      Task: N/A
      Level: Warning
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: C-PC
      Description: 
    The driver \Driver\WudfRd failed to load for the device ROOT\WPD\0000.
    WudfRd driver is a Windows Driver Foundation - User-mode Driver Framework Reflector
    Code:
    Event[3080]:
      Log Name: System
      Source: Microsoft-Windows-Kernel-Processor-Power
      Date: 2012-11-18T17:59:54.377
      Event ID: 55
      Task: N/A
      Level: Information
      Opcode: Info
      Keyword: N/A
      User: S-1-5-18
      User Name: NT AUTHORITY\SYSTEM
      Computer: C-PC
      Description: 
    Processor 3 in group 0 exposes the following power management capabilities:
    
    Idle state type: ACPI Idle (C) States (1 state(s))
    
    Performance state type: ACPI Performance (P) / Throttle (T) States
    Nominal Frequency (MHz): 4400
    Maximum performance percentage: 100
    Minimum performance percentage: 100
    Minimum throttle percentage: 13
    Is your CPU running at 4.4 GHz?

    Your App Event Logs are showing a large amount of games and Steam App crashes.
    I've had this i3 at 4.0Ghz since July 2010, it's only the past month or so that I've ever had a blue screen. The 4.4Ghz is the QPI speed, not the actual clock speed - should I scale this back? I can only do 16x or 18x, so its either 3.8Ghz or 4.4Ghz. I could also try decreasing the overclock (perhaps even go back to stock 2.93Ghz) and see what happens.

    Yes, I had quite a few crashes playing Black Ops 2.
      My Computer


  2. Posts : 45
    Windows 8 Pro x64
    Thread Starter
       #82

    OK, I reset BIOS and am back at paltry 2.93Ghz. At idle the cores now sit at 24C!! Freezing!

    Bizarrely, I ran Windows Experience Index, and I still get a 7.2 CPU rating even though I've gone from 4.0Ghz to 2.93Ghz - does that make any sense?
      My Computer

  3.    #83

    cdog27 said:
    OK, I reset BIOS and am back at paltry 2.93Ghz. At idle the cores now sit at 24C!! Freezing!

    Bizarrely, I ran Windows Experience Index, and I still get a 7.2 CPU rating even though I've gone from 4.0Ghz to 2.93Ghz - does that make any sense?
    Any more BSODs? I think it's takes into consideration the potential of your CPU, not the current clock speed; but I'm not entirely sure myself

    You could try resetting the WEI score.
      My Computer


  4. Posts : 12,177
    Windows 7 Ult x64 - SP1/ Windows 8 Pro x64
       #84

    cdog27 said:
    Dave76 said:
    Is there a reason you're running your OC with locked in CPU frequency and voltage?
    This causes a lot of stress on your CPU, most people are OC'ing with EIST enabled and Balanced Power plan.

    This let's your system idle and gives full power when needed.
    You choice, just a recommendation.
    I thought disabling Speed Step was best practice for overclocking? You want a consistent voltage and don't want the extra load of the CPU having to clock back/up on-demand.
    That was the standard several motherboard versions (years) ago, at first Speed Step wasn't as good as it is now.
    If you visit any OC forums most people recommend using EIST for everyday OC'ing. Except for the hardcore, squeeze every possible MHz because I'm going to throw this CPU and motherboard away after a year, guys.
    If your going for the world record then disable it.
    cdog27 said:
    Dave76 said:
    At this point the crashes are likely coming from your OC, 4.0GHz is pretty high for your CPU and motherboard.
    The OCCT graphs are showing fluctuating 12v and 5v power at your motherboard. This may be caused by the PSU or the motherboard.
    If you want to check into the cause of these crashes you will need to set BIOS to defaults until the cause is found.
    Once the cause is found you can OC again.

    Your App Event Logs are showing a large amount of games and Steam App crashes.
    I've had this i3 at 4.0Ghz since July 2010, it's only the past month or so that I've ever had a blue screen. The 4.4Ghz is the QPI speed, not the actual clock speed - should I scale this back? I can only do 16x or 18x, so its either 3.8Ghz or 4.4Ghz. I could also try decreasing the overclock (perhaps even go back to stock 2.93Ghz) and see what happens.

    Yes, I had quite a few crashes playing Black Ops 2.
    When you extreme OC for long periods you have to accept the accelerated damage to your components. Which may or may not be able to keep performing at the previous levels.

    Two and a half years at fill tilt, I'm not surprised you are starting to see component degradation.

    Test it at default BIOS settings, as you've done, for a while. If it is stable, that's your answer.
    You can probably OC it again but, not so high and I recommend to use EIST (Speed Step) to lessen the stress on your system.

    Getting the same WEI score for your CPU is a little unusual but not unheard of.

    Let us know if you're getting any more crashes.
      My Computer


 
Page 9 of 9 FirstFirst ... 789

  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 20:43.
Find Us