Why do I get a blue-screen error upon shutting 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...

 

[jimmygates]

IT's probably either a) Windows ME HDD Cache problem that's giving you the BSOD's or your using old detonator drivers (6.18 - ?)that were known to give BSOD's alot during Shutdown.



-Jimbo

 

[Dumbledore]

now i dont feel so bad..i have the same problem.

 

[CrimsonWolf]

I hate to say this but I had the very same problem with WinME. I never got around to solving it because I only shut my computer down for when I work on it. Personally I got rid of WinME and put Win98SE back on. Unfortunately, the only way I can help is by bumping you back to the top.

 

[cmaMath13]

The problem is most likely DRIVERS! I just ordered a new system from a good company and they warned me about driver problems and Windows ME.

I think your problem will be fixed in the future, but you will need to wait for the first service pack from MicroSoft.

 

[Mem]

What drivers are you using? try the latest beta 6.49,or 6.47 drivers.

 

[stockjock]

I too had the same problems with BSOD "window protection error". I finally got rid of it by running a FULL scandisk. That stopped it but then the other day I ran the disk defragger and now I get a black screen upon shutdown and the computer won't shut down unless I manually turn it off.

 

[Regalk]

This thread looks dead now - anyway I fixed that problem by updating the det drivers from 6.31 to 6.47 on an MSI 6309 with TNT2. However I have a GF2MX on a Soyo 7VCA system taht has the 6.31 and never a BSOD - go figure

 

[AmdEmAll]

I have the same exact problem. It doesnt have the bsod everytime but almost everytime. So getting the 6.47 drivers fix it? Are they any better then 6.31?

 

[brouillet]

Thanks for the input thus far. Since this is my first PB build, I'm still a bit new to the drivers issues. People keep reffering to thr Det. 6.31, 6.47 and 6.49 drivers, but I'm not clear on what they are talking about? Are these VIA or NVIDIA related? I'm currently using the drivers that came with my Creative Annihilator 2 MX card (4.12). I wasn't sure if I should only use Creative's drivers.

I don't know which VIA 4-in-1 drivers I'm running. How can I determine this?

Thanks, ALL!

 

[AmdEmAll]

You need to get the D3 drivers for you graphics card. Im sure there a lot better then the ones creative gave you. LINK The 4 in 1 patch wont fix it either because I have the latest via 4 in 1 drivers 1.25 I think and I still have the shut down problem.

 

[AmdEmAll]

Damn double post. MEDIAONE SUCKS...

 

[brouillet]

Thanks for the link and info. The NVIDIA web site only appears to offer the 6.31 version, which others have suggested still causes my problem. Where would I get a hold of the newer versions such as 6.47 or 6.49? Thanks

 

[Whitedog]

The problem is you're running 9x crap OS. Format that crappy OS and load Win2000

I, like all of you who are saying "I'm having that problem too!" ran "Me" for about a week. Got Sick of ole BSOD and nuked it.

Windows 2000 is SOOOOO unbelievably stable (for a MS product..hehe) I'll never use another OS... until NT6(?) comes out

 

[TheMasterGhost]

For the latest Det 3 drivers for NVIDIA go here

 

[brouillet]

Thanks to all for your input. I was able to fix the problem simply by updating my Detonator drivers to the 6.49 version.