New
#1
Random BSOD, Freeze, or Black Screen Minutes After Startup
Hi All,
First post here, but have visited often over the years to learn about various subjects. Lately, I've been frequenting the many helpful BSOD pages thanks to the problem that is the subject of this thread. I'm hoping you wizards can help me pinpoint the offending driver or hardware before I resort to random uninstalls and eventually a clean Windows reinstall as more extreme procedures. I know what follows is a read, but it's hopefully well-written, so please bear with.
First, the System Specs
Specs are in my profile. Basically, this is a heavily upgraded OEM, the HP m9252p:
HP Pavilion Elite m9252p Desktop PC Product Specifications HP Pavilion Elite m9252p Desktop PC | HP® Support
The current configuration ran smoothly for over six months before the problem appeared. With the exception of the graphics card (more on that below), the most recent changes were the addition of the two HDDs at the beginning of this year, when migrating to SSD. Before that, the machine was completely problem free going back to its inception in 2008 (she's an old girl, I know).
The Mystery
Currently, the system is at a point where it always freezes, throws a random BSOD, or the screen goes black (monitor goes to sleep) within minutes after startup. It almost always happens within five minutes after the desktop loads, but occasionally up to ten minutes. This always requires a forced restart with a chance of one of these problems occurring again following reboot, for an unpredictable number of times. What began as typically a single occurrence has since become on average two crash/reboot cycles. The record was four.
Once the system is running for at least five minutes (the mystical "five minute rule" as I've come to know it), it works fine. I can leave it idle, or punish it with maxed out (ultimate) settings in Skyrim for hours on end, and it won't so much as hiccup. But after being shut down or in sleep mode for at least some hours, the startup problem always resurfaces in whichever flavors and quantities it decides to take. In all, it's a tolerable nuisance, but one that's surely the manifestation of one or more drivers or hardware gone wild.
Like the worst computing problems, this one arose seemingly out of the ether and has been in a downward spiral since. The variety and frequency of crashes seems to have gotten progressively worse over the more than two months since the problem first appeared. As far as I can tell, it all started with a sudden freeze on July 21 that had me thinking my wireless mouse and keyboard batteries needed replacing. Weeks went by with no problems, until the black screens started occurring. Still, these were intermittent and occurred days or weeks apart. Before long, the first BSODs started appearing. These were also intermittent, at first.
As time went on, it got to the point at which things are now. For basically the entire month of September, there have been one or more BSODs almost daily (uploaded for your debugging pleasure), but in any case, always one or more of the three types of crashes (freeze, BSOD, or black screen) shortly after startup.
Today's session went like this: (1) Freeze three minutes in, forced-reboot; (2) BSOD some minutes in, forced reboot; (3) different BSOD seven minutes in (broke the "five minute rule", I know!), forced reboot; (4) up and running six hours and counting. Each day the experience is different (last night was a black screen and BSOD), but the one constant is the crash(es) almost always occur within five, occasionally ten minutes post startup. Or at least that was the case until yesterday when the system threw a curve ball with a BSOD twenty minutes in. I pray this isn't a new symptom. So far, the two startups since then have remained true to the five (five to ten?) minute rule.
The Detective Work
Needless to say, I have tried everything I can think of in this harrowing driver/hardware whodunit. I started off investigating the basics. There were no manual changes to software, drivers, or hardware immediately prior to the first occurrence. If software or drivers are to blame, it's likely the result of one of those pesky auto- or frequent updaters. I'm looking at you Adobe Flash, Reader, Java, and MS Updates. I deliberately install the aforementioned updates manually, but if one of them, or one like them, caused the problem, it's a latent effect the likes of which are hard for me to trace.
I may have updated the Nvidia graphics and Realtek audio drivers once or twice each in recent history before the problem first arose in July, but it was a while before—three months prior for Realtek and at least a month prior for Nvidia. Besides, aren't we always told to make sure we have the latest drivers? I know driver updates can cause problems as often as they fix them, so I do make it a point to "test drive" them for a while before allowing them to stick around. If a driver update is to blame, again, the path to destruction was surely insidious.
Other measures I've looked into on the software/driver side of the coin include:
- System restore - Not an option because the oldest restore point is 7/30, after the 7/21 onset.
- Clean startup - Based on this tutorial: Troubleshoot Application Conflicts by Performing a Clean Startup. Problem still occurs, suggesting hardware.
- Safe mode - Problem still occurs, suggesting hardware.
- Startup repair – Inspired by: Startup Repair - Run 3 Separate Times. Problem still occurs, suggesting hardware.
- Antivirus/antimalware scans: Ran full tests with both MSE and MBAM as suggested throughout this forum. Nothing but a couple potential Java exploits (damn you Java!). Confession: I've been living dangerously for years with no antivirus software; just router and Windows firewalls and common sense. Based on the essentially clean scan results, I seem to have done okay.
Over the course of this lovely mystery, I've gone back and forth on thinking the cause is software/driver-related versus hardware-related. The progressive nature of the problem certainly suggests dying hardware (a real possibility given some of the core components of this machine have been in use since 2008: motherboard, CPU, power supply). But I find it paradoxical that the problem is limited to shortly after cold startup, and there are never problems under stress (e.g., the aforementioned nonstop hours of gaming). Nonetheless, I've done the essential hardware tests, all of which have come up clean:
- Windows Memory Diagnostic and MemTest86 RAM tests overnight, twice
- Chkdsk, HD Tune, and manufacturer utility checks of both HDDs
- HWiNFO shows temps within normal, even during stress
I've avoided running actual hardware stress tests (e.g., Prime95, IntelBurnTest) because the problem does not seem stress-related at all. Unless somehow the system is more stressed five minutes after cold startup than it is hours into maxed out gaming.
I should also mention that I actually upgraded the graphics card in August, partially hoping it would eliminate the problem. It didn't, and since the problem existed before and after installation, I'm confident ruling out the graphics card itself, though not necessarily the drivers (which are currently up to date).
I've done no overclocking of any kind (and can't with the OEM BIOS).
Finally, I've tried to make sense of the ample BSOD minidumps using BlueScreenView and WinDbg, but to put it simply, they're all over the place. Just about every major hardware driver has been implicated at one point or other, and the logs comprise a veritable who's who of bug checks. I've read that the abundance of Microsoft drivers being implicated suggests hardware failure, but don't know how to narrow it down. However, my expertise at combing minidumps is quite limited, and I hope someone with more experience sees something I don't.
Off hand, is there any specific hardware failure one might suspect given that the problem consistently occurs shortly after cold startup, but never after? I've never experienced power supply failure. Is it likely that? My other "gut feeling" suspect is the Intel Rapid Storage Technology controller driver I installed in March to address an issue where the system would hang coming out of sleep after installing the SSD (doing so worked).
Of note, the SATA controller mode also changed itself from AHCI to RAID when I installed the two HDDs in January, and I cannot switch back to AHCI in the BIOS without Windows failing to load. I've researched this and learned that a clean Windows installation is required to go back to AHCI. So for now, things remain in RAID, even though no array is set up. No idea if this has anything to do with the problem, but it's been like this since the beginning of this year, nearly seven months before the problem surfaced.
Thanks in advance for reading this novel. Any help is greatly appreciated.