Jump to content

Препоръчан пост

System Information (local)

--------------------------------------------------------------------------------

 

computer name: BOBI-PC

windows version: Windows 7 , 6.1, build: 7600

windows dir: C:\Windows

CPU: GenuineIntel Intel® Pentium® Dual CPU E2180 @ 2.00GHz Intel586, level: 6

2 logical processors, active mask: 3

RAM: 4293386240 total

VM: 2147352576, free: 1949593600

 

 

 

--------------------------------------------------------------------------------

Crash Dump Analysis

--------------------------------------------------------------------------------

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Fri 4.2.2011 г. 10:34:53 GMT your computer crashed

crash dump file: C:\Windows\Minidump\020411-17830-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)

Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002A8C803)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® 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 which cannot be identified at this time.

 

 

On Thu 3.2.2011 г. 22:18:54 GMT your computer crashed

crash dump file: C:\Windows\Minidump\020411-19952-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)

Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF80002A53A71, 0x0, 0xFFFFFFFFFFFFFFFF)

Error: KMODE_EXCEPTION_NOT_HANDLED

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a kernel-mode program 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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Thu 3.2.2011 г. 22:15:22 GMT your computer crashed

crash dump file: C:\Windows\Minidump\020411-17940-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x19C90D)

Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002BB290D, 0xFFFFF880009A91D8, 0xFFFFF880009A8A40)

Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

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 the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.

 

 

On Thu 3.2.2011 г. 16:37:43 GMT your computer crashed

crash dump file: C:\Windows\Minidump\020311-18891-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)

Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80002A551F1)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® 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 which cannot be identified at this time.

 

 

On Thu 3.2.2011 г. 16:35:02 GMT your computer crashed

crash dump file: C:\Windows\Minidump\020311-18283-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)

Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80002A531F1)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® 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 which cannot be identified at this time.

 

 

On Thu 3.2.2011 г. 16:33:23 GMT your computer crashed

crash dump file: C:\Windows\Minidump\020311-18423-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)

Bugcheck code: 0xD1 (0xFFFFF88008E96400, 0x2, 0x0, 0xFFFFF88000E24C50)

Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.

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 Thu 3.2.2011 г. 15:54:09 GMT your computer crashed

crash dump file: C:\Windows\Minidump\020311-18688-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)

Bugcheck code: 0xA (0x8, 0x2, 0x0, 0xFFFFF80002A411F1)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® 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 which cannot be identified at this time.

 

 

On Thu 3.2.2011 г. 10:17:48 GMT your computer crashed

crash dump file: C:\Windows\Minidump\020311-18330-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x66580)

Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF80002AA8803)

Error: IRQL_NOT_LESS_OR_EQUAL

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® 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 which cannot be identified at this time.

 

 

On Thu 3.2.2011 г. 10:15:55 GMT your computer crashed

crash dump file: C:\Windows\Minidump\020311-18174-01.dmp

This was probably caused by the following module: ntfs.sys (Ntfs+0x5B58)

Bugcheck code: 0x24 (0x1904FB, 0xFFFFF880092A7228, 0xFFFFF880092A6A90, 0xFFFFF80002AA6F20)

Error: NTFS_FILE_SYSTEM

file path: C:\Windows\system32\drivers\ntfs.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT File System Driver

Bug check description: This indicates a problem occurred in the NTFS file system.

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.

 

 

 

--------------------------------------------------------------------------------

Conclusion

--------------------------------------------------------------------------------

 

9 crash dumps have been found and analyzed.

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.

Link to comment
Сподели другаде

Тогава направи настройките за създаване на dump файлове както са описани в тази тема, след което ще чакаме още 1 забив, за да се създаде пълен файл, който да качиш някъде.

Проблемът в момента е, че имаш само minidump файлове, а информацията в тях е много недостатъчна, за да се локализира проблема.

 

Ако не ти се чака забив, можеш да си актуализираш всички драйвери. То това е добра идея така или иначе.

Link to comment
Сподели другаде

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Гост
Отговори на тази тема

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   Не можете да качите директно снимка. Качете или добавете изображението от линк (URL)

Loading...
×
×
  • Създай ново...