BSOD on Shutdown (W2k-pro)

BradH4

Junior Member
Nov 11, 1999
15
0
0
Every time I restart or shutdown Windows, I get a blue screen which says something on the order of "Driver_Power_State_Failure" It seems to me that this is a power management issue, but I disabled power management in the BIOS, and the problem still occurs. I have an Abit VP6 w/ Dual 700's@1000 and 256MB PC133 CL2 RAM if that helps.
Thanks for any help.
 

loosbrew

Golden Member
Oct 30, 2000
1,336
1
0
try not overclocking the cpu and see what happens. and also check in your apm in windows to see if it is set or not, the bios wouldnt override the win2k settings, i would think.


hth

looooo
 

BradH4

Junior Member
Nov 11, 1999
15
0
0
Thanks for the advice, but setting the speed to default didn't work. I looked for a way to set the Advanced Power options in Control Panel to enable/disable the APM, but I couldn't find anything, I think that is the problem.
 

Panther505

Senior member
Oct 5, 2000
560
0
0
Look in the Device Mangler and let us know what it shows under Computer-- That will tell you what w2K thinks it is.. Also is this a clean install or was the system tranplanted from another MB? If it was a transplant then I would suggest a clean install as the issue may be what W2K saw when it installed on the previous installation.
 

BradH4

Junior Member
Nov 11, 1999
15
0
0
In device manager, under "Computer" it says "ACPI Multiprocessor PC". And yes it is a clean install with the new mobo. Actually I did a clean reinstall a couple times trying to fix the problem, but the error kept happening. Could it be DirectX8 or the video drivers? I am using the v7.17 nvidia drivers. I'll try some earlier drivers and let you know. Thanks for your help!!
 

BradH4

Junior Member
Nov 11, 1999
15
0
0
I took one last look at Microsoft's site and it said to disable CDR4VSD in the device manager under View, show hidden devices. Apparently EZ CD Creater v3.5 or earlier causes problems with W2K. I disabled the CDR4VSD in device manager and there was no BSOD!!!! I then uninstalled my version 3.5 and replaced it with v4.0 and it continues to work. Thanks for the tips everyone!