我的 Windows 8 Pro 新電腦偶爾會出現 BSOD 並帶有悲傷的微笑，但僅限於冷啟動期間。
CPU：i7-3770
MB：華碩 P8B75-M BIOS v.1002
MEM：32GB (4x8Gb) Geil
系統加載後看起來很穩定，即使在高負載下也不會出現故障。我僅在冷啟動期間（而不是重新啟動後）觀察到 BSOD，並且所有錯誤代碼都不同。
有任何想法嗎？
答案1
Windows 8 上的「冷」啟動可能意味著混合啟動 - 重新啟動是老式的「正確」啟動。類似這樣的間歇性錯誤可能很難複製，但您可能想嘗試建立批次檔來運行shutdown /full以執行正確的冷啟動。
如果這有幫助，請嘗試在電源設定中完全關閉快速啟動 - 這可能需要 UAC 特權提升
答案2
您應該執行 chkdsk /F 和 memtest86+ 來測試您的 HDD 和 RAM，因為您會遇到與 NTFS 和記憶體相關的崩潰：
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 00000000000011c1, (reserved)
Arg3: 0000000000000000, Memory contents of the pool block
Arg4: fffff8a0042bf140, Address of the block of pool being deallocated
Debugging Details:
------------------
nt!KeBugCheckEx
nt!ExFreePool
Ntfs!ExFreeToNPagedLookasideList
Ntfs!NtfsDeleteScb
Ntfs!NtfsRemoveScb
Ntfs!NtfsPrepareFcbForRemoval
Ntfs!NtfsTeardownStructures
Ntfs!NtfsDecrementCloseCounts
Ntfs!NtfsCommonClose
Ntfs!NtfsFspClose
nt!ExpWorkerThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 000000000000000d, type of pool violation the caller is guilty of.
Arg2: fffff8a004a64010
Arg3: 0000000074536d4d
Arg4: 75fd8076fbe84b3b
Debugging Details:
------------------
FAULTING_IP:
nt!MiDeleteEmptySubsections+111
fffff800`2923d821 488d3558272900 lea rsi,[nt!MmDeleteSubsectionList (fffff800`294cff80)]
STACK_TEXT:
nt!KeBugCheckEx
nt!ExFreePool
nt!MiDeleteEmptySubsections
nt!MiDereferenceSegmentThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread
SYMBOL_NAME: nt!MiDeleteEmptySubsections+111
IMAGE_NAME: memory_corruption
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff88016ffe460, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff88016ffe3b8, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
------------------
nt!KeBugCheckEx
nt!KiBugCheckDispatch
nt!KiFastFailDispatch
nt!KiRaiseSecurityCheckFailure
WdFilter! ?? ::NNGAKEGL::`string'
fltmgr!DoFreeContext
fltmgr!DoReleaseContext
fltmgr!FltpDeleteContextList
fltmgr!CleanupStreamListCtrl
fltmgr!DeleteStreamListCtrlCallback
nt!FsRtlTeardownPerStreamContexts
Ntfs!NtfsDeleteScb
Ntfs!NtfsRemoveScb
Ntfs!NtfsPrepareFcbForRemoval
Ntfs!NtfsTeardownStructures
Ntfs!NtfsDecrementCloseCounts
Ntfs!NtfsCommonClose
Ntfs!NtfsFspClose
nt!ExpWorkerThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread
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: 000000b50019060b
Arg2: fffff88002bab548
Arg3: fffff88002baad80
Arg4: fffff880017e52f5
Debugging Details:
------------------
Ntfs! ?? ::NNGAKEGL::`string'
Ntfs!NtfsDeleteFcb
Ntfs!NtfsTeardownFromLcb
Ntfs!NtfsTeardownStructures
Ntfs!NtfsDecrementCloseCounts
Ntfs!NtfsCommonClose
Ntfs!NtfsFspClose
nt!ExpWorkerThread
nt!PspSystemThreadStartup
nt!KiStartSystemThread
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: fffff6fc50185e98, memory referenced
Arg2: 0000000000000000, IRQL
Arg3: 0000000000000000, 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: fffff800a2b98353, address which referenced memory
Debugging Details:
------------------
nt!KeBugCheckEx
nt!KiBugCheckDispatch
nt!KiPageFault
nt!MiCaptureAndResetWorkingSetAccessBits
nt!MiTrimOrAgeWorkingSet
nt!MiProcessWorkingSets
nt!MmWorkingSetManager
nt!KeBalanceSetManager
nt!PspSystemThreadStartup
nt!KiStartSystemThread
IMAGE_NAME: memory_corruption
BUCKET_ID_FUNC_OFFSET: d3
FAILURE_BUCKET_ID: AV_nt!MiCaptureAndResetWorkingSetAccessBits
答案3
按照運行 memtest x86+ 的建議，我下載了它，刻錄了啟動 CD，然後啟動了它。兩次完整的pass花了將近12個小時，沒有發現任何錯誤，這很棒：
儘管如此，我還是決定在電腦開機後關閉一段時間後再次啟動memtest。錯誤出現在第一個最簡單的測試：
這讓我很困惑。我甚至嘗試在BIOS中關閉快速啟動，並將POST後的延遲增加到10秒，認為這可能是由於某些硬體的初始化造成的，但沒有成功。上電後不久，memtest仍然發現很少的錯誤，然後系統變得絕對穩定。
這似乎是我的記憶，因為更換記憶體模組確實對我有幫助。需要檢查M/B生產商的合格模組列表，並使用建議的記憶體。
答案4
您是否嘗試檢查主機板上是否有熱裂紋？ DIMM 插槽周圍的實體裂縫或斷線。從某種程度上來說，這是一個記憶體問題...啟動後 15 秒，它會變熱並且所有東西都會膨脹...必須是主機板...而不是記憶體本身。