G
Guest
For the last three days I have had this problem. I have not added any
programs or devices in that time.
At the end of the day when I shut Windows down I get to the screen where it
says "Windows is Shutting Down" and it begins to beep...about a beep per
second. It hangs there and continues to beep. It never shuts down. I end
up pressing and holding the power button until it turns off. The next time I
boot I do not get any error screens saying Windows did not shuit down
properly or anything like that. It boots perfectly and runs all day
perfectly. The only indication that there is a problem is during shutdown.
I am using a HP Pavillion zv5000 with 1 g or ram. The only upgrade I have
done to this computer was the ram, from 512 m to 1 g. I have several
peripherals connected by USB...printer, floppy drive, wireless keyboard and
mouse, scanner. But they have all been hooked up since the day I purchased
this laptop, back in Feb 05. No new programs or devices since.
I can't tell if this is a copmputer problem or a Windows problem. Any tips
on where to begin troubleshooting?
Thanks,
Nate
programs or devices in that time.
At the end of the day when I shut Windows down I get to the screen where it
says "Windows is Shutting Down" and it begins to beep...about a beep per
second. It hangs there and continues to beep. It never shuts down. I end
up pressing and holding the power button until it turns off. The next time I
boot I do not get any error screens saying Windows did not shuit down
properly or anything like that. It boots perfectly and runs all day
perfectly. The only indication that there is a problem is during shutdown.
I am using a HP Pavillion zv5000 with 1 g or ram. The only upgrade I have
done to this computer was the ram, from 512 m to 1 g. I have several
peripherals connected by USB...printer, floppy drive, wireless keyboard and
mouse, scanner. But they have all been hooked up since the day I purchased
this laptop, back in Feb 05. No new programs or devices since.
I can't tell if this is a copmputer problem or a Windows problem. Any tips
on where to begin troubleshooting?
Thanks,
Nate