是什麼導致藍屏並使我的電腦重新啟動?

是什麼導致藍屏並使我的電腦重新啟動?

我需要專家的幫助。最近,我的一個朋友帶來了備件並為我組裝了一台電腦。 PC 的規格如下:

Casing: Aerocool vs92 gaming
Processor: core i7 3.4-3.9GHz 8mb cache LGA1155
Mainboard: msi b75 MA-G43 professional
Memory: Kingston 4GB DDR3 1333
HARDDISK: TOSHIBA 500GB SATA 7200 RPM
GRAPHICS CARD: msi HD 6450 2GB FULL HD HDMI
WINDOWS 7 ULTIMATE 64 bit

我已將小型轉儲檔案上傳到 dropbox 並發布了以下連結:https://www.dropbox.com/s/d1i40f618m1kglc/Minidump.rar

實際上,電腦正在重新啟動,並顯示 bccode 錯誤代碼 2b 和 a。重新安裝顯示卡驅動程式後,電腦正在重新啟動,並出現錯誤 bccode 117、1a、4e、d1 和 a。

有人可以幫助我了解發生了什麼事以及如何解決這個問題嗎?我該換顯卡嗎?我應該改變任何部分來解決這個問題嗎?我需要專家的幫助。請幫我。

答案1

轉儲顯示 RAM 問題(在 nt!NtFreeVirtualMemory 和 nt!MiResolveDemandZeroFault 處崩潰):

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

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa86017ecff0, 2, 1, fffff80002ce835f}

Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+100 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        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: fffffa86017ecff0, 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: fffff80002ce835f, address which referenced memory

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

CURRENT_IRQL:  2

FAULTING_IP: 
nt!MiReplenishPageSlist+100
fffff800`02ce835f f00fba6b1000    lock bts dword ptr [rbx+10h],0

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  firefox.exe

STACK_TEXT:  
nt!KeBugCheckEx
nt!KiBugCheckDispatch
nt!KiPageFault
nt!MiReplenishPageSlist
nt!MiRemoveAnyPage
nt!MiResolveDemandZeroFault
nt!MmAccessFault
nt!KiPageFault
0x0


IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+100

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

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  dllhost.exe

STACK_TEXT:  
nt!KeBugCheckEx
nt! ?? ::FNODOBFM::`string'
nt!NtFreeVirtualMemory
nt!KiSystemServiceCopyEnd
nt!KiServiceLinkage
nt!PspExitThread
nt!PspTerminateThreadByPointer
nt!NtTerminateThread
nt!KiSystemServiceCopyEnd
0x0


FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+339d6

請下載記憶體測試86+,從 ISO 燒錄新的可啟動 CD(如果可能,請使用 CD-RW)(下載並使用影像燒錄若要執行此操作或在 Windows 7 中雙擊 ISO),請重新啟動 PC 並掃描 RAM 4-5 小時以尋找錯誤。如果 memtest86+ 偵測到錯誤,請測試每個模組本身並更換故障的 RAM。

如果memtest沒有報錯,請下載CPU-Z,查看記憶體和 SPD 標籤並驗證當前 RAM 速度和計時是否與您在 SPD 標籤中看到的值相符。如果您的 RAM 以 CR(命令速率)1T 運行,請在 BIOS 中將該值變更為 2T。

相關內容