Computer lock ups...

[dccool879]

unless some nice fellow has a nf4 dagf and i could mail em my chip to hotflash :]

 

[dccool879]

if someone has a different motherboard but same bios chip, would hot flashing still worK?

 

[tkpenalty]

...Guys lockups aren't caused by the motherboard's bios screwing up. They are caused by a failing power supply usually, if it is becoming more and more frequent, with the HDD shutting down because of a power loss (even for 1 second). Dccool, before you do anything else replace the power supply.

 

[Verikon]

...Guys lockups aren't caused by the motherboard's bios screwing up. They are caused by a failing power supply usually, if it is becoming more and more frequent, with the HDD shutting down because of a power loss (even for 1 second). Dccool, before you do anything else replace the power supply.

He already replaced the power supply with another one and had the same problems. It's in his original post.

dccool879, did you ever get a chance to check your hard drives? I see so many bad hard drives everyday, it's my first instinct when something goes wrong with a computer.

 

[tkpenalty]

He already replaced the power supply with another one and had the same problems. It's in his original post.

dccool879, did you ever get a chance to check your hard drives? I see so many bad hard drives everyday, it's my first instinct when something goes wrong with a computer.

My bad... didnt read . Hard drive with faulty molex/SATA connector?

 

[Verikon]

No worries. I think it's probably just a failing hard drive. My brother had the same symptoms, and it was the hard drive mechanically failing. But only dccool879 will be able to give us the answer to this puzzle.

 

[dccool879]

ok, i didnt have a bad flash! :] just computer didnt decide to work after flash, so i took out cmos battery in the morn and then tonight i popped it back and my computer worked and i pissed myself.

and ya i just replaced the powersupply, it's a blast to replace something and have the problem still happen. but that's my fault cause i never tested the powersupply. and it's always good to have a backup b/c my server which is on 24/7 just burned through a powmax one and now has a kingwin psu LOL so ya i give that like a week more.

anyways, im still waiting on the blank cd's, :[. but ever since my computer came back to life tonight, ive had no lock ups

 

[dccool879]

ok it just crashed. let's say it is my hard drive, does this mean data loss?

 

[Verikon]

If you're getting into Windows, you probably have a 95% chance of getting everything off, but the longer you wait, the lower your chances get. I'd suggest backing everything up right now. Once you start getting "unmountable boot volume" errors on start up, or it just doesn't recognize the hard drive in the BIOS anymore, then you have to start worrying. But luckily your machine isn't at that point yet.

Then again the hard drive might be in fine condition. Either way, it's good to have a back up of your data.

 

[Ketxxx]

...Guys lockups aren't caused by the motherboard's bios screwing up.[/B]

please, dont make such n00bish statements, evil n00b. BIOS = Basic Input Output System, do you know what that means, or what it does?

 

[Ketxxx]

ok it just crashed. let's say it is my hard drive, does this mean data loss?

Dont panic so much. Just because there is a possibility your HDD is faulty or dying, doesn't mean it actually is. The most common problem is the MBR (Master Boot Record) screwing up, or, if for some reason your using FAT32 (File Allocation Table) that. Bottom line is before rushing out and buying a new HDD you should backup your data, delete the primary DOS partition, recreate it, and then do an unconditional format on your HDD (in the case of using FAT32)

In the case of using the NTFS file system, let the Win XP setup do a full format of your HDD (NOT the "quick format")

 

[Verikon]

Dont panic so much. Just because there is a possibility your HDD is faulty or dying, doesn't mean it actually is. The most common problem is the MBR (Master Boot Record) screwing up, or, if for some reason your using FAT32 (File Allocation Table) that. Bottom line is before rushing out and buying a new HDD you should backup your data, delete the primary DOS partition, recreate it, and then do an unconditional format on your HDD (in the case of using FAT32)

In the case of using the NTFS file system, let the Win XP setup do a full format of your HDD (NOT the "quick format")

Why would the master boot record be causing crashes while Windows is running? Generally MBR issues cause NTDLR to go missing, or other start up issues, not crashing during Windows. I really think it could be a failing drive or corrupted sectors, as he said it crashed consistently when he was playing BF2, which makes me think there is a certain area of the disc the drive can't read, whether because of corruption or the drive mechanically can't reach it.

Plus he said he had issues when compiling his Linux kernel, which has nothing to do with his DOS partition.

How old is your hard drive anyway dccool879?

 

