M7NCD Pro and S3 Standby -- reboots on resume

[Canuck]

Anyone ever have any luck with getting an M7NCD Pro to resume from standby? I just tried it the other day and it goes to sleep but won't wake up...computer seems to be trying to come out of it but then just reboots.

Specs are 2500+ @ 3200+ speeds and 1GB Ram in dual channel. System is perfectly stable with Prime95 & every program I've ever run. I am using an older bios (I think it's the original one that came with it) so not sure if newer bios' fix the problem.

If anyone has it working could you post your memory size / bios number? I'm thinking it may either have to do with the amount of ram or a bios version.

Thanks.

[kylesb]

I do have s3 and resume working properly on my M7NCD-PRO system, using Nvidia ti4200 vid card and SBLive 5.1 for sound, and a mobile athlon running at 2200 Mhz. I don't have system hooked up atm, so don't have BIOS version, but I know I did flash the BIOS to one other than what came with the board, and in fact, I am not using the latest BIOS, am certain of that. Have 512 meg (2-256 meg Crucial sticks) in the system.

[kylesb]

Although this thread is quite old, there is further info to be shared regarding S3 and nvidia2 chipset based systems.

I recently tried standby again on my Biostar M7NCD-PRO system, and it would not come out of standby, fans spin up, but no video. Hmmm, me thinks, this did work at one time. After considerable fiddling, I finally discovered that if you alter the memory timings to a custom setting, the system does not resume from standby. I think I had to use either the Auto, or SPD setting for the memory timings for standby/resume to work properly. I had set the CAS setting to 2.5 as my memory can handle it, but somehow that mucks up S3 operations.

Oddly, this same issue occurs with my Asus A7N8X-DLX board. Must be something in the BIOS that affects standby/resume features with the nvidia2 chipset and Award/Phoenix BIOS.

So in summary, if you can't get your system to resume from S3 standby, try setting FSB and memory timing CMOS settings to standard values such as auto/SPD settings and 200 MHz FSB.

Also, don't forget to checkout your system setup using dumppo.exe, lots of google links on the web and usenet on how to use this MS utility and where to get it.

I think the same issue occurs when one overclocks the FSB, but have not experimented of late to reconfirm this fact.