Win7 BSOD DRIVER_POWER_STATE_FAILURE

[Acipenser]

Hi Leute,

habe seit ein paar Monaten immer mal wieder den BSOD "DRIVER_POWER_STATE_FAILURE" und "DRIVER_IRQL_NOT_LESS_OR_EQUAL".
In letzter Zeit kam er nun öfters. Habe die Minidumps mal mit WhoCrashed analysiert.
Zum einen scheint es der Audio-Treiber zu sein, aber was hat es mit "ntoskrnl.exe" auf sich?
Schon mal danke für die Hilfe!

Gruß.

Spoiler

System Information (local)
--------------------------------------------------------------------------------

computer name: RECHNER
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: N56VZ, ASUSTeK COMPUTER INC.
CPU: GenuineIntel Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17059897344 total
VM: 2147352576, free: 1888247808




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 27.01.2014 15:24:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012714-7066-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800EDA8060, 0xFFFFF80000B9C3D8, 0xFFFFFA8012343010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 27.01.2014 15:24:38 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800EDA8060, 0xFFFFF80000B9C3D8, 0xFFFFFA8012343010)
Error: DRIVER_POWER_STATE_FAILURE
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 27.01.2014 12:36:30 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012714-8845-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800D657060, 0xFFFFF8000448F3D8, 0xFFFFFA800CE9FC60)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sun 26.01.2014 20:55:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012614-9032-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800E984060, 0xFFFFF80000B9C3D8, 0xFFFFFA80125C9C60)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 25.01.2014 01:54:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012514-8907-01.dmp
This was probably caused by the following module: hdaudbus.sys (0xFFFFF88007B9996A)
Bugcheck code: 0xD1 (0xFFFFF88021CD4020, 0x2, 0x0, 0xFFFFF88007B9996A)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\hdaudbus.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: High Definition Audio Bus Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 21.01.2014 08:29:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012114-7644-01.dmp
This was probably caused by the following module: nvhda64v.sys (0xFFFFF8800E743E3F)
Bugcheck code: 0xD1 (0xFFFFF88022095104, 0x2, 0x0, 0xFFFFF8800E743E3F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvhda64v.sys
product: NVIDIA HDMI Audio Driver
company: NVIDIA Corporation
description: NVIDIA HDMI Audio Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvhda64v.sys (NVIDIA HDMI Audio Driver, NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Fri 17.01.2014 17:33:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011714-7581-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA80123A2440, 0xFFFFF800044863D8, 0xFFFFFA8012D8FC60)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 15.01.2014 09:41:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011514-9516-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA8010D33060, 0xFFFFF80000B9C3D8, 0xFFFFFA80139C8010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 11.01.2014 16:52:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011114-6661-01.dmp
This was probably caused by the following module: nvhda64v.sys (0xFFFFF8800E299E3F)
Bugcheck code: 0xD1 (0xFFFFF88021A5B104, 0x2, 0x0, 0xFFFFF8800E299E3F)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvhda64v.sys
product: NVIDIA HDMI Audio Driver
company: NVIDIA Corporation
description: NVIDIA HDMI Audio Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvhda64v.sys (NVIDIA HDMI Audio Driver, NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Sun 05.01.2014 22:40:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010514-7176-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x9F (0x3, 0xFFFFFA800CD9E060, 0xFFFFF800044813D8, 0xFFFFFA8012229010)
Error: DRIVER_POWER_STATE_FAILURE
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

 

[simpel1970]

WhoCrashed, Bluescreenview und Konsorten arbeiten zu oberflächlich um für alle Absturzprobleme den tatsächlichen Absturzgrund herauszufinden. Hierfür sind die Debugging Tools von Microsoft wesentlich besser geeignet auch wenn die Bedienung etwas umständlicher ist.
Gerade bei den Driver Power State Fehlern (0x9F) erhältst du mit den Tools keine exakten Auswertungen.

Lade einfach mal die Minidumps hier im Thread hoch. Die Minidumps können auch auf einem anderen PC ausgewertet werden. Die Dumps dazu am Besten im ZIP Format einpacken, dann kannst du sie wie ein Bild hier im Thread hochladen. Sofern du ein Zugriffsproblem beim Einpacken haben solltest, kopiere die Dumps vor dem Einpacken einfach in ein Nicht-Windows-Verzeichnis.

Falls du dich selbst mal an den Debugging Tools probieren willst, gibt es z.B. hier eine kurze Anleitung: Bluescreen! - ComputerBase Forum

 

[Acipenser]

Sorry, dass ich so lange nicht geantwortet habe, aber ich ging davon aus, dass ich bei ner Antwort benachrichtigt werde.

Ich hab die letzten 3 Minidumps mal in die Dropbox hochgeladen:
https://www.dropbox.com/sh/pht7sv8y4p6sr62/OrxAKivipP

Hab mal den neusten mit deiner beschriebenen Methode analysiert:

Spoiler

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


Loading Dump File [C:\Users\Jonas\Desktop\042214-13447-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0000a7e2?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`0386caa2?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`001cd022?
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c3c0?
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e17000 PsLoadedModuleList = 0xfffff800`0305a6d0
Debug session time: Tue Apr 22 09:13:22.074 2014 (UTC + 2:00)
System Uptime: 3 days 13:14:48.932
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.
Loading User Symbols
Loading unloaded module list
..................................................
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80102ee060, fffff80000b9c3d8, fffffa8028d70010}

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: USBHUB!_DEVICE_EXTENSION_PDO ***
*** ***
*************************************************************************
Probably caused by : usbhub.sys

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

0: kd> !analyze -v
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80102ee060, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa8028d70010, The blocked IRP

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

*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands 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: USBHUB!_DEVICE_EXTENSION_PDO ***
*** ***
*************************************************************************

DRVPOWERSTATE_SUBCODE: 3

IMAGE_NAME: usbhub.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52954dd0

MODULE_NAME: usbhub

FAULTING_MODULE: fffff88007aff000 usbhub

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

TAG_NOT_DEFINED_c000000f: FFFFF80000BA2FB0

STACK_TEXT:
fffff800`00b9c388 fffff800`02efc8d2 : 00000000`0000009f 00000000`00000003 fffffa80`102ee060 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02e9785c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`02e976f6 : fffffa80`1145fc58 fffffa80`1145fc58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02e975de : 000002ca`880eed4a fffff800`00b9cb18 00000000`012c2cb1 fffff800`0300b8a8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02e973c7 : 000000a7`0f5f7bc3 000000a7`012c2cb1 000000a7`0f5f7b31 00000000`000000b1 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02e848ca : fffff800`03007e80 fffff800`03015cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_3_AmUStor_IMAGE_usbhub.sys

BUCKET_ID: X64_0x9F_3_AmUStor_IMAGE_usbhub.sys

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

Scheint wohl etwas mit den USB-Anschlüssen (usbhub.sys) zu tun zu haben?

Spoiler

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


Loading Dump File [C:\Users\Jonas\Desktop\041814-11013-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 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e5a000 PsLoadedModuleList = 0xfffff800`0309d6d0
Debug session time: Fri Apr 18 11:50:27.588 2014 (UTC + 2:00)
System Uptime: 4 days 17:45:38.447
Loading Kernel Symbols
...............................................................
................................................................
..........................................................
Loading User Symbols
Loading unloaded module list
..................................................
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {fffff880206c0104, 2, 0, fffff8800be03fb7}

*** WARNING: Unable to verify timestamp for nvhda64v.sys
*** ERROR: Module load completed but symbols could not be loaded for nvhda64v.sys
Probably caused by : nvhda64v.sys ( nvhda64v+3fb7 )

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

2: kd> !analyze -v
ERROR: FindPlugIns 8007007b
ERROR: Some plugins may not be available [8007007b]
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff880206c0104, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8800be03fb7, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003107100
GetUlongFromAddress: unable to read from fffff800031071c0
fffff880206c0104 Nonpaged pool

CURRENT_IRQL: 2

FAULTING_IP:
nvhda64v+3fb7
fffff880`0be03fb7 8b00 mov eax,dword ptr [rax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

BUGCHECK_STR: 0xD1

PROCESS_NAME: audiodg.exe

TRAP_FRAME: fffff880203863c0 -- (.trap 0xfffff880203863c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff880206c0104 rbx=0000000000000000 rcx=fffffa8015a98110
rdx=fffffa80104fd2c0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800be03fb7 rsp=fffff88020386550 rbp=fffffa80104fd2b0
r8=fffffa80104fd2b0 r9=000000000023aeb6 r10=0000000000000048
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nvhda64v+0x3fb7:
fffff880`0be03fb7 8b00 mov eax,dword ptr [rax] ds:fffff880`206c0104=????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002ecf169 to fffff80002ecfbc0

STACK_TEXT:
fffff880`20386278 fffff800`02ecf169 : 00000000`0000000a fffff880`206c0104 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`20386280 fffff800`02ecdde0 : 00000000`00000000 00000000`00000000 ffffffff`fffffb80 fffffa80`15a98110 : nt!KiBugCheckDispatch+0x69
fffff880`203863c0 fffff880`0be03fb7 : 00000000`00000000 fffffa80`12de19a0 fffffa80`13837a40 fffffa80`12de1990 : nt!KiPageFault+0x260
fffff880`20386550 00000000`00000000 : fffffa80`12de19a0 fffffa80`13837a40 fffffa80`12de1990 fffffa80`104fd2c0 : nvhda64v+0x3fb7


STACK_COMMAND: kb

FOLLOWUP_IP:
nvhda64v+3fb7
fffff880`0be03fb7 8b00 mov eax,dword ptr [rax]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nvhda64v+3fb7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvhda64v

IMAGE_NAME: nvhda64v.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 52974741

FAILURE_BUCKET_ID: X64_0xD1_nvhda64v+3fb7

BUCKET_ID: X64_0xD1_nvhda64v+3fb7

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

Und hier etwas mit dem Audio-Treiber (audiodg.exe) ?

 

[simpel1970]

Macht nichts

Ich schaue mir die Dumps zu Hause noch mal näher an, aber von dem gezeigten kann man zwei problembehaftete Treiber ausmachen:

-AmUStor.sys (Treibersignatur von Januar 2011 -> Alcor Micro USB Treiber) und
- nvhda64v.sys (Treibersignatur von November 2013 -> Komponente der nVidia HDMI Audio Treiber)

Bei den USB Treiber würde ich bei Asus nach der aktuellsten Version schauen.
Zu den Nvidia Treibern...sind das die aktuellsten von der ASUS Seite, oder direkt von Nvidia? Falls von Nvidia, würde ich diese deinstallieren und die aktuellsten von der Asus Seite installieren.

 

[simpel1970]

Die weitere Analyse hat nichts neues ergeben. Das Absturzbild zeigt sich so, wie ich bereits geschrieben habe.
Hier noch die entscheidende Stelle des Driver Power State Fehlers (mit Geräteinstanz):

!DevObj   !DrvObj            !DevExt   ObjectName
  fffffa8010754060 Unable to load image \SystemRoot\system32\drivers\AmUStor.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for AmUStor.SYS
*** ERROR: Module load completed but symbols could not be loaded for AmUStor.SYS
 \Driver\AmUStor    fffffa80107541b0  InfoMask field not found for _OBJECT_HEADER at fffffa8010754030

  fffffa80106da040  \Driver\ACPI       fffffa800ccfca90  InfoMask field not found for _OBJECT_HEADER at fffffa80106da010

> fffffa800ea03060  \Driver\usbhub     fffffa800ea031b0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode fffffa800e9f65a0 :
  DeviceInst is "USB\VID_058F&PID_6366\058F63666435"
  ServiceName is "AmUStor"


Irp is active with 10 stacks 9 is current (= 0xfffffa80142a4320)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa8010754060 00000000 00000000-00000000    pending
	       \Driver\AmUStor
			Args: 00000000 00000001 00000003 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa80145e76f0    

			Args: 00000000 00000000 00000000 00000000

 

[Acipenser]

Danke für die Mühe!!

Ich hab mir jetzt mal den neusten Alcor SD Card und Nvidia Treiber aufgespielt, den es auf der Asus-Seite für meinen Laptop gab.
Hab dabei zwar die für Win8 ausgewählt, weil die um ein Jahr aktueller waren, aber das sollte ja nichts machen? Zumindest läufts auch unter Win7.

Dann heißt es wohl jetzt abwarten bis zum nächsten BSOD.

 

[Acipenser]

..und der kam schneller als gedacht.

Wieder eine Meldung wegen der nvhda64v.sys. Ich hab mal noch ein bissjen recherchiert und bin dabei auf diesen Hotfix gestoßen:

Project Big Picture: Nvhda64v / HDAudBus.sys BSOD hot fix win 7/8 64 bit

Den hab ich mal installiert, da das genau nach meinem Problem klingt.

 

[simpel1970]

Klingt für mich auch so. Dann hoffe ich mal, dass beide Probleme damit behoben sind.