ASUS M50Vm win7 64bit 2G 近個月來 筆電時常會因為開啟網頁或是玩小遊戲時出現當機現象 除了出現過畫面停滯.畫面只剩小方塊.還出現全螢幕條紋圖案 送去經銷商那檢測後 發現有條記憶體損壞 拔去送修 本來認為問題應該能解決了 但發現這幾日 當機頻率大增(症頭:小方塊.畫面停滯 最大宗是藍白畫面) http://imgur.com/KpUeP,LQBax,1Kcv4,29daF,u9D12,toTs1 此為前日連續當機時所拍下的系統畫面 http://i.imgur.com/1Kcv4.jpg http://i.imgur.com/29daF.jpg http://i.imgur.com/u9D12.jpg http://i.imgur.com/toTs1.jpg 以下是檢測報告連結 http://0rz.tw/rD5hj bluescreen檢測 (excel格式) http://0rz.tw/3DUUq whocrashed檢測 (文字檔格式) Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Mon 2011/12/5 上午 01:21:00 GMT your computer crashed crash dump file: C:\Windows\Minidump\120511-22339-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x12EE64) Bugcheck code: 0x116 (0xFFFFFA80021F9010, 0xFFFFF88005F54E64, 0xFFFFFFFFC00000B5, 0xA) Error: VIDEO_TDR_ERROR file path: C:\Windows\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 260.99 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 260.99 Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 260.99 , NVIDIA Corporation). Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR On Mon 2011/12/5 上午 01:21:00 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x214) Bugcheck code: 0x116 (0xFFFFFA80021F9010, 0xFFFFF88005F54E64, 0xFFFFFFFFC00000B5, 0xA) Error: VIDEO_TDR_ERROR file path: C:\Windows\system32\drivers\dxgkrnl.sys product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: DirectX Graphics Kernel Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sun 2011/12/4 上午 08:58:24 GMT your computer crashed crash dump file: C:\Windows\Minidump\120411-21512-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x75A028) Bugcheck code: 0x116 (0xFFFFFA8007D414E0, 0xFFFFF8800656E028, 0xFFFFFFFFC000009A, 0x4) Error: VIDEO_TDR_ERROR file path: C:\Windows\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 260.99 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 260.99 Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 260.99 , NVIDIA Corporation). Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR On Sat 2011/12/3 上午 05:29:54 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-21450-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000494E74D, 0xFFFFF88006B81770, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 2011/12/3 上午 05:21:25 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-22807-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800049B474D, 0xFFFFF88008714770, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 2011/12/3 上午 05:19:19 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-22729-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000499874D, 0xFFFFF88005CEE770, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 2011/12/3 上午 05:17:48 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-21824-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800049A574D, 0xFFFFF88006B14770, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 2011/12/3 上午 05:08:20 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-21730-01.dmp This was probably caused by the following module: aswmonflt.sys (aswMonFlt+0x36575) Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880045BD688, 0xFFFFF880045BCEF0, 0xFFFFF88000DD511E) Error: NTFS_FILE_SYSTEM file path: C:\Windows\system32\drivers\aswmonflt.sys product: avast! Antivirus System company: AVAST Software description: avast! File System Minifilter for Windows 2003/Vista Bug check description: This indicates a problem occurred in the NTFS file system. A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software). Google query: aswmonflt.sys AVAST Software NTFS_FILE_SYSTEM On Sat 2011/12/3 上午 05:06:08 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-21871-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x19 (0x3, 0xFFFFF8A00207A6E0, 0xFFFDF8A00207A6E0, 0xFFFFF8A00207A6E0) Error: BAD_POOL_HEADER file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 2011/12/3 上午 05:04:32 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-21777-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000499E74D, 0xFFFFF8800AB14770, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 2011/12/3 上午 05:02:53 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-21996-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x19 (0x3, 0xFFFFF8A002086A50, 0xFFFFF8A002086A50, 0xFFF7F8A002086A50) Error: BAD_POOL_HEADER file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 2011/12/3 上午 05:01:21 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-21886-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000494E74D, 0xFFFFF88005D08770, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 2011/12/3 上午 04:59:51 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-21902-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x70740) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000495074D, 0xFFFFF88009EE7770, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\ntoskrnl.exe product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Sat 2011/12/3 上午 04:58:24 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-21496-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x554C1) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960000B54C1, 0xFFFFF88006BD3FA0, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: 多使用者 Win32 驅動程式 Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. On Sat 2011/12/3 上午 04:50:41 GMT your computer crashed crash dump file: C:\Windows\Minidump\120311-22261-01.dmp This was probably caused by the following module: win32k.sys (win32k+0x2288AA) Bugcheck code: 0x3B (0xC0000005, 0xFFFFF960002F88AA, 0xFFFFF88009BBBF20, 0x0) Error: SYSTEM_SERVICE_EXCEPTION file path: C:\Windows\system32\win32k.sys product: MicrosoftR WindowsR Operating System company: Microsoft Corporation description: 多使用者 Win32 驅動程式 Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. The following dump files were found but could not be read. These files may be corrupt: C:\Windows\Minidump\112111-22791-01.dmp -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- On your computer a total of 35 crash dumps have been found. Only 34 could be analyzed. Only 15 are included in this report. 2 third party drivers have been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 260.99 , NVIDIA Corporation) aswmonflt.sys (avast! File System Minifilter for Windows 2003/Vista, AVAST Software) If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems. Read the topic general suggestions for troubleshooting system crashes for more information. Note that it's not always possible to state with certainty whether a reported driver is actually responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further. 請問我的筆電是哪邊出問題了QQ -- ︵◤ ◥ ◣▅▆◢◢◥◥◤◤ ◥◣◣◣ ◥▄▃▄◤ \\ // ＦＡＴＥ／stay night ● ●◣ ▼= =▼◥▂ ▂◤ ◣︶︶◢ ◥ 皿 ◤ ◣ ε ◥ 惡役三人組 ψfennix ▲飯▲ ▼♂▼ ▼冏▼ ■ ▲〒▲ ㄑㄑ http://gsky.pixnet.net/blog --

※ 發信站: 批踢踢實業坊(ptt.cc) ◆ From: 111.253.72.232