BSOD bei Gigabyte 965P-DQ6 mit CM2X1024-6400C4
Moin moin Zusammen,
ich streife nun schon wochenlang durch diverse Forenbeiträge und Internetseiten, jedoch sind alle meine bisherigen Versuche fehlgeschlagen.
Mein Problem? - Ab und zu BSOD.
Nach mehrmaligen Auswerten wohl ein Problem des Arbeitsspeichers, der Grafikkarte oder eines Treibers. Ich habe Treiber de- und installiert und im BIOS diverse Einstellungen ausprobiert.
Zuletzt lief der PC zwei Tage ohne Probleme (leichte Anwendungen wie Office und Bildbetrachtung).
Gestern, während ich ein .gif als Desktophintergrund eingerichtet habe wieder ein Bluescreen. Diesmal mit folgender Auswertung:
__________________________________________________ ____________
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\symbols*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a68000 PsLoadedModuleList = 0xfffff800`02cade90
Debug session time: Sun Feb 27 15:54:06.380 2011 (UTC + 1:00)
System Uptime: 0 days 0:24:00.075
Loading Kernel Symbols
.................................................. .............
.................................................. ..............
...............................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000007ff`fffd8018). Type ".hh dbgerr001" for details
Loading unloaded module list
.....
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {20, fffffa8005aa0c00, fffffa8005aa0c20, 4020015}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for nvlddmkm.sys -
Probably caused by : nvlddmkm.sys ( nvlddmkm+f1fdf )
Followup: MachineOwner
---------
1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa8005aa0c00, The pool entry we were looking for within the page.
Arg3: fffffa8005aa0c20, The next pool entry.
Arg4: 0000000004020015, (reserved)
Debugging Details:
------------------
BUGCHECK_STR: 0x19_20
POOL_ADDRESS: fffffa8005aa0c00 Nonpaged pool
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002c12cae to fffff80002ae8640
STACK_TEXT:
fffff880`04906a98 fffff800`02c12cae : 00000000`00000019 00000000`00000020 fffffa80`05aa0c00 fffffa80`05aa0c20 : nt!KeBugCheckEx
fffff880`04906aa0 fffff880`0f1b1fdf : fffffa80`0599b010 fffff900`c00d4070 fffffa80`484c764e fffff880`0f18faf4 : nt!ExDeferredFreePool+0x12da
fffff880`04906b50 fffff880`0f18eef5 : 00000000`00000060 00000000`00000000 fffffa80`0599b010 fffff880`049070b0 : nvlddmkm+0xf1fdf
fffff880`04906b80 fffff880`0f18feff : fffffa80`0598d010 00000000`00000720 00000000`00000000 00000000`0027bcb0 : nvlddmkm+0xceef5
fffff880`04906bb0 fffff880`0f0e34c3 : fffffa80`00000000 fffffa80`059654a0 fffffa80`05038000 fffffa80`059654a0 : nvlddmkm+0xcfeff
fffff880`04906f10 fffff880`0f216511 : fffff880`0f0e3446 00000000`00000200 fffff880`049077f0 fffffa80`059654a0 : nvlddmkm+0x234c3
fffff880`04906fc0 fffff880`040ca412 : 00000000`00000000 00000000`00000200 fffffa80`059654a0 00000000`00000000 : nvlddmkm+0x156511
fffff880`04906ff0 fffff880`040a0fb2 : 00000000`00000001 fffff8a0`00ece000 fffff880`04907638 fffff800`00000002 : dxgkrnl!DXGCONTEXT::Render+0x78a
fffff880`04907600 fffff960`006cb264 : 00000000`00000000 00000000`00000000 fffff900`c00bf020 00000000`00000000 : dxgkrnl!DxgkCddGdiCommand+0x1ea
fffff880`04907690 fffff960`006c95d5 : fffffa80`05957e80 fffffa80`05957e80 00000000`00000000 fffff900`c00bf020 : cdd!CHwCommandBuffer::FlushGdiCommands+0xb4
fffff880`04907980 fffff960`006c5c6e : ffffffff`fffd73b0 00000000`00000010 00000000`00000000 fffff900`c00bf020 : cdd!CDDPDEV::FlushGdiOutput+0x81
fffff880`049079b0 fffff800`02d85cce : 00000000`02c7f9be fffffa80`0595b060 00000000`00000080 fffffa80`04864330 : cdd!PresentWorkerThread+0x902
fffff880`04907d40 fffff800`02ad9fe6 : fffff800`02c5ae80 fffffa80`0595b060 fffff800`02c68cc0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`04907d80 00000000`00000000 : fffff880`04908000 fffff880`04902000 fffff880`04907350 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+f1fdf
fffff880`0f1b1fdf 4883c428 add rsp,28h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nvlddmkm+f1fdf
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c6da
FAILURE_BUCKET_ID: X64_0x19_20_nvlddmkm+f1fdf
BUCKET_ID: X64_0x19_20_nvlddmkm+f1fdf
Followup: MachineOwner
__________________________________________________ _____________
- Windows 7 Ultimate ist installiert (Neuinstallation bereits erfolgt)
- Memtest86+ bei einem Timing von 4-4-4-12 und 2,1V ohne Fehler durchgelaufen (bei 5-5-5-18 und 1,8V hatte er bei Test Nr. 5 Fehler angezeigt)
- Bios Version F13 ist vorhanden
- Treiberversion der Grafikkarte 8.17.12.6658
Hier seht ihr meine Rechnerkonfiguration:
Computer:
Betriebssystem Windows 7 Ultimate Media Center Edition
DirectX 4.09.00.0904 (DirectX 9.0c)
Motherboard:
CPU Typ Intel Core 2 E6700 , 2666 MHz
Motherboard Name Gigabyte 965P-DQ6
Arbeitsspeicher 4096 MB CMX21024-6400C4
BIOS Typ F13
Anzeige:
Grafikkarte NVIDIA GeForce 9800 GTX+
Monitor SyncMaster 2232BW/2232GW/2232GW Plus,SyncMaster Magic CX2232GW(Digital) [NoDB] (HS2P901969)
Multimedia:
Soundkarte Digitalaudio (S/PDIF) (High Def
Soundkarte Lautsprecher (EasyCall Speakerp
Soundkarte Lautsprecher (High Definition A
Datenträger:
IDE Controller Intel(R) ICH8 2-Port Serieller ATA-Speichercontroller - 2825
IDE Controller Intel(R) ICH8 4-Port Serieller ATA-Speichercontroller - 2820
IDE Controller Standard-Zweikanal-PCI-IDE-Controller
SCSI/RAID Controller Virtual CloneDrive
Festplatte ST31000528AS ATA Device (931 GB, IDE)
Festplatte Brother DCP-150C USB Device
Optisches Laufwerk ELBY CLONEDRIVE SCSI CdRom Device (Virtual CD-ROM)
Optisches Laufwerk PHILIPS SPD2411P ATA Device
Optisches Laufwerk TOSHIBA DVD-ROM SDM2012C ATA Device (16x/48x DVD-ROM)
S.M.A.R.T. Festplatten-Status OK
Partitionen:
C: (NTFS) 109675 MB (49996 MB frei)
H: (NTFS) 237567 MB (115706 MB frei)
I: (NTFS) 476159 MB (70502 MB frei)
J: (NTFS) 30356 MB (25983 MB frei)
Speicherkapazität 833.7 GB (256.0 GB frei)
Eingabegeräte:
Tastatur HID-Tastatur
Maus HID-konforme Maus
Maus HID-konforme Maus
Maus HID-konforme Maus
Netzwerk:
Netzwerkkarte Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller (192.168.2.103)
Peripheriegeräte:
Drucker Adobe PDF
Drucker An OneNote 2010 senden
Drucker Brother DCP-150C
Drucker Fax
Drucker Microsoft XPS Document Writer
USB1 Controller Intel(R) ICH8-Familie USB universeller Hostcontroller - 2830 [NoDB]
USB1 Controller Intel(R) ICH8-Familie USB universeller Hostcontroller - 2831 [NoDB]
USB1 Controller Intel(R) ICH8-Familie USB universeller Hostcontroller - 2832 [NoDB]
USB1 Controller Intel(R) ICH8-Familie USB universeller Hostcontroller - 2834 [NoDB]
USB1 Controller Intel(R) ICH8-Familie USB universeller Hostcontroller - 2835 [NoDB]
USB2 Controller Intel(R) ICH8-Familie USB2 erweiterter Hostcontroller - 2836 [NoDB]
USB2 Controller Intel(R) ICH8-Familie USB2 erweiterter Hostcontroller - 283A [NoDB]
USB-Geräte Brother DCP-150C
USB-Geräte EasyCall Speakerphone
USB-Geräte Generic USB Hub
USB-Geräte Generic USB Hub
USB-Geräte USB-Druckerunterstützung
USB-Geräte USB-Eingabegerät
USB-Geräte USB-Eingabegerät
USB-Geräte USB-Eingabegerät
USB-Geräte USB-Eingabegerät
USB-Geräte USB-Eingabegerät
USB-Geräte USB-Massenspeichergerät
USB-Geräte USB-Verbundgerät
USB-Geräte USB-Verbundgerät
USB-Geräte USB-Verbundgerät
USB-Geräte USB-Verbundgerät
Bitte, wenn jemand mir helfen könnte, Tips hat o.ä. ich wäre sehr dankbar.
EDIT (autom. Beitragszusammenführung):
So, heute, 12:20Uhr erneut ein Bluescreen. Diesmal sieht er folgendermaßen aus:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*C:\symbols*
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02a0a000 PsLoadedModuleList = 0xfffff800`02c4fe90
Debug session time: Mon Feb 28 12:14:37.159 2011 (UTC + 1:00)
System Uptime: 0 days 0:47:25.751
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {0, 2, 1, fffff80002a8ced8}
Probably caused by : hardware ( nt!KiSwapContext+78 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
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 a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002a8ced8, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 0000000000000000
CURRENT_IRQL: 2
FAULTING_IP:
nt!KiSwapContext+78
fffff800`02a8ced8 0000 add byte ptr [rax],al
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xA
PROCESS_NAME: System
TRAP_FRAME: fffff88002fee890 -- (.trap 0xfffff88002fee890)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=000006e700000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002a8ced8 rsp=fffff88002feea20 rbp=fffffa80036dd680
r8=fffff80002c01450 r9=0000000000000000 r10=fffff80002a0a000
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KiSwapContext+0x78:
fffff800`02a8ced8 0000 add byte ptr [rax],al ds:0140:0000=??
Resetting default scope
MISALIGNED_IP:
nt!KiSwapContext+78
fffff800`02a8ced8 0000 add byte ptr [rax],al
LAST_CONTROL_TRANSFER: from fffff80002a89be9 to fffff80002a8a640
STACK_TEXT:
fffff880`02fee748 fffff800`02a89be9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`02fee750 fffff800`02a88860 : fffffa80`04e29020 fffff880`00ea34b1 00000000`00000001 fffff800`02bfce80 : nt!KiBugCheckDispatch+0x69
fffff880`02fee890 fffff800`02a8ced8 : 00000000`0000a434 fffffa80`0527d000 fffffa80`0527d000 fffff880`0f2d9d65 : nt!KiPageFault+0x260
fffff880`02feea20 fffff800`02a8f992 : 00000000`00000001 fffffa80`036dd680 00000000`00000000 00000000`00000000 : nt!KiSwapContext+0x78
fffff880`02feeb60 fffff800`02a929f3 : fffffa80`036dd680 00000296`6f00424c 00000296`00000000 00000296`6f00424c : nt!KiCommitThreadWait+0x1d2
fffff880`02feebf0 fffff800`02a949f9 : fffff800`02c27600 fffff800`02d80f01 fffffa80`036dd600 00000000`00000000 : nt!KeRemoveQueueEx+0x323
fffff880`02feecb0 fffff800`02d27cce : 00000000`00000000 fffffa80`036dd680 00000000`00000080 fffffa80`036cb040 : nt!ExpWorkerThread+0xe9
fffff880`02feed40 fffff800`02a7bfe6 : fffff880`009e9180 fffffa80`036dd680 fffff880`009f3f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02feed80 00000000`00000000 : fffff880`02fef000 fffff880`02fe9000 fffff880`02fee9e0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!KiSwapContext+78
fffff800`02a8ced8 0000 add byte ptr [rax],al
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiSwapContext+78
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: hardware
FAILURE_BUCKET_ID: X64_IP_MISALIGNED
BUCKET_ID: X64_IP_MISALIGNED
Followup: MachineOwner
---------