forum-windows.net
Логин: Запомнить
Пароль:
Добро пожаловать на forum-windows.net! Форум посвящен вопросам установки, настройки и удаления Windows. Чтобы создавать темы и сообщения, необходимо зарегистрироваться.


Автор Сообщение
Сообщение 12.11.2011, 08:57
 Ошибка 1049
Добрый день, при работе около часа, компьютер выключается и вылазеет синий экран
с такой ошибкой. Помогите, не знаю что делать(
Сигнатура проблемы:
Имя события проблемы: BlueScreen
Версия ОС: 6.1.7601.2.1.0.768.2
Код языка: 1049

Дополнительные сведения об этой проблеме:
BCCode: 1000007e
BCP1: C0000005
BCP2: 890DB351
BCP3: 8DE437B4
BCP4: 8DE43390
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Файлы, содержащие сведения об этой проблеме:
C:\Windows\Minidump\111211-22464-01.dmp
C:\Users\EmiiLee\AppData\Local\Temp\WER-38516-0.sysdata.xml


Сообщение 12.11.2011, 15:23
 Re: Ошибка 1049
Здравствуйте.

1. Скачайте, установите и запустите бесплатную версию программы WhoCrashed.

2. В программе WhoCrashed нажмите Analyze.

3. Скопируйте результаты анализа дампа из WhoCrashed и вставьте их в эту тему.


Сообщение 12.11.2011, 16:57
 Re: Ошибка 1049
On Sat 12.11.2011 5:44:15 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrpamp.exe (nt!KeBugCheckEx+0x1E)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFFFFF890DB351, 0xFFFFFFFF8DE437B4, 0xFFFFFFFF8DE43390)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
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: ntkrpamp.exe .
Google query: ntkrpamp.exe SYSTEM_THREAD_EXCEPTION_NOT_HANDLED



On Fri 11.11.2011 14:38:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\111111-19422-01.dmp
This was probably caused by the following module: wudfrd.sys (WUDFRd+0xA13A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFFFFFA21CB13A, 0xFFFFFFFF8DE43830, 0xFFFFFFFF8DE43410)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\Windows\system32\drivers\wudfrd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Windows Driver Foundation - User-mode Driver Framework Reflector
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 which cannot be identified at this time.
вот что показал
это в основном происходит, когда брат в игрушку какую-нибудь играет


Сообщение 12.11.2011, 18:43
 Re: Ошибка 1049
Скачайте и установите хотфикс. Если раньше вы не запрашивали хотфиксы, то ничего страшного в этом нет, просто следуйте инструкции.


Сообщение 12.11.2011, 19:20
 Re: Ошибка 1049
Почему он пишет, обновление не применимо к этому компьютеру?
я все делала по инструкции и пароль он не запросил


Сообщение 16.04.2012, 11:22
 Re: Ошибка 1049
System Information (local)
--------------------------------------------------------------------------------

computer name: OPHELIA-13VPC
windows version: Windows 7 , 6.1, build: 7600
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 4292923392 total
VM: 2147352576, free: 1888845824



--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.


On Mon 16.04.2012 7:55:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041612-25053-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x5EF84)
Bugcheck code: 0xD1 (0x200000000, 0x2, 0x8, 0x200000000)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\tcpip.sys
product: Операционная система Microsoft® Windows®
company: Microsoft Corporation
description: Драйвер TCP/IP
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 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 Mon 16.04.2012 7:55:22 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: 0xD1 (0x200000000, 0x2, 0x8, 0x200000000)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
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 Sun 15.04.2012 11:38:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\041512-20264-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80003C3E178, 0xFFFFF880075030D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 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 Mon 02.04.2012 0:00:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040212-21200-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0x50 (0xFFFFFFFFFFFFFFF8, 0x0, 0xFFFFF9600026ABDC, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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 invalid system memory has been referenced.
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 Sun 01.04.2012 11:00:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040112-23181-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70540)
Bugcheck code: 0xD1 (0xFFFFF88007DBBE40, 0x5, 0x0, 0xFFFFF880101D612A)
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.


Сообщение 16.04.2012, 11:23
 Re: Ошибка 1049
И вот еще.. компьютер очень часто перезагружается с ошибкой..

--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 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.


Сообщение 06.11.2012, 16:53
 Re: Ошибка 1049
Помогите, пожалуйста((( Постоянно вырубается ноут вот с этой ошибкой!
System Information (local)
--------------------------------------------------------------------------------
computer name: KYBI-PC
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Pentium(R) Dual-Core CPU T4200 @ 2.00GHz Intel586, level: 6
2 logical processors, active mask: 3
RAM: 2146553856 total
VM: 2147352576, free: 1935757312
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Tue 06.11.2012 13:33:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110612-18252-01.dmp
This was probably caused by the following module: netw5v64.sys (NETw5v64+0x518A70)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netw5v64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
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: netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED

On Sun 04.11.2012 17:04:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110412-17877-01.dmp
This was probably caused by the following module: netw5v64.sys (NETw5v64+0x518A70)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netw5v64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
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: netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED

On Mon 29.10.2012 17:24:45 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102912-19328-01.dmp
This was probably caused by the following module: netw5v64.sys (NETw5v64+0x518A70)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netw5v64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
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: netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED


Сообщение 06.11.2012, 16:53
 Re: Ошибка 1049
On Fri 26.10.2012 17:58:03 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102612-18891-01.dmp
This was probably caused by the following module: netw5v64.sys (NETw5v64+0x518A70)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netw5v64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
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: netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED

On Tue 16.10.2012 14:11:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\101612-18049-01.dmp
This was probably caused by the following module: netw5v64.sys (NETw5v64+0x518A70)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\netw5v64.sys
product: Intel® Wireless WiFi Link Adapter
company: Intel Corporation
description: Intel® Wireless WiFi Link Driver
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.
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: netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation).
Google query: Intel Corporation KMODE_EXCEPTION_NOT_HANDLED
--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

5 crash dumps have been found and analyzed. A third party driver has 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:

netw5v64.sys (Intel® Wireless WiFi Link Driver, Intel Corporation)

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.


Сообщение 24.08.2013, 16:04
 Re: Ошибка 1049
Доброго времени суток! Беспокоит аналогичная проблема. При играх, после пяти- десяти минут запуска, они с треском вылетают выдавая такое окно: Сигнатура проблемы:
Имя события проблемы: BlueScreen
Версия ОС: 6.1.7601.2.1.0.256.1
Код языка: 1049

Дополнительные сведения об этой проблеме:
BCCode: 124
BCP1: 0000000000000000
BCP2: FFFFFA800717B8F8
BCP3: 0000000000000000
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Файлы, содержащие сведения об этой проблеме:
C:\Windows\Minidump\080513-14461-01.dmp
C:\Users\Denis\AppData\Local\Temp\WER-44257-0.sysdata.xml


Начать новую тему Ответить на тему  [ Сообщений: 12 ]  На страницу 1, 2  След.


 




Powered by phpBB