Help! My new system keeps restarting.... :( - HotUKDeals
We use cookie files to improve site functionality and personalisation. By continuing to use HUKD, you accept our cookie and privacy policy.
Get the HUKD app free at Google Play

Search Error

An error occurred when searching, please try again!

Login / Sign UpSubmit

Help! My new system keeps restarting.... :(

ele-font Avatar
7y, 10m agoPosted 7 years, 10 months ago
Hi people can anyone help please. I just built my new system. Everything boots up fine but as soon as it reaches the Windows XP welcome screen, it restarts :(
I also noticed a 'blue' sceen flashes for 1 sec and then immediately restarts.

My spec:
Intel quad core Q9550
Gigabyte X48 motherboard
Corsair 1066Mhz 2GB memory
Sapphire HD3870 1GB graphic card

This system is connected to my old sata harddrive with Windows XP on it.

Any help will be appreciated thanks.
ele-font Avatar
7y, 10m agoPosted 7 years, 10 months ago
Options

All Comments

(44) Jump to unreadPost a comment
Comments/page:
Page:
#1
um, could be faulty ram?



lol
#2
sounds like a HDD error, you could maybe reinstall the OS on it or try another HDD if you have one, altho a lot of users will know more than me, might be th prob
#3
AugQX
sounds like a HDD error, you could maybe reinstall the OS on it or try another HDD if you have one, altho a lot of users will know more than me, might be th prob


Hmm, the hdd was working fine with my old system. Not sure how to reinstall my OS back on. The new system wont let me boot from CD or floppy :x keeps going on to the Hdd and then restarting :(

ChipSticks
um, could be faulty ram?



lol


Possibly lol although its new so dont know
#4
yup if you got probs try reformatting ur system, do a fresh install of xp, if the prob continues after that, then u have a fault somewhere,, u should be ok after reinstall tho, just update ur drivers and make sure everything is updated, if the prob continues try taking one of the ram out and leave 1 in, if u have an old hard drive put that in to elimanate any probs, so u can rule out certain things,
#5
[FONT="Verdana"]Try booting the computer off of a live Linux distribution CD/DVD so that way at least you can narrow down the problem further on your computer - agree with the earlier post that it is probably the OS installation on the SATA hard disk but at least this allows you to test out the rest.

Cheers, Scotty Boy! :thumbsup:[/FONT]
#6
If you have XP instaled from a different system, then you'd be best off re-installin from scratch, different drivers mobo etc.
set BIOS to boot from dvd/cd
#7
I would try pressing F8 just before it boots into Windows and choose Safe Mode. If it still crashes and reboots, it may be something hardware related.
#8
By the sounds of it you've put together a PC but are actually not sure about what your doing.

You can't just swap one hard drive from one PC to another and expect it to boot as all the hardware drivers are different for the new PC.

You need to re-install windows to get it to work !
#9
Mecoconuts
By the sounds of it you've put together a PC but are actually not sure about what your doing.

You can't just swap one hard drive from one PC to another and expect it to boot as all the hardware drivers are different for the new PC.

You need to re-install windows to get it to work !


Your right! as is everyone else who has mentioned about the Hdd. However I can't seem to reinstall windows. The system does not read anything from my bootable cd nor the floppy :?
#10
bargain surfer
If you have XP instaled from a different system, then you'd be best off re-installin from scratch, different drivers mobo etc.
set BIOS to boot from dvd/cd

+1
Should always reinstall windows if you are going to use a diff motherboard with the same drive
:thumbsup::thumbsup::thumbsup::thumbsup:
#11
ele-font
Your right! as is everyone else who has mentioned about the Hdd. However I can't seem to reinstall windows. The system does not read anything from my bootable cd nor the floppy :?


Do you have an original windows xp cd?
If so you have to streamline it and build in the sata drivers to the new cd that you create.
Info here >Clicky
#12
I had a mate with a similar spec who had the same problem recently. It turned out, problem was caused by me kicking his PC every time he tried to turn it on, because I was jealous of him for having a faster system than me.
#13
Guys, I attempted to reinstall windows as you advised. After I format the Hdd using the XP bootable disk, it restarts and keeps restarting :x what do I do now ? im stuck...
I noticed during formatting, the system only read 136GB instead of the total Hdd size 500GB.
#14
ele-font
Guys, I attempted to reinstall windows as you advised. After I format the Hdd using the XP bootable disk, it restarts and keeps restarting :x what do I do now ? im stuck...
I noticed during formatting, the system only read 136GB instead of the total Hdd size 500GB.


Could be a knacked Hard Drive if it won't even complete the format. :?
#15
ele-font;4100638
Guys, I attempted to reinstall windows as you advised. After I format the Hdd using the XP bootable disk, it restarts and keeps restarting :x what do I do now ? im stuck...
I noticed during formatting, the system only read 136GB instead of the total Hdd size 500GB.

What version of XP are you trying to install? I believe LBA support to go past 137GB drives was added in SP1 but may have been SP2.

John
#16
You may need to d/load the manufacturers HDD installation software, this will fully FDisk/format and create a partition for win XP installation.
This is defo why xp is only recognising 136GB of the total space available.
I had the same problem installing a 250GB HDD and once i hadd/loaded and run the manufacturers installation software i was able to install XP with no problem.

NOTE: Use manufacturers HDD installation software to format the HDD and to create a NEW PARTITION.
Then install win XP but DO NOT CREATE A NEW PARTITION use the partition created by the HDD Manufacturers software.
You should have no further issues after this.
let me know how you get on.
#17
by starting it with incorrect drivers you have caused the system to crash and the result is a surge to the hdd disk head or contact with the platter.
This is a good example of how software can actually damage hardware.
You now need to repair(tell the os not to use that part of disk)
This is done by booting off xp cd, choose repair console, type chkdsk /r, (this may take some time)
After this has finished you should really re-install windows again as the new install may be now corrupted and if you don't it may cause a crash which will need this process repeated.
#18
maddogb
by starting it with incorrect drivers you have caused the system to crash and the result is a surge to the hdd disk head or contact with the platter.
This is a good example of how software can actually damage hardware.
.


I've worked for a while in IT support and I've never seen this happen nor can I believe it would happen - if a hard drive failed due to the PC crashing hard drives would have a very short life indeed. I'ive seen numerous PCs which have had numerous crashes due to a hardware issue yet they have had no problems with their hard drive.

John
#19
maddogb
by starting it with incorrect drivers you have caused the system to crash and the result is a surge to the hdd disk head or contact with the platter.
This is a good example of how software can actually damage hardware.


Can I have an ounce of whatever you were smoking when you wrote this - it's complete garbage. I've worked in IT for about 16 years and NEVER heard of such a thing happening.

For starters, the drivers (whether right or wrong) are just there to tell the OS how to interface with the hardware. It doesn't communicate directly to the platter, it talks to the HDD controller chipset. The addressing of the drive (LBA) has already been defined by the BIOS and so the OS will know to work within these limitations. If this were even a tiny bit true, you'd have people suffering from HDD failure left right and centre because of driver issues.
banned#20
You need to make an SP2 installation of xp onto a Dvd. Its complicated though and you'll need a working pc and access to your systems OEM folder i386. Easier option is to just buy an OEM version of vista.
#21
have you guys ever heard of a bad sector?, there are several reasons why these can happen, degradation of the platter, head/platter contact caused by a knock to the drive etc etc,
trust me following my instructions will lead to this working.
This is not that rare but frontline support will not usually come across this, as a field engineer i come across it once a month.
#22
Could be the PSU isn't powerfull enough, what wattage is it?
#23
maddogb
have you guys ever heard of a bad sector?, there are several reasons why these can happen, degradation of the platter, head/platter contact caused by a knock to the drive etc etc,
trust me following my instructions will lead to this working.
This is not that rare but frontline support will not usually come across this, as a field engineer i come across it once a month.



what?????
banned#24
Alfonse
what?????


Thats what i thought
#25
if you guys don't believe it
take a hdd with xp installed, out of a sis based board with the manuf drivers installed and place it in an intel 845 based board(asrock 845gz) and i guarantee this will happen.
#26
maddogb
if you guys don't believe it
take a hdd with xp installed, out of a sis based board with the manuf drivers installed and place it in an intel 845 based board(asrock 845gz) and i guarantee this will happen.


i have, only the same situation; the system can't start, as XP has a spack attack and can't cope with the number of new devices and drivers to install and the fact that XP does have a limit on the number of times you can change h/w. Best method is to re-install XP a fresh for any new system, but you can sometimes go into safe mode and uninstall drivers and fix h/w issues there but not often, however it certainly DOES NOT kill a HDD because a OS has a fit, please this elementary Desktop Support issues.
#27
maddogb;4111157
if you guys don't believe it
take a hdd with xp installed, out of a sis based board with the manuf drivers installed and place it in an intel 845 based board(asrock 845gz) and i guarantee this will happen.


If this was the problem then surely the specific motherboard doesn't matter? I've transplanted hard drives between completely different systems (such as AMD and Intel, P3 to P4 etc.) and while the new install didn't tend to run that well the hard drive was absolutely fine. In cases where the two were completely incompatible and the new setup just crashed constantly the hard drive ran flawlessly when a compatible motherboard was found.

I've three times moved an install from an sis based machine to another, once to an Intel 845 board (one produced by Intel), once to an Nforce3 and once to an Nforce4. That hard drive is still in a working machine and it functions without issue.

Your explanation doesn't pan out either, you claim this 'power surge' causes the head to hit the platter but if that did happen it's highly unlikely the machine would ever get anywhere near the main Windows screen at all. There's no way an OS crash due to a bad driver damages the hard drive otherwise you'd go through hard drives pretty quickly especially if a machine has a bad piece of hardware.

If this is your level of hardware/software knowledge it's quite worrying if your claim to being a field engineer is genuine.

John
#28
The times when I've moved a HDD from one chipset mobo to another (usually from via to nforce), I just boot from the XP CD and choose the option to repair the current install.

maddogb - what certification do you have and where exactly did you 'learn' that incorrect drivers cause physical HDD issues?
#29
Alfonse
i have, only the same situation; the system can't start, as XP has a spack attack and can't cope with the number of new devices and drivers to install and the fact that XP does have a limit on the number of times you can change h/w. Best method is to re-install XP a fresh for any new system, but you can sometimes go into safe mode and uninstall drivers and fix h/w issues there but not often, however it certainly DOES NOT kill a HDD because a OS has a fit, please this elementary Desktop Support issues.


never said it killed a hdd only said "it happens" (depending on many variables) to cause a bad cluster, which as you know if it is in the middle of boot files will prevent further sucessful boots even if a fresh install is performed


Johnmcl7
If this was the problem then surely the specific motherboard doesn't matter? I've transplanted hard drives between completely different systems (such as AMD and Intel, P3 to P4 etc.) and while the new install didn't tend to run that well the hard drive was absolutely fine. In cases where the two were completely incompatible and the new setup just crashed constantly the hard drive ran flawlessly when a compatible motherboard was found.

I've three times moved an install from an sis based machine to another, once to an Intel 845 board (one produced by Intel), once to an Nforce3 and once to an Nforce4. That hard drive is still in a working machine and it functions without issue.

Your explanation doesn't pan out either, you claim this 'power surge' causes the head to hit the platter but if that did happen it's highly unlikely the machine would ever get anywhere near the main Windows screen at all. There's no way an OS crash due to a bad driver damages the hard drive otherwise you'd go through hard drives pretty quickly especially if a machine has a bad piece of hardware.

If this is your level of hardware/software knowledge it's quite worrying if your claim to being a field engineer is genuine.
John


my claim is genuine and if you reread the original post it was not surge causes head to hit platter it was "surge or head striking platter(usually abrupt power outage)


Xb0xGuru
The times when I've moved a HDD from one chipset mobo to another (usually from via to nforce), I just boot from the XP CD and choose the option to repair the current install.

maddogb - what certification do you have and where exactly did you 'learn' that incorrect drivers cause physical HDD issues?


just because you have successfully done it is a guarantee it will work every time?
the option to perform a repair install is not always successful in these case so i doubt you have come across this issue but that doesn't mean it is not there
i have an hnc in IT support from about 15 yrs ago but have spent 25yrs working i IT and electrical industries

and after all these questions why do you guys fail to answer mine?, have none of you come across bad clusters? if so where do you think these come from if not force or age related failures?
#30
In my experience most bad clusters are a result of force which is why I see far more laptops with boot issues rather than desktops which tend to be static. I've never seen it caused by a driver causing a crash in the operating system and quite frankly if the hard drive/PSU design was that poor was soon be out of business. You claimed above that it would happen every time if moving from an Sis chipset to an 845 setup (with no other factors) yet that guarantee is false as I've never seen it happen that way or any other.

Furthermore even if I did accept what you're saying is true, it clearly doesn't apply here anyway - the machine is consistently reaching the Windows welcome stage even after a reinstall which is not a sign of physical problems with the hard drive. In the cases where a drive does have damage it will rarely get much further than the initial stages of loading the Windows system files rather than the final stage of mounting the last drivers.
#31
Johnmcl7
In my experience most bad clusters are a result of force which is why I see far more laptops with boot issues rather than desktops which tend to be static. I've never seen it caused by a driver causing a crash in the operating system and quite frankly if the hard drive/PSU design was that poor was soon be out of business. You claimed above that it would happen every time if moving from an Sis chipset to an 845 setup (with no other factors) yet that guarantee is false as I've never seen it happen that way or any other.


not false at all but it happens with such regularity i doubted i would be proven wrong because i did indeed state other factors( such as sis own drivers were to be installed because they have been in all cases i saw)
i have replicated this effect twice now by scanning a disk , finding and marking bad sectors with repeated subsequent scans not finding any.
At random points i then ran the restore routine giving various times before the machine either restarted or was visibly non responsive and required manual restarting using front (SW) power off hold
on all events bad clusters were found on subsequent scans. yet failure stopped when replacment board was removed and replaced(again) with an sis630 based board.

Johnmcl7
Furthermore even if I did accept what you're saying is true, it clearly doesn't apply here anyway - the machine is consistently reaching the Windows welcome stage even after a reinstall which is not a sign of physical problems with the hard drive. In the cases where a drive does have damage it will rarely get much further than the initial stages of loading the Windows system files rather than the final stage of mounting the last drivers.


The point of reset is a decent indicator as indeed it is one of the last tasks in the boot schedule but not absolute as the bad cluster could contain ancillary system code such as a av definition file which could also kick in the effect.
As you are clearly interested to a high level in IT maybe consider the complexity of auxiliary factors involved here and don't be so quick to dismiss all of a statement simply because you have not experienced a part of it

Having reread the original post i have to agree that it is a long shot here but it is one as you can see that no one else had previously thought of so may have come in useful to OP therefore aiding in the battery of solutions available both to OP and future readers

back to OP, if my suggestion doesn't do the trick it would be far quicker to perform the repair install with an os cd, of course following a scan with [url]www.malwarebytes.com[/url] just to remove any potential nasties
#32
bargain surfer
You may need to d/load the manufacturers HDD installation software, this will fully FDisk/format and create a partition for win XP installation.
This is defo why xp is only recognising 136GB of the total space available.
I had the same problem installing a 250GB HDD and once i hadd/loaded and run the manufacturers installation software i was able to install XP with no problem.

NOTE: Use manufacturers HDD installation software to format the HDD and to create a NEW PARTITION.
Then install win XP but DO NOT CREATE A NEW PARTITION use the partition created by the HDD Manufacturers software.
You should have no further issues after this.
let me know how you get on.


Iggy the Tecno freaks overcomplicating a simple problem!

Also when d/loading the install software you may also be able to d/load Manufacturers Diagnostics utility which will identify any problems, you do not need an os installed to run diagnostics, so maybe worth running before OS installation to rule out drive failure.

Talk about "making a mountain out of a Molehill!"
#33
try the ram. when i built my pc a few months back it was doing something similar. turns out the ram was in the wrong way around. just try with one ram in the 1st bus. then swap about if doesnt work. rinse and repeat until it works, or possibly doesnt work lol
banned#34
ChipSticks
um, could be faulty ram?


n1ttygr1tty
....try taking one of the ram out and leave 1 in....,


Mclovin
try the ram. when i built my pc a few months back it was doing something similar. turns out the ram was in the wrong way around. just try with one ram in the 1st bus. then swap about if doesnt work. rinse and repeat until it works, or possibly doesnt work lol


Already been suggested twice, guess you don't bother reading other peoples replies.
#35
maddogb;4113963
The point of reset is a decent indicator as indeed it is one of the last tasks in the boot schedule but not absolute as the bad cluster could contain ancillary system code such as a av definition file which could also kick in the effect.
As you are clearly interested to a high level in IT maybe consider the complexity of auxiliary factors involved here and don't be so quick to dismiss all of a statement simply because you have not experienced a part of it


It's not just me that hasn't experienced this, no-one else in the thread has. There's been machines here that have been restarting due to a crash constantly over several days (due to users switching off the monitor and leaving the next shift to report it) but surprise, surprise despite this seemingly being a definite example of the problem the hard drive's health was 100% and worked fine once back in a suitable chassis. I'm not being quick to dismiss anything, as I've said already even if I did accept what you claimed was possible (which I most certainly would not) it still doesn't match the symptoms the person is claiming. If the first crash had indeed damaged the hard drive then it wouldn't be booting to the exact same place on the reboot given it's right at the end of the Windows startup however it is still restarting at the same point. After reinstalling the operating system the odds of the bad data occurring in the identical place on the new install (which itself is a different configuration) are pretty much impossible. It sounds far more likely that there's either a mismatching driver or some incompatibility in the hardware. You also cite specific drivers (sis) to recreate this problem which again clearly cannot be the case as detailed earlier, the drivers have no direct access to the hard drive itself therefore it is the incompatibility which is the issue and there's plenty examples of incompabilities between differing machines which many people will have seen numerous times working in IT yet never a damaged hard drive as a result.

Having reread the original post i have to agree that it is a long shot here but it is one as you can see that no one else had previously thought of so may have come in useful to OP therefore aiding in the battery of solutions available both to OP and future readers


No-one had thought of it because none of us believe this could even happen (I've worked with MSI SIS 630 boards which did not have this 'problem' despite it being guaranteed earlier in the thread) and at best it doesn't even match the symptoms. Rather obviously it shouldn't matter if it's Sis drivers either since the issue is that of the crash otherwise you would be suggesting that Sis drivers are able to cause HD faults that other drivers do not which is not the case. I mean I know some people don't like Sis but even that's stretching it for their drivers. I really hope future readers do not believe they are physically damaging their hard drive if the system crashes.

John
banned#36
dcx_badass
Not really necessary tbh. XP can install fine without them, I've done it on at least 3 SATA PC's with just a normal XP disk.


With the original XP CD you need a floppy disk with your SATA drivers on for XP setup to see the SATA drives, how did you do it without installing the drivers from floppy?
#37
dcx_badass;4114373
Not really necessary tbh. XP can install fine without them, I've done it on at least 3 SATA PC's with just a normal XP disk.

Try a copy of XP with SP2 should work find I recon.


Depends on the sata controller and the XP disk, not all XP disks can install to all sata drives - laptop Vostros would be a recent example, a standard XP SP2 CD cannot see the sata drive. Always worth a shot though as it doesn't take long to establish if it's going to work or not.

John
#38
There is no 'corporate' version of XP however which may mean you are indeed using a modified XP CD with slipstreamed drivers as XP corporate refers to the pirated version of a volume licensed XP.

John
#39
Johnmcl7
There is no 'corporate' version of XP however which may mean you are indeed using a modified XP CD with slipstreamed drivers as XP corporate refers to the pirated version of a volume licensed XP.

John


are you just in an arguing mood? cos the support for sata disks is dependant on the bios not on xp, it is the controllers and whether or not they can emulate a standard ide via bios support which is the deciding factor here
#40
Johnmcl7
There is no 'corporate' version of XP however which may mean you are indeed using a modified XP CD with slipstreamed drivers as XP corporate refers to the pirated version of a volume licensed XP.

John


damn, our site licensed version of XP with a corporate key must be pirated from our Microsoft Account Manager, lol.

All the HDD debate is funny, s/w can't cause a HHD to have h/w failure, only that the HDD can degrade and the s/w (i.e scandisk etc) can assign where the degradation is and highlight them as bad clusters so they aren't used.

Post a Comment

You don't need an account to leave a comment. Just enter your email address. We'll keep it private.

...OR log in with your social account

...OR comment using your social account

Thanks for your comment! Keep it up!
We just need to have a quick look and it will be live soon.
The community is happy to hear your opinion! Keep contributing!