2주 만에 두 번째 bsod를 경험했고 걱정되기 시작했습니다. 여기에 최신 충돌의 덤프가 있습니다. 여기에서 흥미로운 정보를 수집할 수 있는 사람이 있나요?
앞으로 이 문제를 방지하기 위해 비디오, 마우스 등 몇 가지 새로운 드라이버를 설치하고 ASUS AI Suite의 일부 소프트웨어를 제거했습니다.
충돌이 발생했을 때 나는 다음 애플리케이션을 실행하고 있었습니다: postgres 9.2x64 서버, pgadmin, VLC 플레이어(opengl 렌더링 포함), 월드 오브 워크래프트(directx), google chrome, SWTOR 실행기/다운로더, outlook, 가상 상자(w7 포함)(활성)
시스템 세부정보:
OS Name: Microsoft Windows 7 Professional
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Workstation
OS Build Type: Multiprocessor Free
Registered Owner: trip
Registered Organization:
Original Install Date: 11/17/2012, 1:20:01 PM
System Boot Time: 1/24/2013, 9:35:44 PM
System Manufacturer: Asus
System Model: Z77 Sabertooth
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 58 Stepping 9 GenuineIntel ~3501 Mhz
BIOS Version: American Megatrends Inc. 1504, 8/3/2012
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-05:00) Eastern Time (US & Canada)
Total Physical Memory: 16,335 MB
Available Physical Memory: 13,047 MB
Virtual Memory: Max Size: 32,668 MB
Virtual Memory: Available: 28,717 MB
Virtual Memory: In Use: 3,951 MB
Page File Location(s): C:\pagefile.sys
Domain: WORKGROUP
Hotfix(s): 122 Hotfix(s) Installed.
덤프 세부사항:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c3010d90, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff96000239e36, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging Details:
------------------
READ_ADDRESS: fffff900c3010d90 Paged session pool
FAULTING_IP:
win32k!IsThreadHung+22
fffff960`00239e36 488b8170010000 mov rax,qword ptr [rcx+170h]
MM_INTERNAL_CODE: 0
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 50aeecc6
MODULE_NAME: win32k
FAULTING_MODULE: fffff960000d0000 win32k
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
TRAP_FRAME: fffff880028cc710 -- (.trap 0xfffff880028cc710)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000f99a027 rbx=0000000000000000 rcx=fffff900c3010c20
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff96000239e36 rsp=fffff880028cc8a0 rbp=000000000000000f
r8=00009fddc3f269c2 r9=fffff880028cc930 r10=00000000009fddc3
r11=000000000f99a027 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
win32k!IsThreadHung+0x22:
fffff960`00239e36 488b8170010000 mov rax,qword ptr [rcx+170h] ds:fffff900`c3010d90=????????????????
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002e76eec to fffff80002ecefc0
STACK_TEXT:
fffff880`028cc5a8 fffff800`02e76eec : 00000000`00000050 fffff900`c3010d90 00000000`00000000 fffff880`028cc710 : nt!KeBugCheckEx
fffff880`028cc5b0 fffff800`02ecd0ee : 00000000`00000000 fffff900`c3010d90 fffff880`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4514f
fffff880`028cc710 fffff960`00239e36 : fffffa80`0f4fa500 00000000`0000001b 00000000`00000000 fffff880`03317100 : nt!KiPageFault+0x16e
fffff880`028cc8a0 fffff960`0020f906 : 00000000`00000000 00000000`00000002 fffff960`003b6740 fffff900`c011fa18 : win32k!IsThreadHung+0x22
fffff880`028cc8d0 fffff960`0023a448 : fffff900`c06b2040 00000000`0000000f 00000000`0000000c fffff900`c011fa18 : win32k!IsHungWindow+0x1a
fffff880`028cc900 fffff960`00194bdd : fffff900`c2d838e0 00000000`00000001 00000000`00000004 fffff800`02ed7e33 : win32k!xxxHungAppDemon+0x68
fffff880`028cc960 fffff960`0019565b : 00000000`00000000 fffff960`003b6f10 00000000`00000004 00000000`00000001 : win32k!TimersProc+0xf1
fffff880`028cc9b0 fffff960`00125148 : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000348 : win32k!RawInputThread+0x9ab
fffff880`028cca80 fffff960`001a5e9a : fffffa80`00000002 fffff880`028aae00 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`028ccab0 fffff800`02ece253 : fffffa80`0f62d060 00000000`00000004 000007ff`fffd3000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`028ccae0 000007fe`fd8f1eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0310fc78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`fd8f1eea
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!IsThreadHung+22
fffff960`00239e36 488b8170010000 mov rax,qword ptr [rcx+170h]
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: win32k!IsThreadHung+22
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x50_win32k!IsThreadHung+22
BUCKET_ID: X64_0x50_win32k!IsThreadHung+22
Followup: MachineOwner
---------
답변1
제공된 정보에 따르면 읽기를 시도할 때 메모리 문제(RAM, 주 메모리, L2, 비디오 RAM 등)가 발생하는 것 같습니다. SO 또는 프로그램이 메모리 영역을 읽으려고 시도했지만 범위를 벗어났거나 영역이 비어 있고 데이터를 포함해야 하기 때문에 찾지 못하는 경우 오류가 발생합니다.
위의 모든 프로그램을 실행할 때 오류가 발생하면 RAM에 문제가 있을 수 있습니다. 왜냐하면 많은 양을 할당하고 실제 RAM에 문제가 있는 영역이 있을 수 있으므로 오류가 발생하기 때문입니다. 이 부분은 Memtest를 몇 시간 동안 해보면서 테스트 결과에 오류가 있는지 확인할 수 있습니다.