Win2000 rebooting my pc from a bugcheck...?

[MSB23x]

The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x00000004, 0x00000002, 0x00000000, 0x00000004). Microsoft Windows 2000 [v15.2195]. A dump was saved in: C:\WINNT\Minidump\Mini052003-02.dmp.

Have had 4 of these occur now, almost directly related to files being stored on my pc.. what can I do to fix it? The box has been very stable from about 08-2002 till about 3 days ago when I started getting these reboots around 3-4AM according to the event viewer. Could this be related to my harddrive being an IBM 120gxp I think.. I don't really remember since it's been over a year since I added it.

Drivers haven't changed in about a month.

1800+ XP
512M Ram (crucial.com)
ATI 7200
W2k SP3

All help is greatly appreciated.

Thanks,
Mike

 

[techwanabe]

Sounds like the old Blue Screen of Death. I've had issues with that, mostly with NT at my office for the entire 3 years I've been here. My collegue and I have tried to actually investigate the causes by taking the error messages and look them up on the Microsoft knowledgeless base and haven't found any real solutions.

Unfortunately, the only consistent way I can get rid of the BSOD is to reinstall or reimage the PC. There is only one instance where I could make it go away without doing this, and that was a PC where I installed the wrong video driver -the PC would blue screen every time. I changed out the video driver and it went away. I've been told that Win2000 has a much pickier HAL and is more prone to BSOD if you try to say, use a ghost image on a PC with only slightly different hardware. Anyway, drivers could be your problem. Try updating/changing them. I've heard that if the registry has rights issues with users, that can cause issues.

 

[Nothinman]

Unfortunately, the only consistent way I can get rid of the BSOD is to reinstall or reimage the PC.

That is hardly a solution, most of the time it's just a bad driver that needs updated or reinstalled.

I've been told that Win2000 has a much pickier HAL and is more prone to BSOD if you try to say, use a ghost image on a PC with only slightly different hardware

You were told wrong, Win2K and XP are much better at dealing with hardware changes than NT 4. But there are some things (mainly just the IDE controller) that it can't deal with.

First you need to find out waht module the stop error is in, disable automatic rebooting so you can actually see the error.

 

[MSB23x]

Where can I look up the error to find out what exactly is happening?

I will work on disabling automatic reboot.

Thanks for the help.

Mike

 

[Nothinman]

http://www.google.com/search?hl=en&ie=UTF-8&oe=UTF-8&q=0x000000d1+site%3Asupport.microsoft.com&btnG=Google+Search

 

[MSB23x]

I've pretty much narrowed it down to downloading large files, so it's a hard disk error of some sort.

MS has a fix but I don't know how to get to it, it says something about support is $99 per incident or something? Does anyone find this a little rediculous?

Mike

 

[Nothinman]

I would first blame the NIC driver before the hard disk, personally.

 

[MSB23x]

DRIVER_IRQL_NOT_LESS_OR_EQUAL

I wonder what would cause this type of problem now, that didn't happen in the previous 10 months this computer has been up and running?

Nonetheless, I will see if there is an updated NIC driver, as well as the VIA 4-in-1s.

I appreciate all of the help I have gotten here.

Mike

EDIT: Holy macaral, I just realized I've been on these forums for almost 4 years !