Help with Windows 2000 Pro Errors

[SaturnX]

Ok Everyone,
Well recently, I have been having the errors occur in various spot while running in Win2K, they always appear in the same spots. The errors as follows

The Instruction at "0x005402fbf" reference memory at "0x01538245" could not be "read".

Though the #x###### vary from error to error. I have slowly been going through a process of elimination, for sure I know that it is not my HD (IBM 75GXP 30GB) as I ran the Drive Fitness Tests which tests the drive, and passed with flying colours. Well though, I am aware that my PSU is failing on me (my Antec PP303X is on its way to me as we speak) so I was thinking that was one of the culprits. Also, I never seem to get any errors of that sort while running 98SE (dual boot same HD, partitioned). Though I have also suspected my RAM (2 Sticks Generic 64MB) that may be failing, though I did spend several hours playing UT and Q3 to check that thought, and they ran flawlessly. [Edit]I have never seen any errors of that sort while using Windows 98[/Edit]

Well if you're still here after reading that, what suggestions may you have in a way to solve my problem?

--Mark

P.S I beginning to think it's a software prob... Running Win2K Pro SP1

System:
Intel SE440BX-2
Intel PII 400
128 MB RAM (Generic)
30GB IBM 75GXP HD
Hollywood Plus Decoder
SB Live! Value
D-Link DE220 NIC
Dual Win2K Pro SP1 and Win98SE

 

[Floyd]

Just an initial observation, the error sounds like it is related to your system memory (RAM) rather than the hard drive. I noticed in your signature that you're using generic 128MB (not that generic necessarily implies inferior, but it's something to suspect). I'd recommend swapping it with another stick if possible. If the 128MB is comprised of two 64MB sticks, it should be easy enough to try one by itself and then the other.

[edit] Noticed you're dual booting with Win98. Am I to understand you never see this error in Win98? If not, don't rule out the memory just yet. In my experience, Win2k is less tolerant of hardware problems than Win98. The kernel is more robust against poorly-written software, but hardware issues will bring it to its knees. [/edit]

Best regards,
Floyd

 

[SaturnX]

^^^Anyone else have any suggestions?^^^

 

[jaywallen]

Actually, Tharyn, I was thinking the same thing as Floyd when I first read your post. That means that, on this particular issu, a) Floyd was unlucky enough to be as dumb as me, or b) I was lucky enough to be as smart as Floyd.

I have also seen badly behaved applications, particularly memory leakers, produce this message.

Regards,
Jim

 

[Floyd]

Der, uh, what's he talkin about?...I hope it was that "smart" thing.

I really think you should investigate the RAM as the possible culprit. Hopefully your new Antec power supply will arrive soon so you can rule it out.

Have you given a look at the video card? To the best of my knowledge, the error message shouldn't refer to video memory, but I had a card once that would give a recurring and repeatable Memory Parity Error (and BSOD) during any sort of moderate-to-heavy image editing. Evidently it wasn't a hardware problem, as the error message would suggest, because new drivers completely eliminated the problem. I'm bringing this up as a possibility because it seems a lot of manufacturers are dragging their asses on writing reference drivers for Win2k. Good luck!

Best regards,
Floyd

 

[Cyph3r]

This error message is USUALLY in relation to an application. It might be behaving badly(or written for Win98) and as such is not working well in W2K(which is just about as tolerant with flagrant apps as NT is).

As far as the RAM goes, most of the RAM is usually manufactured by a handful of companies and the rest just place their labels on them. So these days that should not be a worry. But indeed, once in a while bad RAM chips can happen. I've been using generic RAM chips in my machines for many years without any problems.

I used to get these kinds of errors in NT when running a 16-bit app or one that said "Run specially in Windows 95/98"..

What I would suggest you do is to attempt to reduce the number of applications you have running in the background. Go to the task manager and see what's going on. In addition, if you have any apps/tools/dodad's starting from the Startup group..then remove/disable them for now..

Try to bring W2K to a base system and see if this error persists..

Also, if you tend to get this error when usually running a certain application, then try to see if there is an upgrade for it.

I always hate suggesting people re-install W2K, but sometimes with the kinds of applications out there, when one of them messes up your machine, the only way to truely restore it to a working/stable condition is to re-install the OS and make sure you install applications that are assured to with the OS..Regards

 

[SaturnX]

Hrmmm....

The more I think about it, and from the responses I've read, it may seem, that the errors may be linked to the fact they may be specifically designed for Win9x. I'm going to look more into this, and in response the above, all my drivers are latest Win2K drivers for each device, though I will be reformatting soon, if anyone has any other suggestions, that would be great.

--Mark