• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2000 Users - Question

thebestMAX

Diamond Member
Hope this is the right forum but Ill probably get better, quicker answers here.

Every once in a while I get a BSOD and the message that "memory is being dumped to disk". I usually just reset my system and go on.

What can you tell me about this if anything?

Should I let the dump finish as it seems to go on forever. What can I learn from it?

Temps are good so not overheating problem and all seems to be running well otherwise.

Any help appreciatted
 
you are getting a memory dump due to a critical system fault

that is bad

you can adjust the size of the core dump, right click my computer, properties, advanced , startup/recovery, write debugging information on the lower half of the window. if you change it from the default (complete memory dump), it will take less time. but the info is probably useless to you anyhow.

you might have bad ram or a bad motherboard, or maybe your OS is just corrupt, i dunno
 
Memory dump in NT or 2000 normally can be linked to some serious hardware problem.... last one I troubleshooted ( couple years ago) was cause one of the memory sticks was going bad....
 
Ill have to get the entire screen if it does it again. I know it does say error in kernel XXXXX but not much else.

Im new to win2000 so was just wondering if this was an uncommon type error. Never saw anything like it in 98 or XP (yet) 😀
 
OK, good info so far. THANKS!

Ram is old PC2100 crucial, 8RDA+ MB and 1700xp oclocked to 2.1G.

Figured the dump would be useless to anyone but a programmer.
 
also, if you are overclocking, step it back and see if it stops doing it. you may be pushing the RAM/system too far over its rated speed.
 
It may be the oclock. Only does it about once a week so hard to slow it down and wait. 😀

If it gets worse, ill do that and maybe start swapping ram. Been wanting an excuse for a faster proc and new memory anyway.

Core dumps in the old days were pretty useless too. Had to send them in to be analysed and by that time that could be done the customer would have bought from someone else. 😀😀
 
The system I built my g/f had this problem, it ended up being a bad stick of RAM.

IIRC you can turn the dump off entirely.

Viper GTS
 
Back
Top