Windows 7 stürzt häufig ab!

burnsy

Cadet 1st Year
Dabei seit
Sep. 2013
Beiträge
10
Hallo zusammen,

das ist mein erster Post hier also bitte wenn ich mich an irgendwas nicht halte einfach Bescheid sagen ich gelobe Besserung ;)

Habe schon die Suche bemüht und einige Ansätze daraus versucht nur leider scheint nichts wirklich bei mir zu klappen.

Ich habe mir selber ein System zusammengestellt mit folgenden Komponenten:
AsRock Z77 PRO3
I5-3570
Alpenföhn Brocken
8 GB DragonRAM (2*4)
Gainward 2GB GTX 660TI Phantom
Samsung SSD 840 Series 120 GB SSD
Hitachi HDS721050CLA360 500 GB HDD
Antech High Current Gamer 620W

Habe den PC sauber aufgesetzt und am Anfang hatte ich starke Probleme mit Bluescreens "Memory Management" habe daraufhin mehrere Tests gefahren und war der Ansicht der RAM sei das Problem, eingesendet nach Kontrolle ohne Fehler zurück bekommen und danach das selbe nochmal mit dem Mainboard.

Das System läuft soweit stabil auch mehrere Stunden, bei Spielen wir CS:GO keine Probleme bei Boarderlands merke ich nach einer Zeit fängt es an zu ruckeln und dann stürzt das Spiel bzw. manchmal auch das Komplette System ab ... die Temperatur von GPU und CPU liegen im Maximalbereich von ~50° nach dem erneuten hochfahren dann häufiger Probleme wenn man 1 Min wartet geht wieder alles ...

Ich habe mit "DriverScanner" alle Treiber soweit möglich geupdated nur leider ist der PC gerade eben auch ohne zutun einfach abgestützt. Ich habe aktuell die RAM schon so gesteckt das diese nicht im Dualchannel-Mode laufen aber immernoch ohne wirkliche Hilfe.

Ich hoffe ich finde hier einen der mir irgendwie weiterhelfen kann oder auch einen Analyseansatz hat.

Danke und Gruß
Burnsy
 

porky

Newbie
Dabei seit
Jan. 2006
Beiträge
3
Klingt für mich nach Überhitzung der CPU . . Check mal den CPU Lüfter . . Fester Sitz .. Ist da silberpaste zwischen CPU und Lüfter ?
Treiber glaube ich nicht . . so wie du es beschreibst müsste es das sein.
Hoffe ich konnte helfen
 

burnsy

Cadet 1st Year
Ersteller dieses Themas
Dabei seit
Sep. 2013
Beiträge
10
Hi,

ja CPU Temp dachte ich auch schon er sitzt nach dem Einsenden des Mainboards ohne Paste drauf aber ich hab die CPU TEMP noch nie über 50° gesehen und das sollte ja eig kein Problem sein oder?

CPU-Z Memory-SPD (nach Text-Output):
Memory SPD
-------------------------------------------------------------------------

DIMM # 1
SMBus address 0x50
Memory type DDR3
Module format UDIMM
Manufacturer (ID) GEIL (7F7F7F1300000000)
Size 4096 MBytes
Max bandwidth PC3-12800 (800 MHz)
Part number CL11-11-11 D3-1600
Manufacturing date Week 49/Year 12
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP yes
XMP revision 1.2
AMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 5.0-5-5-14-19 @ 380 MHz
JEDEC #2 6.0-6-6-16-22 @ 457 MHz
JEDEC #3 7.0-7-7-19-26 @ 533 MHz
JEDEC #4 8.0-8-8-22-30 @ 609 MHz
JEDEC #5 9.0-9-9-24-33 @ 685 MHz
JEDEC #6 10.0-10-10-27-37 @ 761 MHz
JEDEC #7 11.0-11-11-30-41 @ 838 MHz
XMP profile XMP-1600
Specification PC3-12800K
Voltage level 1.500 Volts
Min Cycle time 1.250 ns (800 MHz)
Max CL 11.0
Min tRP 13.75 ns
Min tRCD 13.75 ns
Min tWR 15.00 ns
Min tRAS 35.00 ns
Min tRC 47.50 ns
Min tRFC 300.00 ns
Min tRTP 7.50 ns
Min tRRD 7.50 ns
Command Rate 2T
XMP timings table CL-tRCD-tRP-tRAS-tRC-CR @ frequency (voltage)
XMP #1 11.0-11-11-28-38-2T @ 800 MHz (1.500 Volts)

