My hard drive crashed a while back ago. I got a new one, it's IDE (old one was SATA). I've been using it for about a week or so now. They were both 160 Gigs. Today I get my 500 Gig one in, it's SATA. I wanted to use both of them, have my SATA as a master boot drive and my 160 gig as a backup. My computer didn't see it that way. It wouldn't boot from the SATA, even after I took out the 160 gig IDE it would BSoD. I finally got it all back to running. But not the way I want it, although it is running.
I've had to lower my RAM from 800 to 662 because Windows would BSoD me when I tried to install GPU drivers. So I'm undetermined if it is the GPU, because right now it is running smooth, atm. Or if it is my RAM going bad on me.
So, I have 2 questions, anyway to keep my IDE HD and boot from my SATA? Also, any idea why I can't kick my RAM up to 800? I've ran it on 800 for at least 6 months now no problems, this is the first problems I've had with it.
Thanks in advance.
- Forums
- Cross Site
- Computer Hardware & Troubleshooting
- Need some help with my computer.
Need some help with my computer.Follow
There are ways to edit your MBR however it's easier just to backup your information and then format both drives and go from there.
Huh? Are you talking about virtual memory or physical? Lowering memory wouldn't fix issues unless you have a module going bad and you simply just aren't addressing to it anymore.
Run a MEMTEST and see what you have after that.
MEMTEST86
If your MEMTEST comes back clean after do a full check then you can rule that out.
Booting to your SATA Drive instead of IDE can be done in a complicated way to save your data however whenever you swap your primary drive I find it easier just to again backup and reinstall. When you do the Windows install just make sure you choose the correct drive for your primary(SATA) then just leave the IDE as free space until you can get into Windows and format it as NTFS.
800 is a very odd duck number considering RAM modules at the lowest come in 128 which means your either running mixed memory or you have a shared device taking system memory. For the 600 - 1024 range you have (640, 768, 896, 1024), would it be a correct assumption that your GPU is integrated and using system memory?
The memory being mixed may seem like something strange however if you use two different pairs or singles of memory it can cause issues because each memory module has their own st of timings which can later down the road cause issues. This is why you see so much memory being sold in pairs or pair sets because they should be very very close to identical (I didn't say exact because even pair memory can be slightly different)
Edited, Feb 29th 2008 5:06am by xXBijiontXx
Quote:
I've had to lower my RAM from 800 to 662 because Windows would BSoD me when I tried to install GPU drivers.
Huh? Are you talking about virtual memory or physical? Lowering memory wouldn't fix issues unless you have a module going bad and you simply just aren't addressing to it anymore.
Run a MEMTEST and see what you have after that.
MEMTEST86
If your MEMTEST comes back clean after do a full check then you can rule that out.
Booting to your SATA Drive instead of IDE can be done in a complicated way to save your data however whenever you swap your primary drive I find it easier just to again backup and reinstall. When you do the Windows install just make sure you choose the correct drive for your primary(SATA) then just leave the IDE as free space until you can get into Windows and format it as NTFS.
800 is a very odd duck number considering RAM modules at the lowest come in 128 which means your either running mixed memory or you have a shared device taking system memory. For the 600 - 1024 range you have (640, 768, 896, 1024), would it be a correct assumption that your GPU is integrated and using system memory?
The memory being mixed may seem like something strange however if you use two different pairs or singles of memory it can cause issues because each memory module has their own st of timings which can later down the road cause issues. This is why you see so much memory being sold in pairs or pair sets because they should be very very close to identical (I didn't say exact because even pair memory can be slightly different)
Edited, Feb 29th 2008 5:06am by xXBijiontXx
I'll try memtest, I didn't even think of that. Been fighting with my computer for about 8 hours or so, so it never crossed my mind.
As far as the ram, it is Kingston PC 6400 Hyper X 2gig (2 sticks of 1 gig ram) duel channel. I had to kick it down from 800 MHz to 662 MHz, it just keeps restarting when I kick it up to 800 MHz. The GPU is a eVga nVdia 8600 GT PCI-E. It's all about 6 months old, well that's when I ordered it.
I'll try memtest and see what happens. It may very well be my ram. If so I'll replace it and hope it isn't my GPU, because then I'll have to replace it as well.
I got it to boot from SATA once, but all it did was do a constant restart of the computer. I may try it again. But for now it seem to be working fine as long as I keep my ram at 662 MHz.
More help is still appreciated.
Thanks again.
Update: I ran MemTest with my memory set at 800 MHz and it had over 56,000 errors on test 5, it was still going so I just restarted and ran it on 662 MHz. I got no errors on 662 MHz at test 8, I stopped it there.
So I'm guessing it is my memory, it runs fine at 662MHz, does this mean that it is bad at 800MHz or all the way around? Not sure how that effects it.
Edited, Feb 29th 2008 6:21am by DecendentMonk
As far as the ram, it is Kingston PC 6400 Hyper X 2gig (2 sticks of 1 gig ram) duel channel. I had to kick it down from 800 MHz to 662 MHz, it just keeps restarting when I kick it up to 800 MHz. The GPU is a eVga nVdia 8600 GT PCI-E. It's all about 6 months old, well that's when I ordered it.
I'll try memtest and see what happens. It may very well be my ram. If so I'll replace it and hope it isn't my GPU, because then I'll have to replace it as well.
I got it to boot from SATA once, but all it did was do a constant restart of the computer. I may try it again. But for now it seem to be working fine as long as I keep my ram at 662 MHz.
More help is still appreciated.
Thanks again.
Update: I ran MemTest with my memory set at 800 MHz and it had over 56,000 errors on test 5, it was still going so I just restarted and ran it on 662 MHz. I got no errors on 662 MHz at test 8, I stopped it there.
So I'm guessing it is my memory, it runs fine at 662MHz, does this mean that it is bad at 800MHz or all the way around? Not sure how that effects it.
Edited, Feb 29th 2008 6:21am by DecendentMonk
800 is a very odd duck number considering RAM modules at the lowest come in 128 which means your either running mixed memory or you have a shared device taking system memory. For the 600 - 1024 range you have (640, 768, 896, 1024), would it be a correct assumption that your GPU is integrated and using system memory?
He's talking about speed, not quantity. Thanks for trying to help.
As far as the ram, it is Kingston PC 6400 Hyper X 2gig (2 sticks of 1 gig ram) duel channel. I had to kick it down from 800 MHz to 662 MHz, it just keeps restarting when I kick it up to 800 MHz. The GPU is a eVga nVdia 8600 GT PCI-E. It's all about 6 months old, well that's when I ordered it.
This is most likely caused by two things. One, having your PCI-E bus speed linked to your FSB which causes your video card to crash, and two, manipulating RAM speed by changing your FSB instead of adjusting the ram/FSB multiplier. If you really want to run the ram at 800 (it'll make virtually no noticeable difference), post your BIOS version here. Regardless of the speed you run the ram at, you should unlink the PCI-E bus from the FSB. If I had to make a wild guess, I'd say that you're probably trying to do some sort of jury rigged software based over clock that's not giving you much benefit, and is very likely putting your system at risk of breaking stuff.
If you want to overclock, post about it, along with your BIOS and hardware info, and I can walk you though it from BIOS setup and how to test it for stability and risk
On the Sata Drive vs the IDE drive, Windows doesn't really care much. The original replier is right (sorry, I'm editing, I can't see the screename) in that just reformatting is by far the easiest thing to do. I could walk you through using GParted to change it, but you don't really want two drives with XP System filesystems on them anyway.
Good luck.
Edited, Feb 29th 2008 6:30pm by Smasharoo
Disclaimer:
To make a long story short, I don't take any responsibility for anything I post here. It's not news, it's not truth, it's not serious. It's parody. It's satire. It's bitter. It's angsty. Your mother's a *****. You like to jack off dogs. That's right, you heard me. You like to grab that dog by the bone and rub it like a ski pole. Your dad? Gay. Your priest? Straight. **** off and let me post. It's not true, it's all in good fun. Now go away.
To make a long story short, I don't take any responsibility for anything I post here. It's not news, it's not truth, it's not serious. It's parody. It's satire. It's bitter. It's angsty. Your mother's a *****. You like to jack off dogs. That's right, you heard me. You like to grab that dog by the bone and rub it like a ski pole. Your dad? Gay. Your priest? Straight. **** off and let me post. It's not true, it's all in good fun. Now go away.
Update: I ran MemTest with my memory set at 800 MHz and it had over 56,000 errors on test 5, it was still going so I just restarted and ran it on 662 MHz. I got no errors on 662 MHz at test 8, I stopped it there.
So I'm guessing it is my memory, it runs fine at 662MHz, does this mean that it is bad at 800MHz or all the way around? Not sure how that effects it.
Again, this is probably because your FSB is set too high.
Disclaimer:
To make a long story short, I don't take any responsibility for anything I post here. It's not news, it's not truth, it's not serious. It's parody. It's satire. It's bitter. It's angsty. Your mother's a *****. You like to jack off dogs. That's right, you heard me. You like to grab that dog by the bone and rub it like a ski pole. Your dad? Gay. Your priest? Straight. **** off and let me post. It's not true, it's all in good fun. Now go away.
To make a long story short, I don't take any responsibility for anything I post here. It's not news, it's not truth, it's not serious. It's parody. It's satire. It's bitter. It's angsty. Your mother's a *****. You like to jack off dogs. That's right, you heard me. You like to grab that dog by the bone and rub it like a ski pole. Your dad? Gay. Your priest? Straight. **** off and let me post. It's not true, it's all in good fun. Now go away.
My bios are Phoenix Technologies, LTD. Version 6.00PG, date 07/25/07.
PCI-E Link Width/max supported x16
CPU AMD 64x2 5600 Windsor.
Core speed 2813 or so, it fluctuates.
Multiplier x14
Bus Speed 200
HT Link 1004 it fluctuates as well.
Motherboard, DFI INF NF 570 (SLi) M2/G
FSB/Dram CPU/9
I have everything set to optimal load outs, the only thing I have ever changed is the ram speed to 800. Ran it that way for at least 7 months now.
I only changed it to that because it wouldn't pick up the ram is 800, and I read somewhere that I needed to change it manually.
How do I go about unlinking my PCI-e and my FSB?
It's running pretty good on my IDE drive, I just wanted it all to run off my SATA drive for faster load times, but I decided just to use it for games for the time being. When I put XP on it before and took out the IDE it just kept restarting. I don't want a repeat and have to wipe everything and it still not work. I only have one IDE slot (minus the A drive IDE) on my computer so I have to use it for my DVD RW and HD.
The one time I left my IDE HD alone, just erased the partion on it, and was going to install XP on my SATA, it made me make a partion for my IDE drive. The install said windows needed it on there. I don't understand why, I had my drivers from the floppy on my SATA drive to read it as a disk and allow stuff to be installed. Anyway to get around that? I may just put it on my SATA drive sooner or later and I don't want to run into this again. Sorry for the questions about this, last time it was just a SATA drive and no IDE. It was a little easier as it was just one drive.
Thank you again for the help, it is greatly appreciated.
Update: I just went and changed my ram back to 800, I upped the voltage output on the ram to 1.9v and changed to 800mhz. It seems to be working for the time being. It at least let me get into windows and posting on here. I can't remember if I changed that or not when I upped it 7 months ago, I'm guessing yes, because it needs more voltage. If this is incorrect please let me know. I don't know.
Thanks again, rate ups for the help so far.
Edited, Feb 29th 2008 6:00pm by DecendentMonk
PCI-E Link Width/max supported x16
CPU AMD 64x2 5600 Windsor.
Core speed 2813 or so, it fluctuates.
Multiplier x14
Bus Speed 200
HT Link 1004 it fluctuates as well.
Motherboard, DFI INF NF 570 (SLi) M2/G
FSB/Dram CPU/9
I have everything set to optimal load outs, the only thing I have ever changed is the ram speed to 800. Ran it that way for at least 7 months now.
I only changed it to that because it wouldn't pick up the ram is 800, and I read somewhere that I needed to change it manually.
How do I go about unlinking my PCI-e and my FSB?
It's running pretty good on my IDE drive, I just wanted it all to run off my SATA drive for faster load times, but I decided just to use it for games for the time being. When I put XP on it before and took out the IDE it just kept restarting. I don't want a repeat and have to wipe everything and it still not work. I only have one IDE slot (minus the A drive IDE) on my computer so I have to use it for my DVD RW and HD.
The one time I left my IDE HD alone, just erased the partion on it, and was going to install XP on my SATA, it made me make a partion for my IDE drive. The install said windows needed it on there. I don't understand why, I had my drivers from the floppy on my SATA drive to read it as a disk and allow stuff to be installed. Anyway to get around that? I may just put it on my SATA drive sooner or later and I don't want to run into this again. Sorry for the questions about this, last time it was just a SATA drive and no IDE. It was a little easier as it was just one drive.
Thank you again for the help, it is greatly appreciated.
Update: I just went and changed my ram back to 800, I upped the voltage output on the ram to 1.9v and changed to 800mhz. It seems to be working for the time being. It at least let me get into windows and posting on here. I can't remember if I changed that or not when I upped it 7 months ago, I'm guessing yes, because it needs more voltage. If this is incorrect please let me know. I don't know.
Thanks again, rate ups for the help so far.
Edited, Feb 29th 2008 6:00pm by DecendentMonk
Ok, your board is known to be a pain in the ***, and would benefit a great deal by you flashing the BIOS to the latest revision.
http://www.dfi.com.tw/Support/Download/bios_download_us.jsp?PRODUCT_ID=5115&CATEGORY_TYPE=INFINITY&INDEX_TYPE=null&STATUS_FLAG=A&SITE=NA
Voltage increases RAM stability, but makes it hotter. Your manufacturer specs are actually 1.95, so if it's stable at 1.9, that's fine, if not running it at 2.0 would be fine too.
I'm downloading the manual for your MB to see what the BIOS looks like, I'll get back to you.
http://www.dfi.com.tw/Support/Download/bios_download_us.jsp?PRODUCT_ID=5115&CATEGORY_TYPE=INFINITY&INDEX_TYPE=null&STATUS_FLAG=A&SITE=NA
Voltage increases RAM stability, but makes it hotter. Your manufacturer specs are actually 1.95, so if it's stable at 1.9, that's fine, if not running it at 2.0 would be fine too.
I'm downloading the manual for your MB to see what the BIOS looks like, I'll get back to you.
Disclaimer:
To make a long story short, I don't take any responsibility for anything I post here. It's not news, it's not truth, it's not serious. It's parody. It's satire. It's bitter. It's angsty. Your mother's a *****. You like to jack off dogs. That's right, you heard me. You like to grab that dog by the bone and rub it like a ski pole. Your dad? Gay. Your priest? Straight. **** off and let me post. It's not true, it's all in good fun. Now go away.
To make a long story short, I don't take any responsibility for anything I post here. It's not news, it's not truth, it's not serious. It's parody. It's satire. It's bitter. It's angsty. Your mother's a *****. You like to jack off dogs. That's right, you heard me. You like to grab that dog by the bone and rub it like a ski pole. Your dad? Gay. Your priest? Straight. **** off and let me post. It's not true, it's all in good fun. Now go away.
Thank you for the help. I downloaded the latest bios. Took sometime to get them in, in DOS mod it kept rejecting them so I had to do it from Windows, but it finally took them.
Was installing updates and computer restarted and wouldn't read my IDE drive. I had to take the case side off and mess with the IDE plug in and the power plug to get it back to working. Did this twice to me. Not sure if it was from the memory or what yet.
Again thank you for the help, I think it's almost running stable, as long as I don't get BSoD again I'll be happy. Maybe time to order some new parts and build my computer over. Heard the AMD quad-cores were pretty nice. Not sure how expensive they are, but may have to look into them.
Thanks again.
Update: I can tell exactly when my computer is going to BSoD now, My HD light goes solid red and just stays that way. Then I get the dreaded BSoD, followed by me restarting my computer and my HD not being picked up. It kind of hangs at detecting IDE drives. I have to take the side of my case off and push the IDE and power cables in. Then it detects it no problem.
So far this seems to be the only issue left. I hope anyways.
Edited, Mar 1st 2008 6:56pm by DecendentMonk
Was installing updates and computer restarted and wouldn't read my IDE drive. I had to take the case side off and mess with the IDE plug in and the power plug to get it back to working. Did this twice to me. Not sure if it was from the memory or what yet.
Again thank you for the help, I think it's almost running stable, as long as I don't get BSoD again I'll be happy. Maybe time to order some new parts and build my computer over. Heard the AMD quad-cores were pretty nice. Not sure how expensive they are, but may have to look into them.
Thanks again.
Update: I can tell exactly when my computer is going to BSoD now, My HD light goes solid red and just stays that way. Then I get the dreaded BSoD, followed by me restarting my computer and my HD not being picked up. It kind of hangs at detecting IDE drives. I have to take the side of my case off and push the IDE and power cables in. Then it detects it no problem.
So far this seems to be the only issue left. I hope anyways.
Edited, Mar 1st 2008 6:56pm by DecendentMonk
Quote:
He's talking about speed, not quantity. Thanks for trying to help.
I realize that after his post after mine stating speed. You can edit the addressing values for both physical and virtual memory using 3rd party. His original post stated in no fashion that this was 800Mhz which would have made much less confusion.
Quote:
Update: I can tell exactly when my computer is going to BSoD now, My HD light goes solid red and just stays that way. Then I get the dreaded BSoD, followed by me restarting my computer and my HD not being picked up. It kind of hangs at detecting IDE drives. I have to take the side of my case off and push the IDE and power cables in. Then it detects it no problem.
If you are having to do this several times or every time this could be a bent pin or a broken pin on either the motherboard or hard drive itself. Only way to to solve that is to take your drive and cable out and inspect them carefully for any pin's which may be damaged.
It would be easier to just move to your SATA drive you have and removing the IDE drive until you have windows setup and configured, then just setup the IDE drive as a slave if you need information off it. Remember before doing this to take off any profile security you may have turned on as this will prevent you from getting to your files 9/10 times without using other means such as linux to transport the files off (Linux doesn't care about windows permissions)
Make sure after doing your update to your BIOS to check your memory timings as well. Most memory will come with ideal timing and if you make them to tight they will Bsod as well.
Recent Visitors: 18
All times are in CST
Anonymous Guests (18)
- Forums
- Cross Site
- Computer Hardware & Troubleshooting
- Need some help with my computer.
© 2024 Fanbyte LLC