Hallo,
Ik heb de laatste tijd veel Bluescreens en heb er eens een geanalyseerd. Maar kan er niet echt wijzer van worden wat nu precies de bluescreen veroorzaakt.
Ik hoop dat iemand van jullie hier iets uit kan opmaken?
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030315-22796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Ik heb de laatste tijd veel Bluescreens en heb er eens een geanalyseerd. Maar kan er niet echt wijzer van worden wat nu precies de bluescreen veroorzaakt.
Ik hoop dat iemand van jullie hier iets uit kan opmaken?
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030315-22796-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Code:
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\Debugger symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Symbol search path is: SRV*C:\Windows\Debugger symbols*[url]http://msdl.microsoft.com/download/symbols[/url]
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 9600.17630.amd64fre.winblue_r7.150109-2022
Machine Name:
Kernel base = 0xfffff803`cf606000 PsLoadedModuleList = 0xfffff803`cf8df250
Debug session time: Tue Mar 3 15:31:50.662 2015 (UTC + 1:00)
System Uptime: 0 days 0:03:09.362
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, ffffe0003fdba060, ffffd00057035960, ffffe00044265b10}
Probably caused by : pci.sys
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe0003fdba060, Physical Device Object of the stack
Arg3: ffffd00057035960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00044265b10, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffe0003fde76c0
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4
MODULE_NAME: pci
FAULTING_MODULE: fffff801cf5a3000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
DPC_STACK_BASE: FFFFD0005703CFB0
STACK_TEXT:
ffffd000`57035928 fffff803`cf80ee3e : 00000000`0000009f 00000000`00000003 ffffe000`3fdba060 ffffd000`57035960 : nt!KeBugCheckEx
ffffd000`57035930 fffff803`cf80ed5e : ffffe000`46588f08 00000000`00000001 ffffe000`46588f40 fffff803`cf6b9515 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`57035990 fffff803`cf6ba428 : 00000000`00000000 ffffd000`57035ae0 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`570359e0 fffff803`cf75a4ea : ffffd000`57020180 ffffd000`57020180 ffffd000`5702c3c0 ffffe000`4380b880 : nt!KiRetireDpcList+0x4f8
ffffd000`57035c60 00000000`00000000 : ffffd000`57036000 ffffd000`57030000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.17238
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_image_pci.sys
FAILURE_ID_HASH: {a89ab2d1-2459-89ee-9990-558bbc68ffab}
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe0003fdba060, Physical Device Object of the stack
Arg3: ffffd00057035960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00044265b10, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffe0003fde76c0
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4
MODULE_NAME: pci
FAULTING_MODULE: fffff801cf5a3000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
DPC_STACK_BASE: FFFFD0005703CFB0
STACK_TEXT:
ffffd000`57035928 fffff803`cf80ee3e : 00000000`0000009f 00000000`00000003 ffffe000`3fdba060 ffffd000`57035960 : nt!KeBugCheckEx
ffffd000`57035930 fffff803`cf80ed5e : ffffe000`46588f08 00000000`00000001 ffffe000`46588f40 fffff803`cf6b9515 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`57035990 fffff803`cf6ba428 : 00000000`00000000 ffffd000`57035ae0 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`570359e0 fffff803`cf75a4ea : ffffd000`57020180 ffffd000`57020180 ffffd000`5702c3c0 ffffe000`4380b880 : nt!KiRetireDpcList+0x4f8
ffffd000`57035c60 00000000`00000000 : ffffd000`57036000 ffffd000`57030000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.17238
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_image_pci.sys
FAILURE_ID_HASH: {a89ab2d1-2459-89ee-9990-558bbc68ffab}
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe0003fdba060, Physical Device Object of the stack
Arg3: ffffd00057035960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00044265b10, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffe0003fde76c0
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4
MODULE_NAME: pci
FAULTING_MODULE: fffff801cf5a3000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
DPC_STACK_BASE: FFFFD0005703CFB0
STACK_TEXT:
ffffd000`57035928 fffff803`cf80ee3e : 00000000`0000009f 00000000`00000003 ffffe000`3fdba060 ffffd000`57035960 : nt!KeBugCheckEx
ffffd000`57035930 fffff803`cf80ed5e : ffffe000`46588f08 00000000`00000001 ffffe000`46588f40 fffff803`cf6b9515 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`57035990 fffff803`cf6ba428 : 00000000`00000000 ffffd000`57035ae0 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`570359e0 fffff803`cf75a4ea : ffffd000`57020180 ffffd000`57020180 ffffd000`5702c3c0 ffffe000`4380b880 : nt!KiRetireDpcList+0x4f8
ffffd000`57035c60 00000000`00000000 : ffffd000`57036000 ffffd000`57030000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.17238
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_image_pci.sys
FAILURE_ID_HASH: {a89ab2d1-2459-89ee-9990-558bbc68ffab}
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe0003fdba060, Physical Device Object of the stack
Arg3: ffffd00057035960, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe00044265b10, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffe0003fde76c0
IMAGE_NAME: pci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1d4
MODULE_NAME: pci
FAULTING_MODULE: fffff801cf5a3000 pci
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
DPC_STACK_BASE: FFFFD0005703CFB0
STACK_TEXT:
ffffd000`57035928 fffff803`cf80ee3e : 00000000`0000009f 00000000`00000003 ffffe000`3fdba060 ffffd000`57035960 : nt!KeBugCheckEx
ffffd000`57035930 fffff803`cf80ed5e : ffffe000`46588f08 00000000`00000001 ffffe000`46588f40 fffff803`cf6b9515 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`57035990 fffff803`cf6ba428 : 00000000`00000000 ffffd000`57035ae0 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`570359e0 fffff803`cf75a4ea : ffffd000`57020180 ffffd000`57020180 ffffd000`5702c3c0 ffffe000`4380b880 : nt!KiRetireDpcList+0x4f8
ffffd000`57035c60 00000000`00000000 : ffffd000`57036000 ffffd000`57030000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 6.3.9600.17238
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_pci.sys
BUCKET_ID: 0x9F_3_IMAGE_pci.sys
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_image_pci.sys
FAILURE_ID_HASH: {a89ab2d1-2459-89ee-9990-558bbc68ffab}
Followup: MachineOwner
---------
1: kd> !drvobj ffffe0003fde76c0 f
fffff803cf8c6870: Unable to get value of ObpRootDirectoryObject
fffff803cf8c6870: Unable to get value of ObpRootDirectoryObject
Driver object (ffffe0003fde76c0) is for:
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
\Driver\pci
Driver Extension List: (id , addr)
Device Object list:
ffffe0003fdfd060: Could not read device object
DriverEntry: fffff801cf5aae20 pci!GsDriverEntry
DriverStartIo: 00000000
DriverUnload: fffff801cf6bdb40 sptd
AddDevice: 00000000
Dispatch routines:
[00] IRP_MJ_CREATE fffff803cf701898 nt!IopInvalidDeviceRequest
[01] IRP_MJ_CREATE_NAMED_PIPE fffff803cf701898 nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE fffff803cf701898 nt!IopInvalidDeviceRequest
[03] IRP_MJ_READ fffff803cf701898 nt!IopInvalidDeviceRequest
[04] IRP_MJ_WRITE fffff803cf701898 nt!IopInvalidDeviceRequest
[05] IRP_MJ_QUERY_INFORMATION fffff803cf701898 nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION fffff803cf701898 nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA fffff803cf701898 nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA fffff803cf701898 nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS fffff803cf701898 nt!IopInvalidDeviceRequest
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION fffff803cf701898 nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION fffff803cf701898 nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL fffff803cf701898 nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL fffff803cf701898 nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL fffff801cf5a8e98 pci!PciDispatchDeviceControl
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL fffff803cf701898 nt!IopInvalidDeviceRequest
[10] IRP_MJ_SHUTDOWN fffff803cf701898 nt!IopInvalidDeviceRequest
[11] IRP_MJ_LOCK_CONTROL fffff803cf701898 nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP fffff803cf701898 nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT fffff803cf701898 nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY fffff803cf701898 nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY fffff803cf701898 nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER fffff801cf5a4900 pci!PciDispatchPnpPower
[17] IRP_MJ_SYSTEM_CONTROL fffff801cf5c7808 pci!PciDispatchSystemControl
[18] IRP_MJ_DEVICE_CHANGE fffff803cf701898 nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA fffff803cf701898 nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA fffff803cf701898 nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP fffff801cf5a4900 pci!PciDispatchPnpPower
Laatst bewerkt door een moderator: