BSOD Windows 7 - ntoskrnl.exe+7cc40

Page 3 of 7 FirstFirst 12345 ... LastLast

  1. Posts : 47
    Windows Home Premium 64bit
    Thread Starter
       #21

    I went back into BIOS and looked all over. I saw a VDDNB Over Volage: [AUTO]

    The options on that are -/+ to change values

    Standard = By CPU
    Min = Standard - 0.3000V
    Max = By CPU
    Increment = 0.003125V

    My only options are to set the over voltage up by the increments or down to auto.

    I'm sorry, but i know very little about NB and CPU.
      My Computer


  2. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #22

    Your processor usually runs at a default of VDDNB: 1.1 V (see Voltage Help with AMD and Asus Mobo - Guru3D.com Forums). Try bumping the voltage to VDDNB: 1.2 V.
      My Computer


  3. Posts : 47
    Windows Home Premium 64bit
    Thread Starter
       #23

    I don't want to fry anything so let me see if I understand this...
    You want me to increase the increment to .1V?
    Since it defaults at 1.1V, I'd need to overvoltage it by .1V?

    I did a little reading and I think I understand it...

    The NB handles some of the areas where I've been having my most frequent errors... (RAM controller and PCIE). Will increasing the voltage increase its ability to handle these functions?
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #24

    That is the general idea. Most motherboards are designed to handle 4 GB of RAM with the auto settings. When a user has more than 4 GB, it can sometimes require extra support through the NB voltage to allow the RAM to work as it is supposed to.
      My Computer


  5. Posts : 47
    Windows Home Premium 64bit
    Thread Starter
       #25

    Ok... I went to make your changes (Crashed and went into bios since i was there...)

    I think I discovered the default setting for my CPU and NB

    CPU 1.075
    NB 0.8

    When I started to increase the increment, that is where they started. Do you still think 1.2V is still a good idea for the NB?

    Edit: Added latest dump files.
    Last edited by garthrs; 21 Feb 2012 at 22:58. Reason: added dump files
      My Computer


  6. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #26

    Your NB voltage should be within 0.5 Volts of DRAM voltage. DRAM is set to 1.50 V, so it is not surprising you are crashing if the NB is 0.8 V. Definitely bump the NB Voltage, but first try it at the 1.1 V setting and bump the CPU Voltage to 1.125 V. See if it provides more stability. CPU Voltage should be higher than or equal to NB Voltage.

    Safer would be to adjust the VDDNB Voltage to 1.1 V and leave the CPU Voltage on Auto.
    Last edited by writhziden; 21 Feb 2012 at 23:11. Reason: Safer...
      My Computer


  7. Posts : 47
    Windows Home Premium 64bit
    Thread Starter
       #27

    I'll give a shot.

    Thanks alot for all the help.
      My Computer


  8. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #28

    No problem. Keep us posted on how the RAM settings go. Best of luck.
      My Computer


  9. Posts : 47
    Windows Home Premium 64bit
    Thread Starter
       #29

    No improvement.

    Attached the latest dump files...

    I see so many other people with my problem and there is always a simple "remove this driver"... What I wouldn't give to have those problems.

    What can I try now? I'm out of ideas.

    Thanks again for the help.
      My Computer


  10. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #30

    I do still see
    Code:
    AODDriver2	fffff880`07210000	fffff880`07241000	Wed Jun 15 02:38:35 2011 (4df86f8b)	00012df4		AODDriver2.sys
    I think it is odd that AMD does not give the option to just install the drivers and not the software for your card. Do the following: Find all instances of AODDriver2.sys on your system. Do a search through the command prompt. First, create a system restore point in case these directions have undesired side effects.

    Start Menu -> All Programs -> Accessories -> Right Click Command Prompt -> Run as administrator ->
    cd ..
    cd ..
    dir /a /s AODDriver2.sys

    The last step is a set of commands entered into the command prompt, and after each you hit enter. Go to the directories that have AODDriver2.sys and rename all AODDriver2.sys files to AODDriver2.sys.bak and see if your crashes stop.
      My Computer


 
Page 3 of 7 FirstFirst 12345 ... 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 16:07.
Find Us