+ -
当前位置:首页 → 问答吧 → 电脑成日BLUE SCREEN,求救

电脑成日BLUE SCREEN,求救

时间:2014-08-05

来源:互联网

部电脑唔知几时开始成日BLUE SCREEN,用左WHOCRASHED CHECK,个REPORT
Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 2/8/2014 12:03:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080214-8704-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800147C960, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.



On Sat 2/8/2014 12:03:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800147C960, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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 that cannot be identified at this time.



On Sat 2/8/2014 11:59:39 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080214-10576-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800147C960, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.



On Fri 1/8/2014 12:23:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080114-7456-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800041A9000, 0xFFFFF880050F9790, 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 that cannot be identified at this time.



On Thu 31/7/2014 12:35:42 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073114-5179-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x6F880)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800147C930, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.



On Thu 31/7/2014 10:38:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073114-5974-01.dmp
This was probably caused by the following module: ntfs.sys (Ntfs+0x48AB)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8800123F8AB, 0xFFFFF88004793938, 0xFFFFF880047931A0)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\ntfs.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT 档案系统驱动程式
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
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 that cannot be identified at this time.



On Wed 30/7/2014 2:56:07 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073014-9079-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800147C960, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.



On Wed 30/7/2014 2:51:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073014-5179-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA800147C960, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.



On Wed 30/7/2014 1:55:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073014-5382-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x1A (0x41790, 0xFFFFFA80002B0CE0, 0xFFFF, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 that cannot be identified at this time.



On Tue 29/7/2014 16:20:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\073014-4960-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0xFFFFF6800014CED8, 0x0, 0x0, 0xFFFFF800041EFA56)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 that cannot be identified at this time.


其实咁即系边样野出问题.....我试过重装过WINDOWS/ALL DRIVERS, 都系唔得......成日BLUESCREEN,求救,

作者: 突千杀   发布时间: 2014-08-05

http://computer.discuss.com.hk/v ... &extra=page%3D1

作者: CobyIsaac   发布时间: 2014-08-05