Hallöchen allerseits!
Hab mich jetzt nach längerem rumgeärgere hier registriert und hoffe, dass mir geholfen wird..gif)
Seit ca. 2 Monaten hab ich Probleme mit meinem Pc. Bei Spielen, die ich über Origin spiele (Battlefield 4, Dragon Age Inquisition( <- VORALLEM BEI DIESEM SPIEL) & momentan Battlefield Hardline Beta (wobei bei Battlefield nur die Spiele abstürzen, Bluescreens eher selten auftreten) treten nach unterschiedlichen Abständen die unterschiedlichsten Bluescreens auf. Unten hänge ich mal eine kleine Auswahl an.
Bei Spielen, die ich über Steam spiele, treten keinerlei Abstürze/Bluescreens auf! (Arma 3, CoD, L4D etc.)
Mitte Dezember habe ich meine Grafikkarte ausgetauscht (von einer Radeon HD 6850 auf ne R9 290 von Sapphire), die meiner Meinung nach die Probleme "verstärkt" hat.. Könnte natürlich auch nur Einbildung sein. Eine Rückrüstung ist nicht möglich, da die 6850 beim "sicheren" verstauen einen etwas heftigeren Sturzschaden erlitten hat..
Kleiner Gedankenblitz: Wegen den damaligen Bluescreens bei Battlefield hatte ich die RAM Spannung auf 1.5V erhöht, seitdem waren diese weg. Laut Alternate, wo ich meine Sachen bestellt hatte, läuft die RAM aber mit 1.65V. Kann ich die Spannung ohne Sorgen auf die genannte Spannung erhöhen? Oder bringt mir das dann evtl. nur mehr ärger, bzw. keinen weiteren Vorteil?
Nunja, nun mal zu meinem PC:
Mainboard: ASRock 970 Extreme 4
Prozessor: AMD FX-8150
RAM: GeIL 2x 4GB CL9 10-9-28
Grafikkarte: Sapphire Radeon R9 290 Tri-X
Netzteil: 600W
Betriebssystem: Win7 Professional -> Anfang Januar frisch installiert, kompletter Datenreset, also es kam nur frisch geladenes auf den PC. (Externe Festplatte versehentlich formatiert :'D )
Virenschutz: Kaspersky Internet Security 2015
Temperaturen sind im grünen Bereich: CPU-Temp geht nicht höher als 55° unter Volllast, GPU nicht höher als 75°.
Memtest 4 Stunden lang laufen lassen - keine Fehler.
Prime95 spuckt keine Fehler aus.
Aktuellsten Sound- & Grafiktreiber hab ich installiert.
Nun zu den Bluescreens:
Nummer 1:
Nummer 2:
Nummer 3:
Und nun die von heute:
Nummer 4:
Nummer 5:
Bluescreens sind für mich Neuland. Hab dabei keine Ahnung, wo ich anfangen und aufhören muss.
Deshalb bräuchte ich Hilfe vom Fach.
Danke schonmal im Voraus für die Bemühungen!
Hab mich jetzt nach längerem rumgeärgere hier registriert und hoffe, dass mir geholfen wird.
.gif)
Seit ca. 2 Monaten hab ich Probleme mit meinem Pc. Bei Spielen, die ich über Origin spiele (Battlefield 4, Dragon Age Inquisition( <- VORALLEM BEI DIESEM SPIEL) & momentan Battlefield Hardline Beta (wobei bei Battlefield nur die Spiele abstürzen, Bluescreens eher selten auftreten) treten nach unterschiedlichen Abständen die unterschiedlichsten Bluescreens auf. Unten hänge ich mal eine kleine Auswahl an.
Bei Spielen, die ich über Steam spiele, treten keinerlei Abstürze/Bluescreens auf! (Arma 3, CoD, L4D etc.)
Mitte Dezember habe ich meine Grafikkarte ausgetauscht (von einer Radeon HD 6850 auf ne R9 290 von Sapphire), die meiner Meinung nach die Probleme "verstärkt" hat.. Könnte natürlich auch nur Einbildung sein. Eine Rückrüstung ist nicht möglich, da die 6850 beim "sicheren" verstauen einen etwas heftigeren Sturzschaden erlitten hat..
Kleiner Gedankenblitz: Wegen den damaligen Bluescreens bei Battlefield hatte ich die RAM Spannung auf 1.5V erhöht, seitdem waren diese weg. Laut Alternate, wo ich meine Sachen bestellt hatte, läuft die RAM aber mit 1.65V. Kann ich die Spannung ohne Sorgen auf die genannte Spannung erhöhen? Oder bringt mir das dann evtl. nur mehr ärger, bzw. keinen weiteren Vorteil?
Nunja, nun mal zu meinem PC:
Mainboard: ASRock 970 Extreme 4
Prozessor: AMD FX-8150
RAM: GeIL 2x 4GB CL9 10-9-28
Grafikkarte: Sapphire Radeon R9 290 Tri-X
Netzteil: 600W
Betriebssystem: Win7 Professional -> Anfang Januar frisch installiert, kompletter Datenreset, also es kam nur frisch geladenes auf den PC. (Externe Festplatte versehentlich formatiert :'D )
Virenschutz: Kaspersky Internet Security 2015
Temperaturen sind im grünen Bereich: CPU-Temp geht nicht höher als 55° unter Volllast, GPU nicht höher als 75°.
Memtest 4 Stunden lang laufen lassen - keine Fehler.
Prime95 spuckt keine Fehler aus.
Aktuellsten Sound- & Grafiktreiber hab ich installiert.
Nun zu den Bluescreens:
Nummer 1:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010815-30669-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.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0441e000 PsLoadedModuleList = 0xfffff800`04661890
Debug session time: Thu Jan 8 21:57:57.126 2015 (UTC + 1:00)
System Uptime: 0 days 0:34:18.204
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+15171 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.
FAULTING_IP:
+3263643564353663
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: DragonAgeInqui
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff80004c0d2a8 -- (.exr 0xfffff80004c0d2a8)
ExceptionAddress: fffff80004a0782e (hal!HalPutScatterGatherList+0x00000000000000de)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff80004c0d350 -- (.trap 0xfffff80004c0d350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80004c0d490 rbx=0000000000000000 rcx=fffff80004a2fcd8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004a0782e rsp=fffff80004c0d4e0 rbp=0000000000000c60
r8=fffff80004c0d490 r9=fffff80004a2fc60 r10=0000000000000000
r11=fffff80004c0d4b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
hal!HalPutScatterGatherList+0xde:
fffff800`04a0782e f6470a01 test byte ptr [rdi+0Ah],1 ds:e040:00000000`0000000a=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000448b5be to fffff80004493b90
STACK_TEXT:
fffff800`04c0c388 fffff800`0448b5be : 00000000`00000000 fffff880`01cf38d4 fffff800`04c0cb00 fffff800`044bea90 : nt!KeBugCheck
fffff800`04c0c390 fffff800`044be75d : fffff800`046a2380 fffff800`045df260 fffff800`0441e000 fffff800`04c0d2a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`04c0c3c0 fffff800`044bd535 : fffff800`045e2f64 fffff800`04c0c438 fffff800`04c0d2a8 fffff800`0441e000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`04c0c3f0 fffff800`044ce4c1 : fffff800`04c0d2a8 fffff800`04c0cb00 fffff800`00000000 04000000`00000000 : nt!RtlDispatchException+0x415
fffff800`04c0cad0 fffff800`04493242 : fffff800`04c0d2a8 fffffa80`09344a80 fffff800`04c0d350 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`04c0d170 fffff800`04491b4a : fffffa80`09be5bf0 fffff880`01e692e0 fffffa80`091ee0b8 fffff800`0449cfca : nt!KiExceptionDispatch+0xc2
fffff800`04c0d350 fffff800`04a0782e : fffffa80`09344a80 00000000`00000c60 00000000`00000000 fffffa80`0a466c20 : nt!KiGeneralProtectionFault+0x10a
fffff800`04c0d4e0 fffff880`01c6e6e1 : fffffa80`0a466b50 fffffa80`093295f0 fffffa80`0a466a20 00000000`00000000 : hal!HalPutScatterGatherList+0xde
fffff800`04c0d540 fffff880`03399171 : fffffa80`09329000 fffffa80`0a466a20 fffffa80`09329000 00000000`00000000 : ndis!NdisMFreeNetBufferSGList+0x31
fffff800`04c0d580 fffffa80`09329000 : fffffa80`0a466a20 fffffa80`09329000 00000000`00000000 fffffa80`0b52b3a0 : Rt64win7+0x15171
fffff800`04c0d588 fffffa80`0a466a20 : fffffa80`09329000 00000000`00000000 fffffa80`0b52b3a0 00000000`00000000 : 0xfffffa80`09329000
fffff800`04c0d590 fffffa80`09329000 : 00000000`00000000 fffffa80`0b52b3a0 00000000`00000000 fffff800`04c0d6d8 : 0xfffffa80`0a466a20
fffff800`04c0d598 00000000`00000000 : fffffa80`0b52b3a0 00000000`00000000 fffff800`04c0d6d8 00000000`0000000a : 0xfffffa80`09329000
STACK_COMMAND: kb
FOLLOWUP_IP:
Rt64win7+15171
fffff880`03399171 ?? ???
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: Rt64win7+15171
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt64win7
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4db07445
FAILURE_BUCKET_ID: X64_0x1E_0_Rt64win7+15171
BUCKET_ID: X64_0x1E_0_Rt64win7+15171
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\010815-30669-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.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0441e000 PsLoadedModuleList = 0xfffff800`04661890
Debug session time: Thu Jan 8 21:57:57.126 2015 (UTC + 1:00)
System Uptime: 0 days 0:34:18.204
Loading Kernel Symbols
...............................................................
................................................................
.....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {0, 0, 0, 0}
Unable to load image \SystemRoot\system32\DRIVERS\Rt64win7.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rt64win7.sys
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
Probably caused by : Rt64win7.sys ( Rt64win7+15171 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (Win32) 0 (0) - Der Vorgang wurde erfolgreich beendet.
FAULTING_IP:
+3263643564353663
00000000`00000000 ?? ???
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: 0000000000000000
ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0
BUGCHECK_STR: 0x1E_0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: DragonAgeInqui
CURRENT_IRQL: 2
EXCEPTION_RECORD: fffff80004c0d2a8 -- (.exr 0xfffff80004c0d2a8)
ExceptionAddress: fffff80004a0782e (hal!HalPutScatterGatherList+0x00000000000000de)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
TRAP_FRAME: fffff80004c0d350 -- (.trap 0xfffff80004c0d350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff80004c0d490 rbx=0000000000000000 rcx=fffff80004a2fcd8
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80004a0782e rsp=fffff80004c0d4e0 rbp=0000000000000c60
r8=fffff80004c0d490 r9=fffff80004a2fc60 r10=0000000000000000
r11=fffff80004c0d4b0 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
hal!HalPutScatterGatherList+0xde:
fffff800`04a0782e f6470a01 test byte ptr [rdi+0Ah],1 ds:e040:00000000`0000000a=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff8000448b5be to fffff80004493b90
STACK_TEXT:
fffff800`04c0c388 fffff800`0448b5be : 00000000`00000000 fffff880`01cf38d4 fffff800`04c0cb00 fffff800`044bea90 : nt!KeBugCheck
fffff800`04c0c390 fffff800`044be75d : fffff800`046a2380 fffff800`045df260 fffff800`0441e000 fffff800`04c0d2a8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff800`04c0c3c0 fffff800`044bd535 : fffff800`045e2f64 fffff800`04c0c438 fffff800`04c0d2a8 fffff800`0441e000 : nt!RtlpExecuteHandlerForException+0xd
fffff800`04c0c3f0 fffff800`044ce4c1 : fffff800`04c0d2a8 fffff800`04c0cb00 fffff800`00000000 04000000`00000000 : nt!RtlDispatchException+0x415
fffff800`04c0cad0 fffff800`04493242 : fffff800`04c0d2a8 fffffa80`09344a80 fffff800`04c0d350 00000000`00000000 : nt!KiDispatchException+0x135
fffff800`04c0d170 fffff800`04491b4a : fffffa80`09be5bf0 fffff880`01e692e0 fffffa80`091ee0b8 fffff800`0449cfca : nt!KiExceptionDispatch+0xc2
fffff800`04c0d350 fffff800`04a0782e : fffffa80`09344a80 00000000`00000c60 00000000`00000000 fffffa80`0a466c20 : nt!KiGeneralProtectionFault+0x10a
fffff800`04c0d4e0 fffff880`01c6e6e1 : fffffa80`0a466b50 fffffa80`093295f0 fffffa80`0a466a20 00000000`00000000 : hal!HalPutScatterGatherList+0xde
fffff800`04c0d540 fffff880`03399171 : fffffa80`09329000 fffffa80`0a466a20 fffffa80`09329000 00000000`00000000 : ndis!NdisMFreeNetBufferSGList+0x31
fffff800`04c0d580 fffffa80`09329000 : fffffa80`0a466a20 fffffa80`09329000 00000000`00000000 fffffa80`0b52b3a0 : Rt64win7+0x15171
fffff800`04c0d588 fffffa80`0a466a20 : fffffa80`09329000 00000000`00000000 fffffa80`0b52b3a0 00000000`00000000 : 0xfffffa80`09329000
fffff800`04c0d590 fffffa80`09329000 : 00000000`00000000 fffffa80`0b52b3a0 00000000`00000000 fffff800`04c0d6d8 : 0xfffffa80`0a466a20
fffff800`04c0d598 00000000`00000000 : fffffa80`0b52b3a0 00000000`00000000 fffff800`04c0d6d8 00000000`0000000a : 0xfffffa80`09329000
STACK_COMMAND: kb
FOLLOWUP_IP:
Rt64win7+15171
fffff880`03399171 ?? ???
SYMBOL_STACK_INDEX: 9
SYMBOL_NAME: Rt64win7+15171
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Rt64win7
IMAGE_NAME: Rt64win7.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4db07445
FAILURE_BUCKET_ID: X64_0x1E_0_Rt64win7+15171
BUCKET_ID: X64_0x1E_0_Rt64win7+15171
Followup: MachineOwner
---------
Nummer 2:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020315-19780-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.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`04409000 PsLoadedModuleList = 0xfffff800`0464c890
Debug session time: Tue Feb 3 18:21:15.830 2015 (UTC + 1:00)
System Uptime: 0 days 0:35:52.923
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffff880035e6180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880035e6180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
STACK_TEXT:
fffff880`039e73a8 fffff800`044d6dda : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`035e6180 : nt!KeBugCheckEx
fffff880`039e73b0 fffff800`044899f7 : 00000000`00000000 fffff800`00000004 00000000`00002711 00000000`0000000b : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`039e7440 fffff800`049f9895 : fffff800`04a1f460 fffff880`039e75f0 fffff800`04a1f460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`039e7540 fffff800`0447c3d3 : 00000000`2b97e0ba fffff800`045f9e80 fffff800`045f9e80 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`039e7570 fffff800`044b5773 : fffff800`045f9e80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`039e7700 fffff800`04484d1c : 00000000`00000000 fffffa80`0c141008 00000000`00000000 fffff800`045f5c48 : nt!KxFlushEntireTb+0x93
fffff880`039e7740 fffff800`04469cd4 : 00000000`00000002 c6700000`8612d963 fffff880`039e7a60 00000000`0000b467 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`039e7810 fffff800`044fff75 : fffff800`046b9600 fffff800`00000001 00000000`00000001 fffff880`039e7a70 : nt!MiAgeWorkingSet+0x64a
fffff880`039e79c0 fffff800`04469e06 : 00000000`0000085f 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4c7f6
fffff880`039e7a40 fffff800`0446a2b3 : 00000000`00000008 fffff880`039e7ad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`039e7a90 fffff800`0471c0ca : fffffa80`06e1f660 00000000`00000080 fffffa80`06c7a890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`039e7c00 fffff800`04470be6 : fffff880`035e6180 fffffa80`06e1f660 fffff880`035f10c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`039e7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020315-19780-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.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`04409000 PsLoadedModuleList = 0xfffff800`0464c890
Debug session time: Tue Feb 3 18:21:15.830 2015 (UTC + 1:00)
System Uptime: 0 days 0:35:52.923
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffff880035e6180, 4}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
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: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880035e6180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: d
STACK_TEXT:
fffff880`039e73a8 fffff800`044d6dda : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`035e6180 : nt!KeBugCheckEx
fffff880`039e73b0 fffff800`044899f7 : 00000000`00000000 fffff800`00000004 00000000`00002711 00000000`0000000b : nt! ?? ::FNODOBFM::`string'+0x4e3e
fffff880`039e7440 fffff800`049f9895 : fffff800`04a1f460 fffff880`039e75f0 fffff800`04a1f460 00000000`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`039e7540 fffff800`0447c3d3 : 00000000`2b97e0ba fffff800`045f9e80 fffff800`045f9e80 00000000`00000001 : hal!HalpHpetClockInterrupt+0x8d
fffff880`039e7570 fffff800`044b5773 : fffff800`045f9e80 00000000`00000001 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163
fffff880`039e7700 fffff800`04484d1c : 00000000`00000000 fffffa80`0c141008 00000000`00000000 fffff800`045f5c48 : nt!KxFlushEntireTb+0x93
fffff880`039e7740 fffff800`04469cd4 : 00000000`00000002 c6700000`8612d963 fffff880`039e7a60 00000000`0000b467 : nt!KeFlushMultipleRangeTb+0x28c
fffff880`039e7810 fffff800`044fff75 : fffff800`046b9600 fffff800`00000001 00000000`00000001 fffff880`039e7a70 : nt!MiAgeWorkingSet+0x64a
fffff880`039e79c0 fffff800`04469e06 : 00000000`0000085f 00000000`00000000 fffffa80`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4c7f6
fffff880`039e7a40 fffff800`0446a2b3 : 00000000`00000008 fffff880`039e7ad0 00000000`00000001 fffffa80`00000000 : nt!MmWorkingSetManager+0x6e
fffff880`039e7a90 fffff800`0471c0ca : fffffa80`06e1f660 00000000`00000080 fffffa80`06c7a890 00000000`00000001 : nt!KeBalanceSetManager+0x1c3
fffff880`039e7c00 fffff800`04470be6 : fffff880`035e6180 fffffa80`06e1f660 fffff880`035f10c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`039e7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
Nummer 3:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020415-99169-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.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`0440e000 PsLoadedModuleList = 0xfffff800`04651890
Debug session time: Wed Feb 4 18:58:42.027 2015 (UTC + 1:00)
System Uptime: 0 days 0:20:58.120
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800044b71e1, fffff88008f31f90, 0}
Probably caused by : memory_corruption ( nt!MiGetNextNode+15 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800044b71e1, Address of the instruction which caused the bugcheck
Arg3: fffff88008f31f90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt!MiGetNextNode+15
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx
CONTEXT: fffff88008f31f90 -- (.cxr 0xfffff88008f31f90)
rax=0000000000000000 rbx=fffffa80078b12e0 rcx=fffffa80078b12e0
rdx=000007fffff11000 rsi=fffffa8008fb1650 rdi=000000007fffff11
rip=fffff800044b71e1 rsp=fffff88008f32978 rbp=fffff88008f32b60
r8=000007fffffdffff r9=0000000000000011 r10=0000000000000030
r11=0000000000000000 r12=000000006cecf8f0 r13=fffffa800786d278
r14=ffffffffffffffff r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203
nt!MiGetNextNode+0x15:
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx ds:002b:00000000`00000008=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: bfh.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800044b71e1
STACK_TEXT:
fffff880`08f32978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiGetNextNode+0x15
FOLLOWUP_IP:
nt!MiGetNextNode+15
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiGetNextNode+15
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 548a6e28
STACK_COMMAND: .cxr 0xfffff88008f31f90 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiGetNextNode+15
BUCKET_ID: X64_0x3B_nt!MiGetNextNode+15
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800044b71e1, Address of the instruction which caused the bugcheck
Arg3: fffff88008f31f90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt!MiGetNextNode+15
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx
CONTEXT: fffff88008f31f90 -- (.cxr 0xfffff88008f31f90)
rax=0000000000000000 rbx=fffffa80078b12e0 rcx=fffffa80078b12e0
rdx=000007fffff11000 rsi=fffffa8008fb1650 rdi=000000007fffff11
rip=fffff800044b71e1 rsp=fffff88008f32978 rbp=fffff88008f32b60
r8=000007fffffdffff r9=0000000000000011 r10=0000000000000030
r11=0000000000000000 r12=000000006cecf8f0 r13=fffffa800786d278
r14=ffffffffffffffff r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203
nt!MiGetNextNode+0x15:
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx ds:002b:00000000`00000008=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: bfh.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800044b71e1
STACK_TEXT:
fffff880`08f32978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiGetNextNode+0x15
FOLLOWUP_IP:
nt!MiGetNextNode+15
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiGetNextNode+15
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 548a6e28
STACK_COMMAND: .cxr 0xfffff88008f31f90 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiGetNextNode+15
BUCKET_ID: X64_0x3B_nt!MiGetNextNode+15
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020415-99169-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.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`0440e000 PsLoadedModuleList = 0xfffff800`04651890
Debug session time: Wed Feb 4 18:58:42.027 2015 (UTC + 1:00)
System Uptime: 0 days 0:20:58.120
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 3B, {c0000005, fffff800044b71e1, fffff88008f31f90, 0}
Probably caused by : memory_corruption ( nt!MiGetNextNode+15 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800044b71e1, Address of the instruction which caused the bugcheck
Arg3: fffff88008f31f90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt!MiGetNextNode+15
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx
CONTEXT: fffff88008f31f90 -- (.cxr 0xfffff88008f31f90)
rax=0000000000000000 rbx=fffffa80078b12e0 rcx=fffffa80078b12e0
rdx=000007fffff11000 rsi=fffffa8008fb1650 rdi=000000007fffff11
rip=fffff800044b71e1 rsp=fffff88008f32978 rbp=fffff88008f32b60
r8=000007fffffdffff r9=0000000000000011 r10=0000000000000030
r11=0000000000000000 r12=000000006cecf8f0 r13=fffffa800786d278
r14=ffffffffffffffff r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203
nt!MiGetNextNode+0x15:
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx ds:002b:00000000`00000008=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: bfh.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800044b71e1
STACK_TEXT:
fffff880`08f32978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiGetNextNode+0x15
FOLLOWUP_IP:
nt!MiGetNextNode+15
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiGetNextNode+15
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 548a6e28
STACK_COMMAND: .cxr 0xfffff88008f31f90 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiGetNextNode+15
BUCKET_ID: X64_0x3B_nt!MiGetNextNode+15
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800044b71e1, Address of the instruction which caused the bugcheck
Arg3: fffff88008f31f90, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
nt!MiGetNextNode+15
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx
CONTEXT: fffff88008f31f90 -- (.cxr 0xfffff88008f31f90)
rax=0000000000000000 rbx=fffffa80078b12e0 rcx=fffffa80078b12e0
rdx=000007fffff11000 rsi=fffffa8008fb1650 rdi=000000007fffff11
rip=fffff800044b71e1 rsp=fffff88008f32978 rbp=fffff88008f32b60
r8=000007fffffdffff r9=0000000000000011 r10=0000000000000030
r11=0000000000000000 r12=000000006cecf8f0 r13=fffffa800786d278
r14=ffffffffffffffff r15=0000000000000000
iopl=0 nv up ei pl nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010203
nt!MiGetNextNode+0x15:
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx ds:002b:00000000`00000008=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: bfh.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800044b71e1
STACK_TEXT:
fffff880`08f32978 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiGetNextNode+0x15
FOLLOWUP_IP:
nt!MiGetNextNode+15
fffff800`044b71e1 48394808 cmp qword ptr [rax+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiGetNextNode+15
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 548a6e28
STACK_COMMAND: .cxr 0xfffff88008f31f90 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiGetNextNode+15
BUCKET_ID: X64_0x3B_nt!MiGetNextNode+15
Followup: MachineOwner
---------
Und nun die von heute:
Nummer 4:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020715-24429-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.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`04454000 PsLoadedModuleList = 0xfffff800`04697890
Debug session time: Sat Feb 7 21:39:01.217 2015 (UTC + 1:00)
System Uptime: 0 days 4:39:36.310
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffffffffffffb, 1, fffff800045fdd29, 0}
Unable to load image \SystemRoot\system32\drivers\UHSfiltv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for UHSfiltv.sys
*** ERROR: Module load completed but symbols could not be loaded for UHSfiltv.sys
Could not read faulting driver name
Probably caused by : ks.sys ( ks!KspPropertyHandler+da )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffffffffffffb, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800045fdd29, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80004701100
fffffffffffffffb
FAULTING_IP:
nt!ExAllocatePoolWithTag+119
fffff800`045fdd29 884303 mov byte ptr [rbx+3],al
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800b9af350 -- (.trap 0xfffff8800b9af350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000a rbx=0000000000000000 rcx=fffffa800b0314d1
rdx=fffffa800b01ab11 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800045fdd29 rsp=fffff8800b9af4e0 rbp=fffff80004645880
r8=fffffa800b01ab10 r9=fffff80004454000 r10=fffff80004645880
r11=fffffa800b01ab10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!ExAllocatePoolWithTag+0x119:
fffff800`045fdd29 884303 mov byte ptr [rbx+3],al ds:f060:00000000`00000003=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80004547c40 to fffff800044cae80
STACK_TEXT:
fffff880`0b9af1e8 fffff800`04547c40 : 00000000`00000050 ffffffff`fffffffb 00000000`00000001 fffff880`0b9af350 : nt!KeBugCheckEx
fffff880`0b9af1f0 fffff800`044c8fae : 00000000`00000001 ffffffff`fffffffb 00000000`00000000 ffffffff`fffffff8 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`0b9af350 fffff800`045fdd29 : 00000000`00000000 00000000`000007ff 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0b9af4e0 fffff800`044de246 : fffffa80`06e0aa28 00000000`00000008 00000000`00516c4e 00000000`00000000 : nt!ExAllocatePoolWithTag+0x119
fffff880`0b9af5d0 fffff880`04819f4a : fffffa80`06f22e50 00000000`00000028 fffffa80`06f22bd0 fffffa80`00000000 : nt!ExAllocatePoolWithQuotaTag+0x56
fffff880`0b9af620 fffff880`0481ab47 : fffffa80`06f22bd0 fffff800`00000001 fffff880`04818528 00000000`00000000 : ks!KspPropertyHandler+0xda
fffff880`0b9af690 fffff880`0481b131 : 00000000`c0000010 fffffa80`06f22bd0 fffffa80`07119b00 00000000`00000000 : ks!KspHandleAutomationIoControl+0x2c7
fffff880`0b9af710 fffff880`0481a7bb : fffffa80`09b13bc0 00000000`00000000 00000000`00000001 00000000`00000000 : ks!CKsPin:
ispatchDeviceIoControl+0xcd
fffff880`0b9af770 fffff880`04801560 : 00000000`00000000 fffff800`047b4767 fffff880`0b9afa58 fffffa80`0ae30ac0 : ks!KsDispatchIrp+0xdb
fffff880`0b9af7a0 fffff880`06efe315 : fffffa80`09ee19d0 fffffa80`09f1db40 00000000`00000001 fffffa80`06f22ee0 : ks!CKsDevice:
assThroughIrp+0xc0
fffff880`0b9af7e0 fffffa80`09ee19d0 : fffffa80`09f1db40 00000000`00000001 fffffa80`06f22ee0 fffffa80`09f1db50 : UHSfiltv+0x1315
fffff880`0b9af7e8 fffffa80`09f1db40 : 00000000`00000001 fffffa80`06f22ee0 fffffa80`09f1db50 fffff880`06e9e5fb : 0xfffffa80`09ee19d0
fffff880`0b9af7f0 00000000`00000001 : fffffa80`06f22ee0 fffffa80`09f1db50 fffff880`06e9e5fb fffffa80`09fb59f0 : 0xfffffa80`09f1db40
fffff880`0b9af7f8 fffffa80`06f22ee0 : fffffa80`09f1db50 fffff880`06e9e5fb fffffa80`09fb59f0 00000000`00000000 : 0x1
fffff880`0b9af800 fffffa80`09f1db50 : fffff880`06e9e5fb fffffa80`09fb59f0 00000000`00000000 00000001`00000001 : 0xfffffa80`06f22ee0
fffff880`0b9af808 fffff880`06e9e5fb : fffffa80`09fb59f0 00000000`00000000 00000001`00000001 fffffa80`06f22ee0 : 0xfffffa80`09f1db50
fffff880`0b9af810 fffff880`00000028 : 00000000`0323fd80 fffffa80`06f22bd0 00000000`00000003 fffffa80`06f22bd0 : ksthunk!CKernelFilterDevice::FileObjectToFilterFile+0x6b
fffff880`0b9af840 00000000`0323fd80 : fffffa80`06f22bd0 00000000`00000003 fffffa80`06f22bd0 fffffa80`09f1db40 : 0xfffff880`00000028
fffff880`0b9af848 fffffa80`06f22bd0 : 00000000`00000003 fffffa80`06f22bd0 fffffa80`09f1db40 fffff880`06e9e825 : 0x323fd80
fffff880`0b9af850 00000000`00000003 : fffffa80`06f22bd0 fffffa80`09f1db40 fffff880`06e9e825 fffffa80`06f22e98 : 0xfffffa80`06f22bd0
fffff880`0b9af858 fffffa80`06f22bd0 : fffffa80`09f1db40 fffff880`06e9e825 fffffa80`06f22e98 fffffa80`06f22ee0 : 0x3
fffff880`0b9af860 fffffa80`09f1db40 : fffff880`06e9e825 fffffa80`06f22e98 fffffa80`06f22ee0 fffffa80`06f22ee0 : 0xfffffa80`06f22bd0
fffff880`0b9af868 fffff880`06e9e825 : fffffa80`06f22e98 fffffa80`06f22ee0 fffffa80`06f22ee0 fffffa80`06f22bd0 : 0xfffffa80`09f1db40
fffff880`0b9af870 fffff800`047e70f7 : fffffa80`07dd7f20 fffff880`0b9afb60 fffffa80`00000000 fffffa80`07dd7f20 : ksthunk!CKernelFilterDevice:
ispatchIrp+0x11d
fffff880`0b9af8d0 fffff800`047e7956 : 00000000`0323fba0 00000000`000003bd 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0b9afa00 fffff800`044ca113 : fffffa80`0a3ffb50 00000000`0323fb88 fffff880`0b9afa88 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0b9afa70 00000000`77ba132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0323fb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ba132a
STACK_COMMAND: kb
FOLLOWUP_IP:
ks!KspPropertyHandler+da
fffff880`04819f4a 48894318 mov qword ptr [rbx+18h],rax
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: ks!KspPropertyHandler+da
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ks
IMAGE_NAME: ks.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a3f3
FAILURE_BUCKET_ID: X64_0x50_ks!KspPropertyHandler+da
BUCKET_ID: X64_0x50_ks!KspPropertyHandler+da
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020715-24429-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.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`04454000 PsLoadedModuleList = 0xfffff800`04697890
Debug session time: Sat Feb 7 21:39:01.217 2015 (UTC + 1:00)
System Uptime: 0 days 4:39:36.310
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffffffffffffffb, 1, fffff800045fdd29, 0}
Unable to load image \SystemRoot\system32\drivers\UHSfiltv.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for UHSfiltv.sys
*** ERROR: Module load completed but symbols could not be loaded for UHSfiltv.sys
Could not read faulting driver name
Probably caused by : ks.sys ( ks!KspPropertyHandler+da )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffffffffffffffb, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800045fdd29, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80004701100
fffffffffffffffb
FAULTING_IP:
nt!ExAllocatePoolWithTag+119
fffff800`045fdd29 884303 mov byte ptr [rbx+3],al
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: audiodg.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800b9af350 -- (.trap 0xfffff8800b9af350)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000a rbx=0000000000000000 rcx=fffffa800b0314d1
rdx=fffffa800b01ab11 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800045fdd29 rsp=fffff8800b9af4e0 rbp=fffff80004645880
r8=fffffa800b01ab10 r9=fffff80004454000 r10=fffff80004645880
r11=fffffa800b01ab10 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!ExAllocatePoolWithTag+0x119:
fffff800`045fdd29 884303 mov byte ptr [rbx+3],al ds:f060:00000000`00000003=??
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80004547c40 to fffff800044cae80
STACK_TEXT:
fffff880`0b9af1e8 fffff800`04547c40 : 00000000`00000050 ffffffff`fffffffb 00000000`00000001 fffff880`0b9af350 : nt!KeBugCheckEx
fffff880`0b9af1f0 fffff800`044c8fae : 00000000`00000001 ffffffff`fffffffb 00000000`00000000 ffffffff`fffffff8 : nt! ?? ::FNODOBFM::`string'+0x4518f
fffff880`0b9af350 fffff800`045fdd29 : 00000000`00000000 00000000`000007ff 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`0b9af4e0 fffff800`044de246 : fffffa80`06e0aa28 00000000`00000008 00000000`00516c4e 00000000`00000000 : nt!ExAllocatePoolWithTag+0x119
fffff880`0b9af5d0 fffff880`04819f4a : fffffa80`06f22e50 00000000`00000028 fffffa80`06f22bd0 fffffa80`00000000 : nt!ExAllocatePoolWithQuotaTag+0x56
fffff880`0b9af620 fffff880`0481ab47 : fffffa80`06f22bd0 fffff800`00000001 fffff880`04818528 00000000`00000000 : ks!KspPropertyHandler+0xda
fffff880`0b9af690 fffff880`0481b131 : 00000000`c0000010 fffffa80`06f22bd0 fffffa80`07119b00 00000000`00000000 : ks!KspHandleAutomationIoControl+0x2c7
fffff880`0b9af710 fffff880`0481a7bb : fffffa80`09b13bc0 00000000`00000000 00000000`00000001 00000000`00000000 : ks!CKsPin:

fffff880`0b9af770 fffff880`04801560 : 00000000`00000000 fffff800`047b4767 fffff880`0b9afa58 fffffa80`0ae30ac0 : ks!KsDispatchIrp+0xdb
fffff880`0b9af7a0 fffff880`06efe315 : fffffa80`09ee19d0 fffffa80`09f1db40 00000000`00000001 fffffa80`06f22ee0 : ks!CKsDevice:

fffff880`0b9af7e0 fffffa80`09ee19d0 : fffffa80`09f1db40 00000000`00000001 fffffa80`06f22ee0 fffffa80`09f1db50 : UHSfiltv+0x1315
fffff880`0b9af7e8 fffffa80`09f1db40 : 00000000`00000001 fffffa80`06f22ee0 fffffa80`09f1db50 fffff880`06e9e5fb : 0xfffffa80`09ee19d0
fffff880`0b9af7f0 00000000`00000001 : fffffa80`06f22ee0 fffffa80`09f1db50 fffff880`06e9e5fb fffffa80`09fb59f0 : 0xfffffa80`09f1db40
fffff880`0b9af7f8 fffffa80`06f22ee0 : fffffa80`09f1db50 fffff880`06e9e5fb fffffa80`09fb59f0 00000000`00000000 : 0x1
fffff880`0b9af800 fffffa80`09f1db50 : fffff880`06e9e5fb fffffa80`09fb59f0 00000000`00000000 00000001`00000001 : 0xfffffa80`06f22ee0
fffff880`0b9af808 fffff880`06e9e5fb : fffffa80`09fb59f0 00000000`00000000 00000001`00000001 fffffa80`06f22ee0 : 0xfffffa80`09f1db50
fffff880`0b9af810 fffff880`00000028 : 00000000`0323fd80 fffffa80`06f22bd0 00000000`00000003 fffffa80`06f22bd0 : ksthunk!CKernelFilterDevice::FileObjectToFilterFile+0x6b
fffff880`0b9af840 00000000`0323fd80 : fffffa80`06f22bd0 00000000`00000003 fffffa80`06f22bd0 fffffa80`09f1db40 : 0xfffff880`00000028
fffff880`0b9af848 fffffa80`06f22bd0 : 00000000`00000003 fffffa80`06f22bd0 fffffa80`09f1db40 fffff880`06e9e825 : 0x323fd80
fffff880`0b9af850 00000000`00000003 : fffffa80`06f22bd0 fffffa80`09f1db40 fffff880`06e9e825 fffffa80`06f22e98 : 0xfffffa80`06f22bd0
fffff880`0b9af858 fffffa80`06f22bd0 : fffffa80`09f1db40 fffff880`06e9e825 fffffa80`06f22e98 fffffa80`06f22ee0 : 0x3
fffff880`0b9af860 fffffa80`09f1db40 : fffff880`06e9e825 fffffa80`06f22e98 fffffa80`06f22ee0 fffffa80`06f22ee0 : 0xfffffa80`06f22bd0
fffff880`0b9af868 fffff880`06e9e825 : fffffa80`06f22e98 fffffa80`06f22ee0 fffffa80`06f22ee0 fffffa80`06f22bd0 : 0xfffffa80`09f1db40
fffff880`0b9af870 fffff800`047e70f7 : fffffa80`07dd7f20 fffff880`0b9afb60 fffffa80`00000000 fffffa80`07dd7f20 : ksthunk!CKernelFilterDevice:

fffff880`0b9af8d0 fffff800`047e7956 : 00000000`0323fba0 00000000`000003bd 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x607
fffff880`0b9afa00 fffff800`044ca113 : fffffa80`0a3ffb50 00000000`0323fb88 fffff880`0b9afa88 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
fffff880`0b9afa70 00000000`77ba132a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0323fb58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ba132a
STACK_COMMAND: kb
FOLLOWUP_IP:
ks!KspPropertyHandler+da
fffff880`04819f4a 48894318 mov qword ptr [rbx+18h],rax
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: ks!KspPropertyHandler+da
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ks
IMAGE_NAME: ks.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7a3f3
FAILURE_BUCKET_ID: X64_0x50_ks!KspPropertyHandler+da
BUCKET_ID: X64_0x50_ks!KspPropertyHandler+da
Followup: MachineOwner
---------
Nummer 5:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020715-26535-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.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`04452000 PsLoadedModuleList = 0xfffff800`04695890
Debug session time: Sat Feb 7 16:35:14.903 2015 (UTC + 1:00)
System Uptime: 0 days 2:11:37.900
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff880021c651a, 1, 48}
Unable to load image \SystemRoot\system32\DRIVERS\klflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klflt.sys
*** ERROR: Module load completed but symbols could not be loaded for klflt.sys
Probably caused by : hardware ( klflt+2651a )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880021c651a, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000048, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
klflt+2651a
fffff880`021c651a 085748 or byte ptr [rdi+48h],dl
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000048
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800046ff100
0000000000000048
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: bfh.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800b3334c0 -- (.trap 0xfffff8800b3334c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000004b040000 rbx=0000000000000000 rcx=fffff8a0007c9000
rdx=000000004b041d36 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880021c651a rsp=fffff8800b333650 rbp=fffff8800b333820
r8=fffff8800b333738 r9=0000000000000000 r10=fffffa8006c6e288
r11=fffff8800b333758 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
klflt+0x2651a:
fffff880`021c651a 085748 or byte ptr [rdi+48h],dl ds:c6a0:00000000`00000048=??
Resetting default scope
MISALIGNED_IP:
klflt+2651a
fffff880`021c651a 085748 or byte ptr [rdi+48h],dl
LAST_CONTROL_TRANSFER: from fffff80004513a18 to fffff800044c8e80
STACK_TEXT:
fffff880`0b332c38 fffff800`04513a18 : 00000000`0000001e ffffffff`c0000005 fffff880`021c651a 00000000`00000001 : nt!KeBugCheckEx
fffff880`0b332c40 fffff800`044c8502 : fffff880`0b333418 00000000`044b0000 fffff880`0b3334c0 fffff8a0`1100c930 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`0b3332e0 fffff800`044c707a : 00000000`00000001 00000000`00000048 fffff680`0000e200 00000000`044b0000 : nt!KiExceptionDispatch+0xc2
fffff880`0b3334c0 fffff880`021c651a : 00000000`00000000 00000000`00001c40 00000000`00001c40 00000000`01c40fff : nt!KiPageFault+0x23a
fffff880`0b333650 00000000`00000000 : 00000000`00001c40 00000000`00001c40 00000000`01c40fff 00000000`00000000 : klflt+0x2651a
STACK_COMMAND: kb
FOLLOWUP_IP:
klflt+2651a
fffff880`021c651a 085748 or byte ptr [rdi+48h],dl
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: klflt+2651a
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_klflt.sys
BUCKET_ID: X64_IP_MISALIGNED_klflt.sys
Followup: MachineOwner
---------
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\020715-26535-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.18700.amd64fre.win7sp1_gdr.141211-1742
Machine Name:
Kernel base = 0xfffff800`04452000 PsLoadedModuleList = 0xfffff800`04695890
Debug session time: Sat Feb 7 16:35:14.903 2015 (UTC + 1:00)
System Uptime: 0 days 2:11:37.900
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000005, fffff880021c651a, 1, 48}
Unable to load image \SystemRoot\system32\DRIVERS\klflt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for klflt.sys
*** ERROR: Module load completed but symbols could not be loaded for klflt.sys
Probably caused by : hardware ( klflt+2651a )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff880021c651a, The address that the exception occurred at
Arg3: 0000000000000001, Parameter 0 of the exception
Arg4: 0000000000000048, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
FAULTING_IP:
klflt+2651a
fffff880`021c651a 085748 or byte ptr [rdi+48h],dl
EXCEPTION_PARAMETER1: 0000000000000001
EXCEPTION_PARAMETER2: 0000000000000048
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800046ff100
0000000000000048
ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.
BUGCHECK_STR: 0x1E_c0000005
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: bfh.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff8800b3334c0 -- (.trap 0xfffff8800b3334c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000004b040000 rbx=0000000000000000 rcx=fffff8a0007c9000
rdx=000000004b041d36 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880021c651a rsp=fffff8800b333650 rbp=fffff8800b333820
r8=fffff8800b333738 r9=0000000000000000 r10=fffffa8006c6e288
r11=fffff8800b333758 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
klflt+0x2651a:
fffff880`021c651a 085748 or byte ptr [rdi+48h],dl ds:c6a0:00000000`00000048=??
Resetting default scope
MISALIGNED_IP:
klflt+2651a
fffff880`021c651a 085748 or byte ptr [rdi+48h],dl
LAST_CONTROL_TRANSFER: from fffff80004513a18 to fffff800044c8e80
STACK_TEXT:
fffff880`0b332c38 fffff800`04513a18 : 00000000`0000001e ffffffff`c0000005 fffff880`021c651a 00000000`00000001 : nt!KeBugCheckEx
fffff880`0b332c40 fffff800`044c8502 : fffff880`0b333418 00000000`044b0000 fffff880`0b3334c0 fffff8a0`1100c930 : nt! ?? ::FNODOBFM::`string'+0x487ed
fffff880`0b3332e0 fffff800`044c707a : 00000000`00000001 00000000`00000048 fffff680`0000e200 00000000`044b0000 : nt!KiExceptionDispatch+0xc2
fffff880`0b3334c0 fffff880`021c651a : 00000000`00000000 00000000`00001c40 00000000`00001c40 00000000`01c40fff : nt!KiPageFault+0x23a
fffff880`0b333650 00000000`00000000 : 00000000`00001c40 00000000`00001c40 00000000`01c40fff 00000000`00000000 : klflt+0x2651a
STACK_COMMAND: kb
FOLLOWUP_IP:
klflt+2651a
fffff880`021c651a 085748 or byte ptr [rdi+48h],dl
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: klflt+2651a
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED_klflt.sys
BUCKET_ID: X64_IP_MISALIGNED_klflt.sys
Followup: MachineOwner
---------
Bluescreens sind für mich Neuland. Hab dabei keine Ahnung, wo ich anfangen und aufhören muss.
Deshalb bräuchte ich Hilfe vom Fach.
Danke schonmal im Voraus für die Bemühungen!
Zuletzt bearbeitet: