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

Done! I have no intention of putting it back in.

I think this is where the modem was, it was the uppermost slot anyway.

There are only two options in my BIOS, PCI and AGP. I have an ASRock K7S41GX Motherboard if that helps.

None of the cards or anything else have moved from their original positions, will the interrupts still be affected?

I'm not sure about the PNP page in BIOS and enabling reset config setting, I hope this will be clearer when I'm at home in front of it.

There is a link. Again I'll do that when I get home.

Thanks for this (again).

 

Ok, I'm home now and here's a follow up, having had a BSOD when the computer was sitting idle.

The modem is still out: Connected were (at BSOD):
Motherboard (ASRock K7S41GX);
Processor (AMD Athlon XP 3000+);
Memory (1 stick 512Mb DDR333);
Hard Drive (Maxtor 6Y12OLO 120Gb);
Speakers (Trust ???, 4 speakers connected);
Keyboard, mouse & monitor (plug and play);
Printer (Epson Color 460, power off);
BT Voyager 105 USB ADSL modem.

I have unplugged the speakers and the printer now, although the printer has been powered off throughout.

I checked the BIOS, the only options for video are PCI or AGP, PCI is selected with 64Mb mapped memory as before. I could not find the PNP page, nor the enable reset configuration option.

I have disabled the following 3 options:
Onboard LAN;
Onboard AC'97 Audio;
Onboard MC'97 Modem.

I have run Driver Cleaner, it deleted quite a lot of ATI files, do you think this is significant?

I also set Windows to do a full memory dump instead of a minidump, would the results of this dump be any use to anyone? I can post it but don't want to fill up the thread if its no use to anyone. Part of it is:

BugCheck A, {0, 2, 1, 804dc250}

*** ERROR: Module load completed but symbols could not be loaded for NETFLTDI.SYS
Probably caused by : hardware ( NETFLTDI+1974 )

I'm not sure if I've picked out a relevant part, but people on here seem to speak about the BugCheck bit being significant. I can post the whole debuglog if anyone wants.

