Bantuan BSOD

Komputer telah banyak crash baru-baru ini, berbagai BSODs terlibat. Mencoba menunjukkan masalah (melalui Validasi Driver) hanya menyebabkan lebih banyak crash. Baru saja menginstal dan mencoba menggunakan program debug yang direkomendasikan pada posting lain yang saya baca, dan ia memberi tahu saya bahwa saya tidak memiliki izin untuk mengakses file dump. Adakah yang tahu cara mengatasi hal ini, sehingga saya dapat memposting info dump saya dan mudah-mudahan menghasilkan semacam solusi?

Terima kasih R

Anda memiliki masalah perangkat keras. 1 dump menunjukkan bahwa L1 cache CPU Anda mengalami masalah:

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa800b04c028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b6002000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000035000175, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  NS2.exe

CURRENT_IRQL:  f

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

STACK_TEXT:  
nt!KeBugCheckEx
hal!HalBugCheckSystem
nt!WheaReportHwError
hal!HalpMcaReportError
hal!HalpMceHandler
hal!HalHandleMcheck
nt!KxMcheckAbort
nt!KiMcheckAbort
0x0



IMAGE_NAME:  AuthenticAMD

FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE

FAILURE_ID_HASH_STRING:  km:x64_0x124_authenticamd_processor_cache


2: kd> !errrec fffffa800b04c028
===============================================================================
Common Platform Error Record @ fffffa800b04c028
-------------------------------------------------------------------------------
Record Id     : 01cf8823d8a14be4
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 6/15/2014 2:57:27 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800b04c0a8
Section       @ fffffa800b04c180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : Cache error
Operation     : Generic
Flags         : 0x00
Level         : 1
CPU Version   : 0x0000000000100fa0
Processor ID  : 0x0000000000000002

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800b04c0f0
Section       @ fffffa800b04c240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000002
CPU Id        : a0 0f 10 00 00 08 06 02 - 09 20 80 00 ff fb 8b 17
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800b04c240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800b04c138
Section       @ fffffa800b04c2c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : DCACHEL1_EVICT_ERR 

Tempat sampah kedua menunjukkan kerusakan memori:

*******************************************************************************
*                                                                             *
*                        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: fffffa801c355010, 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: fffff80002b8db07, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d070e0
GetUlongFromAddress: unable to read from fffff80002d07198
 fffffa801c355010 Nonpaged pool

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReleaseConfirmedPageFileSpace+87
fffff800`02b8db07 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  Setup.exe

STACK_TEXT:  
nt!KeBugCheckEx
nt!KiBugCheckDispatch
nt!KiPageFault
nt!MiReleaseConfirmedPageFileSpace
nt! ?? ::FNODOBFM::`string'
nt!NtFreeVirtualMemory
nt!KiSystemServiceCopyEnd
0x0


IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87

FAILURE_ID_HASH_STRING:  km:x64_0xa_nt!mireleaseconfirmedpagefilespace+87

Dump ke-3 menunjukkan masalah NTFS:

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

NTFS_FILE_SYSTEM (24)
    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd
    parameters are the exception record and context record. Do a .cxr
    on the 3rd parameter and then kb to obtain a more informative stack
    trace.
Arguments:
Arg1: 00000000000c08a2
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x24

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

STACK_TEXT:  
nt!KeBugCheckEx
Ntfs!NtfsPagingFileIo
Ntfs! ?? ::FNODOBFM::`string'
fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted
fltmgr!FltpDispatch
nt!IoPageRead
nt!MiIssueHardFault
nt!MmAccessFault
nt!KiPageFault
0x0


IMAGE_NAME:  Ntfs.sys

FAILURE_ID_HASH_STRING:  km:x64_0x24_ntfs!ntfspagingfileio+155

start             end                 module name
fffff880`01222000 fffff880`013c5000   Ntfs       (pdb symbols)          d:\sym\dl\nt\ntfs.pdb\A3FA3C11632A4FC09223AB611D6EFF7F2\ntfs.pdb
    Loaded symbol image file: Ntfs.sys
    Mapped memory image file: d:\sym\dl\Nt\Ntfs.sys\4A5BC14F1a3000\Ntfs.sys
    Image path: \SystemRoot\System32\Drivers\Ntfs.sys
    Image name: Ntfs.sys
    Timestamp:        Tue Jul 14 01:20:47 2009

dump ke-4 juga menunjukkan masalah RAM:

*******************************************************************************
*                                                                             *
*                        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: fffffa80062789a0
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  steamerrorrepo

STACK_TEXT:  
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt!MiRemoveMappedView
nt!MiUnmapViewOfSection
nt!NtUnmapViewOfSection
nt!KiSystemServiceCopyEnd
0x0

Jadi kamu harus lari memtest86 + untuk memeriksa RAM, jika ini baik-baik saja, jalankan chkdsk /f untuk memperbaiki masalah sistem file NTFS.