XP Install Problems, BSOD'S, chkdsk hangs,files not copied, etc

I'll join that fraternity - lets say, its certainly a contributor.

 

Is it? System mismatch how? I'm happy to accept this, just wonder how I should have worked it out.

All correct I think.

Ok, I can take a hint (after about 4 pages of posts ), I'll buy some new memory. I'm not sure what's available on this island so it may be a couple of days delivery time. We're very remote up here. I'm sure the computer shops will have memory, but I will stick to the brands you've recommended.

Ok. I'll work on those things.

The guy who built my machine is out of business and inaccessible to me.

Me too, keep it up guys. Thanks again

 

I'm 220 miles north of mainland Scotland but I'll give it a go!

 

PC2100 running at 266MHz vs Barton Core Athlon K7 running at 333MHz - not an impossible situation but a mismatch forcing asynchronous operation. And, while possible to overclock some PC2100 memory and run at PC2700 speeds (synchronous operation), performance and any resulting errors at this speed will not be recognizable to MemTest. Further, asynchronis operational stability measurement would require different tools. Botttom line - not an optimal situation, especially in light of recurring BSOD's.

 

Gotcha - thanks. I have ordered:

Crucial Part Number: CT6464Z335
Module Size: 512MB
Package: 184-pin DIMM
Feature: DDR PC2700
Specs: DDR PC2700 • CL=2.5 • UNBUFFERED • NON-ECC • DDR333 • 2.5V • 64Meg x 64

I hope that's the right module, the only other 512Mb in PeteC's thread was PC3200 at DDR400.

I'll do the Panda thing right now, and use RegCleaner and RegSeeker. The memory won't be here till Monday at least I think so I can have a weekend off! I'll post back when I've done Panda.

Edit: I tried to reinstall Panda, but it won't let me while I havePanda installed. It won't uninstall it either! Not sure what to do now

 

It's all gone wrong (again!)

I got Panda uninstalled (downloaded a file from their website). However, when I tried to connect AOL it could not connect, blaming Firewall. I was using XP firewall, so I checked it but it seemed to be configured for AOL. I thought it was maybe expecting Panda, and had been having problems with AOL anyway, so I uninstalled and reinstalled it. I also ran RegSeeker and deleted every mention of Panda.

Now, when I boot up, I get "systemroot\windows\system32\autochk.exe not found, cancelling autocheck" where it normally runs chkdsdk after blue screen. Also, AOL will not connect, and I can't turn XP firewall on ( "Windows Firewall settings cannot be displayed...Windows firewall/internet connection sharing service cannot be turned on "). I thought I would use System Restore and go back to yesterday (the only restore point I have, not sure why?), but this failed (the window stopped responding when it should have been shutting down).

Sometimes when I start up I only get my background, no desktop icons, start menu, taskbar or anything else. I can call up Task Manager, and log off or restart, all of which work ok. I'm stumped by this.

I am on hard drive number 2 now, (4Gb with clean 30 day install of XP) so that I can post this. I am going to uninstall Panda from this drive and install AVG free, the worst that can happen is I have to reinstall windows, there's nothing on this disk anyway.

Edit: I think I might keep this drive in until I solve this, to minimise the software/driver issues. I'll go back to my nightmare drive that won't start up properly when I know my hardware is working!

 

Ok, it's Monday morning, here is the News!

I got my memory on Saturday (God bless Crucial and the Royal Mail ). My 4Gb drive was still going blue screen, so I formatted and tried to clean install Windows, and got a BSOD partway through.

I am back on my Maxtor 120 Gb drive now, with minimum hardware attached. I got my internet connection issue sorted after 1 hour on the phone to AOL (winsock files corrupted ). I have XP firewall running, but still sometimes on bootup get "internet connection sharing" errors connected to firewall.

Anyway, that's an aside to the main problem! It all ran fine with the new memory in, till I tried sfc /scannow. It got to about 90% (I honestly thought it would make it) then BSOD. My main problem now is, on startup, chkdsk finds literally hundreds of files crosslinked on allocation or first allocation unit not valid. This morning, it booted up fine and is working at the moment, but chkdsk didn't run as I closed down normally last night.

To cut a long story short, it seems to have stabilised a lot, but I am still getting some blue screens (e.g. last night when flash player was running, IE "experienced an error and has to close down" followed by BSOD).

Is it time for a clean install of Windows (if it will install)? I guess I could use Files and Settings Transfer Wizard, but will this take any problems with it? The reason I'm thinking new install is I obviously have some software issues (corrupt files, chkdsk results) and if I put a new motherboard in I will still have these issues. (Don't worry PeteC, your gamble may well still pay off, motherboard could be coming! )

Thanks guys, I hope you enjoyed your weekend off listening to my moans!

Edit: I just ran chkdsk and it found no problems, but when I get BSOD, on restart it finds hundreds. I rand chkdsk /r, didn't seem to make a lot of difference

 

