Windows 7 冻结和崩溃

Windows 7 冻结和崩溃

好的。所以当 Windows 10 推出时,我升级了。我开始遇到各种问题,大约 2 个月前,我开始遇到死机和 BSOD。因此,在错误不断出现的情况下,我给自己买了一个新硬盘(这样我可以保留 10 个,等到所有错误都解决后再使用),然后在上面放了 7 个,现在这个硬盘有相同的斑点,只是大小是原来的两倍。

但是现在我还是会遇到 BSOD:只有在玩游戏时才会出现这种情况...不过,任何游戏都会出现这种情况。它还会毫无预警地冻结,硬盘似乎运行缓慢。

现在我不知道是硬盘有故障,还是某个驱动程序有故障,还是操作系统有故障,或者是否有些东西不兼容,或者是多种问题的组合。

任何建议或意见都将非常有用,或者如果您能帮助解决这个问题,那将会挽救生命。

我的系统的 Dxdiag

前两次 BSOD 崩溃:

计算机已从错误检测中重新启动。错误检测为:0x0000007e (0xffffffffc0000005、0xfffff80002ef2d72、0xfffff880033e06d8、0xfffff880033dff30)。转储已保存在:C:\Windows\MEMORY.DMP。报告 ID:110515-18283-01。

第三次 BSOD 崩溃:

计算机已从错误检测中重新启动。错误检测为:0x0000003b (0x00000000c0000005, 0xfffff80002ef9d72, 0xfffff880098a0ce0, 0x0000000000000000)。转储已保存在:C:\Windows\MEMORY.DMP。报告 ID:110615-14274-01。

感谢大家的帮助。

答案1

在运行 Windows 7 或 Windows Server 2008 R2 的计算机上,操作系统会间歇性崩溃,并出现“0x0000007E”停止错误消息,修补程序可从以下网址下载https://support.microsoft.com/en-us/kb/2528614

在运行 Windows 7 或 Windows Server 2008 R2 的计算机上使用某些 IEEE 1394 设备时,停止错误代码 0x0000003B (SYSTEM_SERVICE_EXCEPTION),可从以下位置下载修补程序https://support.microsoft.com/en-us/kb/980932

答案2

好的,我检查了转储并显示以下内容:

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ef2d72, The address that the exception occurred at
Arg3: fffff880033e06d8, Exception Record Address
Arg4: fffff880033dff30, Context Record Address

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING:  7601.19018.amd64fre.win7sp1_gdr.150928-1507

SYSTEM_MANUFACTURER:  To be filled by O.E.M.

SYSTEM_PRODUCT_NAME:  To be filled by O.E.M.

SYSTEM_SKU:  SKU

SYSTEM_VERSION:  To be filled by O.E.M.

BIOS_VENDOR:  American Megatrends Inc.

BIOS_VERSION:  2501

BIOS_DATE:  04/03/2014

BASEBOARD_MANUFACTURER:  ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT:  M5A99X EVO R2.0

BASEBOARD_VERSION:  Rev 1.xx

DUMP_TYPE:  2

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80002ef2d72

BUGCHECK_P3: fffff880033e06d8

BUGCHECK_P4: fffff880033dff30

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

FAULTING_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`02ef2d72 48890a          mov     qword ptr [rdx],rcx

EXCEPTION_RECORD:  fffff880033e06d8 -- (.exr 0xfffff880033e06d8)
ExceptionAddress: fffff80002ef2d72 (nt!KxWaitForLockOwnerShip+0x0000000000000012)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CPU_MHZ: 10ee

CPU_VENDOR:  AuthenticAMD

CPU_FAMILY: 15

CPU_MODEL: 2

CPU_STEPPING: 0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%08lx verweist auf Speicher 0x%08lx. Der Vorgang %s konnte nicht im Speicher durchgef hrt werden.

EXCEPTION_CODE_STR:  c0000005

FOLLOWUP_IP: 
nt!KxWaitForLockOwnerShip+12
fffff800`02ef2d72 48890a          mov     qword ptr [rdx],rcx

BUGCHECK_STR:  0x7E

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

STACK_TEXT:  
00 nt!KxWaitForLockOwnerShip
01 nt!KeAcquireInStackQueuedSpinLockAtDpcLevel
02 nt!MiUnlinkPageFromLockedList
03 nt!MiGatherMappedPages
04 nt!MiMappedPageWriter
05 nt!PspSystemThreadStartup
06 nt!KiStartSystemThread


THREAD_SHA1_HASH_MOD_FUNC:  28c09789f81362db835bfb028a5ab3b8588a4574

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  fed4c94be63eb750e0aed24dce2a0e902274ed07

THREAD_SHA1_HASH_MOD:  30a3e915496deaace47137d5b90c3ecc03746bf6

IMAGE_VERSION:  6.1.7601.19018

FAILURE_BUCKET_ID:  X64_0x7E_nt!KxWaitForLockOwnerShip+12

BUCKET_ID:  X64_0x7E_nt!KxWaitForLockOwnerShip+12

PRIMARY_PROBLEM_CLASS:  X64_0x7E_nt!KxWaitForLockOwnerShip+12

OSBUILD:  7601

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 7

OSEDITION:  Windows 7 WinNt (Service Pack 1) TerminalServer SingleUserTS

OSBUILD_TIMESTAMP:  2015-09-29 03:55:44

BUILDDATESTAMP_STR:  150928-1507

BUILDLAB_STR:  win7sp1_gdr

BUILDOSVER_STR:  6.1.7601.19018.amd64fre.win7sp1_gdr.150928-1507

FAILURE_ID_HASH_STRING:  km:x64_0x7e_nt!kxwaitforlockownership+12

这些nt!Mi调用是内存管理函数。

因此,您可能遇到了 RAM 问题。您使用的是 Corsair Vengeance ( CMY8GX3M2A2400C11) RAM,这在使用 ASUS 主板 ( M5A99X EVO R2.0) 时经常会导致稳定性问题。

因此,首先使用 memtest86+ 测试您的 RAM,如果 RAM 没问题,请转到 BIOS/UEFI 并使用较慢的 RAM 时序。如果没有任何帮助,请尝试其他 RAM(但这次不是 Corsair 的)。

相关内容