Docmemory detects your Memory by reading your motherboard BIOS table.If your PC boots up with only 16 MB of memory,you will see a memory count on the Top left corner of your monitor screen, Docmemory will only read 16MB.
Make sure your PC will support higher memory and check for memory compatibility issues.
For memory upgrades please do make sure you purchase your memory from the recommended source- check your user manual for compatible brand upgrades.
I once own a Compaq presario with 16MB of SDRAM. Later -I purchase a 32 MB upgrade from a computer store and try to install the memory and it didn't work. After much frustration - I got online and purchase the original memory from Compaq directly and it work like a champ.
I found out particularly for SDRAM DIMM module - the SPD information that resides in the EEPROM found on the memory module is very crucial, the information varies for different manufacturer. If you stick a Micron 64MB DIMM into a Compaq PC - it may not work ...vice versa.
The next time you buy any upgrades -make sure you know what you are upgrading.
Apparently base from the failure description , the EDO module is indeed faulty, the modules could have a defective memory chip, which could caused any thing to happen including :
a)System reseting after booting up
b)Application error while loading Window Operating system
c)System crashing while using any word processor or spreadsheet application.
Since it gives you a blue screen during bootup- you can no longer used this module as it would be impossible see if any software have been loaded up. You may need to purchase a brand new module from any memory reseller.
We have received several feedback from the field about Docmemory having some problem detecting the correct memory size in the new i810E motherboard,this situation have been resolved with DocMemory V1.4. Please do update your software version to the latest version.
Yes it is possible for you to use DocMemory to test your server memory. When Booting up from Docmemory thru the floppy drive - the Server will be loading DocMemory operating system into the server memory for test execution. Docmemory will not crash your server while testing the memory.
We have added in a troubleshooting guide in our latest user manual V1.41. The details on how to interpret the test results can be found at the Docmemory software download page.The user-manual is formatted in pdf format.
You will need to download a free acrobat reader to read the file. The free download side is found at www.adobe.com.
If when you insert the Diagnostic diskette in the A: drive and power on the computer, it does not load DocMemory Diagnostic, the "boot sequence" may be set to boot to the hard disc drive first.
To change the boot sequence to boot from the A: drive first, you must enter the "Setup" or "CMOS Setup" of your computer. Methods for entering the Setup or CMOS Setup vary depending on your computer's make and model, but most methods consist of pressing a key or key sequence during the initial power on boot sequence. To determine
which key or key sequence to press for your computer, watch the screen closely during boot up for a message like "Press F1 to enter Setup" or something similar. Nearly all systems will continue on automatically after a brief period of time if the key is not pressed, so act quickly. You may have only a few seconds to find and
press the appropriate key or key sequence.
The most common keys or key sequences to enter setup are:
NOTE: Some computers that use the "[CTRL]-[ALT]-[___]" sequences
must be at a prompt before pressing the keys. If you are unsure about how to enter the setup, see the owner's manual for your computer or seek assistance from your computer manufacturer or the
store where you purchased the computer.
If your receive an error message "DocMemory Diagnostic could not read strings from the diskette," make sure the diskette is still in the diskette drive. If the message persists, there may be an error on the diskette. Create a new DocMemory Diagnostic diskette and run the tests again.
The diskette may not have enough free space to write to a report file. Normally this would only happen if the DocMemory Diagnostic has created a large number of fail report files. If this is the case, delete some of the report files or copy them to another diskette and run the tests again.
The diskette may have a bad sector which cannot be written to. Ifthis is the case, create a new DocMemory Diagnostic diskette and run the tests again.