Hi,



i am using Windows Vista 32-bit Bussines editon. I have laptop HP EliteBook 8730w.

This BSOD happen when sending laptop to stand by, reboot, shutdown.

I checked error code on google, and people say that one drivers is not working ok, but i don't know which one.

Could you analise my dump, please?

Thanks in advance,
Dean

Hey,

i don't know which drivers is, because of that i add my minidumps, while i didn't figure out which are causing problems, i thought you could analise my dumps?

Hi,

what can i do in my case to determine which drivers is corrupted ? Do you need any additional informations from my PC?

Most times this error is due to network drivers (as smarteyeball stated) or by video drivers. Beyond that you'll have to use Driver Verifier to see if you can force a crash of the driver that's at fault.

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Automatically select unsigned drivers" and click "Next"
If no drivers show up, then select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Reboot into Windows, turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

Hi,

i enabled verifier on all drivers which are not from microsoft. And reboot server, i hard rebooted while PC didn't shutdown. Then i started, everything went ok, no BSOD when pc was starting. Then i loged in, browsed sth in firefox and check verifier what settings is using and says verify these drivers: all the drivers that i selected. Then i try to reboot laptop, and it didn't do it well, i wait and wait and it came to BSOD, here is the dump.

What can i do ?

This is an issue with the PnP subsystem on your computer. I'll have to do some research on this and get back to you later on tonight.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\FUBAR-RC1-Desktop\Downloads\last_minidump\Mini060809-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
Machine Name:
Kernel base = 0x82848000 PsLoadedModuleList = 0x8295fc70
Debug session time: Mon Jun  8 10:53:36.396 2009 (GMT-4)
System Uptime: 0 days 0:17:14.430
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 258, 0, 0}

Probably caused by : ntkrpamp.exe ( nt!PopBuildDeviceNotifyLis****chdog+27 )

Followup: MachineOwner
---------

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000004, The power transition timed out waiting to synchronize with the Pnp
    subsystem.
Arg2: 00000258, Timeout in seconds.
Arg3: 00000000, The thread currently holding on to the Pnp lock.
Arg4: 00000000

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  4

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82b215d7 to 829150e3

STACK_TEXT:  
8293db4c 82b215d7 0000009f 00000004 00000258 nt!KeBugCheckEx+0x1e
8293db68 828fec40 937d2a10 937d2a00 e6c884c0 nt!PopBuildDeviceNotifyLis****chdog+0x27
8293dc88 828fe876 8293dcd0 68919302 8293dcd8 nt!KiTimerListExpire+0x367
8293dce8 828fe3c3 00000000 00000000 00010305 nt!KiTimerExpiration+0x2a0
8293dd50 828fcedd 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
8293dd54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!PopBuildDeviceNotifyLis****chdog+27
82b215d7 cc              int     3

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!PopBuildDeviceNotifyLis****chdog+27

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  49ac8fb4

FAILURE_BUCKET_ID:  0x9F_VRF_nt!PopBuildDeviceNotifyLis****chdog+27

BUCKET_ID:  0x9F_VRF_nt!PopBuildDeviceNotifyLis****chdog+27

Followup: MachineOwner
---------

The only thing that I've been able to find is this driver that's very, very old:
8598f000 8598f680 giveio giveio.sys Wed Apr 03 22:33:25 1996 (316334F5)

Do you use some sort of port tracker? A search of the web for giveio.sys revealed this link: giveio.sys Windows process - What is it?

Also, this driver is very old:
8fac2000 8fad6a40 aksifdh aksifdh.sys Tue Oct 26 08:18:45 2004 (417E40A5)

It could have something to do with Aladdin security stuff ( Aladdin - Software security, internet security, content security, dongle and USB solutions )

Finally, this is the other very old driver:
ad97f000 ad98e000 DgiVecp DgiVecp.sys Wed Aug 11 02:39:36 2004 (4119BF28)

Links that may apply to it:
dgivecp.sys - At your option
DgiVecp.sys Windows process - What is it?

I'd update these 3 drivers immediately. Also, keep Driver Verifier running to see if there's another BSOD with more info.