Hallo, ich hatte schon mal probleme mit blue screens gehabt, allerdings wurden die probleme beseitigt. Ich hatte mich jetzt ans OC gewagt und auch die werte hier reingepostet und sie mit prime getestet. CPU max temp lag um die 45°C.
Ich hatte auch während des Spielens keine probleme gehabt.
Als ich den Rechner hochgefahren hatte hing es sich kurz auf und dann kam es zum bluescreen. Ich habe es mit windebugg ausgewertet nur verstehe ich leider von den Daten die da ausspuckt nicht wirklich etwas.
Würde mich sehr freuen wenn mir jemand daraus die Ursache nennen würde
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030610-17347-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`03057e50
Debug session time: Sat Mar 6 10:17:32.684 2010 (GMT+1)
System Uptime: 0 days 0:10:23.291
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d8959af539, b3b7465ee818d43f, fffff880017347e0, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8959af539, Reserved
Arg2: b3b7465ee818d43f, Reserved
Arg3: fffff880017347e0, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
Debugging Details:
------------------
BUGCHECK_STR: 0x109
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002e8bf00
STACK_TEXT:
fffff880`02fd9598 00000000`00000000 : 00000000`00000109 a3a039d8`959af539 b3b7465e`e818d43f fffff880`017347e0 : nt!KeBugCheckEx
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
fffff88001734800-fffff88001734806 7 bytes - ndis!WppTraceCallback+20
[ d2 49 8b f9 45 21 55:82 00 00 00 a1 00 00 ]
fffff88001734808-fffff88001734811 10 bytes - ndis!WppTraceCallback+28 (+0x08)
[ 40 8a f1 80 f9 03 0f 86:a1 00 00 00 a1 00 00 00 ]
fffff88001734814-fffff8800173481a 7 bytes - ndis!WppTraceCallback+34 (+0x0c)
[ 80 f9 05 0f 86 6b 01:a1 00 00 00 82 00 00 ]
fffff8800173481c-fffff88001734824 9 bytes - ndis!WppTraceCallback+3c (+0x08)
[ 00 80 f9 07 0f 86 41 02:a1 00 00 00 a1 00 00 00 ]
fffff88001734826-fffff8800173482c 7 bytes - ndis!WppTraceCallback+46 (+0x0a)
[ 80 f9 08 0f 85 32 02:00 00 a1 00 00 00 a1 ]
fffff8800173482f-fffff88001734834 6 bytes - ndis!WppTraceCallback+4f (+0x09)
[ 48 8b ac 24 90 00:00 a1 00 00 00 82 ]
fffff88001734837-fffff8800173485d 39 bytes - ndis!WppTraceCallback+57 (+0x08)
[ 33 db 83 3d 20 c1 fe ff:00 a1 00 00 00 a1 00 00 ]
fffff88001734860-fffff88001734868 9 bytes - ndis!WppTraceCallback+80 (+0x29)
[ c0 41 83 f8 04 0f 82 fc:82 00 00 00 82 00 00 00 ]
fffff8800173486b-fffff88001734870 6 bytes - ndis!WppTraceCallback+8b (+0x0b)
[ 41 89 01 41 c7 45:00 82 00 00 00 82 ]
fffff88001734872 - ndis!WppTraceCallback+92 (+0x07)
[ 04:00 ]
fffff88001734874 - ndis!WppTraceCallback+94 (+0x02)
[ 00:82 ]
fffff88001734876-fffff8800173489e 41 bytes - ndis!WppTraceCallback+96 (+0x02)
[ e9 ec 01 00 00 48 8b 55:00 00 80 fa a0 ff 63 28 ]
fffff880017348a0-fffff880017348a1 2 bytes - ndis!WppTraceCallback+c0 (+0x2a)
[ 10 08:82 00 ]
fffff880017348a3-fffff880017348ac 10 bytes - ndis!WppTraceCallback+c3 (+0x03)
[ 21 5d 2c 88 5d 29 e9 b9:00 00 00 06 00 00 00 00 ]
fffff880017348ae-fffff880017348c4 23 bytes - ndis!WppTraceCallback+ce (+0x0b)
[ 4c 8b 75 20 48 8b 40 10:00 00 7b e9 06 fb 00 00 ]
fffff880017348c7-fffff880017348cb 5 bytes - ndis!WppTraceCallback+e7 (+0x19)
[ c0 e9 9a 01 00:00 d0 99 06 03 ]
fffff880017348cd-fffff88001734969 157 bytes - ndis!WppTraceCallback+ed (+0x06)
[ 4d 85 f6 75 0d 8b f3 45:48 fc 00 80 c1 21 cf 08 ]
fffff8800173496b-fffff8800173496d 3 bytes - ndis!WppTraceCallback+18b (+0x9e)
[ e9 f7 00:f0 f3 ee ]
fffff8800173496f-fffff8800173497f 17 bytes - ndis!WppTraceCallback+18f (+0x04)
[ 00 41 ba 23 00 00 c0 41:f0 f3 ee 00 f0 f3 ee 00 ]
360 errors : !ndis (fffff88001734800-fffff8800173497f)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------
Ich hatte auch während des Spielens keine probleme gehabt.
Als ich den Rechner hochgefahren hatte hing es sich kurz auf und dann kam es zum bluescreen. Ich habe es mit windebugg ausgewertet nur verstehe ich leider von den Daten die da ausspuckt nicht wirklich etwas.
Würde mich sehr freuen wenn mir jemand daraus die Ursache nennen würde
Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\030610-17347-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e1a000 PsLoadedModuleList = 0xfffff800`03057e50
Debug session time: Sat Mar 6 10:17:32.684 2010 (GMT+1)
System Uptime: 0 days 0:10:23.291
Loading Kernel Symbols
...............................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 109, {a3a039d8959af539, b3b7465ee818d43f, fffff880017347e0, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a039d8959af539, Reserved
Arg2: b3b7465ee818d43f, Reserved
Arg3: fffff880017347e0, Failure type dependent information
Arg4: 0000000000000001, Type of corrupted region, can be
0 : A generic data region
1 : Modification of a function or .pdata
2 : A processor IDT
3 : A processor GDT
4 : Type 1 process list corruption
5 : Type 2 process list corruption
6 : Debug routine modification
7 : Critical MSR modification
Debugging Details:
------------------
BUGCHECK_STR: 0x109
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: CODE_CORRUPTION
PROCESS_NAME: System
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80002e8bf00
STACK_TEXT:
fffff880`02fd9598 00000000`00000000 : 00000000`00000109 a3a039d8`959af539 b3b7465e`e818d43f fffff880`017347e0 : nt!KeBugCheckEx
STACK_COMMAND: kb
CHKIMG_EXTENSION: !chkimg -lo 50 -d !ndis
fffff88001734800-fffff88001734806 7 bytes - ndis!WppTraceCallback+20
[ d2 49 8b f9 45 21 55:82 00 00 00 a1 00 00 ]
fffff88001734808-fffff88001734811 10 bytes - ndis!WppTraceCallback+28 (+0x08)
[ 40 8a f1 80 f9 03 0f 86:a1 00 00 00 a1 00 00 00 ]
fffff88001734814-fffff8800173481a 7 bytes - ndis!WppTraceCallback+34 (+0x0c)
[ 80 f9 05 0f 86 6b 01:a1 00 00 00 82 00 00 ]
fffff8800173481c-fffff88001734824 9 bytes - ndis!WppTraceCallback+3c (+0x08)
[ 00 80 f9 07 0f 86 41 02:a1 00 00 00 a1 00 00 00 ]
fffff88001734826-fffff8800173482c 7 bytes - ndis!WppTraceCallback+46 (+0x0a)
[ 80 f9 08 0f 85 32 02:00 00 a1 00 00 00 a1 ]
fffff8800173482f-fffff88001734834 6 bytes - ndis!WppTraceCallback+4f (+0x09)
[ 48 8b ac 24 90 00:00 a1 00 00 00 82 ]
fffff88001734837-fffff8800173485d 39 bytes - ndis!WppTraceCallback+57 (+0x08)
[ 33 db 83 3d 20 c1 fe ff:00 a1 00 00 00 a1 00 00 ]
fffff88001734860-fffff88001734868 9 bytes - ndis!WppTraceCallback+80 (+0x29)
[ c0 41 83 f8 04 0f 82 fc:82 00 00 00 82 00 00 00 ]
fffff8800173486b-fffff88001734870 6 bytes - ndis!WppTraceCallback+8b (+0x0b)
[ 41 89 01 41 c7 45:00 82 00 00 00 82 ]
fffff88001734872 - ndis!WppTraceCallback+92 (+0x07)
[ 04:00 ]
fffff88001734874 - ndis!WppTraceCallback+94 (+0x02)
[ 00:82 ]
fffff88001734876-fffff8800173489e 41 bytes - ndis!WppTraceCallback+96 (+0x02)
[ e9 ec 01 00 00 48 8b 55:00 00 80 fa a0 ff 63 28 ]
fffff880017348a0-fffff880017348a1 2 bytes - ndis!WppTraceCallback+c0 (+0x2a)
[ 10 08:82 00 ]
fffff880017348a3-fffff880017348ac 10 bytes - ndis!WppTraceCallback+c3 (+0x03)
[ 21 5d 2c 88 5d 29 e9 b9:00 00 00 06 00 00 00 00 ]
fffff880017348ae-fffff880017348c4 23 bytes - ndis!WppTraceCallback+ce (+0x0b)
[ 4c 8b 75 20 48 8b 40 10:00 00 7b e9 06 fb 00 00 ]
fffff880017348c7-fffff880017348cb 5 bytes - ndis!WppTraceCallback+e7 (+0x19)
[ c0 e9 9a 01 00:00 d0 99 06 03 ]
fffff880017348cd-fffff88001734969 157 bytes - ndis!WppTraceCallback+ed (+0x06)
[ 4d 85 f6 75 0d 8b f3 45:48 fc 00 80 c1 21 cf 08 ]
fffff8800173496b-fffff8800173496d 3 bytes - ndis!WppTraceCallback+18b (+0x9e)
[ e9 f7 00:f0 f3 ee ]
fffff8800173496f-fffff8800173497f 17 bytes - ndis!WppTraceCallback+18f (+0x04)
[ 00 41 ba 23 00 00 c0 41:f0 f3 ee 00 f0 f3 ee 00 ]
360 errors : !ndis (fffff88001734800-fffff8800173497f)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
BUCKET_ID: X64_MEMORY_CORRUPTION_LARGE
Followup: memory_corruption
---------
