Hallo Community!
Wie oben schon beschrieben habe ich mit dem Epu 6 Engine ein Problem.
Und zwar läuft mein System nur im ab dem Modus High Performance auswärts sprich Turbo Mode wäre darüber,
alle anderen Stufen wie die Medium Power Saving Mode und Max. Power Saving Mode verursachen einen Bluescreen.
Das hat mit soweit nicht gestört bis zum heutigen Tag an dem ich meinen Rechner mit leiseren Lüfter und Dämmmatten austatte und somit in den Genuss von Ruhe kommen möchte.
Da geht kein Weg daran vorbei die Kalibrierung von der Epu Engine in den Griff zu bekommen.
Die Bluescreenmeldung lautet wie folgt:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8b0f0c0, 2, 1, fffff88004b1054d}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000008b0f0c0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004b1054d, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800035120e8
GetUlongFromAddress: unable to read from fffff80003512198
0000000008b0f0c0 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
dxgmms1!VidSchiProcessDpcCompletedPacket+129
fffff880`04b1054d 8c4800 mov word ptr [rax],cs
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE: FFFFF88003122FB0
TRAP_FRAME: fffff8800311b780 -- (.trap 0xfffff8800311b780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000008b0f0c0 rbx=0000000000000000 rcx=00000000ffffffff
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b1054d rsp=fffff8800311b910 rbp=00000000746b5044
r8=fffff8800311b950 r9=0000000000000000 r10=fffffa8005e587d0
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgmms1!VidSchiProcessDpcCompletedPacket+0x129:
fffff880`04b1054d 8c4800 mov word ptr [rax],cs ds:00000000`08b0f0c0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032e0be9 to fffff800032e1640
STACK_TEXT:
fffff880`0311b638 fffff800`032e0be9 : 00000000`0000000a 00000000`08b0f0c0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0311b640 fffff800`032df860 : 00000000`0005bff5 fffff880`1011164c fffff880`101116d2 fffffa80`05e680d0 : nt!KiBugCheckDispatch+0x69
fffff880`0311b780 fffff880`04b1054d : fffff880`0311b950 fffffa80`05e58010 fffffa80`05e67000 00000000`0005bff5 : nt!KiPageFault+0x260
fffff880`0311b910 fffff880`04b0fe00 : fffffa80`00000000 fffffa80`03c51000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x129
fffff880`0311b9b0 fffff880`04b0fc4c : fffffa80`08c92550 fffffa80`05e58010 fffff880`0311bb00 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`0311ba00 fffff880`04a161cf : fffffa80`04c72480 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`0311ba50 fffff880`10111597 : fffffa80`04e5f000 fffffa80`04e5f000 00000000`00000000 00000000`0005bff5 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`0311ba80 fffffa80`04e5f000 : fffffa80`04e5f000 00000000`00000000 00000000`0005bff5 fffff880`1011152e : nvlddmkm+0xbd597
fffff880`0311ba88 fffffa80`04e5f000 : 00000000`00000000 00000000`0005bff5 fffff880`1011152e fffffa80`04e5f000 : 0xfffffa80`04e5f000
fffff880`0311ba90 00000000`00000000 : 00000000`0005bff5 fffff880`1011152e fffffa80`04e5f000 00000000`00000000 : 0xfffffa80`04e5f000
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms1
fffff88004b10540-fffff88004b10546 7 bytes - dxgmms1!VidSchiProcessDpcCompletedPacket+11c
[ f0 41 01 8c 24 b4 03:92 84 4f 00 95 87 45 ]
fffff88004b10548-fffff88004b10556 15 bytes - dxgmms1!VidSchiProcessDpcCompletedPacket+124 (+0x08)
[ 00 f0 41 01 8c 24 94 03:97 8b 43 00 95 8c 48 00 ]
fffff88004b10558-fffff88004b1056a 19 bytes - dxgmms1!VidSchiProcessDpcCompletedPacket+134 (+0x10)
[ 00 8b c1 f0 0f c1 85 2c:55 9d 6f 00 5a c7 a1 00 ]
fffff88004b1056c-fffff88004b1057e 19 bytes - dxgmms1!VidSchiProcessDpcCompletedPacket+148 (+0x14)
[ 00 a8 08 74 18 83 a5 90:a1 a0 50 00 9f 9d 4f 00 ]
60 errors : !dxgmms1 (fffff88004b10540-fffff88004b1057e)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE_64
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_64
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_64
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_memory_corruption_large_64
FAILURE_ID_HASH: {c79799b7-1616-424a-38ef-dba1562684b4}
Followup: memory_corruption
Wäre schön wenn ich es endlich mal hinbekommen würde , da ich schließlich den Rechner schon 5 Jahre besitze und immer den CPU-Lüfter auf volllast jagen muss
Wie oben schon beschrieben habe ich mit dem Epu 6 Engine ein Problem.
Und zwar läuft mein System nur im ab dem Modus High Performance auswärts sprich Turbo Mode wäre darüber,
alle anderen Stufen wie die Medium Power Saving Mode und Max. Power Saving Mode verursachen einen Bluescreen.
Das hat mit soweit nicht gestört bis zum heutigen Tag an dem ich meinen Rechner mit leiseren Lüfter und Dämmmatten austatte und somit in den Genuss von Ruhe kommen möchte.
Da geht kein Weg daran vorbei die Kalibrierung von der Epu Engine in den Griff zu bekommen.
Die Bluescreenmeldung lautet wie folgt:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {8b0f0c0, 2, 1, fffff88004b1054d}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: 0000000008b0f0c0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff88004b1054d, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800035120e8
GetUlongFromAddress: unable to read from fffff80003512198
0000000008b0f0c0 Nonpaged pool
CURRENT_IRQL: 2
FAULTING_IP:
dxgmms1!VidSchiProcessDpcCompletedPacket+129
fffff880`04b1054d 8c4800 mov word ptr [rax],cs
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xD1
PROCESS_NAME: System
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
DPC_STACK_BASE: FFFFF88003122FB0
TRAP_FRAME: fffff8800311b780 -- (.trap 0xfffff8800311b780)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000008b0f0c0 rbx=0000000000000000 rcx=00000000ffffffff
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88004b1054d rsp=fffff8800311b910 rbp=00000000746b5044
r8=fffff8800311b950 r9=0000000000000000 r10=fffffa8005e587d0
r11=0000000000000003 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
dxgmms1!VidSchiProcessDpcCompletedPacket+0x129:
fffff880`04b1054d 8c4800 mov word ptr [rax],cs ds:00000000`08b0f0c0=????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff800032e0be9 to fffff800032e1640
STACK_TEXT:
fffff880`0311b638 fffff800`032e0be9 : 00000000`0000000a 00000000`08b0f0c0 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`0311b640 fffff800`032df860 : 00000000`0005bff5 fffff880`1011164c fffff880`101116d2 fffffa80`05e680d0 : nt!KiBugCheckDispatch+0x69
fffff880`0311b780 fffff880`04b1054d : fffff880`0311b950 fffffa80`05e58010 fffffa80`05e67000 00000000`0005bff5 : nt!KiPageFault+0x260
fffff880`0311b910 fffff880`04b0fe00 : fffffa80`00000000 fffffa80`03c51000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiProcessDpcCompletedPacket+0x129
fffff880`0311b9b0 fffff880`04b0fc4c : fffffa80`08c92550 fffffa80`05e58010 fffff880`0311bb00 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpcWorker+0x198
fffff880`0311ba00 fffff880`04a161cf : fffffa80`04c72480 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms1!VidSchDdiNotifyDpc+0x94
fffff880`0311ba50 fffff880`10111597 : fffffa80`04e5f000 fffffa80`04e5f000 00000000`00000000 00000000`0005bff5 : dxgkrnl!DxgNotifyDpcCB+0x77
fffff880`0311ba80 fffffa80`04e5f000 : fffffa80`04e5f000 00000000`00000000 00000000`0005bff5 fffff880`1011152e : nvlddmkm+0xbd597
fffff880`0311ba88 fffffa80`04e5f000 : 00000000`00000000 00000000`0005bff5 fffff880`1011152e fffffa80`04e5f000 : 0xfffffa80`04e5f000
fffff880`0311ba90 00000000`00000000 : 00000000`0005bff5 fffff880`1011152e fffffa80`04e5f000 00000000`00000000 : 0xfffffa80`04e5f000
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !dxgmms1
fffff88004b10540-fffff88004b10546 7 bytes - dxgmms1!VidSchiProcessDpcCompletedPacket+11c
[ f0 41 01 8c 24 b4 03:92 84 4f 00 95 87 45 ]
fffff88004b10548-fffff88004b10556 15 bytes - dxgmms1!VidSchiProcessDpcCompletedPacket+124 (+0x08)
[ 00 f0 41 01 8c 24 94 03:97 8b 43 00 95 8c 48 00 ]
fffff88004b10558-fffff88004b1056a 19 bytes - dxgmms1!VidSchiProcessDpcCompletedPacket+134 (+0x10)
[ 00 8b c1 f0 0f c1 85 2c:55 9d 6f 00 5a c7 a1 00 ]
fffff88004b1056c-fffff88004b1057e 19 bytes - dxgmms1!VidSchiProcessDpcCompletedPacket+148 (+0x14)
[ 00 a8 08 74 18 83 a5 90:a1 a0 50 00 9f 9d 4f 00 ]
60 errors : !dxgmms1 (fffff88004b10540-fffff88004b1057e)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE_64
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_64
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE_64
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:x64_memory_corruption_large_64
FAILURE_ID_HASH: {c79799b7-1616-424a-38ef-dba1562684b4}
Followup: memory_corruption
Wäre schön wenn ich es endlich mal hinbekommen würde , da ich schließlich den Rechner schon 5 Jahre besitze und immer den CPU-Lüfter auf volllast jagen muss