buy another cable just incase.
Here is what happenned. you did not install sata2 driver during installation w/ sata2 set to sata mode (in bios).
this time, buy another cable.
set sata2 to sata mode in bios
install sata2 drivers from floppy during winxp installation.
when in windows, install agp driver from asrock cd, reboot. install lan, reboot, install audio driver reboot.
go to windows update and let window update.
designit, what you are saying makes sense, except many of us have tried different SATA cables. Perhaps the SATA connectors on the board are defective.
professor, when your computer was on the desk, was it close to any items such as a cable/dsl modem, router, cordless phone, or UPS?
professor, when your computer was on the desk, was it close to any items such as a cable/dsl modem, router, cordless phone, or UPS?
@crabbyman: Oops, missed that part about an entirely new board (<-blind), if it IS a different one, then definately reinstall everything. Also, it depends on the situation what to do. If I got a different board, I would have needed a new Video card which means an extra $400 ontop of the wasted $100 on the POS. I could have gotten an SATA PCI controller, but I don't know how reliable they are, even then they are $40; a new IDE HDD costs $67, I decided to just go with a new drive. However, it isn't so simple with the rest of you with your Raptors, 250Gb, Raid, SATA2 drives. You guys probably use way more space and a new drive would be both slow and small and way too expensive (more than $100); I got by on 40Gb for about 4-5 years (only had to start deleting stuff at year 3 or 4.
Don't know if moving the entire system to the floor or on a table would work for me, may just be lucky? Mines is in a cabinet (built for towers and was $50...), and I hate hearing the fans at ear level. My old system never had a problem where the system is now. Also, there really isn't any place to put the tower since the table I bought is small(as I wanted) and has space for a monitor. IDE still flawless after taking out SATA, so I don't know if interference somehow specifically targets the one part of the Southbridge controlling the SATA, but nothing else (conspiracy?). Every other part of the POS works fine, except Ram, but that's the onboard memory controller of the A64 probably.
~My POS mobo came with a red cable which took Hercules to originally pull it off the mobo (slides right off now or maybe I should just stop rocking it?). Also, person I sold my SATA to using the cable I used, no problem what so ever.
Don't know if moving the entire system to the floor or on a table would work for me, may just be lucky? Mines is in a cabinet (built for towers and was $50...), and I hate hearing the fans at ear level. My old system never had a problem where the system is now. Also, there really isn't any place to put the tower since the table I bought is small(as I wanted) and has space for a monitor. IDE still flawless after taking out SATA, so I don't know if interference somehow specifically targets the one part of the Southbridge controlling the SATA, but nothing else (conspiracy?). Every other part of the POS works fine, except Ram, but that's the onboard memory controller of the A64 probably.
~My POS mobo came with a red cable which took Hercules to originally pull it off the mobo (slides right off now or maybe I should just stop rocking it?). Also, person I sold my SATA to using the cable I used, no problem what so ever.
I am thinking, when you installed winxp in first place, the cable was loose and win did not install properly.
did you install sata2 drivers from floppy right before installing winxp?
sata2 need to be in sata mode (in bios), during winxp installation.
just incase. buy another cable and a fresh winxp install. just make sure the jmicron sata2 drivers are coppied into floppy and no problem as far as sata2 drivers is concerned.
The thing is that for me, the problems have nothing to do with the right windows drivers because sometimes the board woudn't even see the drive in the BIOS!
I have installed windows 4 times now. No freezes this time so far. Note that the very first install was stable for 1+ month until I RMA'd the mobo and put in the replacement.
Yes, on installs 2-4. First install was in IDE mode.
I bought 2 new SATA cables and neither one fixed the problem.
look inside the sata cable w/ a magnifier and if you see any pin not same plane as others, your cable is bad. the pins in sata cable are spring like and sometimes one or 2 pins flatten. this is a flaw w/ sata system. IDE cables plug into pins w/ good contact. sata cable are bad in this regard. the cable may seems snug, but if you look inside the plug, chances are a pin is flat and contact is lost. best thing to do is buy another cable and try to be easy w/ it.
It is a possibility, but extremely unlikely for these reasons:
1) My first cable worked fine for a year and a half in my old motherboard (DFI lanparty UT). It didn't with the the asrock.
2) I switched to a different cable. It connects very tightly. It still didn't work properly in SATA mode.
3) When my drive magically dissapeared, it came back again after cycling the power. Sometimes once would be enough, sometimes more. I didn't move/touch/jiggle the wire or touch the connection.
4) Now that I've set the drive to IDE mode in the BIOS, I havn't had a single problem. It's been about 5 hours, so I can't really say if this cured my problems until a few more days though.
Who knows, it could just be a huge coincidence my first cable (which was perfectly fine before) just died the moment I got my new motherboard, that my other cable (the new one that came with the asrock MB) was also defective and that the new cable just happened to work once I set the SATA2 mode to IDE in the bios. If I get any other lockups, I'll go get a new cable. But it's also possible that the SATA connectors on the MB itself are crappy.
1) My first cable worked fine for a year and a half in my old motherboard (DFI lanparty UT). It didn't with the the asrock.
2) I switched to a different cable. It connects very tightly. It still didn't work properly in SATA mode.
3) When my drive magically dissapeared, it came back again after cycling the power. Sometimes once would be enough, sometimes more. I didn't move/touch/jiggle the wire or touch the connection.
4) Now that I've set the drive to IDE mode in the BIOS, I havn't had a single problem. It's been about 5 hours, so I can't really say if this cured my problems until a few more days though.
Who knows, it could just be a huge coincidence my first cable (which was perfectly fine before) just died the moment I got my new motherboard, that my other cable (the new one that came with the asrock MB) was also defective and that the new cable just happened to work once I set the SATA2 mode to IDE in the bios. If I get any other lockups, I'll go get a new cable. But it's also possible that the SATA connectors on the MB itself are crappy.
Wireless router & cable modem were a few feet away (they're actually closer now, but not on the same level), the only thing really close was the LCD monitor and my optical mouse...
not necessarily. if i change the FSB at *all* on my ECS 848P the Silicon Image SATA RAID chip fails to see the SATA1 drive thats on it... so it isn't always the cable... although it's obviously worth checking, as well as trying the other SATA plugs on the motherboard!
We are not talking about overclocking here or silicon image.
When system is not overclocked and sata drive is not recognized, 99% of times is either bad cable, bad pin contact, or bad bios flash. Or just plain bad HDD.
Rule of thumb governs here. Check the cable, the power, and bios settings.
most of the time people forget to set the bios in sata mode during winxp installation, or did not install sataII drivers @ winxp installation.
Check this guide, link below, and do a fresh winxp install on your sataII
http://www.ocforums.com/showthread.php?t=446236
When system is not overclocked and sata drive is not recognized, 99% of times is either bad cable, bad pin contact, or bad bios flash. Or just plain bad HDD.
Rule of thumb governs here. Check the cable, the power, and bios settings.
most of the time people forget to set the bios in sata mode during winxp installation, or did not install sataII drivers @ winxp installation.
Check this guide, link below, and do a fresh winxp install on your sataII
http://www.ocforums.com/showthread.php?t=446236
Good thread designit. No new info there, but good for people who haven't learned the steps the hard way.
Bad news at my end: the freezing began again today on my new installation after 5 days of stability
. First freeze after 30 min. memtest run and 30 min. Windows usage while visiting macromedia.com (I've read about flash related problems before, but not on stock boards). Second freeze after reboot and 5 min. of Windows usage. Third freeze after reboot and just reaching Windows desktop.
Then I shutdown, disconnected the power, and removed the SATA cable: the snap-together casing at one end looked a bit open, and one pin looked slightly out of place. I hope that's what was causing the problem. I have now replaced with a new SATA cable without any obvious defects and will see if I can get past Imp's one week failure rate.
Bad news at my end: the freezing began again today on my new installation after 5 days of stability
. First freeze after 30 min. memtest run and 30 min. Windows usage while visiting macromedia.com (I've read about flash related problems before, but not on stock boards). Second freeze after reboot and 5 min. of Windows usage. Third freeze after reboot and just reaching Windows desktop.Then I shutdown, disconnected the power, and removed the SATA cable: the snap-together casing at one end looked a bit open, and one pin looked slightly out of place. I hope that's what was causing the problem. I have now replaced with a new SATA cable without any obvious defects and will see if I can get past Imp's one week failure rate.
Good. Hope the cable was the problem. I suggest a fresh hdd format and winxp install. this way you will not have any freeze caused by corrupted OS.
Leme know if freezing gone. Hope so. But just incase its back, I am afraid the problem may be something else beside the mobo. It could be your cpu about to give you fairwell. what was the highest temp the cpu ran into?
Leme know if freezing gone. Hope so. But just incase its back, I am afraid the problem may be something else beside the mobo. It could be your cpu about to give you fairwell. what was the highest temp the cpu ran into?
As much as I'd like to think it was just the cable, I don't really see how a cable would work for days at a time, and then crap out. And when it craps out, it works again after a reset or turning the power off for a while or just reseting enough times(30+). On SATA(addition: I've tried BOTH channels with #2 dying faster than #1), it had trouble detecting the drive during boot; when it did detect it, it couldn't find the OS. I've run windows system file checks a few times with no errors. XP ran fine for days before even hiccupping upon a supposed "fix". Also, my HDD never dropped a single UDMA step even at its worst. When I moved to the SATAII channel, it never had a problem finding the drive, but after working for days, it would just start erroring. The weird thing is that whenever I moved anything but the SATA connector, it worked again for near a week (remember the IDE1 CD to IDE2 "fix"?).
In retrospect, I definately should have tried switching out cables, but the reason I never did was due to the fact that this board shipped with an inherent "cold boot problem" (clearly a design defect of the mobo<please switch the b with f>). The rest of the issues I got just seemed like an amplification of this defect to me. Also, as many have stated, they did switch out cables. There seem to be a few too many people with the exact problem with only the board in common. Also, we can't all have defective CPUs. By the way, I broke the 1 week barrier on Monday with this CPU and IDE (SATA still rocking in other system). Lots of people who DO get the thing to run properly still get the cold boot problem, but it runs fine the other 90%(yep, pulled that out of you know what) of the time. It's possible the channels on the board are from a bad batch, but since we have different revisions, they may just suck.
Extra thought: When I had two HDDs installed, BIOS showed a fluctuation of 0.07 volts on the 12v rail. Was it the PSU? Doubt it, it was still within the 5% variance, and new HDD runs fine.
100 ~So I remember what I was *itching about~
In retrospect, I definately should have tried switching out cables, but the reason I never did was due to the fact that this board shipped with an inherent "cold boot problem" (clearly a design defect of the mobo<please switch the b with f>). The rest of the issues I got just seemed like an amplification of this defect to me. Also, as many have stated, they did switch out cables. There seem to be a few too many people with the exact problem with only the board in common. Also, we can't all have defective CPUs. By the way, I broke the 1 week barrier on Monday with this CPU and IDE (SATA still rocking in other system). Lots of people who DO get the thing to run properly still get the cold boot problem, but it runs fine the other 90%(yep, pulled that out of you know what) of the time. It's possible the channels on the board are from a bad batch, but since we have different revisions, they may just suck.
Extra thought: When I had two HDDs installed, BIOS showed a fluctuation of 0.07 volts on the 12v rail. Was it the PSU? Doubt it, it was still within the 5% variance, and new HDD runs fine.
100 ~So I remember what I was *itching about~
Don't be so optimistic designit! :laugh: Several weeks ago, I logged CPU & GPU temps and voltages during the freezing, and saw nothing out of the ordinary for the CPU. The graphics card showed some odd spkes (+/-) for a millisecond once in a while that did not coincide with freezing. I think I'll wait for another freeze before I decide to go for fresh install #5.
Try this bios (04xx) and you will never have cold boot problem.
I dont understand. If you used the cable on SATAII(red plug on mobo) and installed winxp in sata mode(w/ sata2 drivers off of floppy), and you moved the cable to sata plug(black suckets)??????
No wonder you have problems.
You either install winxp in IDE mode and can use both sata(black plugs) and sataII(red plug), bios set to IDE.... or install winxp in sata mode and must only use sataII(red plug)
and sataII set to sata mode in bios. You can not switch between ide and sata mode, if you installed winxp in sata mode (drivers off of floppy).
Am I making sense here?
If you mix matche back and forth, your winxp definitely is corrupted and you need to reformat the hdd and fresh install- bottom line.
You do what you did here to any mobo and you will never get any mobo stable.
Decide what mode you want to use the hdd-sataII(red plug), raid(sata black plugs), or just plain ide mode. And then install winxp accordingly.
link below is a german bios that works great. you need winrar to unzip it.
http://www.pc-treiber.net/download-file-255.html
I dont understand. If you used the cable on SATAII(red plug on mobo) and installed winxp in sata mode(w/ sata2 drivers off of floppy), and you moved the cable to sata plug(black suckets)??????
No wonder you have problems.
You either install winxp in IDE mode and can use both sata(black plugs) and sataII(red plug), bios set to IDE.... or install winxp in sata mode and must only use sataII(red plug)
and sataII set to sata mode in bios. You can not switch between ide and sata mode, if you installed winxp in sata mode (drivers off of floppy).
Am I making sense here?
If you mix matche back and forth, your winxp definitely is corrupted and you need to reformat the hdd and fresh install- bottom line.
You do what you did here to any mobo and you will never get any mobo stable.
Decide what mode you want to use the hdd-sataII(red plug), raid(sata black plugs), or just plain ide mode. And then install winxp accordingly.
link below is a german bios that works great. you need winrar to unzip it.
http://www.pc-treiber.net/download-file-255.html
I don't have a SATA 2 drive. I have a Seagate 7200.7 SATA1 drive. When I installed winXP, I had my drived plugged into the black SATA port on the motherboard. I tried different cables, and all the SATA connectors and still got the random freezes where it looks like the MB suddenly does not see the drive. Just for fun, I tried plugging in my drive into the SATA 2 plug (the red one) with this plug set to SATA mode. Obviously this didn't work. However, now I have my drive plugged into this very same connector, but have set the mode to IDE in the BIOS. Since this, I have not had a single problem (it's now been ~2 days). My computers has gone into hibernate, and I've turned it off and rebooted. No problems yet (the problems usually were worse if I rebooted, or left the computer off for a while).
I have not jiggled the cable or anything, all I've done was switch the mode to IDE in the BIOS. I still think that the problem is with the motherboard and not the cables or cpu, or anything else. Two weeks ago, I had the same exact components as I have now working perfectly fine with my DFI lanparty UT motherboard. I have a good quality power supply (Seasonic 400W super tornado). All that I did was change MB's and cpu. I've tested the cpu using super pi and sisoft for hours, overclocked at 2500 MHz (from 2000MHz), and it ran fine without any problems! The lockups that I have experienced have even happened when cool 'n quiet was enabled at which the cpu was running at 1000Mhz, and in general havn't overclocked this system and still got the lockups, so I'm sure that it's not cpu related. This leaves me with one single thing that has changed in my system that could be responsible for the problems: the motherboard. You could argue that it's driver related, but the fact that sometimes the BIOS doesn't even see the cpu rules out this possibility.
Again, I've tried different cables, and this isn't the issue.
Anyway, by process of elimination, and by the fact that all is working perfectly now and all I've done was set the drive to IDE mode in the BIOS makes me believe that the problem is indeed related to the motherboard.
I could be wrong, but at this point I don't really care because my system is now stable. I'm tired of messing around with it!
I have not jiggled the cable or anything, all I've done was switch the mode to IDE in the BIOS. I still think that the problem is with the motherboard and not the cables or cpu, or anything else. Two weeks ago, I had the same exact components as I have now working perfectly fine with my DFI lanparty UT motherboard. I have a good quality power supply (Seasonic 400W super tornado). All that I did was change MB's and cpu. I've tested the cpu using super pi and sisoft for hours, overclocked at 2500 MHz (from 2000MHz), and it ran fine without any problems! The lockups that I have experienced have even happened when cool 'n quiet was enabled at which the cpu was running at 1000Mhz, and in general havn't overclocked this system and still got the lockups, so I'm sure that it's not cpu related. This leaves me with one single thing that has changed in my system that could be responsible for the problems: the motherboard. You could argue that it's driver related, but the fact that sometimes the BIOS doesn't even see the cpu rules out this possibility.
Again, I've tried different cables, and this isn't the issue.
Anyway, by process of elimination, and by the fact that all is working perfectly now and all I've done was set the drive to IDE mode in the BIOS makes me believe that the problem is indeed related to the motherboard.
I could be wrong, but at this point I don't really care because my system is now stable. I'm tired of messing around with it!
I got this board just under a week ago. So like most just plugged up old IDE HD and went to see if it booted no go BSOD. So needing a new HD anyway and knowing I had to do fresh install went out and got WD 2500k SATA2 HD. Installed on SATA 1 im having same problems as rest of you. Along with some problems with my USB as well causing BSOD. Ive honestly never got so many BSOD in my life and I know for a fact its not Windows. So in all fairness im annoyed. Ok I think it has to do with the USB controller becasue my wireless starts going sometimes it BSOD on me and as well as other errors totally suggesting hardware problems well its not my hardware as it worked flawlessly on my last box and the new HD is solid as well is the install of windows. I got this board fairly cheap and would have never bought but I have a perfectly good x800 that has not got its fair use. Looking into reviews seems like the board was solid. I looked forward to giving ASrock a try seemed like the had a good thing going. Well im upset on the support and known problems not being resolved ASAP. I know they are getting flooded with requests and might take me more troubleshooting time to get it resolved. Looking through the forums I see those getting it to work are getting it to work through sacrfice. which is not kewl. Any ideas guys on my setup and what I can do?
939 dual X2 4200
WD 2500K SATA
Two Maxtor IDE
Plextor 716
x800
500w PSU
1 gig ddr 400
939 dual X2 4200
WD 2500K SATA
Two Maxtor IDE
Plextor 716
x800
500w PSU
1 gig ddr 400
I got this board just under a week ago. So like most just plugged up old IDE HD and went to see if it booted no go BSOD. So needing a new HD anyway and knowing I had to do fresh install went out and got WD 2500k SATA2 HD. Installed on SATA 1 im having same problems as rest of you. Along with some problems with my USB as well causing BSOD. Ive honestly never got so many BSOD in my life and I know for a fact its not Windows. So in all fairness im annoyed. Ok I think it has to do with the USB controller becasue my wireless starts going sometimes it BSOD on me and as well as other errors totally suggesting hardware problems well its not my hardware as it worked flawlessly on my last box and the new HD is solid as well is the install of windows. I got this board fairly cheap and would have never bought but I have a perfectly good x800 that has not got its fair use. Looking into reviews seems like the board was solid. I looked forward to giving ASrock a try seemed like the had a good thing going. Well im upset on the support and known problems not being resolved ASAP. I know they are getting flooded with requests and might take me more troubleshooting time to get it resolved. Looking through the forums I see those getting it to work are getting it to work through sacrfice. which is not kewl. Any ideas guys on my setup and what I can do?
939 dual X2 4200
WD 2500K SATA
Two Maxtor IDE
Plextor 716
x800
500w PSU
1 gig ddr 400
939 dual X2 4200
WD 2500K SATA
Two Maxtor IDE
Plextor 716
x800
500w PSU
1 gig ddr 400
Obviously your Seagate is sataII if it works in the red plug.
The only problem I see here is not setting the bios correctly and did not install winxp correctly.
Just for the "f" of it read theses 2 links and do as suggested and then come back here complain if no luck. Read post # 490 in the first link.
http://www.ocforums.com/showthread.php?t=411749&page=17&pp=30
http://www.ocforums.com/showthread.php?t=446236
The only problem I see here is not setting the bios correctly and did not install winxp correctly.
Just for the "f" of it read theses 2 links and do as suggested and then come back here complain if no luck. Read post # 490 in the first link.
http://www.ocforums.com/showthread.php?t=411749&page=17&pp=30
http://www.ocforums.com/showthread.php?t=446236
I have still that damn
Machine Check Exception
0x0000009c
grrrrrr! I can't never finish a defrag of C: :-(. My XP SP2 is a fresh install on C: partition, On SATAII (red connector) in SATA mode or IDE mode i can't ever install XP! Now XP is loading well (no cold boot issue) but i am using my Hitachi SATA2 Drive T7K250 250GB in IDE mode on SATA1 connector (bios in NON-RAID mode) and sometimes i get that error :-(. Do you think changing controller and using a PCI one could fix this problem? Maybe a 20? PCI-SATA card? Or do i must buy the promise one SATAII150 TX4 ? I don't want to buy another motherboard...and I don't want to change my drive that is really fast :-( ! I've tried using the SATA2 controller..but if i install correctly XP...then i have that cold boot problem :-(
Machine Check Exception
0x0000009c
grrrrrr! I can't never finish a defrag of C: :-(. My XP SP2 is a fresh install on C: partition, On SATAII (red connector) in SATA mode or IDE mode i can't ever install XP! Now XP is loading well (no cold boot issue) but i am using my Hitachi SATA2 Drive T7K250 250GB in IDE mode on SATA1 connector (bios in NON-RAID mode) and sometimes i get that error :-(. Do you think changing controller and using a PCI one could fix this problem? Maybe a 20? PCI-SATA card? Or do i must buy the promise one SATAII150 TX4 ? I don't want to buy another motherboard...and I don't want to change my drive that is really fast :-( ! I've tried using the SATA2 controller..but if i install correctly XP...then i have that cold boot problem :-(
Hi Designit,
I appreciate your efforts in trying to help me. Regarding my drive, I know for a fact that it is SATAI not SATAII. If you don't believe me, check out this link: http://www.seagate.com/cda/products/dis...es/marketing/detail/0,1081,586,00.html . Obviously my drive doesn't work in the SATA2 plug when I set the bios to SATA mode. However, ever since I've used this plug and put it to IDE mode, I havn't had any problems whatsoever.
I know that the problem is not driver related. This doesn't explain the fact that the BIOS would sometimes lose my drive when it was connected to the SATA1 plugs.... While a loose cable is a possibility then, I've allready explained why I think that it's highly unlikely. From my, and other people's experience, I'm certain that the problem is the SATA on the motherboard...
My system is so stable now that I've decided to clock my cpu (an athlong 64 X2 3800) to 2500MHz. It's running just fine, and I have absolutely no problems anymore.
I appreciate your efforts in trying to help me. Regarding my drive, I know for a fact that it is SATAI not SATAII. If you don't believe me, check out this link: http://www.seagate.com/cda/products/dis...es/marketing/detail/0,1081,586,00.html . Obviously my drive doesn't work in the SATA2 plug when I set the bios to SATA mode. However, ever since I've used this plug and put it to IDE mode, I havn't had any problems whatsoever.
I know that the problem is not driver related. This doesn't explain the fact that the BIOS would sometimes lose my drive when it was connected to the SATA1 plugs.... While a loose cable is a possibility then, I've allready explained why I think that it's highly unlikely. From my, and other people's experience, I'm certain that the problem is the SATA on the motherboard...
My system is so stable now that I've decided to clock my cpu (an athlong 64 X2 3800) to 2500MHz. It's running just fine, and I have absolutely no problems anymore.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 21K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 23K
-
-
Facebook
Twitter