|
|
|
|
| Компьютерный форум OSzone.net » Сфера Microsoft » Устранение критических ошибок Windows » BSOD - 0x000000C2: BAD_POOL_CALLER |
|
|
BSOD - 0x000000C2: BAD_POOL_CALLER
|
|
(*.*) Сообщения: 36497 |
Ресурсы, которые помогут Вам устранить эту ошибку:
|
|
|
------- Отправлено: 21:34, 03-03-2007 |
|
Ветеран Сообщения: 890
|
Профиль | Отправить PM | Цитировать Цитата Petya V4sechkin:
Может его подложить в System32?..... чёт вигня какаято... |
|
|
Последний раз редактировалось DimonNT, 06-09-2013 в 18:38. Отправлено: 09:25, 01-01-2013 | #451 |
|
Сообщения: 53189
|
Профиль | Отправить PM | Цитировать DimonNT, к сожалению, в дампах причина не указана.
Проверку драйверов включить невозможно? Тогда попробуйте переименовать файлы:
|
|
Последний раз редактировалось Petya V4sechkin, 01-01-2013 в 12:04. Отправлено: 10:11, 01-01-2013 | #452 |
|
Новый участник Сообщения: 5
|
Профиль | Отправить PM | Цитировать Данная ошибка возникает при открытии определенных сайтов(стоит только открыть и сразу синий экран с перезагрузкой), либо во время их просмотра.
Винда чистая (Windows 7 Home Basic x63, только установил). Скрин синего экрана: http://savepic.ru/4299378.jpg Незнаю что делать. Пожалуйста помогите разобраться. Код:
 Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\009\031813-13728-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02855000 PsLoadedModuleList = 0xfffff800`02a9ae90
Debug session time: Mon Mar 18 17:35:22.791 2013 (GMT+3)
System Uptime: 0 days 0:06:51.711
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C2, {7, 1097, 50a921c, fffff80000ba2a00}
Unable to load image \SystemRoot\system32\DRIVERS\vwififlt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vwififlt.sys
*** ERROR: Module load completed but symbols could not be loaded for vwififlt.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!PVOID ***
*** ***
*************************************************************************
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_TRACKER_BIG_PAGES ***
*** ***
*************************************************************************
Cannot get _POOL_TRACKER_BIG_PAGES type size
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : vwififlt.sys ( vwififlt+69c0 )
Followup: MachineOwner
---------
|
|
Отправлено: 19:32, 18-03-2013 | #453 |
|
Сообщения: 53189
|
Профиль | Отправить PM | Цитировать HTI, выполните, пожалуйста, пункт 3 прикрепленной темы
Важно! Прежде чем задать вопрос, прочтите эту тему! |
|
Отправлено: 19:35, 18-03-2013 | #454 |
|
Новый участник Сообщения: 5
|
Профиль | Отправить PM | Цитировать Цитата Petya V4sechkin:
Код:
Сигнатура проблемы: Имя события проблемы: BlueScreen Версия ОС: 6.1.7601.2.1.0.768.3 Код языка: 1049 Дополнительные сведения об этой проблеме: BCCode: c2 BCP1: 0000000000000007 BCP2: 0000000000001097 BCP3: 00000000052210AE BCP4: FFFFF80000BA2A00 OS Version: 6_1_7601 Service Pack: 1_0 Product: 768_1 Файлы, содержащие сведения об этой проблеме: C:\Windows\Minidump\031813-13884-01.dmp C:\Users\Пользователь\AppData\Local\Temp\WER-33789-0.sysdata.xml Ознакомьтесь с заявлением о конфиденциальности в Интернете: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0419 Если заявление о конфиденциальности в Интернете недоступно, ознакомьтесь с его локальным вариантом: C:\Windows\system32\ru-RU\erofflps.txt |
|
|
Отправлено: 20:10, 18-03-2013 | #455 |
|
Новый участник Сообщения: 5
|
Профиль | Отправить PM | Цитировать |
|
Отправлено: 20:22, 18-03-2013 | #456 |
|
Сообщения: 53189
|
Профиль | Отправить PM | Цитировать HTI, сбой на RTL8187Se.sys - драйвер Realtek Wireless (обновите на официальном сайте или отсюда).
Также советую обновить Atheros здесь. |
|
Отправлено: 20:41, 18-03-2013 | #457 |
|
Новый участник Сообщения: 5
|
Профиль | Отправить PM | Цитировать Petya V4sechkin а какую версию драйвера Atheros мне нужно скачать. Попробовал Atheros L2 Fast Ethernet 10/100Base-T Controller (L2) (Drivers) он мне пишет что в ноуте нет такого оборудования или что то типа того.
|
|
Отправлено: 22:07, 18-03-2013 | #458 |
|
Сообщения: 53189
|
Профиль | Отправить PM | Цитировать Цитата HTI:
У вас Atheros AR8132 - выбирайте драйвер для серии AR813x/AR815x/AR816x. |
|
|
Отправлено: 22:14, 18-03-2013 | #459 |
|
Новый участник Сообщения: 5
|
Профиль | Отправить PM | Цитировать Petya V4sechkin большущее спасибо!!! Очень рад, что нашел вас, а то незнаю чтоб делал!!! Я уж думал, что с железом что-то не в порядке. После обновления драйвера Realtek Wireless проблема исчезла.
Интересно и немного странно почему тот драйвер, что идет с виндой создавал такой сбой... Винда ведь новая и установлена с официального образа. |
|
Последний раз редактировалось HTI, 18-03-2013 в 22:26. Причина: грамматическая ошибка Отправлено: 22:25, 18-03-2013 | #460 |
|
Участник сейчас на форуме |
 |
Участник вне форума |
 |
Автор темы |
 |
Сообщение прикреплено |
| |||||
| Название темы | Автор | Информация о форуме | Ответов | Последнее сообщение | |
| BAD_POOL_CALLER ect | Eugeniy | Лечение систем от вредоносных программ | 9 | 02-01-2010 13:52 | |
|
|
Время: 12:36. | © OSzone.net 2001-
|
|
Powered by: vBulletin Copyright ©2000 - 2024, Jelsoft Enterprises Ltd. |