I think this will be the test. If Widows install does not go smoothly then I doubt the system will ever be stable afterwards.

Pull out and reseat any connections that you have not changed, like the data cable connectors at the motherboard, the data cable for the floppy drive, the power cable connectors including the motherboard power connector.

Other areas I would also consider would that it may be a power supply problem or a problem setting the resources (Edit: I think Rockster2U covered resources unless it requires disabling onboard hardware).

You have mentioned the file system a lot. Swap drive data cables if you can. Check the jumper settings of all the drives. If one drive may be jumpered as CS and another as master or slave on the same (40 lead?) cable, it can give the IDE controllers a real headache.

Unless anybody else could see other areas, I would go along with getting a new mobo. I would not try to find the problem through the 120Gb drive, just concentrate on if you can get a good install of Windows on the 4Gb.

See what the others may think.

Matt

 

I'm in agreement with Matt and Pete re: next logical steps and think it might be helpful to define the approach to a clean installation. Is there a 4 pin 12V connector on your motherboard and is it connected? Ideally, I'd prefer to have you FDisk that little 4 Gig drive, wiping out the MBR and any partitions so you've got one block of unallocated space. Then use your XP CD to ubild a partiton and do a full format and then on to your installation. Absent that approach, use the XP CD to first remove the exisiting partiton(s) and then create a partition and then a full format. No third party disc tools please. If you get any kind of "file can not be copied" - "retry" from CD, please advise. If you get any kind of Blue screen during the installation, please advise.

Immediately after the windows installation and with no network connection (disconnect ethernet cable before doing any of the above), use your motherboard CD to install SIS drivers, followed by any and all other drivers. Can you connect to the Internet without installing AOL software? Not sure how your ISP is configured but you did say you have broadband. I'd like to see you hold off on AOL and I'd also like to know what version you've been using but I'm getting way ahead of myself so lets follow what Matt and Pete have have suggested.

 

Ok guys, thanks for that. Again, I'm at work, but I will work on these things when I get home in (hopefully) about 4 hours time. The XP install does mention "Cannot copy... ", but I can't remember the file name. There were a couple of files, one copied on 1st retry, the other I retried about 8 times (frustration more than hope) and it seemed to copy after that. I'll try the install as you suggest and keep note of any problems.

One BSOD while doing an install mentioned ntfs.exe (I tried installing it on NTFS[formatted by XP CD] and FAT32[formatted by system floppy]). Any thoughts on this?

Motherboard is now strong favourite I think, but I like the idea of working through these steps, eliminating causes as we go.

Thanks again

 

This is indicative (although could be other causes too) of memory read errors and since we know you have decent memory in there now, it points to power, motherboard or cpu. This could also be a BIOS setting so when you get home, the first thing I would like to do is get a read on your core voltage from the BIOS power setting (or similar) page of your BIOS. This, before you go any further. I will then possibly make one suggestion as a work around but please don't rush into an installation until we look at a couple of tweaks to your current settings.



Edit: I'd also like a reading from your power page of the BIOS as to the actual running voltage of your memory and what the Crucial spec (sheet that came with your memory or a sticker on the actual dimm) calls for. I think the spec may be a high as 2.8, but want your confirmation on this and a reading from the BIOS - not from the first setup page, but from near the back which will also list actual temperatures, voltages etc.

Second Edit: Is there a little square (aprx 1cm² )white 4 hole female socket on the motherboard and is anything plugged into it?

 

Ok I'll do that first, I'll post with the voltages about 4pm GMT (3 and a half hours from now. You (Rockster2U) mention wiping out the MBR and partitions. I already took it to 1 partition, but don't know what MBR is . I think I can connect to the internet without the AOL software, I have a network connection set up to do this at present, as it is quicker, easier and more reliable than AOL software. I can't see why I cannot set it up prior to installing AOL, so I'll do that.

As to holding off on an install, I have a blank 4Gb drive which I can install XP on without damaging anything, so I'll keep experimenting with that, following your steps. Thanks.

 

Ok, I have:

CPU Core 1.63V
+3.3V 3.33V
+5V 4.95V
+12V 12.15V
+5V Standby 4.90V

There is also:
Debug info F FF 26(sometimes 27) FF
Debug info T 34 56 255
Debug Info V 67(or 66) 00 D0 B8(or B7) BD C0 C7 (01)

The voltages are all fairly stable.

Sorry this post is later than expected, how do your car tyres know when you're having a bad day?!?!?!?!

My motherboard is running at 55 celcius, but manufacturers claim it can handle way more than this (80C if I remember correctly).

Any clues?

 

I meant CPU not mobo, sorry! And the weather up here is crappy, the only place in the UK that's not warm and sunny. We get grey, misty with the threat of rain!!!

Edit: I'm signing off now, off to a meeting. I'll work on the rest when I get back, if I'm too late it might be tomorrow. Any further suggestions will be read then. Thanks again