Anzeige

Am Puls von Microsoft

Anzeige

System Langsames Herunterfahren und sporadische Bluescreens - was tun?

Ur7urn

Herzlich willkommen
Hallo ich bin neu hier :)

verwende Vista Ultimate 32-Bit SP2 Fiinal und wenn ich meinen Rechner herunterfahren möchte dann dauert es unregelmäßig(!) sehr lang (5 min.) dann folgt ein Bluescreen und er startet einfach neu. :cry:

hier das hjt-log:

Logfile of Trend Micro HijackThis v2.0.2
Scan saved at 22:39:29, on 19.06.2009
Platform: Windows Vista SP2 (WinNT 6.00.1906)
MSIE: Internet Explorer v8.00 (8.00.6001.18702)
Boot mode: Normal

Running processes:
C:\Windows\system32\Dwm.exe
C:\Windows\system32\taskeng.exe
C:\Windows\Explorer.EXE
C:\Windows\RtHDVCpl.exe
C:\Program Files\Avira\AntiVir Desktop\avgnt.exe
C:\Program Files\Zone Labs\ZoneAlarm\zlclient.exe
C:\Program Files\Logitech\SetPoint\SetPoint.exe
C:\Program Files\Common Files\Logishrd\KHAL2\KHALMNPR.EXE
C:\Windows\system32\wbem\unsecapp.exe
C:\Program Files\Internet Explorer\iexplore.exe
C:\Program Files\Internet Explorer\iexplore.exe
C:\Program Files\Internet Explorer\iexplore.exe
C:\Program Files\Trend Micro\HijackThis\HijackThis.exe

