|Is this computer connected to a UPS ?|
If yes, did you install the software for it for monitoring the UPS in Windows ?
"Please also note that once computer goes into this digital power save mode, no action will bring the computer out of this mode and I have to reset my computer and reboot. "
When you install Windows from scratch, you MUST install the main chipset drivers for your mboard after Window's Setup has finished . The main chipset drivers have *.inf files that tell the operating system the capabilities of the main chipset and if Windows does not have that info you're likely to have problems.
If your mboard has USB 2.0 controllers the built in support for them and USB 2.0 devices is NOT automatically installed until AFTER the main chipset drivers have been installed.
Your drives will probably NOT be able to run at the speed thay are capable of in Windows, and the ACPI features of the mboard - Standby, Hibernate, sometimes Restart in Windows; Wake on ... in the bios regarding Windows - may NOT work properly, until AFTER you have installed the main chipset drivers.
"digital power save mode" is probably an ACPI feature.
(Unless you have a UPS, you have installed the monitoring software for it in Windows, it's a feature of that software, and a countdown timer has been enabled to switch it on in that software. )
A common symptom of you having NOT installed the main chipset drivers is you can't get the system to come out of a Standby or Hibernate or power saving mode of one kind or another once it has gone into it.
It's also possible that you un-intentionaly changed a default setting in the bios regarding that "digital power save mode" , in which case loading bios defaults in the bios Setup should get rid of the problem, but on the other hand when the operaing system has the proper ACPI info, it usually has no problem over-riding the bios from using any ACPI settings in the bios that would cause the computer to go into a Standby or Hibernate or power saving mode of any kind. The ones for Windows are all normally only triggered after xx minutes of user inactivity. They should NEVER come on when you're still actually doing something with the computer (other than just reading).