It sounds like the issue is with the raid dimm. Could you power down, the unplug the raid battery from the controller, then reseat the raid dimm. After that then reconnect the battery and boot and see if error clears. Also, boot to the controller and then go to Ctrl Mgmt and get the package and revision of the controller.
the system that you have may have min. memory required to run, when going over that amount, or use more that 1 slot, the system may require ram fan, to keep the memory cool.
4 Gigs of memory is sufficient (not optimal, but if you have a 32 bit OS there are limitations), if you do not have a resident program using to much memory. SQL or other programs, unrestrained will allocate a high amount of memory (generally they can be restrained by setting parameters). Even so, programs will restrain themselves enough to leave sufficent memory for the OS.
Very likely you have either a program bug or bad driver causing a memory leak. Google "memory leak diagnose" . I have a few clients with DCs 4Gigs, with SQL, AV software, resident backup software etc, and the DCs are perfectly stable. Unlikely it is a "bad" ram stick unless you get BSODs or "rollovers", same would happen with a hardware issue with the disk subsystem. Malware/viruses/rootkits can also cause this.
First update all driver and firwmare, update all resident programs, get all the newest MSUpdates.
Run Malwarebytes and a few rootkit revealer programs. Run a free web based virus scanner, other then supplied by your present AV program.
Down and dirty memory leak detection....
After server is restarted, settles down for 5-30 minutes, open taskmanager, sort on memory use, any program which continues to increase memory use, without returning it after a short time, is leaking (generally).
"Another information is that the DC has enabled write chaching on disk"
This perfectly acceptible with a hardware based raid adapter (with battery). On a standard disk controller it is not acceptible.
DELL-Chris H
Moderator
•
9.7K Posts
0
February 17th, 2012 08:00
It sounds like the issue is with the raid dimm. Could you power down, the unplug the raid battery from the controller, then reseat the raid dimm. After that then reconnect the battery and boot and see if error clears. Also, boot to the controller and then go to Ctrl Mgmt and get the package and revision of the controller.
CANDYMANGANDY
17 Posts
1
February 25th, 2012 12:00
the system that you have may have min. memory required to run, when going over that amount, or use more that 1 slot, the system may require ram fan, to keep the memory cool.
pcmeiners
4 Operator
•
1.8K Posts
0
February 25th, 2012 14:00
4 Gigs of memory is sufficient (not optimal, but if you have a 32 bit OS there are limitations), if you do not have a resident program using to much memory. SQL or other programs, unrestrained will allocate a high amount of memory (generally they can be restrained by setting parameters). Even so, programs will restrain themselves enough to leave sufficent memory for the OS.
Very likely you have either a program bug or bad driver causing a memory leak. Google "memory leak diagnose" . I have a few clients with DCs 4Gigs, with SQL, AV software, resident backup software etc, and the DCs are perfectly stable. Unlikely it is a "bad" ram stick unless you get BSODs or "rollovers", same would happen with a hardware issue with the disk subsystem. Malware/viruses/rootkits can also cause this.
First update all driver and firwmare, update all resident programs, get all the newest MSUpdates.
Run Malwarebytes and a few rootkit revealer programs. Run a free web based virus scanner, other then supplied by your present AV program.
Down and dirty memory leak detection....
After server is restarted, settles down for 5-30 minutes, open taskmanager, sort on memory use, any program which continues to increase memory use, without returning it after a short time, is leaking (generally).
"Another information is that the DC has enabled write chaching on disk"
This perfectly acceptible with a hardware based raid adapter (with battery). On a standard disk controller it is not acceptible.