My computer has a LOT of problems =(

[Everlast746]

At first, my computer would be randomly restarting. I download things all the time, could be a virus. This started right after installed Diablo II. So I decided to see if reformatting my C partition (nothing but windows stuff on it) and I reinstall with Windows XP 64-bit edition. (At this point I bought a new power supply to see if that was the problem.. it wasn't so I returned it) It has all kinds of problems (sound drivers for my motherboard doesn't work, Diablo II crashing with some random error) so I go and borrow a friends Windows XP Pro disk to try to install that, and this is when the biggest problems start. So I start formatting to this version of windows and I get the error when it is copying files (many of the files I had to hit retry several times one) ntfs.sys 0x00000024 in a blue screen. So I figured there must be something wrong with this CD, and decide to go back to Windows 64-bit until I could find another version of windows. I start formatting with the 64-bit CD again and when it is copying files (with only a few retry on certain files) it gets the same error. Now I guess it is a hard drive problem, buy a new one, and it turns out it isn't (haven't returned yet). I then get another version of Windows XP Pro to see if both CD's are broken. I put in this CD and right after it says "Setup is starting windows" it shows an error saying "CDFS_FILE_SYSTEM" at the top and "cdfs.sys" at the bottom. I tried taking out each ram and trying each individually, using only one of my two sticks it got a little further, when copying files it got to the file cdcopy.dll and it wouldn't work, I decided to see what would happen if I skipped it, and it comes out with the same "cdfs.sys" error again. :mad: I then get an extra CD drive from a friend (it was only an 8x, but it worked for him to install XP) and in the last XP cd I used (the one with the cdfs.sys problem) it still had the same problem at the same time (I didn't bother trying the ram again). I tried the original two (my 64-bit and my friends regular, which both has ntfs.sys error) and they restarted right after it said "setup is inspecting your hardware configuration" at the very beginning after booting from disk. One time I was lucky enough to get to after it says "setup is starting up windows" then asked to hit enter to continue, and it restarted. One time with the second XP cd (the one with the ntfs.sys error but not the 64-bit edition) it got to some point before letting me hit enter to continue it came up with a blue screen saying "USBPort.sys" "0x000000D1" at the bottom and "DRIVER_IRQL_NOT_LESS_OR_EQUAL" at the top. From the last problem there I am assuming it is the motherboard.

I do remember before I got all new computer parts my computer was restarting randomly and I did not know the problem. My main problem is not being able to install windows. Anyone have any idea what the problem is?

all of my computer parts are about 5 months old (other than the new hard drive[only a week old but plan to return since it is not the problem] and the CD drive [got it on christmas])

comp specs:

Motherboard: Abit AL8-V

CPU: 3.0 ghz Pentium 4(i think its pentium 4, if there is any way to check without the box let me know)

RAM: 2x 512mb Corsair DDR2 PC4200

Hard drive(old):western digital 120gb 7200 rpm 8mb cache

Hard drive(new): Maxtor 100gb 7200 rpm 8mb cache

Power supply: some random 430 watt one. (the one i bought and returned was 600 watts, infinity i believe)

DVD/CD-RW: 52x 32x 52x 16x

of course this happens right befor oblivion comes out =(

[Lazy8]

Bought a new HDD? Dewd...you're gonna be so PO'd if socket creep was your problem!

Start with the basics:

Disconnect all peripherals

Remove all hardware not essential for starting Windows (CD drives, extra HDDs, PCI cards, reduce memory banks to minimum number)

Ensure installed devices are undamaged, and have full contact with their sockets (check removable chips on cards & Mobo too)

Power on, enter BIOS setup first, and make sure settings are appropriate for the hardware you expect to install

Use your original Windows installation disc for full install...it already worked once, and is licensed for your machine

If you get to this point, plug in your extra data hard drives later, retrieve and back up (only) your vital data, wipe & format (just in case a virus took you down). Don't click on anything that hasn't had a full scan

Install remaining components one at a time, put 'em through their paces, check DevMgr & Event Log for alerts

Don't install Diablo (Quake, Doom...or whatever) before services hotfixes, and latest drivers

Give us a followup post if you found a solution or more questions

[Everlast746]

What's socket creep? if it's simple, I won't be PO's ^^

What are peripherals?

I only have one cd drive in the computer at the moment, no PCI cards (does video card count? thats PCI-e) and how do i reduce memort to minimum number?

I lost my original windows disk, it shouldn't matter should it?

i unplugged the hard drive with the virus when I plugged in the new one i bought.

[Thunderbolt 2864]

Could be your RAM. Just today I had to remove one of my 512MB RAM off my motherboard because it made my computer constantly freeze and blue screens of death similar like yours. If you have 2 RAM, remove one of them and see what happens. Reformatting your computer won't resolve anything if its a hardware fault.

If the problem still persists, bring it back to the computer store where you brought it. They'll be able to tell you whats wrong.

Edited March 21, 2006 by Thunderbolt 2864

[Lazy8]

Socket Creep = removable chips loosening, caused by thermal cycles over a period of time

Peripherals = any hardware not installed inside the case

Your old hard drive may be plugged into another computer. If you do this, rt-click My Computer, select 'Manage', and open Disk Management. Don't add or delete partitions, or format--just make sure the drive is recognized and is assigned a letter. Don't add, delete or open files--scan for virus & spyware (give it the works, with updated defs). If malfunction is hardware instead of OS, You may be able to reuse it without reinstalling Windows.

For diagnostic purposes, remove all components except PSU, motherboard, video card, primary HDD (you can use the old one if you're sure it's bug free). Pull LAN, modem, other PCI cards(if installed), and all but one memory stick (if that leaves you enough for Windows to run). Make sure power and data connections are firmly seated on all components. If it boots without any of those errors (no matter how slowly), it's bound to be one of the removed pieces. Begin reinstalling them and running the PC, one at a time.

Defective RAM is a common cause of bizarre & seemingly unrelated faults. Download one of these, burn to disk, and run on your bad computer. They are self-booting, so you may be able to do this before all previous steps.

Original disk matters! You can install using another's CD, but never activate with Microsoft (30-day maximum use). If your PC came with factory restore disk (labeled with PC manufacturer), you may send for a replacement--sometimes for a small charge. If it's home built, you'll have to find your original licensed CD, or buy a new copy of Windows.

[Everlast746]

seems to be RAM, I ran memtest and got 57146 errors over 1 hour and 25 minutes. Soooo does that mean the RAM is bad? new RAM, doesn't cost much, and that makes me happy ^^

[LLXX]

You can try overvolting your RAM and then testing again, or underclock it. It might save you from having to buy new RAM.

[nr23]

Hi i am a newbie here, how to "overvolting your RAM"

thanks

[LLXX]

In the BIOS setup there is a "Frequency and Voltage" option, find the setting for "RAM Voltage", "DDR2.5" or similar, and set it to the first setting above standard (normally +0.1v, +0.2v, +0.3v, etc.)

[Lazy8]

If overvolting and underclocking can serve the same purpose, which one is a better diagnostic aid? Is the risk of hardware damage between overvolting and underclocking methods meaningfully different?

[LLXX]

I'd overvolt first, because underclocking decreases the performance while overvolting does not.

Overvolting *might* damage the RAM, but since his RAM is already not in perfect condition and most overclockers will overvolt the RAM to over 3v (from the standard 2.5v) I'd say the risk is minimal. At worst, the errors might remain, in the best case your RAM works perfectly again.

[Lazy8]

Temporary reduction of speed is small sacrifice for troubleshooting purposes, especially if the RAM in question is otherwise warranteed. No problem with an occasional hardware tweak, as long as our self-admitted n00bs are advised of potential risks to their system.

Since this is one mod I have not yet made, I'll be the one to guess: System clock speed is major factor determining voltage requirements of RAM & CPU--supply voltage must be proportional to frequency. Insufficient voltage causes partial or total failure--unstable performance, various Windows stop errors, or behavior mimicking Everlast746's computer--but little risk of permanent damage. Overvoltage will allow RAM to meet increased demand of overclocking, with overheat risk (or even burnout). Are my guesses fairly accurate? If too much voltage is applied, is possible harm limited to the RAM bank itself?

[gdogg]

try running memory on a different divider (less)

if that dont help, force looser timings.

ddr 2 uses lots less volts then ddr. so dont push the volts too much.

lets say, timings are 4-4-4-12 try 5-5-5-15

also check the bios for things like cpc or command per clock set that to 2 also.

check in memtest again using test 5 and 8.

then if those are error free for 10 passes each, then your problems will no doubt be gone.

Edited March 24, 2006 by gdogg