R1 - HKCU\Software\Microsoft\Internet Explorer\Main,Search Page = Bing
R0 - HKCU\Software\Microsoft\Internet Explorer\Main,Start Page = MSN.com
R1 - HKLM\Software\Microsoft\Internet Explorer\Main,Default_Page_URL = MSN.com
R1 - HKLM\Software\Microsoft\Internet Explorer\Main,Default_Search_URL = Bing
R1 - HKLM\Software\Microsoft\Internet Explorer\Main,Search Page = Bing
R0 - HKLM\Software\Microsoft\Internet Explorer\Main,Start Page = MSN.com
R0 - HKLM\Software\Microsoft\Internet Explorer\Search,SearchAssistant =
R0 - HKLM\Software\Microsoft\Internet Explorer\Search,CustomizeSearch =
R0 - HKCU\Software\Microsoft\Internet Explorer\Toolbar,LinksFolderName =
O1 - Hosts: ::1 localhost
O2 - BHO: AcroIEHelperStub - {18DF081C-E8AD-4283-A596-FA578C2EBDC3} - C:\Program Files\Common Files\Adobe\Acrobat\ActiveX\AcroIEHelperShim.dll
O2 - BHO: Groove GFS Browser Helper - {72853161-30C5-4D22-B7F9-0BBC1D38A37E} - C:\Program Files\Microsoft Office 2007\Office12\GrooveShellExtensions.dll
O2 - BHO: Java(tm) Plug-In 2 SSV Helper - {DBC80044-A445-435b-BC74-9C25C1C588A9} - C:\Program Files\Java\jre6\bin\jp2ssv.dll
O4 - HKLM\..\Run: [Kernel and Hardware Abstraction Layer] KHALMNPR.EXE
O4 - HKLM\..\Run: [RtHDVCpl] RtHDVCpl.exe
O4 - HKLM\..\Run: [avgnt] "C:\Program Files\Avira\AntiVir Desktop\avgnt.exe" /min
O4 - HKLM\..\Run: [ZoneAlarm Client] "C:\Program Files\Zone Labs\ZoneAlarm\zlclient.exe"
O4 - HKUS\S-1-5-19\..\Run: [Sidebar] %ProgramFiles%\Windows Sidebar\Sidebar.exe /detectMem (User 'LOKALER DIENST')
O4 - HKUS\S-1-5-19\..\Run: [WindowsWelcomeCenter] rundll32.exe oobefldr.dll,ShowWelcomeCenter (User 'LOKALER DIENST')
O4 - HKUS\S-1-5-20\..\Run: [Sidebar] %ProgramFiles%\Windows Sidebar\Sidebar.exe /detectMem (User 'NETZWERKDIENST')
O4 - Global Startup: Logitech SetPoint.lnk = C:\Program Files\Logitech\SetPoint\SetPoint.exe
O8 - Extra context menu item: Nach Microsoft E&xel exportieren - res://C:\PROGRA~1\MICROS~2\Office12\EXCEL.EXE/3000
O9 - Extra button: An OneNote senden - {2670000A-7350-4f3c-8081-5663EE0C6C49} - C:\PROGRA~1\MICROS~2\Office12\ONBttnIE.dll
O9 - Extra 'Tools' menuitem: An OneNote s&enden - {2670000A-7350-4f3c-8081-5663EE0C6C49} - C:\PROGRA~1\MICROS~2\Office12\ONBttnIE.dll
O9 - Extra button: Research - {92780B25-18CC-41C8-B9BE-3C9C571A8263} - C:\PROGRA~1\MICROS~2\Office12\REFIEBAR.DLL
O13 - Gopher Prefix:
O16 - DPF: {5AE58FCF-6F6A-49B2-B064-02492C66E3F4} (MUCatalogWebControl Class) - http://catalog.update.microsoft.com/...?1243884312442
O16 - DPF: {8AD9C840-044E-11D1-B3E9-00805F499D93} (Java Runtime Environment 1.6.0) - http://dl8-cdn-09.sun.com/s/ESD7/JSC...ws-i586-jc.cab
O17 - HKLM\System\CCS\Services\Tcpip\..\{786F680F-960F-4BF9-891A-0D5C7BF88698}: NameServer = 192.168.2.1
O18 - Protocol: grooveLocalGWS - {88FED34C-F0CA-4636-A375-3CB6248B04CD} - C:\Program Files\Microsoft Office 2007\Office12\GrooveSystemServices.dll
O23 - Service: AMD External Events Utility - AMD - C:\Windows\system32\atiesrxx.exe
O23 - Service: Avira AntiVir Planer (AntiVirSchedulerService) - Avira GmbH - C:\Program Files\Avira\AntiVir Desktop\sched.exe
O23 - Service: Avira AntiVir Guard (AntiVirService) - Avira GmbH - C:\Program Files\Avira\AntiVir Desktop\avguard.exe
O23 - Service: Logitech Bluetooth Service (LBTServ) - Logitech, Inc. - C:\Program Files\Common Files\Logishrd\Bluetooth\LBTServ.exe
O23 - Service: Steam Client Service - Valve Corporation - C:\Program Files\Common Files\Steam\SteamService.exe
O23 - Service: TrueVector Internet Monitor (vsmon) - Check Point Software Technologies LTD - C:\Windows\System32\ZoneLabs\vsmon.exe

--
End of file - 4831 bytes

hier die minidumps:

Minidumps.rar - FileFactory


was kann das sein??? :( :cry:


Vielen Dank im Voraus!! (y)
 
Zuletzt bearbeitet von einem Moderator:
Anzeige

koelner42

Student des Lebens
:) Hm kann dir da nicht wirklich helfen da ich leider nicht viel mit deinen Daten anfangen kann bin da nicht so bewandert:(

aber hätte vielleicht trotzdem einen Lösungsansatz. als erstes solltest du den automatischen neustart ausschalten so kannst du in der fehlermeldung des bluescreens sehen wo das problem herkommt und dann schau mal hier:

http://www.drwindows.de/vista-fehlersuche-und-troubleshooting/12024-blue-screen-analyse.html

da steht auch wie du den automatischen neustart abschalten kannst. hoffe es hilft dir ein wenig

MfG Peter
 
Zuletzt bearbeitet von einem Moderator:

Nebula

nicht mehr wegzudenken
@Ur7urn
Du hast laut deinem Log zwei Antiviren Programme installiert?Das verträgt sich nicht wirklich gut.Das könnte die langen Zeiten beim Herunterfahren erklären.
 
Zuletzt bearbeitet von einem Moderator:

Ur7urn

Herzlich willkommen
Hallo und vielen Dank für die prompten Antworten :),

