New computer sometimes restarts ??

Hello, here is my first post.

I have a problem with my new computer I put together. Every once in a while it dies just after I start it up and reboots itself.

It gets as far as bringing up the task bar and then suddenly there's a blue screen with writing on it and it restarts. The blue screen only lasts a fraction of a second so I can't actually read what's written there.

Any ideas what could be wrong? This only happens maybe 1 in 5 times when I turn it on.

Cheers

 

what is your operating system and have you updated all your programs including your os??

 

I have Windows XP SP2 and I have all the latest updates. All my software is up to date as well. Any recommendations?

 

rightclickmycomputer>advancedtab>startupandrecoverybutton
tick write to system log
untick automatically reboot

When the next failure (stop errror) occurs it that blue screen will remain and show an error message.

Post this message, including the code numbers.

It is possible you have a processor or connector or pci card/memory not properly seated.
Recheck them all.

 

I found where the problem is!

I opened the case and noticed that when I turn the computer on the CPU fan doesn't spin properly. Instead it kind of tries to move every second or so. Then when the computer restarts itself the CPU fan starts to spin... so question now is why does it not spin straight away?? Why does the computer have to reboot itself to get the fan going??

 

Yup, assembly error or faulty fan.

The hesitant starting is probably due to the fan but will still act the same if there is another assembly fault.

If the you are sure there are no obstructions to the fan blade and the fan's cable is intact and it still happens after you have checked all other installations/connections then don't mess about, get a new fan. reliable fans are critical to system health.

 

Nope... I was wrong! I rebooted the computer and the fan was spinning perfectly the whole time and yet the computer rebooted it self again twice this time!

When it finally boots up without restarting I get the "The system has recovered from a serious error." message. I click on the error report contents and it says the following:

Error signature
BCCode : 10000050 BCP1 : AA2F610E BCP2 : 00000000 BCP3 : 8052AB28
BCP4 : 00000000 OSVer : 5_1_2600 SP : 2_0 Product 256_1

Does this mean anything to anyone?

 

The cause may be different in you pc but the logic is similar.
Work through the suggestions in this thread.

http://forums.majorgeeks.com/showthread.php?t=131196

 

Did you do this?

 

Nope not yet. If I ask it not to reboot, can it damage my computer? Doesn't it reboot itself to avoid damage?

Oh and I had to use a video camera to capture that blue screen just before the computer restarts. I have attached the JPG to this message.

 

I'm having the same problem on my pc, except that it's ALWAYS restarting after the loading bar.

You won't damage your pc if you turn that option off. All that will happen is the blue screen will stay on and you'll have to restart/turn off your pc yourself. I can't help with your problem, except to say maybe insert your xp disk and run 'chkdsk /f'. If I had a start up disk, I'm pretty sure that would fix my problem you see.

*Sorry I meant try running 'sfc /scannow'.

 

Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA



Causes : The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.





Solution :

Look for other hardware issues. Remove any newly installed Hardware.

Run any system diagnostics that are supplied by your computer manufacturer, especially a RAM check.

Perform a Driver Rollback if incase a driver has been updated for a particular component.

 

Definitely take a close look at your ram. I'd venture to guess that's the most likely culprit. I had a very similiar issue a while back. Windows kept doing a ram dump to their techs, and half the time on restart when it recovered, it said it was a driver problem. I updated all the drivers on my computer and it sill did it. What it came down to was a faulty memory chip, and when critical system info was stored on it, it caused the computer to fault and restart. If you'd like a memory upgrade anyways this would be a great thing to look at. :cool

 

I'm having the exact same symptoms with my pc. Everytime I boot up it will load the OS and at some point (sometimes immediately upon trying to load OS and sometimes a few seconds after loading taskbar) the system reboots and continues rebooting the same way until I shut it down manually.

The only to fix I've found is to completely reformat the drive. Then it works until I try to install any kind of software (other than OS and drivers) at which point it will resume with the reboot problem.

This only occurred with my SATA drive until I tried running my ATA with the SATA when they both started rebooting. That might mean it has something to do with boot record? I don't get why it has to be a memory problem.

 

Perhaps you can clarify a few points.

