Odpowiedz

Kernel-Power

 
MoR4oR
Wdrażany
Liczba postów: 11
Post: #1

Kernel-Power


Witam, od niedawna mam zwiechy z komputerem poprzez niejaki proces systemowy "Kernel-Power", temperatury podzespołów są w normie... Opis błędu :
Kod:
- <Event xmlns="http: //schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
  <EventID>41</EventID>
  <Version>2</Version>
  <Level>1</Level>
  <Task>63</Task>
  <Opcode>0</Opcode>
  <Keywords>0x8000000000000002</Keywords>
  <TimeCreated SystemTime="2011-05-02T07: 17: 32.147200000Z" />
  <EventRecordID>37620</EventRecordID>
  <Correlation />
  <Execution ProcessID="4" ThreadID="8" />
  <Channel>System</Channel>
  <Computer>Krzychu</Computer>
  <Security UserID="S-1-5-18" />
  </System>
- <EventData>
  <Data Name="BugcheckCode">0</Data>
  <Data Name="BugcheckParameter1">0x0</Data>
  <Data Name="BugcheckParameter2">0x0</Data>
  <Data Name="BugcheckParameter3">0x0</Data>
  <Data Name="BugcheckParameter4">0x0</Data>
  <Data Name="SleepInProgress">false</Data>
  <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
  </Event>

Odczytałem również pliki .dmp z których wynika że błąd jest związany z procesem "ctaud2k"


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


Loading Dump File [C: \Windows\Minidump\043011-12901-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 Personal
Built by:  7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x82e3c000 PsLoadedModuleList = 0x82f84810
Debug session time:  Sat Apr 30 08: 55: 46.778 2011 (GMT+2)
System Uptime:  0 days 0: 00: 12.230
*********************************************************************
* 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
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {0, 2, 1, 82ea32af}

*** WARNING:  Unable to verify timestamp for mssmbios.sys
*** ERROR:  Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING:  Unable to verify timestamp for ctaud2k.sys
*** ERROR:  Module load completed but symbols could not be loaded for ctaud2k.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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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 :  ctaud2k.sys ( ctaud2k+55556 )

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

0:  kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1:  00000000, memory referenced
Arg2:  00000002, IRQL
Arg3:  00000001, bitfield :
    bit 0 :  value 0 = read operation, 1 = write operation
    bit 3 :  value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4:  82ea32af, address which referenced memory

Debugging Details:
------------------

***** 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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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+                                    *
*********************************************************************

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.

MODULE_NAME:  ctaud2k

FAULTING_MODULE:  82e3c000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:   4ba208ab

WRITE_ADDRESS:  unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000000

CURRENT_IRQL:   0

FAULTING_IP:  
nt+672af
82ea32af 8939            mov     dword ptr [ecx],edi

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0xA

LAST_CONTROL_TRANSFER:   from 82ea32af to 82e827eb

STACK_TEXT:  
WARNING:  Stack unwind information not available. Following frames may be wrong.
8e7279ac 82ea32af badb0d00 00000000 82ed5b11 nt+0x467eb
8e727a80 82e67d59 86c2cf60 00000022 00000000 nt+0x672af
8e727aa8 82ed9b75 00000000 86c2cd78 94c801cb nt+0x2bd59
8e727ac8 94c80556 86620008 86620008 866200c0 nt+0x9db75
8e727ae0 94c7feae 86c2cd78 86620008 8e727b08 ctaud2k+0x55556
8e727af0 82e784bc 86c2cd78 86620008 8e727b8c ctaud2k+0x54eae
8e727b08 83018edf 85725690 85726758 85725690 nt+0x3c4bc
8e727b38 82fefb3d 85725690 00000000 85726758 nt+0x1dcedf
8e727b90 82e50c3a 85725690 00000002 9161f928 nt+0x1b3b3d
8e727bbc 82fef951 0000000a 9161f928 00000000 nt+0x14c3a
8e727bd0 82fef8b7 00000002 0000000a 00000000 nt+0x1b3951
8e727c04 82fef238 85725690 9161f928 00000002 nt+0x1b38b7
8e727cc4 82ff1210 8e727cf4 00000000 8d5805a0 nt+0x1b3238
8e727cdc 82ff2d58 00000000 86d01638 8576a020 nt+0x1b5210
8e727d00 82ea9f2b 86d01638 00000000 8576a020 nt+0x1b6d58
8e727d50 8304a66d 00000001 a3cbc520 00000000 nt+0x6df2b
8e727d90 82efc0d9 82ea9e1e 00000001 00000000 nt+0x20e66d
00000000 00000000 00000000 00000000 00000000 nt+0xc00d9


STACK_COMMAND:   kb

FOLLOWUP_IP:  
ctaud2k+55556
94c80556 ?              ?

SYMBOL_STACK_INDEX:   4

SYMBOL_NAME:   ctaud2k+55556

FOLLOWUP_NAME:   MachineOwner

IMAGE_NAME:   ctaud2k.sys

BUCKET_ID:   WRONG_SYMBOLS

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

0:  kd> lmvm ctaud2k
start    end        module name
94c2b000 94caa600   ctaud2k  T (no symbols)          
    Loaded symbol image file:  ctaud2k.sys
    Image path:  \SystemRoot\system32\drivers\ctaud2k.sys
    Image name:  ctaud2k.sys
    Timestamp:         Thu Mar 18 12: 04: 11 2010 (4BA208AB)
    CheckSum:          00090F31
    ImageSize:         0007F600
    Translations:      0000.04b0 0000.04e4 0409.04b0 0409.04e4
0:  kd> lmvm ctaud2k
start    end        module name
94c2b000 94caa600   ctaud2k  T (no symbols)          
    Loaded symbol image file:  ctaud2k.sys
    Image path:  \SystemRoot\system32\drivers\ctaud2k.sys
    Image name:  ctaud2k.sys
    Timestamp:         Thu Mar 18 12: 04: 11 2010 (4BA208AB)
    CheckSum:          00090F31
    ImageSize:         0007F600
    Translations:      0000.04b0 0000.04e4 0409.04b0 0409.04e4
(Ten post był ostatnio modyfikowany: 02.05.2011 11:14 przez MoR4oR.)

02.05.2011 08:23

Znajdź wszystkie posty użytkownika
Odpowiedz cytując ten post
siódmy
Młodszy user systemu

Liczba postów: 74
Post: #2

RE: Kernel-Power


Wskocz na Hotfix tam Ci pomogą.

04.05.2011 13:28

Znajdź wszystkie posty użytkownika
Odpowiedz cytując ten post
Odpowiedz

« Starszy wątek | Nowszy wątek »

Temat został oceniony na 0 w skali 1-5 gwiazdek.
Zebrano 0 głosów.