Why do I receive blue-screen error when sutting down ME???

[brouillet]

Almost randomly, I encounter a blue-screen error shortly after initiating the shutdown option with Windows ME. The message reads, "Windows protection error. You need to restart your computer. System haulted." [CTRL][ALT][DEL] is useless at this point. I have to click the physical restart/power switch on my case to actually shut down/restart the PC. Once I restart, ScanDisk runs automatically before booting back to the desktop.

Why is it doing this? What is a "Windows protection error?" I had heard about ME shutdown problems involving fast HDs with 2MB cache, but have istalled the patch from MS Update site.

I'm running the following equipment:

* AMD Duron 750 (not overclocked)
* 128MB Crucial RAM
* IBM Deskstar 30gig 7200 HD (ATA 66 mode)
* Microstar 6330 K7T Pro mobo
* Creative Anihillator 2 MX

Is my hardrive likely becoming corrupt beyond repair? What can I do to remedy this problem? Thank for any and all help!

Steve...

 

[Mal007colm]

I get the same message sometimes. I really think ME has two many problems and may just go back to WIN98SE. Well I am going to try a clean install of ME first then if I still get these random lock ups I am going back to 98SE.

AMD Duron 700
Asus A7V mobo
Maxtor 15.2 gig

 

[DocDoo]

brouillet.... I have been testing this on several PC's, try this:

Everytime you want to "shutdown" hit CTRL+ALT+DEL and choose the "Shut Down" button. Try this for the next several.... and post back.

Sounds like something is not releasing....

PS. I have not heard anything on the "fast HD's with 2MB cache" problem, is this documented?

ALSO: Try using the DEFAULT 640x480 16 color video drivers, post results.

 

[brouillet]

DOCDOO: Thanks for the idea. I'll see what happens.

As far as the HD problem, yes it is documented on Microsoft's Update Web site. Unless you've already installed it, it should show as a critical update and reference fast hard drives and failed cache write errors. There have also been long posts on the Anandtech boards. Search for IBM, since the first major case involved this brand of HD, though it may not be limited to IBMs.

 

[brouillet]

I was able to fix the problem by updating to the Det 6.39 drivers.