To Joe,
I have to thank you beyond words for your post here. I bought an HP
Pavilion 9000 series notebook from Best Buy back in June and it worked
wonderfully until about mid July when I had my first blue screen
(0X0000009f). After about five BSODs, I took it to Geek Squad and they
didn't know what was causing it or what to tell me. I have struggled with
this for MONTHS. It wasn't until last night, and 15 BSODs later, that I
finally got this post on a Yahoo search. I did just as you said and found
the driver that was causing all of the BSODs. It is a driver related to my
built in webcam and unfortunatly the update that Microsoft released for PCT -
Streaming Media and Broadcast - Simplo Webcam in July is the cause. My first
BSOD occurred 3 days after this installation, so I just want to warn everyone
that this is a horrible possibility associated with that update and I do NOT
recommend it. I'm going to try rolling back my driver in hopes of undoing
this change that I did way back in July.
Again, thank you Joe. You don't know how crazy this has driven me over the
past few months and your post help me accomplish something in 4 hours that I
have been working on for months.
Hoping the rollback will work,
Brittany
"Joe Guidera" wrote:
> I suspect items 1 and 2 are the same related issue. What you can do is
> configure Vista so it won't automatically reboot on a blue screen by;
>
> Hit the start button and type "system" or open control panel/system
> Select "advanced system settings"
> Hit the "settings" button under "startup and recovery"
> Uncheck "automatically restart" under "System Failure"
>
> Now, when you machine blue screens it won't automatically reboot any more
> and you can get a better look to see if a specific driver is mentioned.
>
> If not, what you'll need to do is download and install the WINDBG tool from
> Microsoft's web site.
>
> You'll need to run it as an administrator
> Then use it to open the minidump file created that should be stored in
> c:\windows\minidump
>
>
> Issue the following commands:
>
> .symfix
> .reload
> !analyze -v
>
> This should provide you with some information as to the likely driver that
> is causing the blue screen (among other information).
>
> For example below is the output on one of my dumps that pinpoints my problem
> as vmnetsrv.sys (which is part of Virtual PC 2007).
>
> In regards to your question when you attempt to put the machine to
> sleep/hibernate, when the screen goes blank WAIT. Wait at least 10-15
> minutes. It will likely finally blue screen which is useful in determining
> what driver is at fault.
>
> Best of luck,
> Joe
>
> --------------------------------- debug output -----------------------
> 0: kd> .symfix
> No downstream store given, using C:\Program Files\Debugging Tools for
> Windows\sym
> 0: kd> .reload
> Loading Kernel Symbols
> .................................................. .................................................. .................................................. ..........................
> Loading User Symbols
> Loading unloaded module list
> .............
> 0: kd> !analyze -v
> ************************************************** *****************************
> *
> *
> * Bugcheck Analysis
> *
> *
> *
> ************************************************** *****************************
>
> DRIVER_POWER_STATE_FAILURE (9f)
> A driver is causing an inconsistent power state.
> Arguments:
> Arg1: 00000003, A device object has been blocking an Irp for too long a time
> Arg2: 85844510, Physical Device Object of the stack
> Arg3: 8793a030, Functional Device Object of the stack
> Arg4: 892a62d0, The blocked IRP
>
> Debugging Details:
> ------------------
>
> *** WARNING: Unable to verify timestamp for VMNetSrv.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> VMNetSrv.sys
>
> DRVPOWERSTATE_SUBCODE: 3
>
> DEVICE_OBJECT: 8793a030
>
> DRIVER_OBJECT: 879382e0
>
> IMAGE_NAME: VMNetSrv.sys
>
> DEBUG_FLR_IMAGE_TIMESTAMP: 45b74b89
>
> MODULE_NAME: VMNetSrv
>
> FAULTING_MODULE: 8c71f000 VMNetSrv
>
> CUSTOMER_CRASH_COUNT: 2
>
> DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
>
> BUGCHECK_STR: 0x9F
>
> PROCESS_NAME: System
>
> CURRENT_IRQL: 2
>
> LAST_CONTROL_TRANSFER: from 8284ada0 to 828d85c9
>
> STACK_TEXT:
> 8360adf4 8284ada0 0000009f 00000003 85844510 nt!KeBugCheckEx+0x1e
> 8360ae50 82850441 8360af5c 8360af28 00000001 nt!PopCheckIrpWatchdog+0x165
> 8360ae90 828a99d1 82909fc0 00000000 407c8cd0 nt!PopCheckForIdleness+0x33f
> 8360af88 828a9321 00000000 00000000 000d910e nt!KiTimerExpiration+0x498
> 8360aff4 82890d8d 838d7a30 00000000 00000000 nt!KiRetireDpcList+0xba
> 8360aff8 838d7a30 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x3d
> WARNING: Frame IP not in any known module. Following frames may be wrong.
> 82890d8d 00000000 0000001a 00c1850f bb830000 0x838d7a30
>
>
> STACK_COMMAND: kb
>
> FOLLOWUP_NAME: MachineOwner
>
> FAILURE_BUCKET_ID: 0x9F_IMAGE_VMNetSrv.sys
>
> BUCKET_ID: 0x9F_IMAGE_VMNetSrv.sys
>
> Followup: MachineOwner
> ---------
>
> ----------------------------------- debug output ----------------------
>
> "Kcpirana" <> wrote in message
> news:E5C5479C-80D3-47B2-B2FB-...
> > I'm posting this in a few places, so hopefully someone far smarter than I
> > will run across it. I'm at my wits' end and I can't get any assistance
> > from Microsoft or Toshiba on a two-week-old notebook! Here goes:
> >
> > 1) Two or three times, I've gotten a blue screen. The stop error message
> > is pfn_list_corrupt. Vista shuts down and pretty much restarts itself
> > normally. When the boot option menu comes up, it has normal start-up
> > highlighted. In Control Panel>Problem Reports, this appears to be a
> > device driver, but I can't find anything wrong! My printer works (Lexmark
> > 7100 network printer, not directly connected), which is my first suspect.
> >
> > 2) Sleep mode now appears to not even go into effect now. My little power
> > light won't flash amber (which is how you tell your notebook is sleeping
> > on this Toshiba), it just stays active, although the screen goes to black.
> > So, I can't tell if I still have the problem of it not waking up still,
> > because now it won't go to sleep!
> >
> > 3) This is a stupid thing, but I can't read "sign in" to rate or respond
> > to these newsgroups in Windows Mail. I press the Sign In button, but it
> > does nothing! So, I read the post (or create one as I'm doing now), I
> > reply or hit send, and Windows Mail freezes! I have to use Task Manager
> > to restart the program and then sometimes I'm all signed in. Once (only
> > once) I had the pop-up box to sign into Microsoft communities come up, I
> > logged in, the notebook thought a minute and then decided to give me yet
> > another blue screen with the pfn code. I have no idea whether that's even
> > related, but it's aggravating. I would like to be able to use Windows
> > Mail in the way it appears to be intended. I'm going to C&P this before I
> > try to send it, because Windows Mail is going to freeze up again and I'll
> > lose this. (Maybe this is an easy fix and I'm an idiot? - When you read
> > this, I will have frozen and restarted Windows Mail to get it here.)
> >
> > 4) I called Toshiba - they have NO idea except to do a system recovery
> > (which they don't even say will fix the issue and seems to be pretty much
> > their knee-jerk response to everything - the other "fix" was to just not
> > use sleep!). But I've JUST gotten my files all back up to date, I don't
> > have a good way of backing everything up, and I REALLY don't want to start
> > from scratch again!
> >
> > 5) And I'm a little frightened to even try a system recovery, because even
> > though I purchased this computer on 4/26/07, Microsoft's on-line help
> > (which should be free for 90 days from purchase date) tells me my product
> > ID for Vista isn't valid! I had a problem activating it from the get-go
> > and had to call Microsoft and they gave me some other product ID number,
> > which now they tell me is invalid?
> >
> > I'm using a brand-new Toshiba Satellite A205-S4577, 1 gb ram, and it came
> > with Vista Home Premium preinstalled. I haven't installed much of
> > anything, except Office 2007, iTunes (has worked), a Palm (not working,
> > but did), and my network printer (working). Any help anyone can offer
> > would be GREATLY appreciated!
> >
> >