Im trying to upgrade my memory 512MB (2x256DDR333) into 1G for K8VHA
board, AMD 64 Processor and Windows XP Pro O.S. but problem occurs
always rebooting and i cant read the BSOD message.
I thought that the memory is the problem and i try it to another PC,
Pentium 4, L4VXA2 Board, Windows XP Pro O.S. and its working fine.
I try to re-install the O.S. using 1GB (2x512DDR333)but when it comes
to "windows starting" during installation my PC hang, I replace the
memory into 512MB and the installation is working OK.
I already check the board if it is supported upto 1GB and its supported
upto 2GB.
I also swap the hard disk with windows xp pro and memory 1GB that's
working in Pentium 4 into AMD64 but still the windows is not working
properly always rebooting and rebooting.
The BIOS is also upto date. New Board, New Memory and Hard Disk.
What do you think the problem is? any help? thanks and hoping for your
reply.
Confuse
-
Mad_Haggis
- Senior Member
- Posts: 4128
- Joined: Sun Mar 07, 2004 12:00 pm
-
Mad_Haggis
- Senior Member
- Posts: 4128
- Joined: Sun Mar 07, 2004 12:00 pm
it does work..ScottE wrote:Kick your computer a few times. That will fix it.
Post a couplelinks if i can, deleted everything else, yes, i am felling the effects of alcohol, but to my statisfaction...
Speedguide = 10,000,000.0000000W0w
http://www.tbreak.com/reviews/printpage.php?id=255
http://www.ocworkbench.com/2003/gigabyt ... vnxp-1.htm
http://www.overclockersclub.com/?read=7157755
http://www.biostar.com.tw/awards/index.php3
I just want to help... I love Speedguide...
I hear some K8 boards can be pretty picky about brand memory, check with the board manufacturer to see if yours is supported. Is it ECC? Does it need ECC? Just a few things for you to check. Good luck.Tazmaniac wrote:Thanks to all your reply. Hope someone will help me..This forum is to get answer to someone from your problem, not insulting someone!
(I'll go ahead and be the first ass to say it: "This shoulda been in Hardware & Overclocking!")
I think my memory is quiet good because its working in cmos or boot up the only problem is when the windows xp logo load the system reboot using K8VHA AMD64.
As i said its working fine when i use it on another PC with Pentium 4 ECS board.
When I exploring the CMOS on Pentium 4 PC the DDR Timing Setting on DRAM Configuration is on Manual
And I check the DRAM configuration on K8VHA AMD64 the DDR timing has no option "Manual" the option only is 100, 133, 166 and AUTO.
I check this website: http://img.hexus.net/Bio/VIABDRAM.jpg
"However, the K8VHA Pro does make some form of amends in the DRAM settings section. Our initial look at the Athlon 64 and associated chipsets highlighted that manufacturers, initially at least, wanted to focus on stability before performance. DRAM timings were locked out. We managed to run 2 x 256MB of Corsair XMS3500C2 at the latencies shown above. The settings were verified by CPU-Z (v1.19b). An on-die memory controller is a powerful performance tool, but if the user can further lower overall RAM latencies with tight, manual timings, so much the better. You'll see that performance was excellent. The maximum memory clock can be set to either the preferred 200MHz or 166MHz, 133MHz and even 100MHz. The CPU's 'FSB' speeds range from 200MHz to 250MHz, giving a maximum CPU clock of 2500MHz."
Do you this could be the problem? I already contact the motherboard distributor still no answer. As above said DRAM timing are locked out. We managed to run 2 x 256...How to unlocked it? I want to set my DDR Timing.
Thank you.
As i said its working fine when i use it on another PC with Pentium 4 ECS board.
When I exploring the CMOS on Pentium 4 PC the DDR Timing Setting on DRAM Configuration is on Manual
And I check the DRAM configuration on K8VHA AMD64 the DDR timing has no option "Manual" the option only is 100, 133, 166 and AUTO.
I check this website: http://img.hexus.net/Bio/VIABDRAM.jpg
"However, the K8VHA Pro does make some form of amends in the DRAM settings section. Our initial look at the Athlon 64 and associated chipsets highlighted that manufacturers, initially at least, wanted to focus on stability before performance. DRAM timings were locked out. We managed to run 2 x 256MB of Corsair XMS3500C2 at the latencies shown above. The settings were verified by CPU-Z (v1.19b). An on-die memory controller is a powerful performance tool, but if the user can further lower overall RAM latencies with tight, manual timings, so much the better. You'll see that performance was excellent. The maximum memory clock can be set to either the preferred 200MHz or 166MHz, 133MHz and even 100MHz. The CPU's 'FSB' speeds range from 200MHz to 250MHz, giving a maximum CPU clock of 2500MHz."
Do you this could be the problem? I already contact the motherboard distributor still no answer. As above said DRAM timing are locked out. We managed to run 2 x 256...How to unlocked it? I want to set my DDR Timing.
Thank you.
Your system is set to reboot upon encountering an error. If you can get in safe mode and change the advanced option you should be able to see the message.
Right click on MY COMPUTER, left click properties, left click Advanced Tab, left click startup and recovery, Uncheck all the boxes under System Failure and change the Write debugging information to none. then click OK
Reboot and see if you can see what the error is.
Hope this helps.
Pie
Right click on MY COMPUTER, left click properties, left click Advanced Tab, left click startup and recovery, Uncheck all the boxes under System Failure and change the Write debugging information to none. then click OK
Reboot and see if you can see what the error is.
Hope this helps.
Pie
SG Pimp Name : *Treacherous P. Shizzle*
*
The fight for our way of life needs to be fought on our own soil, for our own people and because of our own interests.
*
Hey, If Me & My Buddies Were Making Billions of Dollars I'd Tell Ya What Ya Wanted To Hear Too!
*
The fight for our way of life needs to be fought on our own soil, for our own people and because of our own interests.
*
Hey, If Me & My Buddies Were Making Billions of Dollars I'd Tell Ya What Ya Wanted To Hear Too!