DIMM # 2
SMBus address 0x51
Memory type DDR3
Module format UDIMM
Manufacturer (ID) GEIL (7F7F7F1300000000)
Size 4096 MBytes
Max bandwidth PC3-12800 (800 MHz)
Part number CL11-11-11 D3-1600
Manufacturing date Week 49/Year 12
Number of banks 8
Nominal Voltage 1.50 Volts
EPP no
XMP yes
XMP revision 1.2
AMP no
JEDEC timings table CL-tRCD-tRP-tRAS-tRC @ frequency
JEDEC #1 5.0-5-5-14-19 @ 380 MHz
JEDEC #2 6.0-6-6-16-22 @ 457 MHz
JEDEC #3 7.0-7-7-19-26 @ 533 MHz
JEDEC #4 8.0-8-8-22-30 @ 609 MHz
JEDEC #5 9.0-9-9-24-33 @ 685 MHz
JEDEC #6 10.0-10-10-27-37 @ 761 MHz
JEDEC #7 11.0-11-11-30-41 @ 838 MHz
XMP profile XMP-1600
Specification PC3-12800K
Voltage level 1.500 Volts
Min Cycle time 1.250 ns (800 MHz)
Max CL 11.0
Min tRP 13.75 ns
Min tRCD 13.75 ns
Min tWR 15.00 ns
Min tRAS 35.00 ns
Min tRC 47.50 ns
Min tRFC 300.00 ns
Min tRTP 7.50 ns
Min tRRD 7.50 ns
Command Rate 2T
XMP timings table CL-tRCD-tRP-tRAS-tRC-CR @ frequency (voltage)
XMP #1 11.0-11-11-28-38-2T @ 800 MHz (1.500 Volts)

DIMM # 1
SPD registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 13 11 0B 02 04 21 00 01 03 11 01 08 0A 00 FE 00
10 69 78 69 3C 69 11 18 81 20 08 3C 3C 00 F0 83 05
20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30 00 00 00 00 00 00 00 00 00 00 00 00 0F 01 20 00
40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70 00 00 00 00 00 83 13 00 12 49 00 00 00 00 FA F0
80 43 4C 31 31 2D 31 31 2D 31 31 20 44 33 2D 31 36
90 30 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0 0C 4A 01 12 01 08 00 00 11 2A 0A 6E 80 00 6E 6E
C0 6E 78 11 18 7C 3F 00 60 09 3C 3C 00 F0 3C 00 00
D0 10 00 00 00 00 00 00 00 00 00 00 81 00 00 00 00
E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

DIMM # 2
SPD registers
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00 13 11 0B 02 04 21 00 01 03 11 01 08 0A 00 FE 00
10 69 78 69 3C 69 11 18 81 20 08 3C 3C 00 F0 83 05
20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30 00 00 00 00 00 00 00 00 00 00 00 00 0F 01 20 00
40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70 00 00 00 00 00 83 13 00 12 49 00 00 00 00 FA F0
80 43 4C 31 31 2D 31 31 2D 31 31 20 44 33 2D 31 36
90 30 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00
A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B0 0C 4A 01 12 01 08 00 00 11 2A 0A 6E 80 00 6E 6E
C0 6E 78 11 18 7C 3F 00 60 09 3C 3C 00 F0 3C 00 00
D0 10 00 00 00 00 00 00 00 00 00 00 81 00 00 00 00
E0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
F0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Ist das so ok?
 

burnsy

Cadet 1st Year
Ersteller dieses Themas
Dabei seit
Sep. 2013
Beiträge
10
memo.jpg

