Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
nv ram!!
- Thread starter 210291
- Start date
If it's stopping at the RAM-check stage, it's not even reading the HDD, is it? There's still a load of POSTing and BIOS passing to do before that point.
If you're having an issue before you even get to booting the OS, there are two possibilities: hardware error, or incorrect BIOS settings. If it's the former it'll be a pig to diagnose, but I'd try swapping the RAM for a start. Either way, the first thing I'd do is reset the BIOS (there should be a jumper near the CMOS battery or, if it comes to it, you can just remove the battery for a minute). If that solves the problem then have a look in the BIOS and set it up properly. If it doesn't, your hardware's properly knackered somewhere - whether RAM, CPU or motherboard. If you want to diagnose properly you'll need another rig to swap bits out of.
If you're having an issue before you even get to booting the OS, there are two possibilities: hardware error, or incorrect BIOS settings. If it's the former it'll be a pig to diagnose, but I'd try swapping the RAM for a start. Either way, the first thing I'd do is reset the BIOS (there should be a jumper near the CMOS battery or, if it comes to it, you can just remove the battery for a minute). If that solves the problem then have a look in the BIOS and set it up properly. If it doesn't, your hardware's properly knackered somewhere - whether RAM, CPU or motherboard. If you want to diagnose properly you'll need another rig to swap bits out of.
well don't be confused by the term NVRAM - its not the same thing as main memory or what is commonly known as RAM.
The NV is for non-volitile which means they usually are going to use the term to refer to CMOS or the BIOS flash part itself (sometimes still refered to as a ROM even though its no longer a ROM in the contemporary machine).
In the first case (if referring to CMOS) then clearing CMOS should be sufficient to clear the problem, in the second case, it will almost definately require you to flash your BIOS. Do you know where to get a new copy of your BIOS and its flashing guide?
additionaly, it may have actually finished checking NVRAM and moved on to some other thing, but not reached a part that displays some new message, so still its possible there is some hardware issue.
In fact, it almost has to be a hardware issue as your BIOS hasn't changed since it was installed. The flash part may be going bad or your CMOS battery could be dead - how old is your system?
The NV is for non-volitile which means they usually are going to use the term to refer to CMOS or the BIOS flash part itself (sometimes still refered to as a ROM even though its no longer a ROM in the contemporary machine).
In the first case (if referring to CMOS) then clearing CMOS should be sufficient to clear the problem, in the second case, it will almost definately require you to flash your BIOS. Do you know where to get a new copy of your BIOS and its flashing guide?
additionaly, it may have actually finished checking NVRAM and moved on to some other thing, but not reached a part that displays some new message, so still its possible there is some hardware issue.
In fact, it almost has to be a hardware issue as your BIOS hasn't changed since it was installed. The flash part may be going bad or your CMOS battery could be dead - how old is your system?
Dillinger99
Technical User
Do you have a PCI or AGP graphics card as well as onboard graphics capabilities?
A little background on the NVRAM, that is the portion where the CMOS SETUP stores information about the HARDWARE of the PC...
in the CMOS SETUP there is an option to clear this area and have it rewritten with the new information about the installed hardware... problems in this area usually indicates a piece of hardware is being adressed wrongly, because it either changed or the NVRAM has false information (usually happens when HDD's change or sometimes with NICs)...
Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
in the CMOS SETUP there is an option to clear this area and have it rewritten with the new information about the installed hardware... problems in this area usually indicates a piece of hardware is being adressed wrongly, because it either changed or the NVRAM has false information (usually happens when HDD's change or sometimes with NICs)...
Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
Well . . . kinda
NVRAM can mean a number of different things. It can mean CMOS which in most systems corrispond to setup, but it can any type of non-volitile storage.
Usually in fact (in the PC/x86 realm), NVRAM specifically refers any non-volitile storage other than CMOS. Ussually then a special section of the BIOS flash part which is used for non-setup data, e.g. ESCD, SMBIOS, HHF/HHM, and event logging.
Actually though in contemporary systems it is becoming more likely that set-up data will be stored both in traditional CMOS and in NVRAM.
As systems transition to EFI in the next few years, manufactures will hope to see CMOS removed from designes entirely as EFI has no need or use for CMOS with an EFI aware OS (theoretically the 2nd release of longhorn will be EFI aware).
NVRAM can mean a number of different things. It can mean CMOS which in most systems corrispond to setup, but it can any type of non-volitile storage.
Usually in fact (in the PC/x86 realm), NVRAM specifically refers any non-volitile storage other than CMOS. Ussually then a special section of the BIOS flash part which is used for non-setup data, e.g. ESCD, SMBIOS, HHF/HHM, and event logging.
Actually though in contemporary systems it is becoming more likely that set-up data will be stored both in traditional CMOS and in NVRAM.
As systems transition to EFI in the next few years, manufactures will hope to see CMOS removed from designes entirely as EFI has no need or use for CMOS with an EFI aware OS (theoretically the 2nd release of longhorn will be EFI aware).
- Status
Similar threads
- Locked
- Question