[dccool879]

ordered it 10/5/2005, samsung spinpoint P, http://www.newegg.com/Product/Product.asp?Item=N82E16822152020
and then from 8/4/2004 i bought a WD
http://www.newegg.com/Product/Product.asp?Item=N82E16822144122
^(didnt i buy that HD for that much 2 yrs ago??? lol)

the os is on the SATA samsung

 

[Ketxxx]

Why would the master boot record be causing crashes while Windows is running? Generally MBR issues cause NTDLR to go missing, or other start up issues, not crashing during Windows. I really think it could be a failing drive or corrupted sectors, as he said it crashed consistently when he was playing BF2, which makes me think there is a certain area of the disc the drive can't read, whether because of corruption or the drive mechanically can't reach it.

Plus he said he had issues when compiling his Linux kernel, which has nothing to do with his DOS partition.

How old is your hard drive anyway dccool879?

I cant be arsed with details, so i'll summarise with its all in the ballpark, and until you have experienced many anomalous odd behaviors, its not something thats easy to put in terms for folk to understand.

 

[AshenSugar]

if hes under 2k/xp/2k3 he can use a command line to convert fat32 to ntfs, this also tends to fix problems with file table in my exp, and for the love of god DONT USE FAT its trash!!!

 

[dccool879]

who said i was using fat?? lol. i have 3 ntfs partitions, and 1 ext 2 partitions that i can access in windows. i have tried "unmounting" the ext2 from windows, but i still got a crash.

 

[Verikon]

I cant be arsed with details, so i'll summarise with its all in the ballpark, and until you have experienced many anomalous odd behaviors, its not something thats easy to put in terms for folk to understand.

Hmm, well I'll have to keep that in the back of my head. Next time I run into issues like this I'll have to remember it could be the MBR.

Well that Samsung is only a year old, but it still could be failing. My Maxtor 200GB SATA died after 6 months, so you can just get lemon drives. Or like Ketxxx said, it might just be a partition table issue or an issue with the MBR.

 

[AshenSugar]

boot from windows cd, use recover consol, run 2 commands
fixmbr
fixboot

after you run a full chkdsk ofcorse!!!! this should take care of mbr errors

 

[Taz100420]

ordered it 10/5/2005, samsung spinpoint P, http://www.newegg.com/Product/Product.asp?Item=N82E16822152020
and then from 8/4/2004 i bought a WD
http://www.newegg.com/Product/Product.asp?Item=N82E16822144122
^(didnt i buy that HD for that much 2 yrs ago??? lol)

the os is on the SATA samsung

I had a samsung spinpoint 160GB HDD and it went out within 3 months of having it, imo they are junk

 

[dccool879]

The type of the file system is NTFS.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Deleting index entry upd0C32.ver in index $I30 of file 19476.
Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.

hmmm. i'm not nearly as knowledgable about windows as i am about linux so i'm going to ask first, should i allow write with chdsk and see what happens?

 

[Verikon]

CHKDSK will try to restore data that's been corrupted or has had its index messed up. If the data is in really rough shape, you do run the chance of losing it. I'd recommend backing up your data before running it in read/write mode. This could be a sign that you have bad sector/failing hard drive. Or just a really messed up file system.

When I upgraded to SLI, Windows didn't like the second card being in there and started to get really flaky, so I ran a repair install thinking my install had been corrupted which just made it worse, since Windows refused to boot after that point. I ran CHKDSK and it had to reset file permissions on 70,000 files. It was kind of nerve racking.

 

[Ketxxx]

if bad sectors are found and your given the option, dont "flag" them as a messed up file table can give bogus reports like that. so revert to the windows cd and doing a full (not quick) hdd format, as the full format sets your drive back to all zeros.

 

[dccool879]

i only have my music backed up though, that's all the stuff that i can back up. would formatting just one partition (windows os) fix the problem? no right? because linux has the problem too...

 

[Ketxxx]

you could format just your os partition, but its a tricky situation, theoretically it should fix your os partition if its a naff file system. as that partition is treated as another drive, but because physically it is still just one drive, sharing the same platters and so forth, it may not.

 

[dccool879]

i just ran http://www.samsung.com/Products/HardDiskDrive/utilities/hutil.htm because i had a blank floppy, still don't have any blank cd's. anyways, after the full diagnostic it found nothing wrong with my drive. is this to trust, and maybe look at other hardware/software to blame?