Firstly what do you mean by reformat?

The format command will leave a dodgy sector untouched, so run check disk first. You can run check disk from the recovery console if need be.

Secondly I'm not sure where your operating system is SATA or PATA?

If on the SATA how many slots has your motherboard and is the bios set to boot from the one you have the OS on?

If you are getting restarting, go back through this forum and set the pc to halt at the blue screen then post the exact error message.

Does the problem also occur in safe mode?
Does the problem occur if you install software before additional drivers are installed, but after windows? You may need to install the drivers one at a time to test this.

Let us know how you get on.

 

By reformat I mean popping my XP Pro setup disk in my DVD drive, booting from it, deleting the old partition, and creating a new partition in place of the old one.

I've never used checkdisk myself, although I've heard the term pushed about before, it sounds like something I might want to know about :drool ...

I actually have two drives, one PATA and one SATA, that both have XP Pro on them.

My board, a K8N SLI-F, has four SATA connectors. My SATA drive is plugged into the fourth because of space.

I've had the blue screen of death 2x without having to change settings (which is fortunate because I couldn't change the settings if I tried because the drive keeps rebooting before I can do anything), and this is what it said (after informing me of the dangerous state of affairs and urging me to check my memory): *** STOP: 0x0000007F (0x0000000D, 0x00000000 [etc.])

I've never tried to boot into safe mode. The idea never occurred to me for some reason.

The problem, in both instances, occurred after I installed a software application (first time a WLAN monitor, second time a firewall/A-virus prog.), but it had no problem with the OS or any of the drivers I installed.

I am becoming convinced that my problems are driver-related primarily because I've not installed any and my system has been acting like crap... I am now reformatting for the third time and on this round I will use some SATA drivers or some RAID drivers or some SATA RAID drivers or even some SATA/PATA RAID drivers until it works.

edit:
Upon looking back over the thread I can't help wondering why nobody mentioned anything about updating/reinstalling some hardrive/controller drivers. It seems like the obvious thing to think about when you have mysterious hardrive reboot problems.

 

Sounds awfully complicated to me - but perhaps enuf to keep Tim awake.

Like I said if a drive has bad sector format will not cure it. You need to run check disk.
You can do this froma command prompt
chkdsk /r

or you can do this from a working copy of windows by right clicking on the drive in my computer or explorer and choosing properties.
Click check now
tick both check options
click start
Windows may offer to check on next restart if
restart.

Once you have done this you can be pretty sure the drive is OK.
I have seen actual windows installations fail with checkdisk run first.

On the subject of other possibilities, Tim is quite right you may need to hit F6 to install your SATA drivers during XP installation.

I have also recently had a rootkit which caused constant restarting on XP

There are many possible causes - You just have to keep going until you have eliminated all of them.

 

That's something I've been wondering about because hitting f6 to install SATA drivers before OS install has never seemed to work for me. In other words, I hit f6 when instructed by screen and nothing whatsoever happens. My keyboard has an flock feature that could be messing this up though.

Out of curiosity, what kind of mobo do you have jakub?

 

I booted it to safe mode successfully... once. After that it will not boot into any kind of advanced boot option.

How do I run checkdisk assuming that I don't have an operating operating system (which I most definitely do not)?

 

Use your windows disk to boot the pc to the recovery console.

Ensure yout bios is set to boot from CD
Insert Windows CD and reboot
When setup starts press R to got to the recovery console
Type the number of the operating system
Type an administrator password
if you don't use one press enter
At the command prompt which opens

Type
chkdsk /r (enter)

 

I have run a hardrive checker (provided by Hitachi specifically for this purpose) which found nothing wrong either with the PATA or SATA. I have also run a memory tester for several hours that found nothing wrong with my RAM. I've read posts over on the MSI forums saying that certain drivers have issues with large SATA hardrives.

The problem is no software related (because I've flattened the drives three times w/out effect)
The problem is not with the hardrives or RAM (because I've done extensive diagnostics on them)
Oddly enough booting up with one stick of RAM seemed to get my system to boot a little further and to BSOD with some more grace than previously but I have no alternate RAM sticks to try.