Gaming PC - geplagt von Bluescreens - aber nur wenn keine "Last" ô.O

AW: Gaming PC - geplagt von Bluescreens - aber nur wenn keine "Last" ô.O

so... wieder zurück vom Urlaub sry, dass es so lange gedauert hat...

also: die harten Timings mag er einfach nicht. Neuinstallation von Windows war so gar nicht mehr möglich, weil er beim Extrahiern der Dateien schon Fehler hatte und mit einem Bluescreen (Memory Mangement) abgeschmiert ist.
Deswegen haben wir das Bios auf Werkseinstellungen zurückgedreht und 8-8-8-20 Timings eingestellt und die Spannung auf 1,25V gestellt, wie von steinschock empfohlen :schief:.
Installiern von Windows ging dann, aber beim Installieren von div. Software (Firefox, usw.) waren dann wieder die heiß geliebten Bluescreens da, erneut mit Memory Management.

Ich hab dann gleich mal das Debuggertool installieren wollen, ging aber nicht, weil ein Bluescreen beim Installieren kam.
Die Spannung soll ja laut der Artikelbeschreibung von Alternate bei den RAMs auf 1,6V stehen, deswegen hab ich im BIOs QPI/DRAM Spannung auf 1,6V eingestellt. Jetzt ließ sich das Debuggingtool problemlos installiern. Die Ergebnisse der beiden Bluescreens:

Erster Bluescreen:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\090411-9750-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.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c08000 PsLoadedModuleList = 0xfffff800`02e4de90
Debug session time: Sun Sep 4 14:40:01.585 2011 (UTC + 2:00)
System Uptime: 0 days 0:05:44.709
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa8001bd3440, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001bd3440
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: SDKSetup.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002cf5fd0 to fffff80002c88640

STACK_TEXT:
fffff880`09f4d828 fffff800`02cf5fd0 : 00000000`0000001a 00000000`00041790 fffffa80`01bd3440 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09f4d830 fffff800`02cbbfd9 : fffff8a0`00000000 00000000`1d0a8fff 00000000`00000000 00000000`fffeffff : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`09f4d9f0 fffff800`02f9f731 : fffffa80`06d13930 00000000`00000000 fffffa80`08bd1ce0 fffffa80`08bd1ce0 : nt!MiRemoveMappedView+0xd9
fffff880`09f4db10 fffff800`02f9fb33 : fffff880`00000000 00000000`1d000000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09f4dbd0 fffff800`02c878d3 : fffffa80`07460060 fffff880`09f4dca0 fffffa80`08ae2060 fffffa80`05889e60 : nt!NtUnmapViewOfSection+0x5f
fffff880`09f4dc20 00000000`778515ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1d5fdb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778515ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36024
fffff800`02cf5fd0 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36024

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001bd3440
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: SDKSetup.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002cf5fd0 to fffff80002c88640

STACK_TEXT:
fffff880`09f4d828 fffff800`02cf5fd0 : 00000000`0000001a 00000000`00041790 fffffa80`01bd3440 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09f4d830 fffff800`02cbbfd9 : fffff8a0`00000000 00000000`1d0a8fff 00000000`00000000 00000000`fffeffff : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`09f4d9f0 fffff800`02f9f731 : fffffa80`06d13930 00000000`00000000 fffffa80`08bd1ce0 fffffa80`08bd1ce0 : nt!MiRemoveMappedView+0xd9
fffff880`09f4db10 fffff800`02f9fb33 : fffff880`00000000 00000000`1d000000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09f4dbd0 fffff800`02c878d3 : fffffa80`07460060 fffff880`09f4dca0 fffffa80`08ae2060 fffffa80`05889e60 : nt!NtUnmapViewOfSection+0x5f
fffff880`09f4dc20 00000000`778515ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1d5fdb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778515ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36024
fffff800`02cf5fd0 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36024

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001bd3440
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: SDKSetup.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002cf5fd0 to fffff80002c88640

STACK_TEXT:
fffff880`09f4d828 fffff800`02cf5fd0 : 00000000`0000001a 00000000`00041790 fffffa80`01bd3440 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09f4d830 fffff800`02cbbfd9 : fffff8a0`00000000 00000000`1d0a8fff 00000000`00000000 00000000`fffeffff : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`09f4d9f0 fffff800`02f9f731 : fffffa80`06d13930 00000000`00000000 fffffa80`08bd1ce0 fffffa80`08bd1ce0 : nt!MiRemoveMappedView+0xd9
fffff880`09f4db10 fffff800`02f9fb33 : fffff880`00000000 00000000`1d000000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09f4dbd0 fffff800`02c878d3 : fffffa80`07460060 fffff880`09f4dca0 fffffa80`08ae2060 fffffa80`05889e60 : nt!NtUnmapViewOfSection+0x5f
fffff880`09f4dc20 00000000`778515ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1d5fdb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778515ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36024
fffff800`02cf5fd0 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36024

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001bd3440
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: SDKSetup.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002cf5fd0 to fffff80002c88640

STACK_TEXT:
fffff880`09f4d828 fffff800`02cf5fd0 : 00000000`0000001a 00000000`00041790 fffffa80`01bd3440 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09f4d830 fffff800`02cbbfd9 : fffff8a0`00000000 00000000`1d0a8fff 00000000`00000000 00000000`fffeffff : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`09f4d9f0 fffff800`02f9f731 : fffffa80`06d13930 00000000`00000000 fffffa80`08bd1ce0 fffffa80`08bd1ce0 : nt!MiRemoveMappedView+0xd9
fffff880`09f4db10 fffff800`02f9fb33 : fffff880`00000000 00000000`1d000000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09f4dbd0 fffff800`02c878d3 : fffffa80`07460060 fffff880`09f4dca0 fffffa80`08ae2060 fffffa80`05889e60 : nt!NtUnmapViewOfSection+0x5f
fffff880`09f4dc20 00000000`778515ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1d5fdb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778515ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36024
fffff800`02cf5fd0 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36024

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

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

0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa8001bd3440
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: SDKSetup.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002cf5fd0 to fffff80002c88640

STACK_TEXT:
fffff880`09f4d828 fffff800`02cf5fd0 : 00000000`0000001a 00000000`00041790 fffffa80`01bd3440 00000000`0000ffff : nt!KeBugCheckEx
fffff880`09f4d830 fffff800`02cbbfd9 : fffff8a0`00000000 00000000`1d0a8fff 00000000`00000000 00000000`fffeffff : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`09f4d9f0 fffff800`02f9f731 : fffffa80`06d13930 00000000`00000000 fffffa80`08bd1ce0 fffffa80`08bd1ce0 : nt!MiRemoveMappedView+0xd9
fffff880`09f4db10 fffff800`02f9fb33 : fffff880`00000000 00000000`1d000000 fffffa80`00000001 00000000`00000001 : nt!MiUnmapViewOfSection+0x1b1
fffff880`09f4dbd0 fffff800`02c878d3 : fffffa80`07460060 fffff880`09f4dca0 fffffa80`08ae2060 fffffa80`05889e60 : nt!NtUnmapViewOfSection+0x5f
fffff880`09f4dc20 00000000`778515ba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`1d5fdb78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x778515ba


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36024
fffff800`02cf5fd0 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36024

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

Followup: MachineOwner
---------
Zweiter Bluescreen:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\090411-10654-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.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c18000 PsLoadedModuleList = 0xfffff800`02e5de90
Debug session time: Sun Sep 4 14:33:37.370 2011 (UTC + 2:00)
System Uptime: 0 days 0:01:29.494
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa80012090c0, ffff, 0}

Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+36024 )

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

