W2K Shutdown/Restart problem after registry change

Gigabyte GA7DPXDW-P, latest bios Windows 2000 SP2 LSI 53C1030 SCSI HDA All motherboard drivers installed. I thought that it might be a good idea to wipe the pagefile before shuttingdown or restarting, so I enabled the following: Administrative Tools > Local Security Policy > Local Policies > Security Optio ...

Everything New Technology 1823 This topic was started by ,



data/avatar/default/avatar40.webp

3 Posts
Location -
Joined 2003-03-04
Gigabyte GA7DPXDW-P, latest bios
Windows 2000 SP2
LSI 53C1030 SCSI HDA
 
All motherboard drivers installed.
 
 
I thought that it might be a good idea to "wipe"
the pagefile before shuttingdown or restarting, so
I enabled the following:
 
 
Administrative Tools > Local Security Policy >
Local Policies > Security Options > Clear
virtual memory pagefile when system shutsdown
 
 
I found that this took longer to do than I would suffer,
so I disabled it. That's when the problem occured.
 
When doing a shutdown or restart, the system just "sits"
after the message "Windows is shutting down." The hardrive
becomes active for a second or so, then...it just
hangs there. I need to press the reset button.
 
I removed the AGP, PCI bridge and IDE busmaster drivers and
reinstalled just the AGP and PCI bridge drivers. No joy.
 
 
Open to suggestions.

Participate on our website and join the conversation

You have already an account on our website? Use the link below to login.
Login
Create a new user account. Registration is free and takes only a few seconds.
Register
This topic is archived. New comments cannot be posted and votes cannot be cast.

Responses to this topic



data/avatar/default/avatar40.webp

3 Posts
Location -
Joined 2003-03-04
OP
Yes, I checked this as you requested and the value is"0"
 
Perhaps I should just reinstall.
 
Thanks for the reply.


data/avatar/default/avatar40.webp

3 Posts
Location -
Joined 2003-03-04
OP
For what it's worth:
 
I restarted in "safe" mode and when I chose "restart," it worked; did not
need to press the reset button.
 
So, is this a driver problem? If so, which?
 
Very wierd.