also ich habe nur einen virenscanner und der lautet Avira AntiVir ;o)

Warum wurd' mein Threadname geändert? War doch aussagekräftiger, der fährt ja nicht immer langsam herunter, sondern nur wenn es zum bluescreen kommt! :(

Wenn ich mit Debugging Tools for Windows die Minidump (vom letzten Bluescreen) öffne ("Open Crash Dump..."), kommt folgendes:

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


Loading Dump File [C:\Users\Standard\Desktop\Minidump\Mini061909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x82000000 PsLoadedModuleList = 0x8210d930
Debug session time: Fri Jun 19 21:50:17.963 2009 (GMT+2)
System Uptime: 0 days 2:38:53.681
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 84e52b70, 86cae030, 85fea808}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_IRP ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+bb899 )

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

Hoff ihr könnt mir helfen :cry: ;)

mfg
 

Franz

Moderator
Arbeite nochmals genau das Tutorial ab.
Du hast entweder den symbol - Pfad nicht korrekt angegeben oder
die 'falschen' symbols geladen.
 

Ur7urn

Herzlich willkommen
soo das 5. mal bearbeitet ^^ aber noch immer keine Antworten =(

hier jetzt endlich die frische Analyse der MEMORY.DMP:

Microsoft (R) Windows Debugger Version 6.11.0001.404 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:\Program Files\Debugging Tools for Windows (x86)\Symbol File*Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x82009000 PsLoadedModuleList = 0x82116930
Debug session time: Sun Jun 21 00:21:47.446 2009 (GMT+2)
System Uptime: 0 days 2:41:38.539
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols

Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 84e53030, 86ad1380, 8487fe00}

Probably caused by : nvm60x32.sys

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

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: 84e53030, Physical Device Object of the stack
Arg3: 86ad1380, Functional Device Object of the stack
Arg4: 8487fe00, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: 8487fe00

DEVICE_OBJECT: 86ad1380

DRIVER_OBJECT: 86aec658

IMAGE_NAME: nvm60x32.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45272d83

MODULE_NAME: nvm60x32

FAULTING_MODULE: 8931c000 nvm60x32

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 82033ca0 to 820c4899

STACK_TEXT:
820f5acc 82033ca0 0000009f 00000003 84e53030 nt!KeBugCheckEx+0x1e
820f5b28 820342de 820f5ba0 85dc2ad8 00000000 nt!PopCheckIrpWatchdog+0x1ad
820f5b68 820742e0 8210dca0 00000000 800e393e nt!PopCheckForIdleness+0x343
820f5c88 82073ea0 820f5cd0 86c43a02 820f5cd8 nt!KiTimerListExpire+0x367
820f5ce8 82073a63 00000000 00000000 00097c80 nt!KiTimerExpiration+0x22a
820f5d50 8207259d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
820f5d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_nvm60x32.sys

BUCKET_ID: 0x9F_IMAGE_nvm60x32.sys

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

Dies ist noch der Hinweis von Windows auf den Bluescreen:

Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.0.6002.2.2.0.256.1
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: 9f
BCP1: 00000003
BCP2: 84E53030
BCP3: 86AD1380
BCP4: 8487FE00
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\Mini062109-01.dmp
C:\Users\Standard\AppData\Local\Temp\WER-44772-0.sysdata.xml
C:\Users\Standard\AppData\Local\Temp\WERCF3F.tmp.version.txt

Lesen Sie unsere Datenschutzrichtlinie:
Microsoft-Absturzanalyse

Habe sogar Neustart bei Systemfehler abgeschaltet, hier nun ein "Screenshot":



Hoffe ihr könnt jetzt was damit anfangen. ;)))