7: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffffa80012090c0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: userinit.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002d05fd0 to fffff80002c98640

STACK_TEXT:
fffff880`08019888 fffff800`02d05fd0 : 00000000`0000001a 00000000`00041790 fffffa80`012090c0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`08019890 fffff800`02c6a4f9 : ffffffff`00000000 00000000`0023ffff fffffa80`00000000 fffffa80`08127220 : nt! ?? ::FNODOBFM::`string'+0x36024
fffff880`08019a50 fffff800`02f6e09a : fffff8a0`01b6b750 00000000`00000001 00000000`00000000 fffffa80`08127220 : nt!MmCleanProcessAddressSpace+0x679
fffff880`08019aa0 fffff800`02f516dc : 00000000`00000000 00000000`00000001 000007ff`fffdc000 00000000`00000000 : nt!PspExitThread+0x56a
fffff880`08019ba0 fffff800`02c978d3 : fffffa80`0868a060 fffff880`00000000 fffffa80`08127220 00000000`0035efb0 : nt!NtTerminateProcess+0x138
fffff880`08019c20 00000000`77ad15da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0023f7f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77ad15da


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+36024
fffff800`02d05fd0 cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+36024

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a

FAILURE_BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

BUCKET_ID: X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+36024

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

Momentan schaut da System recht stabil aus... ich werd mal weiter testen und berichten, falls sich nochmal was tut.

Schonmal Danke an alle Helfer!

acid_g
 
AW: Gaming PC - geplagt von Bluescreens - aber nur wenn keine "Last" ô.O

Hi,
ich melde mich jetzt hier auchmal:
Bei mir habe ich genau die gleichen Probleme.

Beim Zocken bekomme ich auch nie Bluescreens.
Auf dem Dekstop, werden die Bluescreens von willkürlichen Programmen ausgelöst.
Das scheint bei dir ja auch der Fall zu sein.

Häufige Fehlermeldungen bei mir:
  • Memory Managment
  • System Service Exeption
 
AW: Gaming PC - geplagt von Bluescreens - aber nur wenn keine "Last" ô.O

Die Spannung soll ja laut der Artikelbeschreibung von Alternate bei den RAMs auf 1,6V stehen, deswegen hab ich im BIOs QPI/DRAM Spannung auf 1,6V eingestellt. Jetzt ließ sich das Debuggingtool problemlos installiern.

Die Einstellung für die RAM Spannung lautet im Bios "DRAM Bus Voltage". Hier müsstest du die 1,6V einstellen.
Die QPI/DRAM Spannung sollte m.W. nicht mehr als 1.35V betragen. Hier würde ich aufpassen, bevor du dir die CPU oder das Board grillst.
 
AW: Gaming PC - geplagt von Bluescreens - aber nur wenn keine "Last" ô.O

Die Einstellung für die RAM Spannung lautet im Bios "DRAM Bus Voltage". Hier müsstest du die 1,6V einstellen.
Die QPI/DRAM Spannung sollte m.W. nicht mehr als 1.35V betragen. Hier würde ich aufpassen, bevor du dir die CPU oder das Board grillst.

ok hab jetzt die RAM Spannung auf 1,6V und die QPI/DRAM Spannung auf 1,25V gesetzt. Sollte stimmen oder?
Die Bluescreens sind dann nämlich wieder da...:(
 
Zurück