gerne :)
Ergänzung ()

Hatte gerade wieder im normalen Windows Betrieb (chrome offen und Problembericht am senden) einen Bluescreen Memorymanagement mit 0x0*01A irgendwas, hatte leider nicht aufschreiben können :/
Ergänzung ()

hatte gerade wieder einen bluescreen mit memorymanagement 0x0*01A ...

Computer lief ganz normal in Windows ohne wirkliche Last nur bissel am surfen und Musik (youtube am hören) auch aktuell musste ich Chrome 3 mal neu starten um hier posten zu können :/

*confused*
 

burnsy

Cadet 1st Year
Ersteller dieses Themas
Dabei seit
Sep. 2013
Beiträge
10
es wurde ein update beim einsenden durchgeführt, ich kann ein reset machen, soll ich?
 

burnsy

Cadet 1st Year
Ersteller dieses Themas
Dabei seit
Sep. 2013
Beiträge
10
Er konnte 13 Dumps allerdings ohne full memory dump analysieren:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Wed 04.09.2013 15:53:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090413-5725-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80044A4890, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 04.09.2013 15:53:09 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80044A4890, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 04.09.2013 14:26:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090413-5881-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x51 (0x1, 0xFFFFF8A013644410, 0x426F000, 0x465)
Error: REGISTRY_ERROR
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe registry error has occurred.
This bug check indicates there is a problem related to your registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 03.09.2013 19:05:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090313-8595-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80044F7930, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 02.09.2013 16:19:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090213-6895-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x1F15)
Bugcheck code: 0x24 (0xC08A5, 0x0, 0x0, 0x0)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 02.09.2013 16:16:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\090213-10030-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800449B170, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 29.07.2013 18:16:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072913-6099-01.dmp
This was probably caused by the following module: cdd.dll (0xFFFFF96000660061)
Bugcheck code: 0x50 (0xFFFFF900D29A79D4, 0x0, 0xFFFFF96000660061, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\cdd.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Canonical Display Driver
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Mon 22.07.2013 23:40:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\072313-6442-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80044FA960, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 03.07.2013 19:35:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070313-6442-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002E7EFB1, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 01.07.2013 21:04:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\070213-7176-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x5002, 0xFFFFF70001080000, 0x567A, 0x4005679FFFFFFFE)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 29.06.2013 14:11:21 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062913-6224-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002E84E84, 0xFFFFF8800AFE44A0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 28.06.2013 17:39:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\062813-6224-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75C00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80044BE900, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 28.05.2013 20:19:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\052813-6052-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x4688)
Bugcheck code: 0x24 (0x1904FB, 0xFFFFF8800ADE7858, 0xFFFFF8800ADE70B0, 0xFFFFF880016DB9EE)
Error: NTFS_FILE_SYSTEM
file path: C:\Windows\system32\drivers\ntfs.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: NT-Dateisystemtreiber
Bug check description: This indicates a problem occurred in the NTFS file system.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
ich stell mal auf full memory dumps um, habe parallel im bios mal das XMP Profil 1.2 für den RAM fest eingestellt. ich bin gespannt :)
 

burnsy

Cadet 1st Year
Ersteller dieses Themas
Dabei seit
Sep. 2013
Beiträge
10
thx wenn ein neuer dump kommt werte ich den mal aus und poste es hier. Ich glaube die alten machen keinen sinn da ich ja jetzt schon was verändert habe.
 

MagicAndre1981

Admiral
Dabei seit
Feb. 2004
Beiträge
7.455

burnsy

Cadet 1st Year
Ersteller dieses Themas
Dabei seit
Sep. 2013
Beiträge
10
so leider hatte ich heute im leerlauf wieder einen bs... es hat vorher aber echt lange gehalten ...
hier die analyse:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
contains the address of the PFN for the corrupted page table page.
On a 32 bit OS, parameter 2 contains a pointer to the number of used
PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa80044edac0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41790

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT

PROCESS_NAME: rundll32.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff800030f4d40 to fffff80003083b80