Another curious thing it does (not sure if it'll give a clue) is that it seems to have lost my internet history since yesterday. Also it used to present me with a 'log on' screen at start up (I only have one user profile) and now it doesn't (as of a couple of weeks ago). I'm not bothered by either of these things but they might point to a fault???

 

And again, BSOD even after the changes I have mentioned. This time the same part of the debuglog says:

BugCheck 50, {80d4b456, 0, 80d4b456, 0}

Probably caused by : ntoskrnl.exe ( nt!KiTrap0E+cc )

Edit: I have both these logs available if anyone wants a look.

I think it's as confused as me!!!!!

Another thing I've not mentioned yet but seems like it might be connected, I often get "Generic Host Processes for Win 32 has encountered a problem and needs to close" errors, also sometimes the same msg for Internet Explorer, Real Player, Windows Media Player. These often occur shortly before a BSOD. Could this have any connection?

 

I was hoping you wouldn't say that! Ok, if that's the way to go, anybody got any suggestions on decent ones to buy. I don't want to spend a lot then find out that's not my problem.

It seems like I need socket A, socket 754, socket 939 or socket AM2. Is that right? Will all these work with an Athlon XP 3000+? Anything I need to know before I change it (I've never changed a motherboard before)?

I thought (one more try) that I would put the graphics card in and nothing else, in case the onboard graphics are contributing, but now I've typed it it doesn't make sense, as the problem happened when I had the card in.

Oh well, onwards and upwards!!

 

You do mean you got the drivers from the Asrock website:
http://www.asrock.com.tw/support/download.asp?Model=K7S41GX

Have you updated the BIOS? I think that is worth trying. Arie might be right that it is a problem with the motherboard, but from my experience, if there is a piece of hardware that is faulty you can reproduce the error consistently and it will point to the hardware that is faulty. "Errors all over the place" are the BIOS setting the wrong configuration or drivers acting incorrectly. The most recent BIOS update was from June and dealt with ATI graphics (although not your model). Maybe you have already updated it.

If you want to avoid unnecessary expense The last things I would try are taking the motherboard out and run it sitting on a sheet of cardboard. If you take it out and find an errant bolt sitting underneath you will kick yourself
The other is reformatting and reinstalling Windows. I know it's painful, but I don't think your motherboard plays happily with ATI graphics or their drivers. If you try, you should run the ATI card at Windows installation and see if it is stable (do you have a spare HDD to run a test install of Windows?).

You might all want to look here:
http://www.techspot.com/vb/topic45928.html
Eerily similar, page fault in non paged area, NETFLTDI.SYS error, ATI graphics.

Matt

 

Yes, that's where I got them. I'm willing to try again though.

No, I choked a bit at doing this (because of the warnings on the same asrock website), but I'm going to do that today when I get home.

I have tried this, installing windows on a clean 4Gb drive, it got so far through install then BSOD. I have also formatted and reinstalled on my current drive about 5 times.

Hmmm, Panda software, me too. However, i have reinstalled that several times since problems started.

Thanks.

 

Ok thanks PeteC, could have been a bit of a disaster!

I think I'll try to update the BIOS when I get home, but failing that I think a new motherboard might be the answer. If I do that I'll be asking advice beforehand for sure!

You're right, I am in the UK (Shetland Islands).

Thanks again

 

Darn - sorry I missed all of the action here. I think its time for all to slow down a bit or we're going to need a bigger dart board to keep throwing until something sticks.

That first error, as Mattman stated, is Panda related according to a quick Google Search and the second error is related to your boot.ini file. Both may be a result of a necessary driver not loading. So what do we do from here? Buy a new computer? Sure fix, but is it necessary?

All of these suggestions may provide some relief but I'm going to go back to what I said in the first place - The characteristic behavior you have described sure sounds memory related to me. Several posts ago, I suggested that we leave the memory alone for the time being but I don't think we can do this any longer for fear that you will have purchased a new video card, a new sound card, a new network card, a new motherboard, a different processor, perhaps a new computer desk and maybe even a new home.

Let me direct your attention to this thread. Similar, but not really the same issue - however, note the solution.

OK - what is a guy supposed to do now? Lets keep it simple unless its already too late. Keep your ATI card on the kitchen table for the time being. And yes, your onboard video shows as PCI on that motherboard. Look for a utility called Clean Up! using google. Download it, install it and run it in the custom option but deselect remove cookies. Leave everything else at default. Reboot. Download the latest RegSeeker beta and install it and run it. Select clean registry and remove everything it finds (set it to save all changes) Uninstall Panda. Reboot. Run RegSeeker again and then reboot. Re-install a fresh version of Panda (or use AVG free) and do your definition updates. Run RegSeeker again and reboot. Now, pull your memory and use a pencil eraser to clean the contacts (wiping down, not across) and follow that up with a Q-Tip soaked in isoproponal. Let it dry and re-insert it. Upon boot, head back into your BIOS and set your memory on auto this time and run your machine for a while. Post back any errors and what you were doing. I also would like to know what brand of memory this is and what Everest has to say about it - a description. With that information, I may be able to help you set manual timings that are more forgiving but I'll stand on my initial comments - this all sounds very suspicious re: having all the benchmarks of a simple memory related issue.

Again, sorry I missed all the action - got tangled up last night trying to help someone remove a RootKit from his customers machine - unfortunately, no such luck - it is smarter than us.



Edit: Run memory diagnostics again that are linked in Mattman's signature and if all goes well, run SFC /scannow from a command prompt using XP CD to repair any corrupt system files

 

Simple??? I'll give it a go. Should I do this before, after or instead of updating the BIOS? Having seen this step by step I think I preferred darts!!

I will try these suggestions tonight and see what info I can get for you.

Or should I just try underclocking my RAM as in the thread you mention?

Thanks.

 

I have done all this, running RegSeeker twice each time. First run found 534 entries! I've only just finished so no errors yet, I'll let you know.

I have two different memory set-ups, both of which have given me the same problems:

Set 1: 1 x TMTC (?) 512Mb DDR333 CL2.5 (CAS Latency - see, I do pay attention! )

Set 2: 2 x VData 256Mb DDR266 (2.5)

At the moment I am on set 2 but have been on both at some time through these problems.

Everest has this to say:
SPD Memory Modules
DIMM1 256MB PC2100 DDR SDRAM (2.5-3-3-6 @133MHz) (2.0-2-2-5 @100MHz)
DIMM2 {Exactly the same}

Is this what you're looking for?
Also under CPU Speed it has:
Memory Bus 134.37 MHz
Does this have any bearing?
If you need more info from Everest let me know.

I have run the memory diagnostics on both sets of memory, both check fine after 4 passes. I tried to run SFC /scannow, when I put in my disk it said "The CD you have inserted is the wrong CD, insert Windows XP Professional" or something like that. It is a genuine XP CD, it checks out in Genuine Advantage, so why should this be? I got it from the guy who built my basic system, but I'm starting to lose a bit of faith in him! XP seems genuine though, correct packaging and everything.

I think I'll run the extended tests of the memory diagnostics overnight, see if that shows anything up. From now on, I will be keeping this memory set installed.

Thanks guys, I am learning (slowly and hopefully this machine will be up and running soon.

 

OK, you 2x256 memory is the PC2100 (266MHz) that doesn't match your Barton core CPU which runs at 333MHz. This means you are running in an Asynchronous mode (processor running different speed than memory) which your SIS chipset will obviously do but its not as good as some others in doing this. I believe you have to run your memory in auto or set it manually to run this way (Asynchronous). The 512 stick of PC2700 (333MHz) does match your CPU front side bus speed (333MHz) and should be a better match for your system but this appears to be the memory that is giving you more problems. This is the stick I would be more inclined to use (because of its speed) but it sounds like the no-name dodgy RAM so I'd test it thoroughly before coming to any conclusions. Now, a question for you - you seem to favor the 2x256 and there is nothing wrong with this but I am wondering why? Does this seeemingly run better with fewer errors?



Edit - almost forgot. You'll need to create a slipstreamed CD which includes SP2 or borrow a friends XP CD which includes SP2 if you can't run SFC /scannow. Arie did a very good instructional How-To on creating a slipstreamed CD which is around here somewhere.
Next Edit - maybe the guy who built your PC has a slipstreamed CD that he'd be willing to lend you if you explained your problem.

 

I think the 2 x 256 does run better, that's what I had in when I had seeming stability on about page 2 of this thread. I made the schoolboy error of thinking the problem was solved (with the speakers) and put back in the other memory (I didn't even take note of when I put it back in but think it was before the graphics card!) So I'm now thinking you're right, the memory stick may be dodgy. I would personally favour the 1x512, as it's mine! The 2x256 is borrowed from my brother in law.

Both test good with the diagnostics from mattman's signature, but only on basic test. I've yet to run extended test, I'll let that run while I'm at work today. (on the 512 I think)

Ok - I'll try to find the How-To. The guy who built my PC was trying to start up a business, I found him online. Unfortunately his business has since ceased to exist so I have no way of getting in contact with him. I don't think he's too dodgy (apart from sending out no-name memory), as when I had a problem before (memory, surprisingly), he replaced it no problem.

I'll try the slipstreamed CD (again, after work in around 10 hours time). Meantime, I'll run mem diagnostics on the 512.

Cheers

 

Ok, do I need Nero for that? I have a very old version of Nero, which won't do some of the things in the article (eg Don't add the ;1 extension). Do I need to buy the new Nero?

Also, should I be updating the BIOS sometime in among all this? I didn't do it last night as I was following Rockster2U's suggestions re Clean Up! and RegSeeker.

Incidentally, I've not had any problems yet since yesterday, but I've not had it running for long either so I don't take it as fixed!

 

Just checking in before getting a few hours of sleep. Thanks Pete, and while I certainly don't pretend to have a monopoly on brains - things were just getting a little too fast for me re: lets try this, lets try that.

bluepeter75 - through all of this, the main thing is that we need to be patient and methodical. There are a lot of good thoughts and some great guidance coming from several very well informed experienced contributors but lets stay focused on going slowly regardless of the direction taken. We are a long way from having anything resolved here but through a process of elimination, we just might get lucky.

As to flashing your BIOS - this has considerable merit but personally, I'd prefer to verify your system files first and see if we can't get some stability. And, based upon Mattman's find re: a BIOS update that resolved some ATI problems I'd call it essential before you throw that video card back in. However, lets keep that card on the kitchen table for a while longer because right now it only confuses the issue with one more variable.

 

Thanks guys, I really appreciate you sticking with this (Rockster2U, PeteC, mattman and Arie). All your contributions are welcomed. I will follow the step by steps given by Rockster2U at the moment as PeteC suggests, but I hope that doesn't put the rest of you off contributing, any input you give is a learning experience for me.

As it stands, my PC is running extended windows memory diagnostics on the 1x512Mb memory (I hope, I'm at work 30 miles away but the wife tells me it's running ).

I plan to do the same on the 2 x 256Mb sticks, possibly tonight depending on how long it takes. I will also try to make a slipstreamed disk (or borrow one with SP2 on it if I can) and try sfc /scannow.

I think that'll put me up to date with Rockster2U's instructions.

I'll hang fire and post any results from these tests, thanks again all.

 

BIOS update, always some thing to try before throwing the motherboard away ...which was what I was trying to point out at that stage.

I've been watching closely and yes, it is an area to be trod slowly and carefully and for fear of "stomping around" I have not intruded again.

Rockster is guiding at this point and I have wanted to encourage this. Working on an "updated platform" (BIOS upgrade) may not be a bad call...up to you Rockster.

I'd ask, was the system ever really stable with this configuration? Has it always been unstable?

I'll but in again later if necessary

Matt