Sweary help time GO: re, ntdll.dll fuck ups and poss mem iss

[buzzmong]

Right. This computer was built from parts 2 days before I came to uni.

I'm FAIRLY sure it passed a mem test (should have fucking done, sticks were only 6 months old and hardly used, but did work). Will sort out doing a proper mem test once I get a floppy disk.

Not a new HDD, and the rest of the hardware is all tested fine.

However, 2 weeks ago it starting bitching about ntdll errors when programs were crashing, most noticably Winamp, but others are fucking up as well, Generals wouldn't work properly earlier (might have been a bad install from a phyically cracked CD). But apart from that, it's mostly working.

Now, I'd just like to mention that this is the 3rd install on this machine, and the first that works, I had ntdll errors after two fresh XP installs when I was building the fucking thing, from a CD that works perfectly, used on my working home pc which has been fine for 6 months, is scratch free blah blah blah.

I'm looking for possible problems with it that I can't think of myself:

I'm erring towards HDD / CD drive errors due to the previous fuck ups with this file, except the drive manufacture date is Oct 06 (so, it's pretty much brand new) and it's not been stressed (used as an internet machine only).

Drivers should all be fine as well so that shoudn't be a problem.

Anyone else think of what could be causing repeated fuck ups with this file/machine?

I'll probably nuke it in a few days, and when I get a fresh install done, will use Acronis to make a proper image of C:.


Also, just for prosperity, anyone know if it's possible to fettle MemTest onto a USB stick?

[Dr. kitteny berk]

I'd suspect you has a memory issue (it's not uncommon for it to die kinda randomly)

http://www.memtest.org/#downiso get the usb key version.

it's also worth swapping memory around in slots too

[FatherJack]

Some checks, in sort-of order:

1. University (residential) networks are typically riddled with virii, so check you still get errors from a clean, network-disconnected install.
2. Hardware. Replace the disk if you can, triple-check the memory's seated.
3. Try with bare-bones: no CD drive, no soundcard, vidcard, half RAM, etc until you find something that makes the errors start to occur. Also try to find a different Windows install CD. Even XP home or something older.
4. Power's always an issue - is your PSU up to the job?
5. Mobo. Replace it.

[buzzmong]

I'll mention now that all the hardware worked together fine, ran games blah blah, under a 2000 install for the last 6 months. So I'm going to rule out general hardware for now barring memory.

Mobo is an Abit AV8 Rocket Boy (or 3rd Eye as it's apparently known everywhere else).

Memory in question is some OCZ Gold DDR PC3200 stuff, 2x 512mb (Part no: OCZ4001024DCGE-K)

This system was installed and formatted at home, off the internet, running via my router (had up to date anti virii and spyware etc setup files on it ready to go before format).


Funky LCD thing is currently sitting on code 26, which is:

1. If Early_Init_Onboard_Generator is not defined Onboard clock generator initialization. Disable respective clock resource to empty PCI & DIMM slots.
2. Init onboard PWM
3. Init onboard H/W monitor devices


Which is annoying as it COULD be a memory issue, or it might not be.

[Dr. kitteny berk]

I'm tempted to ignore the win2k working thing.

mainly because between then and now you've probably opened the case many times, poked around in stuff, stuck it in the back of a car and so on.


from the LCD thing it sounds like it might just be memory, so test that in every possible combo.

Also you may want to try resetting the bios in case the memory has collected any weird timings or voltaged at some point.


mostly I just figure it's dumb to try anything else with issues like this until memory has been completely ruled out (as iffy memory can make any and every part of a machine look like it's dying)

[buzzmong]

Well, tried each RAM stick individually. Still same errors.


HOWEVER, MS support says most ntdll errors are due to software and exceptions (apparently ntdll.dll handles exceptions that are passed upto it), and in a brief twist of fate, if I load Winamp and close it before it crashes, I get a Windows C++ Runtime error!

Which is odd as no-one else has mentioned it on Winamp's forum, so I'm gonna say it's a chunky software error.

Either way, will buy a new sata disk this week for use in this machine.

[buzzmong]

Update, uninstalled Winamp 5.5, dropped to 5.35, seems to be working fine.

I also uninstalled MS .Net Framework 3.0, as that's the only non critical windows update I can think of that I chose to install, and the only different bit of software really that's not on my other PC.

Will play with it some more and see what happens.

[HereComesPete]

Shouldn't be either. This sounds to me like a b0rken windows install, it really does. I had very similar problems when I got around to my scheduled format/reinsall spruce up phase, I fucked up the slip streaming stuff, and it fell over in a massive way, it would work fine, or shit itself, at random. Had to redo from start. That was fixed by a whole new cleaning of the boot partition and a new install of xp. It's a rather drastic step, so I'd recommend doing everything that is possible before trying this, driver fettling etc, but if all else fails, do a KV and nuke the fucker from a truly extra-planetary level.

[buzzmong]

It was fucking up under 5.35 before, I upgraded to see if it fixed it, 5.5 will probably work fine, and it's not the first time I've had problems with the .net framework either.

I recall having to format my 2800+ XP system last time because it broke itself installing an early version of the 2.0 framework.


Still, it's rock steady again now. Everything is working, not crashing (Winamp was running for oooh, 30-60 seconds tops). Not had any bsod in games since the uninstall. Yays.



/moans why he didn't think of it a week ago.

[cheeseandham]

http://www.5punk.co.uk/wiki/index.php?t ... d.21.21.21

[buzzmong]

http://www.5punk.co.uk/wiki/index.php?t ... d.21.21.21

I did read it, deemed it not useful as I'm not inexperienced, obviously as this topic has proved, just stupid.

Besides, I was FAIRLY sure it wasn't hardware, turns out I was right.

[deject]

I'm actually liking the new Winamp 5.5 skin they made. It's worth checking out.

[cheeseandham]

I did read it, deemed it not useful as I'm not inexperienced, obviously as this topic has proved, just stupid.

Besides, I was FAIRLY sure it wasn't hardware, turns out I was right.

Fair enough, although I linked it as I updated it with some of the extra BartPE stuff after your posts so I was highlighting it and the changes for others as well as yourself - obviously having a second OS to boot to or proven working OS can help a lot when deciding whether hardware or not.

Anyway, we all have our stupid moments Only last week I ranted at my partner not being able to install a NAS over the phone to which he said "have you turned it on". I ranted back saying "of course it's on, I have one of these, the lights on the front and there are network activity lights on the back, of course it's....oh yeah... wait a moment"

Stupid NAS, looking like it's on when it's not