BSOD After Long Period Of Shutdown On Startup, Random Power Shut Off
Dec 12, 2011
My computer gets at least ONCE BSOD every time I turn it on after a long period of shutdown. It also sometimes randomly just shuts off or give me additional BSODs. It has got to the point that I can't even load to windows recently, which lead me to reformat my computer. I know the drivers here are not the latest ones, I am trying to use only the drivers from the CDs that came with the hardwares because the last time I used all the latest ones it still caused BSODs. I am not sure what other information I need to post up.
Windows 7 Ultimate x64 - fresh reformat
ASUS M4A77TD Pro
AMD Athlon II X4 635 2.9Ghz Socket AM3 95W
Crucial 4GB DDR3-1333 (PC 10600) MT16JTF51264AZ-1G4H1 (It's a 2x 4GB set, but I'm just using once at the moment to filter out problems)
SAPPHIRE Vapor-X Radeon HD 4850 1GB 156-bit GDDR3
Western Digital Caviar Black 640GB 7200RPM SATA
Antec Trupower 650W
Windows 7 home premium pretty sure it is an X64 Randomly shuts OFF not DOWN, then when upon restart (manually pushing the power button) it opens like normal put my login password in and it opens fine then reopens the last program running automatically.
i used to get the BSOD very often so i decided to recover the system to the initial state . i did that and everything was fine , then i updated the windows 7 service pack 1 and finished the installation and rebooted my computer , the start-up at least took half an hour at that time and the service pack 1 installation showed "not successful " i tried to again to update the service pack1 which showed 73.6mb - 892.6mb so i updated it again and again the same thing happened.
I recently built a pc but been having random BSODs. I have updated all my drivers to the latest versions. The most recent BSOD I got is today while surfing the net.
It displayed MEMORY_MANAGEMENT and fltmgr.sys
My PC Specs: i5 3570k z77 extreme4 corsair vengeance low profile ram (2 x 4gb) sapphire 7850 (non oc version) 128gb crucial m4 ssd / 500gb sata2 seagate hdd antec 620m psu windows 7 home premium 64 bit
If the computer is shut down and disconnected from the power supply for about 5 hours or longer I get a bluescreen right after the windows boot screen. Otherwise it starts without problems and works fine. My workaround for the problem after long shut down is to switch on the power supply, then immediately switch it off and then on again. This works always fine!
My System:
Windows 7 Home Premium 64bit SP1 AMD Phenom II X6 1090T Black Edition Asus M4A89GTD PRO/USB3 4GB (2x2) 1333-777 RAM ATI Radeon HD 5570
Blue Screen: *** STOP: 0x0000001E (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)
I already used all of the windows debugging, diagnostic tools and Memtest but without success.
Been having some crashes.At first they occurred on start up. Claiming the computer wasn't properly shut down. Now today, the other crashes started, with the first happening out of nowhere, the second happening upon starting a video game. I've been without crashes for a while now, only having used my browser(Opera) and copying some files to an external hard drive. As well as the SF tool.I only have 2 dump files available. SF tool file should be in attachments, unless I made a mistake somewhere
Why does my screen sometimes goes blank after a period of inactivity ( like 8 hours )? And sometimes not!. My monitor screen just turns off ( yellow light ). Then i just turn my mouse and screen goes back to normal. ITS TOTALLY RANDOM!
I disabled the screen saver and I disabled the option of the OS turning off the screen. Yet, the screen will still turn itself off after a period of inactivity. I'm currently using a Asus Monitor 19'
my pc is: 7 3770k 3.5 ghz Asus Gtx 680 Asus Sabertooth Z77 2x4gb ram DDR3 Corsair Vengeance White 1600 LP Arctic Be Quiet Dark Power Pro 1000W drivers 301 WHQL.
I have a problem with my PC. It's running Windows 7 Ultimate 32 bit, with ATI Radeon 4600. When I was working in Google Sketch Up, BSOD with 0x0000009f appears. Here you have a zip file with minidumbs?
I am getting a BSOD sometimes when I shut down my computer. My computer has to be on and idle for a while (close to 4 hours) for this to happen. I never put my computer to sleep or hibernate. Can anyone do a minidump check to see what is going on? I tried to do this myself but there is issues with the symbols. (Which one should I use for x64 Windows 7).
I'm hoping someone could give me some pointers on how to go about investigating my PC switching itself off after approximately 10 minutes of inactivity (not sleeping, as Windows is configured to do after 30 mins). The PC is used as a media centre with xbmc running as the frontend.If I leave the computer unattended whilst in XBMC. the computer will switch off after approximately 10 mins. I haven't (yet) checked if it happens outside of XBMC, though I suspect it will.The eventviewer shows: The previous system shutdown at <time> on <date> was unexpected.But nothing else of significance.The reason I'm convinced this is software related is because the shutdown always occurs around about 10 mins after leaving the PC alone, with no input. I havent timed it precisely, but will do so when I next get a chance.If I am using the PC in any way, or watching a film, it does *not* shutdown. There are no errors apart from that in the eventviewer log - i.e. no boot menu when you power back on to recommend safe mode, no message on starting windows to say it shutdown unexpectedly. I havent actually observed the shutdown myself yet, so Im not sure if there is a bluescreen or not.
I have a rig I use occasionally, as HTPC and occasional mule work, file service, etc.I would like to not have it simply sleep when I have left it running and not returned, but rather have it shutdown properly.Is there a way to do this within Windows 7 controls, or is there an aftermarket, shareware, or scripting way to do so?
I've got randomly occouring BSODs on my Dell XPS 9000. The BSOD is always a driver power state failure. My system is ~3 years old. Running a 2 year old Win 7 Ultimate x64 image.
I've experienced some issue with my PC recently and formatting it didn't help. Please find attached the required files. The BSOD are essentially random, and sometimes when I power up the PC, it just doesn't startupt, staying stuck in the BIOS or something. I have an Acer predator, Windows 7 64 bits (OEM)
I have been getting random BSOD every day almost every 30 or 15 mins.I think it is hardware problem becouse even on fresh windows 7 install it still getting BSOD.
PC Specs:
OS NameMicrosoft Windows 7 Professional Version6.1.7601 Service Pack 1 Build 7601 Other OS Description Not Available OS ManufacturerMicrosoft Corporation System NameGOSHET0-PC System ManufacturerBIOSTAR Group System ModelP31-A7
I've been having increasing problems with my Asus g73jh. Love the performance, but been having random crashes concerning video i assumed. Updated the graphics drivers as well as ran a bios flash on the laptop. The unit always has a problem with being moved and I just moved it for the first time in around 6 months (been using it connected to my screen in living room) to bring to class and it crashed with a page fault error when I arrived at class, then again with another bsod when I got home and unpacked it.
I use my PC for audio production and I have a few external controller devices that are USB powered, for example a midi keyboard. I recently had to build PC due to a theft....long story short after building the new PC I've noticed that my USB buses have continual power to these external devices after I've powered down the PC. My old windows 7 PC did not do this. Is there a setting I can change to shut off power to the USB buses when I power off the PC? Or is this a hardware issue?
Ever since I got my Dell Inspiron 15r a few months ago I've been getting random blue screens of death, about every 1-2 weeks.I've tried using Google to find a solution but I can't seem to find the right one for my situation, so I came here.They do NOT happen when I boot up the computer. Usually it's when I close the display, I'll leave it on and later find it with the blue screen.I got BlueScreenView so I have a few details available.It's always "DRIVER_POWER_STATE_FAILURE" and caused by ntoskrnl.exe+8207a
this is the second time I've gotten this message in the last 3 days and both times my Pc was turned on and left when I was absent. Here are the details!
It seems i have narrowed down my issue that I have been dealing with for it seems like months now. Well essentially my system will reboot anytime it sits for an extended period of time (about 15 to 20 Minutes). My computer will go into standby mode. I do have it set for my computer to never sleep but only my screens. I have followed the BSOD instructions and do and those to attach to this post. Here is the additional information regarding this problem... Is Windows 7 . . . - x86 (32-bit) or x64 ? - x64 - the original installed OS on the system? Yes - an OEM or full retail version?Full retail version - What is the age of system (hardware)? Eh, varies video cards about a year old, memory and hardrives are about the same length of time. Chip is fairly new within a few months. - What is the age of OS installation (have you re-installed the OS?) OS was freshly reinstalled on 11/17/2011. All drivers for all pieces of hardware in my machine have had the newest drivers updated, including my video cards. I have also done the BIOS update for both of my video cards available from Palit. Oddly enough i can play Starcraft II for hours and no issue with rebooting... only when it sits for an extended period of time as mentioned earlier.
Over the past 2 years my PC has been afflicted with random power off/power on/reboot events.It will go for months without these and then have multiples of the events in a day. (I had 8 of them 3 days ago.)I assume I have a hardware problem, but nothing has been found and I'm grasping at straws.The time between power off and power on is several seconds.I had assumed this rules out a software cause, but maybe I'm wrong. I know Windows can schedule a power off, but can it tell BIOS (or something) to power back on in a few seconds?I know blaming the power supply is a much more simple explanation, but then I'm left with explaining the intermittent nature of the failure.
My computer shutting Down has been staying on longer than it used to. Please let me know what I need to do to make it run faster again like when after I first bought it
- Running windows 7 home premium - Latest windows 7 updates
Some extra information - when my wireless signal for the wireless keyboard goes out (randomly), the usb port (usb extension) stops working for that port, however if you take it out and replug, still doesn't work. only way to "fix" this is by force restarting by turning it off with the power button (I can't even shutdown because it hangs there anyways).
I'm not sure what it could be, whether its new windows update, or new applications I installed (well, I don't really install many new apps, and i have roughly the same things I did when I first got my laptop). Its literally impossible to shutdown it successfully (well i never decide to wait ages, but if the laptop doesn't shut down in a few mins, something has to be wrong) - same applies to the restart, both doesn't work unless I force it with the power button.
Here's an example below: Windows has shutdown: Shutdown Duration : 19478ms IsDegradation : false Incident Time (UTC) : 05T16:35:07.937364300Z
Some of the applications I use are trivial (like trillian, skype, steam, etc) and i've had all these programs before and it was fine, able to shut down and so on.
Gateway DX4850 i5 2300 CPU 2.8 GHZ 6GB RAM 64 bit operating system Windows 7 Home Premium Service Pack 1
This problem started about 2 months ago. Windows takes a long time to shut down, at least 5 minutes. Sometimes it doesn't shut down and reboots.Every shuts down normally, then the grey screen "SHUTTING DOWN" just seems to hang.On one recommendation I updated the BIOS, that didn't seem to work.I scanned in safe mode with Malware Bytes Anti Malware and the computer is clean. I use AVAST antivirus.
For the last 2 days i have been trying to diagnose why my PC is taking anything between 1min 30sec and 3min to shutdown.I found that if i booted into my desktop (fully loaded) then shut down, my shutdown time is between 9 and 12 seconds! However if i boot into desktop then use any program or game, then i had the long shutdown time.Event log showed the ShutdownKernelTime to be between 120000 and 150000 when i had the long shutdowns.For your info, for testing purposes the programs i used are firefox 10.0 (opening 3 websites) and Windows Live Mail. IF for any reason i got a successful quick shutdown after running these i then ran GTA IV for 5min then tried a shutdown.So far i have tried: Disabling all services and startup entries in msconfig. Got same results as above Various combinations of service and startup entries in msconfig. Same result as above Booting into safe mode running same test. I get a successful quick shutdown. Checked the registry for any page file clearing at shutdown. Complete disk defrag Advanced System Care 5 Scan and repair Updating any drivers if update available Running a shutdown trace using Windows SDK. This however works by restarting the PC then running the trace so imitates me booting in to desktop and shutdown again which works fine so as expected the trace shows everything working as it should. I tried adding firefox and Windows live mail to startup folder hoping just the simple opening of these programs would cause whatever happens to give me a long shutdown time. It seems though like i need to open the 3 websites to create the issue however the only time to do this would be the delayed shutdown stage which im advised you shouldn't touch anything at this stage? could anyone advise on this? Hopefully one of you's out there with a bit more knowledge can point me in a new direction that puts me closer to solving this.I used to have Ntune (Nvidia) for GPU Fan control and MSI Afterburner for GPU Overlocking, however after trying one after the other enabled/disabled etc i found i got successful quick shutdowns but long shutdown then returned after playing GTA IV. I uninstalled MSI Afterburner and now only use Ntune for both GPU Overcloking and Fan Control. Current Startup's enabled:Realtek HD Audio Manager RocketDock NVIDIA Ntune Avast Antivirus Quote Originally Posted by whs In regedit,navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControl Double click on WaitToKillServiceTimeout and set it to 2000 - that is milliseconds. Then OK. Initially solved the long shutdown if i used my programs as detailed above but has since returned after using the programs for a longer time and watching a HD game review.
I'm currently pissed off about tmy unit which is taking too long to shutdown. I've tried the methods posted here to lessen the startup time and shut-down time of a computer but it only affected the booting process. when I shutdown it still takes that long even with the tweaks.
my new windows install has suddenly started to take several minutes to shutdown. I only had a few programs installed when this started. I un-installed each program and did a registry clean to see if any of them was causing the issue, but nothing helped. All that are now installed are the motherboard drivers and such.
This is a list of what is still installed:
Etron USB3.0 Controler Intel Control Center Intel HD Graphics Driver Intel Management Engine Intel Rapid Storage Realtek Ethernet Realtek Audio Driver
I have gone through some things to try to determine what is causing the issue, but have had no success. I checked the shutdown performance logs, and there were allot of warnings. These just seemed to give the shutdown time, but no indication of what was causing the delay. This issue did not exist when I first installed. The computer has no internet connection at the moment, so I have not done windows update or anything like that. There is no possibility of their being a virus for the same reason.Before uninstalling the apps, I tried msconfig with selective startup (all boxes unchecked), and diagnostic startup and neither reduces the shutdown time.
