Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a Gateway P7811FX that dual-boots Win7 and Vista. It was running great for over a year until a few weeks ago when I got my first-ever BSOD. As the title says, the code was 9F, which when I Googled it seems to mostly happen when changing power states (nope) or when using a Firewire hard drive (also nope).

My first suspicion was a driver issue, Win7 still being new-ish and all, and having recently updated my video card drivers, so I booted back into Vista, which I hadn't even touched in almost a month. That ran smoothly for a day or so, but recently it also bluescreened, same STOP 9F error.

I'm starting to get worried -- it's still covered by a BB extended warranty, so if I can prove there's a hardware problem I should be able to get it fixed/replaced in short order, but nothing seems to actually cause the problem. Sometimes it runs through demanding games for hours without a hiccup, then BSOD while I have 3 tabs open in a web browser. Sometimes it bombs out when I'm not even using the computer at all -- I think once it might even have woken from having the screen off (not suspend or hibernate, though) to freeze up.

My main concern is that if I can't reproduce the problem I don't know how to prove that it happens, or determine if it's been fixed after sending it in. What should one do to troubleshoot such a problem, esp. on an integrated system like a laptop, where you can't just start swapping out components until you find the flaky one?

UPDATE: per this post I downloaded and ran BlueScreenView and a) all my BSODs have in fact been 9Fs, b) all have been caused by address "ntoskrnl.exe+71f00" (so I guess my driver theory is out?), and c) there have been 8 on Win7 alone since 11/24, though it seems like it's gotten worse in the last week. Not sure how much that helps, but there you go.

share|improve this question

closed as off topic by quack quixote, BinaryMisfit Jan 24 '10 at 0:32

Questions on Super User are expected to relate to computer software or computer hardware within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

The fact that the blue screen happened in Windows code in no way absolves the drivers - it could be that the driver did something wrong in a call to the OS, which the OS responded to by bugchecking. Further, if BlueScreenView didn't have symbols for the driver, then that reporting may be somewhat wrong, which, given the large + value is not unlikely. – Michael Kohne Jan 23 '10 at 22:28
voting to close as no-longer-relevant. if the OP comes back with new information he can ping the mods and request it be reopened. – quack quixote Jan 24 '10 at 0:12
up vote 0 down vote accepted

Such a problem can be explained in 2 ways: hardware or software.

However, in your particular case I understand that you never had these problems in Vista, that you didn't touch Vista since, but that the same problem is now occurring in Vista.

It is very important that there were no driver updates to Vista, but that it's now BSODing. As Vista and Win7 have the same driver base, if Windows Update was set to auto-update, then this pollutes my above logic. (please confirm that there weren't.)

For me, this is proof enough that the problem is hardware, enough to activate the warranty.

Just to make sure, you may have a look at the Event Log, run memtest86+, and install some monitoring tools:

GPU-Z will tell you the temperature of the video card
SpeedFan for the CPU
Active@ Hard Disk Monitor for the hard disk.

share|improve this answer
I'm pretty sure heat was not the issue; I've had heat problems before and it wasn't even warm to the touch when these happened. I guess the HDD could be a problem, but that's pretty unlikely as each OS runs from a different hard drive and I don't think I was flogging the other OS's hard drive during any of the crashes. I should have an old memtest86+ boot CD lying around somewhere; I'll give it a shot and see if it finds something the Windows 7 boot menu memory test didn't (I ran that and forgot to mention in my OP -- no probs, obviously) – James B Dec 25 '09 at 21:36
And the Event Log? – harrymc Dec 26 '09 at 8:36

Not the answer you're looking for? Browse other questions tagged .