• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Non stop rebooting

X

Xpage

Senior member
Bascially, i made a system over them summer and was able to OC it to 2.7 ghz (opteron 165) and stripped raid.

Anyway the system ran fine as I kept it as 2.5 ghz or 1.12ghz when idle. Anyway I tried ot go on windows today and I was on my desktop, double clicked a file and the PC turned off.

I started it up and then when the windows PX logo appears (and the scrolling blue bar) then PC gives em a 1/2 BSOD which I cannot read and restarts.

I tried booting in safe mode with no luck and in normla mode too. I turned down my fsb from 275 (with a 1:2 divider) to 220 and I still cannot boot windows.

NV raid says my array is healthy, so I would asusme that means both of my drives are plugged it and haven't become loose.

I have alot of digital images I want to recover so I'm hoping you all can help me out. I've been realy busy lately so I haven't backed up like I do every month or two. I think my last backup is about 3-4 months old.



Anyway I think I will
1) Check my raid data cables

2) unplug my PC for 20 minutes and try again (friend said to try that)

3) try using my backup HD (my this PC) as the boot drive and hoping I can transfer the files from the raid array

4) Try a windows repair on my raid array (I think I need to find my drivers disk)

5) relying on you for this or more!


Most of option other than 1&2 will kinda be a pain in the butt as I have a big presentation on Tuesday and all this ***t happened when I tried to open the folder contianing my ppt presentation.


HELP!!!!!!!!!




 
If it shut down it could be due to CPU temps in which case if the CPU overheated too much the CPU could be damaged. Or it could be the PSU crapped out and isn't providing stable power anymore. What PSU you have?
 
Also, try (gasp) clocking it to spec. And if you have a camcorder, aim it at the screen and see if you can capture the BSOD message, then use the camera to read what the message says.
 
yeah I am going to try going abck to normal. Temps in bios read 22C and 25C for CPU and chipset)

PS = Antec TP II 550W
 
Hmm, tried, resetting the BIOS

everything is running at their stock rating, I even tried below their stock rating, still encountered the same problem./


tried a new hard drive with windows on it and I encountered the same problem (even with the other HDDs off).

I can get into bios fine and such so I am wondering if it is a CPU problem or memory problem. The PSU volatge outpouts seem fine so I do not think it may be that.


I'm about to take some old memory from my last PC and use it in this one as the old memory works fine, I'll also memtest my memory i was OCing with to make sure nothing went wrong with that.


I'm curious how I would know the CPU is bad?
 
hmmm, using the other new stick of memory I get the same problems, HDD won't boot.

even worse is that running memests won't work. I get
Warning: address line A20 already enabled


ok, guess tomarrow i do a fresh windows install failing that, switch PS, failing that MB then CPU

 
Originally posted by: GalvanizedYankee
I doubt your CPU is bad.

Read symptoms http://www.badcaps.net/Ident/ If you register for thier forums, please give Galvanized the referral.

Read symptoms http://www.motherboardrepair.com/

Inspect the board well, then open and inspect the TPII for bad caps as well, if it's out of warrenty.

A bad stick of RAM can cause constant reboots also.


...Galvanized
Click to expand...
I agree with Galvanized... before you bother doing anything else, check the caps on your motherboard. If that's the issue then you will save time if you find it before you go ahead and troubleshoot everything else.

The last "rebooter" I worked on had several blown caps... good luck.
 
Originally posted by: Xpage
Hmm, tried, resetting the BIOS

everything is running at their stock rating, I even tried below their stock rating, still encountered the same problem./


tried a new hard drive with windows on it and I encountered the same problem (even with the other HDDs off).

I can get into bios fine and such so I am wondering if it is a CPU problem or memory problem. The PSU volatge outpouts seem fine so I do not think it may be that.


I'm about to take some old memory from my last PC and use it in this one as the old memory works fine, I'll also memtest my memory i was OCing with to make sure nothing went wrong with that.


I'm curious how I would know the CPU is bad?
Click to expand...

Fair enough!
 
Caps wree all good.

I bought a new HDD< fresh install of WIndows XP, set it up so it would detect my raid array, then plugged in my raid array and it detected errors on it, then procdded to fix them.

Somehow I got a few corrupt files that more or less caused the reboots, odd thing is that it was also on my backup HDD (unless I forgot to do a fresh install on that when I upgraded, since making a new master boot record and boot table didn't work using windows XP recovery)

Using that abckup HDD after attempting to fix it via repair windows via the CD I managed ot get into safe mode but normal mode would give me 2 errors a 0x00000050 or some other one.


Thankfully its fixed and wasn't too hard. Just posting this as a FYI to anybody who has similar problems in the future
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top