两周内我第二次遇到了蓝屏，我开始担心了，这是最近一次崩溃的转储，有人可以在这里收集一些有趣的信息吗？
为了避免将来出现这种情况，我安装了一些新的驱动程序：视频、鼠标......并通过 ASUS AI Suite 删除了一些软件。
崩溃发生时，我正在运行以下应用程序：postgres 9.2x64 服务器、pgadmin、带 opengl 渲染的 VLC 播放器、魔兽世界 (directx)、谷歌浏览器、SWTOR 启动器/下载器、outlook、带 w/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，而物理 RAM 中可能存在问题的区域，因此导致故障。您可以通过进行几个小时的 Memtest 来检查这部分，并检查测试中是否有任何错误。