No cold boot into windows

hhesser

New member
PRIVATE FIRST CLASS
Joined
Nov 3, 2009
Messages
10
HI, All.  I just finished the build down below.  This is my first build ever and right up front, I will say I really don't know much at all about building computers, but we all have to start somewhere.  I have been lurking here for awhile, and it has influenced some items that I purchased for my first build, but I am new enough that I don't even know where to find some of the screens that you guys have posted to troubleshoot a problem so I will be very slow on the uptake. 

Windows will not power up in the mornings unless I power down during post-screen.  I just have a blank screen, and Windows will not boot unless I reset the power button.  The memory is placed in the proper slots as per the downloaded GD65 manual and is seated correctly.  This morning early I tried just for the heck of it I tried the OC genie as per the directions.  The system would not boot at all, and at post, it kept cycling on and off.  I had to hold the power button down for awhile to get the unit to shut down.  I decided not to try that again.  Right now I would just like to get the system to boot on first power up and would appreciate any suggestions and specific direction about how I might follow your advice.
Thank you.
 
No not yet. Have not tried anything until I get a few responses because I have to do one thing every mornings or however long it takes to get a cold boot. I guess i should figure that out also. I can try that when I get back home today. Then try to boot to windows. thanks
 
OK reset cmos yesterday. Used the jumper method. Got the MSI logo screen then the following message, matrix storage manager option rom v8.9.0.1023 pch-d wraid5 right (c) 2003-09 intel corporation, then it froze. I am going to recheck bios later after I reread the manual. Any ideas of what to look for? Shutting it down for 2 to 3 hours and it will boot thru to win 7 but over night it won't. So I can only make a couple of changes at a time to try to narrow it down.
 
Start by getting the memory out of the equation as much as possible:  use one memory module only @DDR2-1333 @1.6V.  Set the Command Rate to 2N/2T and retest.
 
First, thanks for the reply. Would you mind telling me where I can find in bios  command rate option for 2n/2t ? Yes I am a new at this. I can see you rolling your eyes now :grin:. I did pull the dimm 3 ram out. 
 
Okay. I went to cell menu and dropped to DRAM Timing Mode, changed from Auto to Manual which highlighted Advance DRAM configuration, pressed Enter; the first line of Channel 1 reads CH1 1T/2T Memory Timing with 1 in brackets [1]. I can't make changes to that. Is this default correct?
 
When the number in brackets to the right of 1T/2T Memory Timing is highlighted, using the + / - on the num pad only advances the number in bracket to 1, 2, 3 and back again. Should I set it at 2 and reboot.  I don't see 1N/2T anywhere.
THX.
 
Set 1T/2T Memory Timing  at [2] for each channel.
The BIOS requires you to change the memory timings by the channel; simply scrolling the menu down gets you to channel 2.
 
I only have Channel 1.  I only have one stick of RAM installed.  If I have both installed, will that give me Channel 2?
 
Thanks for the help. I will see after a cold boot if I can boot to windows. By the way your English is good.
 
Well this morning for the first time since I built this confuser it booted straight to windows. I am HAPPY.  Thank-you anDrasch and Jacktn for your help. Now if I really understood what I did. :bonk: I need to find some reading material written for novices.  tks
 
:biggthumbsup: I hope it is fixed now.
The Command Rate  is the latency, which is required in the selection of individual memory chips, more specifically, the address and command decode latency.
The latency time indicates how long a memory bank bears addressing signal before the control of the rows and columns is done to the memory matrix.
Basically it is the time the chipset needs to access the data from RAM.
The higher the value  the more clock cycles are required for the processing.
In your case, the setting 1 was too fast.
 
Back
Top