STACK_TEXT:
fffff880`0ed616e8 fffff800`030f4d40 : 00000000`0000001a 00000000`00041790 fffffa80`044edac0 00000000`0000ffff : nt!KeBugCheckEx
fffff880`0ed616f0 fffff800`030b67f9 : 00000000`00000000 000007fe`eecd2fff fffffa80`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`0ed618b0 fffff800`0339df51 : fffffa80`0caea170 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiRemoveMappedView+0xd9
fffff880`0ed619d0 fffff800`0339e353 : 00000000`00000000 000007fe`eec30000 fffffa80`00000001 fffffa80`0caf1a80 : nt!MiUnmapViewOfSection+0x1b1
fffff880`0ed61a90 fffff800`03082e13 : fffffa80`0e7484c0 fffff880`0ed61b60 fffffa80`0e720060 000007fe`eec30000 : nt!NtUnmapViewOfSection+0x5f
fffff880`0ed61ae0 00000000`77a7155a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`000eb518 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77a7155a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+35084
fffff800`030f4d40 cc int 3

SYMBOL_STACK_INDEX: 1

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

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 51db806a

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

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

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

burnsy

Cadet 1st Year
Ersteller dieses Themas
Dabei seit
Sep. 2013
Beiträge
10
Ok und wie bekomme ich das jetzt gelöst?
Habe die RAM schon eingesendet :/

oder soll ich einfach andere kaufen, sind die DragonRAM nicht ok?
 

burnsy

Cadet 1st Year
Ersteller dieses Themas
Dabei seit
Sep. 2013
Beiträge
10
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION (c1)
Special pool has detected memory corruption. Typically the current thread's
stack backtrace will reveal the guilty party.
Arguments:
Arg1: fffff98049a80c30, address trying to free
Arg2: fffff98049a80347, address where one bit is corrupted
Arg3: 00000000009b03d0, (reserved)
Arg4: 0000000000000032, caller is freeing an address where nearby bytes within the same page have a single bit error

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


BUGCHECK_STR: 0xC1_32

SPECIAL_POOL_CORRUPTION_TYPE: 32

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80003107c73 to fffff80003078b80

