0
Windows Vista Home Premium Bluescreen ( VISTA DRIVER FAULT )
Hallo Leute,
wollte mich mal hier erkundigen ob ihr mir helfen könnt.
Hatte grad mal ein Bluescreen und möchte gerne wissen woran es lag..
Hoffe ihr könnt mir helfen.. er passierte wirkürlich.. einfach so.. keine ahnung :\
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x82239000 PsLoadedModuleList = 0x82350c70
Debug session time: Wed Oct 1 19:57:48.511 2008 (GMT+2)
System Uptime: 0 days 21:51:27.731
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, 805d1120, 1}
* ERROR: Module load completed but symbols could not be loaded for sptd.sys
* ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
* ERROR: Module load completed but symbols could not be loaded for acehlp10.sys
Probably caused by : sptd.sys ( sptd+1516a )
Followup: MachineOwner
0: kd> !analyze -v
*
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 805d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
Debugging Details:
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x101
PROCESS_NAME: System
CURRENT_IRQL: 1c
LAST_CONTROL_TRANSFER: from 822f1321 to 82306163
STACK_TEXT:
8232e850 822f1321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8232e884 822f102d 000aa81b 000000d1 8232e944 nt!KeUpdateRunTime+0xd5
8232e884 822f0cc0 000aa81b 000000d1 8232e944 nt!KeUpdateSystemTime+0xed
8232e910 8223f671 0000000e 8223f712 8a2ac890 nt!KiIpiSendPacket+0xac
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 nt!KeIpiGenericCall+0x6e
8232e990 8a2ad16a 0000001f 8a2ac75c 8232e9b4 acpi!ACPIIrpDispatchDeviceControl+0xa4
WARNING: Stack unwind information not available. Following frames may be wrong.
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 sptd+0x1516a
8232e9d8 8a2a8ea7 00000103 87d239e8 87e64008 acpi!ACPIIrpDispatchDeviceControl+0xa4
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 sptd+0x10ea7
8232ea64 87507518 87507310 8232ea74 00000000 acpi!ACPIIrpDispatchDeviceControl+0xa4
8232ea8c 8a4e9779 87d61680 87dc0018 87d61694 0x87507518
8232eaac 8a4ec335 87dc0018 4a000000 822f5053 PxHelp20+0x2779
8232ead0 8e9a4908 8a9ac1f4 87d615c8 8a9ae000 PxHelp20+0x5335
8232eae4 822f5053 00000000 87d5d980 87d5d980 acehlp10+0x908
8232eafc 8a99f264 87d2bb70 87d239c8 87d2bab8 nt!IofCallDriver+0x63
8232eb10 8a99f45d 87d2bb70 87d239e0 00000000 CLASSPNP!ClasspSendMediaStateIrp+0x2ec
8232eb28 8a99f2af 87d2bb70 87b463e4 8236dcc0 CLASSPNP!ClassCheckMediaState+0x54
8232eb48 82273598 87d2bab8 00000000 8232eb94 CLASSPNP!ClasspTimerTick+0x41
8232eb68 822efd00 8236dca0 0236dc44 34c47c9a nt!IopTimerDispatch+0x49
8232ec88 822ef8c0 8232ecd0 8760af02 8232ecd8 nt!KiTimerListExpire+0x367
8232ece8 822ef483 00000000 00000000 004cf65b nt!KiTimerExpiration+0x22a
8232ed50 822edf9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
8232ed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
STACK_COMMAND: kb
FOLLOWUP_IP:
sptd+1516a
8a2ad16a 0000 add byte ptr [eax],al
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: sptd+1516a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sptd
IMAGE_NAME: sptd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 477bbd59
FAILURE_BUCKET_ID: 0x101_sptd+1516a
BUCKET_ID: 0x101_sptd+1516a
Followup: MachineOwner
0: kd> !analyze -v
*
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 805d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
Debugging Details:
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x101
PROCESS_NAME: System
CURRENT_IRQL: 1c
LAST_CONTROL_TRANSFER: from 822f1321 to 82306163
STACK_TEXT:
8232e850 822f1321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8232e884 822f102d 000aa81b 000000d1 8232e944 nt!KeUpdateRunTime+0xd5
8232e884 822f0cc0 000aa81b 000000d1 8232e944 nt!KeUpdateSystemTime+0xed
8232e910 8223f671 0000000e 8223f712 8a2ac890 nt!KiIpiSendPacket+0xac
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 nt!KeIpiGenericCall+0x6e
8232e990 8a2ad16a 0000001f 8a2ac75c 8232e9b4 acpi!ACPIIrpDispatchDeviceControl+0xa4
WARNING: Stack unwind information not available. Following frames may be wrong.
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 sptd+0x1516a
8232e9d8 8a2a8ea7 00000103 87d239e8 87e64008 acpi!ACPIIrpDispatchDeviceControl+0xa4
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 sptd+0x10ea7
8232ea64 87507518 87507310 8232ea74 00000000 acpi!ACPIIrpDispatchDeviceControl+0xa4
8232ea8c 8a4e9779 87d61680 87dc0018 87d61694 0x87507518
8232eaac 8a4ec335 87dc0018 4a000000 822f5053 PxHelp20+0x2779
8232ead0 8e9a4908 8a9ac1f4 87d615c8 8a9ae000 PxHelp20+0x5335
8232eae4 822f5053 00000000 87d5d980 87d5d980 acehlp10+0x908
8232eafc 8a99f264 87d2bb70 87d239c8 87d2bab8 nt!IofCallDriver+0x63
8232eb10 8a99f45d 87d2bb70 87d239e0 00000000 CLASSPNP!ClasspSendMediaStateIrp+0x2ec
8232eb28 8a99f2af 87d2bb70 87b463e4 8236dcc0 CLASSPNP!ClassCheckMediaState+0x54
8232eb48 82273598 87d2bab8 00000000 8232eb94 CLASSPNP!ClasspTimerTick+0x41
8232eb68 822efd00 8236dca0 0236dc44 34c47c9a nt!IopTimerDispatch+0x49
8232ec88 822ef8c0 8232ecd0 8760af02 8232ecd8 nt!KiTimerListExpire+0x367
8232ece8 822ef483 00000000 00000000 004cf65b nt!KiTimerExpiration+0x22a
8232ed50 822edf9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
8232ed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
STACK_COMMAND: kb
FOLLOWUP_IP:
sptd+1516a
8a2ad16a 0000 add byte ptr [eax],al
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: sptd+1516a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sptd
IMAGE_NAME: sptd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 477bbd59
FAILURE_BUCKET_ID: 0x101_sptd+1516a
BUCKET_ID: 0x101_sptd+1516a
Followup: MachineOwner
0: kd> lmvm sptd
start end module name
8a298000 8a395000 sptd (no symbols)
Loaded symbol image file: sptd.sys
Image path: \SystemRoot\System32\Drivers\sptd.sys
Image name: sptd.sys
Timestamp: Wed Jan 02 17:35:37 2008 (477BBD59)
CheckSum: 000B04F0
ImageSize: 000FD000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
Hier aus der Ereignisanzeige:
Das Zeitlimit (30000 ms) wurde beim Warten auf eine Transaktionsrückmeldung von Dienst ShellHWDetection erreicht.
Hoffe ihr könnt damit mehr anfangen als ich ! Vielen Dank im vrraus!
wollte mich mal hier erkundigen ob ihr mir helfen könnt.
Hatte grad mal ein Bluescreen und möchte gerne wissen woran es lag..
Hoffe ihr könnt mir helfen.. er passierte wirkürlich.. einfach so.. keine ahnung :\
Microsoft (R) Windows Debugger Version 6.8.0004.0 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6001.18063.x86fre.vistasp1_gdr.080425-1930
Kernel base = 0x82239000 PsLoadedModuleList = 0x82350c70
Debug session time: Wed Oct 1 19:57:48.511 2008 (GMT+2)
System Uptime: 0 days 21:51:27.731
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*
- *
- Bugcheck Analysis *
- *
Use !analyze -v to get detailed debugging information.
BugCheck 101, {31, 0, 805d1120, 1}
* ERROR: Module load completed but symbols could not be loaded for sptd.sys
* ERROR: Module load completed but symbols could not be loaded for PxHelp20.sys
* ERROR: Module load completed but symbols could not be loaded for acehlp10.sys
Probably caused by : sptd.sys ( sptd+1516a )
Followup: MachineOwner
0: kd> !analyze -v
*
- *
- Bugcheck Analysis *
- *
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 805d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
Debugging Details:
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x101
PROCESS_NAME: System
CURRENT_IRQL: 1c
LAST_CONTROL_TRANSFER: from 822f1321 to 82306163
STACK_TEXT:
8232e850 822f1321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8232e884 822f102d 000aa81b 000000d1 8232e944 nt!KeUpdateRunTime+0xd5
8232e884 822f0cc0 000aa81b 000000d1 8232e944 nt!KeUpdateSystemTime+0xed
8232e910 8223f671 0000000e 8223f712 8a2ac890 nt!KiIpiSendPacket+0xac
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 nt!KeIpiGenericCall+0x6e
8232e990 8a2ad16a 0000001f 8a2ac75c 8232e9b4 acpi!ACPIIrpDispatchDeviceControl+0xa4
WARNING: Stack unwind information not available. Following frames may be wrong.
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 sptd+0x1516a
8232e9d8 8a2a8ea7 00000103 87d239e8 87e64008 acpi!ACPIIrpDispatchDeviceControl+0xa4
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 sptd+0x10ea7
8232ea64 87507518 87507310 8232ea74 00000000 acpi!ACPIIrpDispatchDeviceControl+0xa4
8232ea8c 8a4e9779 87d61680 87dc0018 87d61694 0x87507518
8232eaac 8a4ec335 87dc0018 4a000000 822f5053 PxHelp20+0x2779
8232ead0 8e9a4908 8a9ac1f4 87d615c8 8a9ae000 PxHelp20+0x5335
8232eae4 822f5053 00000000 87d5d980 87d5d980 acehlp10+0x908
8232eafc 8a99f264 87d2bb70 87d239c8 87d2bab8 nt!IofCallDriver+0x63
8232eb10 8a99f45d 87d2bb70 87d239e0 00000000 CLASSPNP!ClasspSendMediaStateIrp+0x2ec
8232eb28 8a99f2af 87d2bb70 87b463e4 8236dcc0 CLASSPNP!ClassCheckMediaState+0x54
8232eb48 82273598 87d2bab8 00000000 8232eb94 CLASSPNP!ClasspTimerTick+0x41
8232eb68 822efd00 8236dca0 0236dc44 34c47c9a nt!IopTimerDispatch+0x49
8232ec88 822ef8c0 8232ecd0 8760af02 8232ecd8 nt!KiTimerListExpire+0x367
8232ece8 822ef483 00000000 00000000 004cf65b nt!KiTimerExpiration+0x22a
8232ed50 822edf9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
8232ed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
STACK_COMMAND: kb
FOLLOWUP_IP:
sptd+1516a
8a2ad16a 0000 add byte ptr [eax],al
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: sptd+1516a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sptd
IMAGE_NAME: sptd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 477bbd59
FAILURE_BUCKET_ID: 0x101_sptd+1516a
BUCKET_ID: 0x101_sptd+1516a
Followup: MachineOwner
0: kd> !analyze -v
*
- *
- Bugcheck Analysis *
- *
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000031, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 805d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
Debugging Details:
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x101
PROCESS_NAME: System
CURRENT_IRQL: 1c
LAST_CONTROL_TRANSFER: from 822f1321 to 82306163
STACK_TEXT:
8232e850 822f1321 00000101 00000031 00000000 nt!KeBugCheckEx+0x1e
8232e884 822f102d 000aa81b 000000d1 8232e944 nt!KeUpdateRunTime+0xd5
8232e884 822f0cc0 000aa81b 000000d1 8232e944 nt!KeUpdateSystemTime+0xed
8232e910 8223f671 0000000e 8223f712 8a2ac890 nt!KiIpiSendPacket+0xac
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 nt!KeIpiGenericCall+0x6e
8232e990 8a2ad16a 0000001f 8a2ac75c 8232e9b4 acpi!ACPIIrpDispatchDeviceControl+0xa4
WARNING: Stack unwind information not available. Following frames may be wrong.
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 sptd+0x1516a
8232e9d8 8a2a8ea7 00000103 87d239e8 87e64008 acpi!ACPIIrpDispatchDeviceControl+0xa4
8232ea30 807b3084 85c545d8 8732c3a8 807b1521 sptd+0x10ea7
8232ea64 87507518 87507310 8232ea74 00000000 acpi!ACPIIrpDispatchDeviceControl+0xa4
8232ea8c 8a4e9779 87d61680 87dc0018 87d61694 0x87507518
8232eaac 8a4ec335 87dc0018 4a000000 822f5053 PxHelp20+0x2779
8232ead0 8e9a4908 8a9ac1f4 87d615c8 8a9ae000 PxHelp20+0x5335
8232eae4 822f5053 00000000 87d5d980 87d5d980 acehlp10+0x908
8232eafc 8a99f264 87d2bb70 87d239c8 87d2bab8 nt!IofCallDriver+0x63
8232eb10 8a99f45d 87d2bb70 87d239e0 00000000 CLASSPNP!ClasspSendMediaStateIrp+0x2ec
8232eb28 8a99f2af 87d2bb70 87b463e4 8236dcc0 CLASSPNP!ClassCheckMediaState+0x54
8232eb48 82273598 87d2bab8 00000000 8232eb94 CLASSPNP!ClasspTimerTick+0x41
8232eb68 822efd00 8236dca0 0236dc44 34c47c9a nt!IopTimerDispatch+0x49
8232ec88 822ef8c0 8232ecd0 8760af02 8232ecd8 nt!KiTimerListExpire+0x367
8232ece8 822ef483 00000000 00000000 004cf65b nt!KiTimerExpiration+0x22a
8232ed50 822edf9d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
8232ed54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49
STACK_COMMAND: kb
FOLLOWUP_IP:
sptd+1516a
8a2ad16a 0000 add byte ptr [eax],al
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: sptd+1516a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: sptd
IMAGE_NAME: sptd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 477bbd59
FAILURE_BUCKET_ID: 0x101_sptd+1516a
BUCKET_ID: 0x101_sptd+1516a
Followup: MachineOwner
0: kd> lmvm sptd
start end module name
8a298000 8a395000 sptd (no symbols)
Loaded symbol image file: sptd.sys
Image path: \SystemRoot\System32\Drivers\sptd.sys
Image name: sptd.sys
Timestamp: Wed Jan 02 17:35:37 2008 (477BBD59)
CheckSum: 000B04F0
ImageSize: 000FD000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
Hier aus der Ereignisanzeige:
Das Zeitlimit (30000 ms) wurde beim Warten auf eine Transaktionsrückmeldung von Dienst ShellHWDetection erreicht.
Hoffe ihr könnt damit mehr anfangen als ich ! Vielen Dank im vrraus!
Share on Facebook
Share on Twitter
Share on Reddit
Share on LinkedinPlease also mark the comments that contributed to the solution of the article
Content-Key: 98284
Url: https://administrator.de/contentid/98284
Printed on: April 19, 2024 at 02:04 o'clock