Greetz
 
Zuletzt bearbeitet:

koelner42

Student des Lebens
soo das 5. mal bearbeitet ^^ aber noch immer keine Antworten =(

hier jetzt endlich die frische Analyse der MEMORY.DMP:

Microsoft (R) Windows Debugger Version 6.11.0001.404 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:\Program Files\Debugging Tools for Windows (x86)\Symbol File*Symbol information
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.x86fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0x82009000 PsLoadedModuleList = 0x82116930
Debug session time: Sun Jun 21 00:21:47.446 2009 (GMT+2)
System Uptime: 0 days 2:41:38.539
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols

Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, 84e53030, 86ad1380, 8487fe00}

Probably caused by : nvm60x32.sys

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

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: 84e53030, Physical Device Object of the stack
Arg3: 86ad1380, Functional Device Object of the stack
Arg4: 8487fe00, The blocked IRP

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


DRVPOWERSTATE_SUBCODE: 3

IRP_ADDRESS: 8487fe00

DEVICE_OBJECT: 86ad1380

DRIVER_OBJECT: 86aec658

IMAGE_NAME: nvm60x32.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45272d83

MODULE_NAME: nvm60x32

FAULTING_MODULE: 8931c000 nvm60x32

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 82033ca0 to 820c4899

STACK_TEXT:
820f5acc 82033ca0 0000009f 00000003 84e53030 nt!KeBugCheckEx+0x1e
820f5b28 820342de 820f5ba0 85dc2ad8 00000000 nt!PopCheckIrpWatchdog+0x1ad
820f5b68 820742e0 8210dca0 00000000 800e393e nt!PopCheckForIdleness+0x343
820f5c88 82073ea0 820f5cd0 86c43a02 820f5cd8 nt!KiTimerListExpire+0x367
820f5ce8 82073a63 00000000 00000000 00097c80 nt!KiTimerExpiration+0x22a
820f5d50 8207259d 00000000 0000000e 00000000 nt!KiRetireDpcList+0xba
820f5d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: 0x9F_IMAGE_nvm60x32.sys

BUCKET_ID: 0x9F_IMAGE_nvm60x32.sys

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

Dies ist noch der Hinweis von Windows auf den Bluescreen:

Problemsignatur:
Problemereignisname: BlueScreen
Betriebsystemversion: 6.0.6002.2.2.0.256.1
Gebietsschema-ID: 1031

Zusatzinformationen zum Problem:
BCCode: 9f
BCP1: 00000003
BCP2: 84E53030
BCP3: 86AD1380
BCP4: 8487FE00
OS Version: 6_0_6002
Service Pack: 2_0
Product: 256_1

Dateien, die bei der Beschreibung des Problems hilfreich sind:
C:\Windows\Minidump\Mini062109-01.dmp
C:\Users\Standard\AppData\Local\Temp\WER-44772-0.sysdata.xml
C:\Users\Standard\AppData\Local\Temp\WERCF3F.tmp.version.txt

Lesen Sie unsere Datenschutzrichtlinie:
Microsoft-Absturzanalyse

Habe sogar Neustart bei Systemfehler abgeschaltet, hier nun ein "Screenshot":



Hoffe ihr könnt jetzt was damit anfangen. ;)))

Greetz

Hm hab was gefunden schau mal hier :WinTotal - Tipps - Bluescreen: Driver_Power_State_Failure

müßte dir eigendlich helfen
Gruß Peter
P.s wenn es nicht weggeht könnte es auch ein alter treiber sein bspw. von NVIDIA schau dafür dann auch mal hier: http://forum.chip.de/windows-vista/driver_power_state_failure-973577.html
 
Zuletzt bearbeitet:

Franz

Moderator
Das ist der nVidia-Treiber, der die Bluescreens verursacht.
Um welche Treiber-Version handelt es sich hier?
Den Treiber würde ich als erstes gegen einen älteren/neueren austauschen,
wie schon koelner42 erwähnte.
 
Anzeige
Oben