STACK_TEXT:
fffff880`20738998 fffff800`03107c73 : 00000000`000000c1 fffff980`49a80c30 fffff980`49a80347 00000000`009b03d0 : nt!KeBugCheckEx
fffff880`207389a0 fffff800`031808f3 : 00000000`10000004 fffff880`046128a2 fffff880`20738c80 00000000`00000000 : nt!MiCheckSpecialPoolSlop+0x83
fffff880`207389e0 fffff800`031ab93b : fffff800`03003000 00000000`63694d46 ffffffff`fff81d00 00000000`00000000 : nt!MmFreeSpecialPool+0x1d3
fffff880`20738b20 fffff880`0115f041 : fffffa80`0b501658 fffff880`0115f329 fffff880`20738000 00000000`00000002 : nt!ExDeferredFreePool+0xf33
fffff880`20738bd0 fffff880`0115d6df : fffffa80`078b5960 fffffa80`078b5960 fffff980`01ca6c00 fffffa80`0b501300 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x6c1
fffff880`20738c60 fffff800`03522860 : fffffa80`0b501300 fffffa80`0b501300 fffffa80`069e65f0 fffffa80`0bb723d0 : fltmgr!FltpDispatch+0xcf
fffff880`20738cc0 fffff800`0337722e : fffffa80`0bb72400 00000000`00000001 fffffa80`0b501300 fffffa80`078b5960 : nt!IovCallDriver+0xa0
fffff880`20738d20 fffff800`03081e54 : fffffa80`06c91f00 fffffa80`0bb5c060 fffffa80`072318a0 fffff6fc`c02343f0 : nt!IopDeleteFile+0x11e
fffff880`20738db0 fffff800`03371054 : fffffa80`0bb5c060 00000000`00000000 fffffa80`0a09a9f0 00000000`00000000 : nt!ObfDereferenceObject+0xd4
fffff880`20738e10 fffff800`03371604 : 00000000`0000362c fffffa80`0bb5c060 fffff8a0`00001760 00000000`0000362c : nt!ObpCloseHandleTableEntry+0xc4
fffff880`20738ea0 fffff800`03077e13 : fffffa80`0a09a9f0 fffff880`20738f70 00000000`00000000 fffff980`346d8f10 : nt!ObpCloseHandle+0x94
fffff880`20738ef0 fffff800`030743d0 : fffff880`01186f06 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`20739088 fffff880`01186f06 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff880`20739090 fffff880`01180e1e : fffff980`346d8f10 00000000`00000000 00000000`00000000 fffff800`03050cc2 : fltmgr! ?? ::NNGAKEGL::`string'+0x1f06
fffff880`207390d0 fffff880`0116cb9d : c00000bb`03328c00 00000000`00000000 fffff980`11276fb0 fffff880`2073a000 : fltmgr!FltpCreateFileNameInformation+0xee
fffff880`20739130 fffff880`01166bf6 : fffffa80`07448000 fffff980`112764c0 fffff980`02eae8f8 00000000`00000000 : fltmgr!HandleStreamListNotSupported+0x15d
fffff880`20739170 fffff880`0116db44 : fffffa80`0b718500 00000000`00000000 fffff980`112764c0 00000000`00000401 : fltmgr! ?? ::FNODOBFM::`string'+0x30f3
fffff880`207391f0 fffff880`01db5b33 : fffff980`346d8f10 fffff980`4a2d4d80 fffff880`207393a0 00000000`00000000 : fltmgr!FltGetFileNameInformation+0x184
fffff880`20739280 fffff980`346d8f10 : fffff980`4a2d4d80 fffff880`207393a0 00000000`00000000 00000000`00000000 : avgmfx64+0x3b33
fffff880`20739288 fffff980`4a2d4d80 : fffff880`207393a0 00000000`00000000 00000000`00000000 fffffa80`06c8b418 : 0xfffff980`346d8f10
fffff880`20739290 fffff880`207393a0 : 00000000`00000000 00000000`00000000 fffffa80`06c8b418 00000000`00000010 : 0xfffff980`4a2d4d80
fffff880`20739298 00000000`00000000 : 00000000`00000000 fffffa80`06c8b418 00000000`00000010 fffff800`032302c8 : 0xfffff880`207393a0


STACK_COMMAND: kb

FOLLOWUP_IP:
avgmfx64+3b33
fffff880`01db5b33 ?? ???

SYMBOL_STACK_INDEX: 12

SYMBOL_NAME: avgmfx64+3b33

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: avgmfx64

IMAGE_NAME: avgmfx64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5213d761

FAILURE_BUCKET_ID: X64_0xC1_32_VRF_avgmfx64+3b33

BUCKET_ID: X64_0xC1_32_VRF_avgmfx64+3b33

Followup: MachineOwner
---------
nach Aktivierung des special Pools.
Ich glaub langsam ich kauf mir einfach ganz neue Ram, weiß einer welche zu dem Board 100%tig passen? :/
 

Randy89

Captain
Dabei seit
Mai 2013
Beiträge
3.287
Zuletzt bearbeitet:

burnsy

Cadet 1st Year
Ersteller dieses Themas
Dabei seit
Sep. 2013
Beiträge
10
in den beiden listen ist ja der Dragonram drin :/ daher bin ich hier vorsichtig ... OS ist 64bit und ich finde 8 GB absolut ausreichend, ist nur zum arbeiten und spielen da reicht das aus meiner Sicht dicke.
 

Randy89

Captain
Dabei seit
Mai 2013
Beiträge
3.287
- wenn der Dragonram nicht so gut läuft, nimm halt einen anderen RAM aus der Liste, kannst ruhig auch zur 1333MHz Variante greifen, hauptsache 1.5V

- wenn du nur Home Basic hast, wärst du auch mit 64 Bit schon an deinem Limit, aber wenn dir das noch eine ganze weile dicke reicht, spricht nichts dagegen
 
Top