Witam,
Moj sprzęt
Pamięć Corsair Vengeance LPX DDR4, 2x8GB, 3200MHz, CL16
Karta graficzna Gigabyte GeForce GTX 1080 Ti AORUS 11GB GDDR5X (352 bit),
Procesor Intel Core i7-8700K, Hexa Core, 3.70GHz, 12MB, LGA1151, 14nm,
Płyta główna MSI Z370 Tomahawk
Zasilacz be quiet! Pure Power 10 700W
System windows 10
Mam problem z błędami dotyczące pamięci ram
wywala mi ekran memory management error
Odpaliłem diagnostykę ramu win 10
Przeskanowałem ramy memtest86
Moją oczą ukazało errory value109 jak na tym filmki(nie jest to moj filmik)
wkleiłem Minidump do analizatora błędów
*** Memory manager detected 48501 instance(s) of page corruption, target is likely to have memory corruption.
Moje pytanie co teraz ? reklamacja czy to ja coś zle robie
i jest to usterka do naprawy
Zapomniałem dodać ze zmiana slotu ramu nic nie daje
Moj sprzęt
Pamięć Corsair Vengeance LPX DDR4, 2x8GB, 3200MHz, CL16
Karta graficzna Gigabyte GeForce GTX 1080 Ti AORUS 11GB GDDR5X (352 bit),
Procesor Intel Core i7-8700K, Hexa Core, 3.70GHz, 12MB, LGA1151, 14nm,
Płyta główna MSI Z370 Tomahawk
Zasilacz be quiet! Pure Power 10 700W
System windows 10
Mam problem z błędami dotyczące pamięci ram
wywala mi ekran memory management error
Odpaliłem diagnostykę ramu win 10
Spoiler:
"The Windows Memory Diagnostic tested the computer's memory and detected hardware errors. To identify and repair these problems, contact the computer manufacturer"
Spoiler:
+ System
- Provider
[ Name] Microsoft-Windows-MemoryDiagnostics-Results
[ Guid] {5F92BC59-248F-4111-86A9-E393E12C6139}
EventID 1102
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2018-09-05T09:13:49.484337100Z
EventRecordID 2729
Correlation
- Execution
[ ProcessID] 7216
[ ThreadID] 7220
Channel System
Computer DESKTOP-79NDIK9
- Security
[ UserID] S-1-5-18
- UserData
- Results
LaunchType Manual
CompletionType Fail
MemorySize 16338
TestType 10
TestDuration 1350
TestCount 12
NumPagesTested 4123300
NumPagesUnTested 1722
NumBadPages 8
T1NumBadPages 8
T2NumBadPages 8
T3NumBadPages 8
T4NumBadPages 8
T5NumBadPages 8
T6NumBadPages 8
T7NumBadPages 8
T8NumBadPages 8
T9NumBadPages 8
T10NumBadPages 8
T11NumBadPages 8
T12NumBadPages 8
T13NumBadPages 0
T14NumBadPages 0
T15NumBadPages 0
T16NumBadPages 0
- Provider
[ Name] Microsoft-Windows-MemoryDiagnostics-Results
[ Guid] {5F92BC59-248F-4111-86A9-E393E12C6139}
EventID 1102
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8000000000000000
- TimeCreated
[ SystemTime] 2018-09-05T09:13:49.484337100Z
EventRecordID 2729
Correlation
- Execution
[ ProcessID] 7216
[ ThreadID] 7220
Channel System
Computer DESKTOP-79NDIK9
- Security
[ UserID] S-1-5-18
- UserData
- Results
LaunchType Manual
CompletionType Fail
MemorySize 16338
TestType 10
TestDuration 1350
TestCount 12
NumPagesTested 4123300
NumPagesUnTested 1722
NumBadPages 8
T1NumBadPages 8
T2NumBadPages 8
T3NumBadPages 8
T4NumBadPages 8
T5NumBadPages 8
T6NumBadPages 8
T7NumBadPages 8
T8NumBadPages 8
T9NumBadPages 8
T10NumBadPages 8
T11NumBadPages 8
T12NumBadPages 8
T13NumBadPages 0
T14NumBadPages 0
T15NumBadPages 0
T16NumBadPages 0
Przeskanowałem ramy memtest86
Moją oczą ukazało errory value109 jak na tym filmki(nie jest to moj filmik)
Spoiler:
wkleiłem Minidump do analizatora błędów
*** Memory manager detected 48501 instance(s) of page corruption, target is likely to have memory corruption.
Spoiler:
Instant Online Crash Analysis, brought to you by OSR Open Systems Resources, Inc.
Show DivPrimary Analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`dbc8d000 PsLoadedModuleList = 0xfffff802`dc03b210
Debug session time: Tue Sep 18 05:23:22.670 2018 (UTC - 4:00)
System Uptime: 0 days 0:29:18.593
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffff8800b7a96b0
Arg3: 0000000000000000
Arg4: 0000000000000001
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
BAD_PAGES_DETECTED: bd75
LAST_CONTROL_TRANSFER: from fffff802dbd7c846 to fffff802dbe36380
STACK_TEXT:
ffff8f0f`4481ee98 fffff802`dbd7c846 : 00000000`0000001a 00000000`00041790 fffff880`0b7a96b0 00000000`00000000 : nt!KeBugCheckEx
ffff8f0f`4481eea0 fffff802`dbd796a9 : ffff8f0f`4481f039 00002000`00000200 00000000`00000000 00000000`00000000 : nt!MiDeleteVa+0x15d6
ffff8f0f`4481efc0 fffff802`dbd79ab2 : ffff8f0f`4481f590 ffffd280`f46d2e38 ffff8f0f`00000000 ffff8f0f`00000000 : nt!MiWalkPageTablesRecursively+0x299
ffff8f0f`4481f0a0 fffff802`dbd79ab2 : ffff8f0f`4481f590 ffffd2e9`407a3690 ffff8f0f`00000001 ffff8f0f`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffff8f0f`4481f180 fffff802`dbd79ab2 : ffff8f0f`4481f590 ffffd2e9`74a03d18 ffff8f0f`00000002 ffff8f0f`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffff8f0f`4481f260 fffff802`dbd777b7 : ffff8f0f`4481f590 ffffd2e9`74ba5018 ffffb906`00000003 ffff9606`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffff8f0f`4481f340 fffff802`dbd61ec3 : ffff8f0f`4481f590 ffff9606`00000001 ffff9606`00000000 ffff9606`00000000 : nt!MiWalkPageTables+0x1e7
ffff8f0f`4481f430 fffff802`dc20acf5 : ffff9606`08005080 ffff9606`00000000 ffff9606`0f94a570 ffff9606`08005080 : nt!MiDeleteVad+0x8d3
ffff8f0f`4481f760 fffff802`dc20ab17 : ffff9606`0f800e90 ffff9606`0f800e90 ffff9606`0f94a570 ffff9606`11f87a80 : nt!MiCleanVad+0x4d
ffff8f0f`4481f790 fffff802`dc1ff88d : ffffffff`00000000 ffffffff`ffffffff ffff8f0f`4481fa01 ffff9606`11f87580 : nt!MmCleanProcessAddressSpace+0x11f
ffff8f0f`4481f810 fffff802`dc131af4 : ffff9606`11f87580 ffffd409`472f5060 ffff8f0f`4481fa80 00000000`00000000 : nt!PspRundownSingleProcess+0x129
ffff8f0f`4481f890 fffff802`dc23b8f3 : 00000000`00000000 ffff8f0f`4481fa01 000000d2`973c8000 ffff9606`08005080 : nt!PspExitThread+0x5ac
ffff8f0f`4481f990 fffff802`dbe46a43 : ffff9606`00001a88 ffff9606`08005080 ffff9606`11f87580 00000000`00000000 : nt!NtTerminateProcess+0xeb
ffff8f0f`4481fa00 00007ffb`5272a474 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000d2`9715fc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffb`5272a474
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 48501 instance(s) of page corruption, target is likely to have memory corruption.
This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Show DivCrash Code Links
Show DivLoaded Module List
Show DivRaw Stack Contents
Show DivDump Header Information
Show DivStrings
Show DivPrimary Analysis
Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 8 Kernel Version 17134 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff802`dbc8d000 PsLoadedModuleList = 0xfffff802`dc03b210
Debug session time: Tue Sep 18 05:23:22.670 2018 (UTC - 4:00)
System Uptime: 0 days 0:29:18.593
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, The subtype of the bugcheck.
Arg2: fffff8800b7a96b0
Arg3: 0000000000000000
Arg4: 0000000000000001
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
BUGCHECK_STR: 0x1a_41790
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 2
BAD_PAGES_DETECTED: bd75
LAST_CONTROL_TRANSFER: from fffff802dbd7c846 to fffff802dbe36380
STACK_TEXT:
ffff8f0f`4481ee98 fffff802`dbd7c846 : 00000000`0000001a 00000000`00041790 fffff880`0b7a96b0 00000000`00000000 : nt!KeBugCheckEx
ffff8f0f`4481eea0 fffff802`dbd796a9 : ffff8f0f`4481f039 00002000`00000200 00000000`00000000 00000000`00000000 : nt!MiDeleteVa+0x15d6
ffff8f0f`4481efc0 fffff802`dbd79ab2 : ffff8f0f`4481f590 ffffd280`f46d2e38 ffff8f0f`00000000 ffff8f0f`00000000 : nt!MiWalkPageTablesRecursively+0x299
ffff8f0f`4481f0a0 fffff802`dbd79ab2 : ffff8f0f`4481f590 ffffd2e9`407a3690 ffff8f0f`00000001 ffff8f0f`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffff8f0f`4481f180 fffff802`dbd79ab2 : ffff8f0f`4481f590 ffffd2e9`74a03d18 ffff8f0f`00000002 ffff8f0f`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffff8f0f`4481f260 fffff802`dbd777b7 : ffff8f0f`4481f590 ffffd2e9`74ba5018 ffffb906`00000003 ffff9606`00000000 : nt!MiWalkPageTablesRecursively+0x6a2
ffff8f0f`4481f340 fffff802`dbd61ec3 : ffff8f0f`4481f590 ffff9606`00000001 ffff9606`00000000 ffff9606`00000000 : nt!MiWalkPageTables+0x1e7
ffff8f0f`4481f430 fffff802`dc20acf5 : ffff9606`08005080 ffff9606`00000000 ffff9606`0f94a570 ffff9606`08005080 : nt!MiDeleteVad+0x8d3
ffff8f0f`4481f760 fffff802`dc20ab17 : ffff9606`0f800e90 ffff9606`0f800e90 ffff9606`0f94a570 ffff9606`11f87a80 : nt!MiCleanVad+0x4d
ffff8f0f`4481f790 fffff802`dc1ff88d : ffffffff`00000000 ffffffff`ffffffff ffff8f0f`4481fa01 ffff9606`11f87580 : nt!MmCleanProcessAddressSpace+0x11f
ffff8f0f`4481f810 fffff802`dc131af4 : ffff9606`11f87580 ffffd409`472f5060 ffff8f0f`4481fa80 00000000`00000000 : nt!PspRundownSingleProcess+0x129
ffff8f0f`4481f890 fffff802`dc23b8f3 : 00000000`00000000 ffff8f0f`4481fa01 000000d2`973c8000 ffff9606`08005080 : nt!PspExitThread+0x5ac
ffff8f0f`4481f990 fffff802`dbe46a43 : ffff9606`00001a88 ffff9606`08005080 ffff9606`11f87580 00000000`00000000 : nt!NtTerminateProcess+0xeb
ffff8f0f`4481fa00 00007ffb`5272a474 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
000000d2`9715fc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffb`5272a474
STACK_COMMAND: kb
SYMBOL_NAME: PAGE_NOT_ZERO
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID: PAGE_NOT_ZERO
Followup: MachineOwner
---------
*** Memory manager detected 48501 instance(s) of page corruption, target is likely to have memory corruption.
This free analysis is provided by OSR Open Systems Resources, Inc.
Want a deeper understanding of crash dump analysis? Check out our Windows Kernel Debugging and Crash Dump Analysis Seminar (opens in new tab/window)
Show DivCrash Code Links
Show DivLoaded Module List
Show DivRaw Stack Contents
Show DivDump Header Information
Show DivStrings
Moje pytanie co teraz ? reklamacja czy to ja coś zle robie

Zapomniałem dodać ze zmiana slotu ramu nic nie daje