Stop: 0x0000001A MEMORY_MANAGEMENT

[groovin]

Hi, I have a NT 4.0 server sp6a running SQL Server 2000. Recently it has had some problems with a drive failing, but that has been replaced. It has run smoothly for about a month now, but today the server BSOD'd:

Stop: 0x0000001A ( 1x00041284 <more parameters> )
MEMORY_MANAMGEMENT

and then it listed more dumps and a mix of driver names.

I've checked the MS kbase and found some references to it being either a bad RAM problem or a "general memory management issue". Googling, I've only found the same stuff repeated.

My first instinct tells me its the RAM and that I should replace it. I didnt build this server, so I am not sure what quality of RAM is in it. Of course all the parts are server grade from well known vendors, but who knows, maybe the RAM was skimped on. While I order new RAM for this machine, I was wondering if anyone out there has seen this problem before. Some sites i foudn said to check for "general mem management problems".. but that doesnt really tell me too much. Does anyone have any suggestions?

many thanks

 

[mattjurado]

Are there any patterns as to when this happens? Have you checked to make sure there are no background programs or services running that shouldn't be? Have you made sure your swap file is large enough (should be at least double the amount of ram you have)? Have you scanned for virus/spyware?

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[groovin]

hey matt,

this has only happened once. services and page file look in order and the system looks clean virus wise. Nightly backups run without a hitch.

 

[mattjurado]

1 blue screen after running for a month? That's it? Obviously you have rebooted and are running by now.

I wouldn't go swapping memory yet. I would let it run and see when it happens again. If its a daily problem, then you might move forward and troubleshoot. If its a once a month thing, you do own a Microsoft product. Monthly reboots are a part of life for MANY people. You may simply want to create a batch file or script that reboots that server every few weeks.

Matt J.

Please always take the time to backup any and all data before performing any actions suggested for ANY problem, regardless of how minor a change it might seem. Also test the backup to make sure it is intact.

 

[groovin]

yes, i rebooted that sucker right away and everything worked fine, SQL included.

this server has run quite well (for an old MS product) for the last 3-4 years, only needing reboots for updates. thats why it is concerning for something like this to happen. i guess we all got used to it running so smoothly that when something actually does happen it really sticks out.

thanks again for your input.