BlueScreen

_StreloK_,

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe

переводится примерно так:
Невозможно загрузить \SystemRoot\system32\ntkrnlpa.exe
Внимание: Невозможно проверить цифровые подписи ntkrnlpa.exe

Дистрибутив не от Васи Пупкина?
У вас:

7600.16385.x86fre.win7_rtm.090713-1255

У меня:
7600.16385.090713-1255_x86fre_client_en-us_Retail_Ultimate-GRMCULFRER_EN_DVD.iso
Похоже что от него.
Антивирус стоит? Проверяли?

Как мне кажется проблема никакого отношения к utorrent не имеет.

Andrey100, с каких это пор timestamp переводится как цифровые подписи?
_StreloK_, поставьте обновления и правильно укажите путь к символам.

Арсений - про путь к символам - расскажите, пожалуйста, подробнее
обновления стоят все, автоматом
дрова к сетевухам - родные виндовые, вчера обновились (бсод был и до и после)

Андрей - строго utorrent, потому как машинка отлично работает, пока торрент не запустишь. 5-15 секунд - и привет(
7264 вела себя также, кстати
нод 4 стоит, обновляется

Кстати. Вот не знаю... но у меня подозрение тоже на эту вещь. Потому как пару раз бсоды вылазили именно после торрента. Пользую биткомет... но как проверить без него... вот думаю.

_StreloK_ писал:про путь к символам - расскажите, пожалуйста, подробнее

forums.php?m=posts&p=176355#176355

аднака и чего изменилось?

Loading Dump File [C:\tmp\082209-28812-011.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8180f000 PsLoadedModuleList = 0x81957810
Debug session time: Sat Aug 22 10:57:30.661 2009 (GMT+4)
System Uptime: 0 days 0:47:23.395
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
..........................

это оно косяк вызывает?
Unable to load image \SystemRoot\system32\ntkrnlpa.exe
если я правильно понял, этот исполняемый файл - ядро. и он не запускается в win32 среде

По поводу Symbols лучше скачать и установить http://www.microsoft.com/whdc/devtools/debugging/symbolpkg.mspx#d

толку столько же - я ровным счётом не понимаю, что происходит
но бсод достал
готов снести это шустрое Г и возвернуть старую добрую висту аио сп2

Loading Dump File [C:\tmp\082209-28812-011.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Windows\Symbols*http://msdl.microsoft.com/download/symbols;C:\Symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8180f000 PsLoadedModuleList = 0x81957810
Debug session time: Sat Aug 22 10:57:30.661 2009 (GMT+4)
System Uptime: 0 days 0:47:23.395
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols


всё, разобрался(кажется), всем спасибо
это таки wi-fi адаптер. и дрова его - виндовые, а не родные. щас от произвонителя нарою

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
FAULTING_MODULE: 8180f000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49a5fef3
BUGCHECK_STR: 0xc2_7
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 87e22651 to 8192e1b6
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
8078ae14 87e22651 8078ae74 00000000 8078ae3c nt+0x11f1b6
8078ae24 8913350d 8078ae74 00000030 00000000 ndis!NdisFreeMemory+0x16
8078ae3c 8913b0c4 8078ae74 00000030 8078ae7a RTL8187Se!PlatformFreeMemory+0x1b
8078ae6c 891564ef 83952c70 84dc45be 84dc45be RTL8187Se!DrvIFIndicatePacket+0x294
8078ae94 8915661c 84dce000 84dc45be 84dce673 RTL8187Se!ProcessReceivedPacket+0x163
8078aeb0 891588ba 84dce000 84d70008 84dce000 RTL8187Se!RxHandleInterrupt+0xc7
8078aecc 8913a543 00000080 00000000 849060e0 RTL8187Se!NicIFHandleInterrupt+0x10e
8078aee4 87e6c309 84dce000 00000000 8078af10 RTL8187Se!N6PciHandleInterrupt+0x17
8078af20 87e179f4 84dbee3c 00dbee28 00000000 ndis!ndisMiniportDpc+0xe2
8078af48 818773b5 84dbee3c 84dbee28 00000000 ndis!ndisInterruptDpc+0xaf
8078afa4 81877218 81938d20 840a3a88 00000000 nt+0x683b5
8078aff4 818769dc a762b808 00000000 00000000 nt+0x68218
8078aff8 a762b808 00000000 00000000 00000000 nt+0x679dc
818769dc 00000000 00000000 00000000 00000000 0xa762b808
STACK_COMMAND: kb
FOLLOWUP_IP:
RTL8187Se!PlatformFreeMemory+1b
8913350d ?? ???
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: RTL8187Se!PlatformFreeMemory+1b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: RTL8187Se
IMAGE_NAME: RTL8187Se.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner

на 7100 первое время вылетало вот это

Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16397.x86fre.win7_gdr_staging.090720-1852
Machine Name:
Kernel base = 0x82c1d000 PsLoadedModuleList = 0x82d65810
Debug session time: Mon Aug 24 13:04:57.331 2009 (GMT+4)
System Uptime: 0 days 4:19:49.046
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols



На ровном месте а потом прекратилось хотя ничего такого не удалял.


на 7600 сейчас опять такой же синий экран с этим ntkrnlpa.exe вылетает

дрова от нвидия последние стоят, антивир нод смарт секьюрити.

из за чего это может быть? C&Q у проца отключена.

_StreloK_, у вас проблема в драйвере сетевой карты Realtek

SYMBOL_NAME: RTL8187Se!PlatformFreeMemory+1b

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: RTL8187Se

IMAGE_NAME: RTL8187Se.sys

Какая у вас сетевая карта? Какой драйвер на неё стоит?

Знающие люди расшифруйте плиз!

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Шурик\Documents\091909-34055-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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82c15000 PsLoadedModuleList = 0x82d5d810
Debug session time: Sat Sep 19 16:30:54.350 2009 (GMT+6)
System Uptime: 0 days 4:00:41.067
*********************************************************************
* 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\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {1b005110, 2, 8, 1b005110}

*** WARNING: Unable to verify timestamp for kl1.sys
*** ERROR: Module load completed but symbols could not be loaded for kl1.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!_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 : kl1.sys ( kl1+28cc0 )

Followup: MachineOwner
---------

anarhyst писал:* 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+ *

Так дело не пойдёт... Настройте дебаггер на получение символов онлайн (Post #176355) и повторите анализ. На вскидку могу сказать, что проблема в антивирусе Касперского, а точнее в его драйвере:

anarhyst писал:Probably caused by : kl1.sys ( kl1+28cc0 )

anarhyst,
Для поиска кода ошибки BlueScreen воспользуйтесь лучше программой

BlueScreenView v1.05
Web site: http://www.nirsoft.net

Бэлиан,
хорошая прога

а терь подскажите мне,во всем виноват Касперский секьюрити 2010?

RAZORBLADE, он самый. И не только у вас такая проблема... forums.php?m=posts&p=179884#179884