Bardzo częsty BlueScreen i reset komputera

[cosik_ktosik]

win32k to grafika.
Zobacz sterowniki o nazwie omega.

[luzak25]

Zainstalowałem te sterowniki i wyskoczył znowu taki błąd podczas instalacji Subedita oraz Winampa:

Kod: Zaznacz cały

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


Loading Dump File [C:\WINDOWS\Minidump\Mini041111-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 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Apr 11 12:12:41.968 2011 (GMT+2)
System Uptime: 0 days 1:51:01.549
*********************************************************************
* 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 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 1000000A, {565351ec, 2, 1, 80500204}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for Npfs.SYS
*** ERROR: Module load completed but symbols could not be loaded for Npfs.SYS
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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 : Npfs.SYS ( Npfs+5e09 )

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

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: 565351ec, 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: 80500204, 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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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: Npfs

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  41107b86

WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 565351ec

CURRENT_IRQL:  2

FAULTING_IP:
nt+29204
80500204 55              push    ebp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from 804fd24e to 80500204

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
ad1f7bd4 804fd24e 00000001 00000000 00000001 nt+0x29204
ad1f7be8 804fa744 84ecbfa8 84ecbf68 00000000 nt+0x2624e
ad1f7c08 804f0498 84ecbfa8 85ac20e0 00000000 nt+0x23744
ad1f7c3c eef22e09 8542b700 8620fda0 8658b318 nt+0x19498
ad1f7c60 804eddf9 8621c200 8658b318 806d02d0 Npfs+0x5e09
ad1f7c84 805716b8 8621c200 8658b318 8629a028 nt+0x16df9
ad1f7d38 8053c808 000000a4 00000000 00000000 nt+0x9a6b8
ad1f7d64 7c90eb94 badb0d00 0106fd38 6417114f nt+0x65808
ad1f7d68 badb0d00 0106fd38 6417114f 872026be 0x7c90eb94
ad1f7d6c 0106fd38 6417114f 872026be 00000000 0xbadb0d00
ad1f7d70 6417114f 872026be 00000000 00000000 0x106fd38
ad1f7d74 872026be 00000000 00000000 00000000 0x6417114f
ad1f7d78 00000000 00000000 00000000 00000000 0x872026be


STACK_COMMAND:  kb

FOLLOWUP_IP:
Npfs+5e09
eef22e09 ??              ???

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  Npfs+5e09

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  Npfs.SYS

BUCKET_ID:  WRONG_SYMBOLS

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



Komputer wcześniej chodził ok. godzinę nic na nim nie robiłem ale się nie wyłączał.

[XMan]

Zainstalowałeś prawidłowo Chipset ?
Jakie masz kodeki ?
Sprawdź jeszcze inne sterowniki do karty dźwiękowej.
/mogą być starsze/.
Nie pomoże to wrzuć logi wg. tego regulaminu :
bezpieczenstwo/nowy-regulamin-dzialu-bezpiecze-stwo-t1887.html

[luzak25]

Kodeków nie instalowałem, właśnie zainstalowałem sterowniki do karty dźwiękowej nowsze bo wcześniej miałem starsze.

Zainstalowałeś prawidłowo Chipset ?

Tzn. jak prawidłowo, jak mogę to sprawdzić? Instalowałem wszystkie potrzebne sterowniki jakie miałem.

[XMan]

Zainstaluj np. kodeki Dostępne tylko dla zarejestrowanych użytkowników
lub FFDShow 23.03.2011 + Real Alternative Lite.

W Menedżerze urządzeń nie ma żółtych wykrzykników lub znaków zapytania ?

[luzak25]

OK zaraz zainstaluje. W menadżerze urządzeń nic takiego nie mam.

-- 11 kwi 2011, 17:16 --

Wykonałem wszystkie porady ze wcześniejszych postów ale niestety problem nadal występuje więc jak mnie proszono umieszczam logi oraz raport z ostatniego błędu. Logów z programu DDS nie dam rady umieścić ponieważ podczas skanowania wyskakuje Bluescreen i komp się restartuje. Z tego co zauważyłem problem występuje najczęściej podczas instalowania programów, jeśli zostawię komputer włączony to raczej wtedy nic złego się nie dzieje ale także bardzo często komputer się restartował podczas instalowania sterowników do karty graficznej więc może z nią jest jakiś problem.

Kod: Zaznacz cały

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


Loading Dump File [C:\WINDOWS\Minidump\Mini041111-03.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 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Mon Apr 11 16:39:04.078 2011 (GMT+2)
System Uptime: 0 days 0:03:38.645
*********************************************************************
* 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 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
.........
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 805d5d43, aff988e0, 0}

***** 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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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 : win32k.sys ( win32k+4456e )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 805d5d43, The address that the exception occurred at
Arg3: aff988e0, Trap Frame
Arg4: 00000000

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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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: win32k

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  41107f7a

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo

FAULTING_IP:
nt+fed43
805d5d43 c1e803          shr     eax,3

TRAP_FRAME:  aff988e0 -- (.trap 0xffffffffaff988e0)
ErrCode = 00000002
eax=00000008 ebx=bbe60000 ecx=00000008 edx=00000008 esi=bbe9a450 edi=bbe601b8
eip=805d5d43 esp=aff98954 ebp=aff98b08 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
nt+0xfed43:
805d5d43 c1e803          shr     eax,3
Resetting default scope

CUSTOMER_CRASH_COUNT:  3

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

LAST_CONTROL_TRANSFER:  from bf84456e to 805d5d43

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
aff98b08 bf84456e bbe60000 00000009 0000005c nt+0xfed43
aff98b1c bf843ff2 86327238 0000005c 00002000 win32k+0x4456e
aff98b80 bf8e5e7b aff98b9c 0000029d 00000081 win32k+0x43ff2
aff98bd0 bf8482c9 00000000 852ba020 00000000 win32k+0xe5e7b
aff98cc0 bf80ef2c 852ba020 00000000 00000000 win32k+0x482c9
aff98cd4 bf80f032 852ba020 00000000 00000000 win32k+0xef2c
aff98cf0 805c113b 852ba020 00000000 80552190 win32k+0xf032
aff98d54 8053c50e 000010dc 0013f460 0013f464 nt+0xea13b
aff98d58 00000000 0013f460 0013f464 7c90eb94 nt+0x6550e


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k+4456e
bf84456e ??              ???

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  win32k+4456e

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  win32k.sys

BUCKET_ID:  WRONG_SYMBOLS

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



Dostępne tylko dla zarejestrowanych użytkowników
Dostępne tylko dla zarejestrowanych użytkowników
Dostępne tylko dla zarejestrowanych użytkowników
Dostępne tylko dla zarejestrowanych użytkowników

[djkamil09061991]

Teraz dalej jest błąd sterownika od grafiki, czy próbujesz instalowac różne wersję sterowników???? Przed instalacją nowych odinstalowywujesz stare?

[luzak25]

Zawsze przed instalacja usuwałem stare sterowniki, instalowałem chyba 3 różne wersje sterowników i za każdym razem błąd występowała a poza tym kilka razy komp się restartował i musiałem zaczynać instalację od nowa. Teraz mam zainstalowane sterowniki omega ale miałem też problem z instalacją Windowsa ponieważ w czasie instalacji wyskakiwał mi Bluescreen i nie mogłem dokończyć instalacji a żadnych sterowników jeszcze nie miałem zainstalowanych a nawet Windows nie był do końca zainstalowany. Dopiero jak wziąłem inną wersje Windowsa to udało mi się zainstalować.

-- 15 kwi 2011, 15:01 --

Odświeżam temat ponieważ odinstalowałem zupełnie sterowniki od grafiki i komputer przestał się resetować. Może trzeba by było wymienić kartę graficzną bo ona robi jakiś problem?

[djkamil09061991]

Może trzeba by było wymienić kartę graficzną bo ona robi jakiś problem?

Ja bym na twoim miejscu próbował wielu sterowników od grafiki, sam miałem podobny problem i wiele wersji sterowników testowałem aż wkońcu trafiłem na stabilne, tak więc popatrz inne wersje

[luzak25]

Odświeżam temat.

Ja bym na twoim miejscu próbował wielu sterowników od grafiki, sam miałem podobny problem i wiele wersji sterowników testowałem aż wkońcu trafiłem na stabilne, tak więc popatrz inne wersje

Wypróbowałem kilkanaście i nic to nie dało. Odinstalowałem nawet całkiem sterowniki od grafiki i długi czas nie było Bluescreenow ale ostatnio znów się zaczęły pokazywać. Wklejam raport z błedami.

Kod: Zaznacz cały

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


Loading Dump File [C:\WINDOWS\Minidump\Mini081711-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 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed Aug 17 16:27:00.625 2011 (GMT+2)
System Uptime: 0 days 0:22:27.194
*********************************************************************
* 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 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
.........
Unable to load image win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf831dd4, f464eef0, 0}

***** 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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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 : win32k.sys ( win32k+31dd4 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: bf831dd4, The address that the exception occurred at
Arg3: f464eef0, Trap Frame
Arg4: 00000000

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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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: win32k

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  41107f7a

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instrukcja spod "0x%08lx" odwo

FAULTING_IP:
win32k+31dd4
bf831dd4 66837b3000      cmp     word ptr [ebx+30h],0

TRAP_FRAME:  f464eef0 -- (.trap 0xfffffffff464eef0)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=fffffff0 edx=bf831dba esi=f464f3b4 edi=00000000
eip=bf831dd4 esp=f464ef64 ebp=f464f164 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010246
win32k+0x31dd4:
bf831dd4 66837b3000      cmp     word ptr [ebx+30h],0     ds:0023:00000030=????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

LAST_CONTROL_TRANSFER:  from bf853e90 to bf831dd4

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
f464f164 bf853e90 e301a010 00000000 f464f980 win32k+0x31dd4
f464f810 bf81263e e301a010 f464f86c e11ae008 win32k+0x53e90
f464fa98 bf813b36 f464fd38 e3045e9c e3045ef8 win32k+0x1263e
f464fc00 bf80dda0 f464fd38 7ffdc1dc 00000060 win32k+0x13b36
f464fd54 8053c7da 00000091 00ebfb20 00ebfb40 win32k+0xdda0
f464fd64 7c90eb94 badb0d00 00ebfb20 01304000 nt+0x657da
f464fd68 badb0d00 00ebfb20 01304000 e0c10842 0x7c90eb94
f464fd6c 00ebfb20 01304000 e0c10842 00000000 0xbadb0d00
f464fd70 01304000 e0c10842 00000000 00000000 0xebfb20
f464fd74 e0c10842 00000000 00000000 00000000 0x1304000
f464fd78 00000000 00000000 00000000 00000000 0xe0c10842


STACK_COMMAND:  kb

FOLLOWUP_IP:
win32k+31dd4
bf831dd4 66837b3000      cmp     word ptr [ebx+30h],0

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  win32k+31dd4

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  win32k.sys

BUCKET_ID:  WRONG_SYMBOLS

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



Kod: Zaznacz cały

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


Loading Dump File [C:\WINDOWS\Minidump\Mini081711-02.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 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 XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed Aug 17 16:59:49.656 2011 (GMT+2)
System Uptime: 0 days 0:04:15.220
*********************************************************************
* 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 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 1000000A, {ab34245c, 2, 0, 8050de80}

***** 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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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 : ntoskrnl.exe ( nt+36e80 )

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

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: ab34245c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, 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: 8050de80, 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                                     ***
***                                                                   ***
*************************************************************************
*********************************************************************
* 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: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  41107b0c

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
 ab34245c

CURRENT_IRQL:  2

FAULTING_IP:
nt+36e80
8050de80 8b460c          mov     eax,dword ptr [esi+0Ch]

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xA

LAST_CONTROL_TRANSFER:  from 805a4197 to 8050de80

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
ee0c8c08 805a4197 04781201 85c4a020 007ffff8 nt+0x36e80
ee0c8c28 8050f841 85c4a020 85c4a158 85c4a020 nt+0xcd197
ee0c8c60 805c7230 00c4a020 85d228e0 85d22b28 nt+0x38841
ee0c8d08 805c73f2 00000001 85d228e0 00000000 nt+0xf0230
ee0c8d28 805c75cd 85d228e0 00000001 ee0c8d64 nt+0xf03f2
ee0c8d54 8053c808 00000000 00000001 0110bdc0 nt+0xf05cd
ee0c8d64 7c90eb94 badb0d00 0110bdb8 ee0c8d98 nt+0x65808
ee0c8d68 badb0d00 0110bdb8 ee0c8d98 ee0c8dcc 0x7c90eb94
ee0c8d6c 0110bdb8 ee0c8d98 ee0c8dcc 00000000 0xbadb0d00
ee0c8d70 ee0c8d98 ee0c8dcc 00000000 00000000 0x110bdb8
ee0c8d74 ee0c8dcc 00000000 00000000 00000000 0xee0c8d98
ee0c8d98 00000000 7c90eb94 00001000 046d0000 0xee0c8dcc


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt+36e80
8050de80 8b460c          mov     eax,dword ptr [esi+0Ch]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt+36e80

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  ntoskrnl.exe

BUCKET_ID:  WRONG_SYMBOLS

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



Myślałem żeby wymienic kartę graficzna ale teraz nie mam już pojęcia co robić

[XMan]

IRQL_NOT_LESS_OR_EQUAL

- wszędzie to widzę od początku do końca
Moim zdaniem tj. problem ze sterownikami do karty graficznej lub innymi.
Często w przeszłości tak miałem - 99% były to problemy ze sterownikami do karty graficznej.
Na jaki mają być w końcu system ?

Zainstaluj Aida32 3.94.2
Otwórz program --> Komputer --> Podsumowanie --> spisz/podaj informacje z pozycji:
--> Nazwa płyty głównej.
--> Mikroukład płyty głównej.
--> Karta graficzna (Ekran --> Karta wideo).

kliknij aby powiększyć :
Dostępne tylko dla zarejestrowanych użytkowników

Nie wykaże odpowiednich danych Aida32 to sprawdź za pomocą Dostępne tylko dla zarejestrowanych użytkowników.

Sterowniki do karty graficznej Radeon 9550 mogę podać tylko mi chodzi o płytę główną oraz mikroukład płyty głównej.

[greh]

IRQL_NOT_LESS_OR_EQUAL

A nie ma czasem konfliktu przerwań pomiędzy poszczególnymi urządzeniami kompa?

[luzak25]

Windows XP Professional Service Pack 2 32 Bit
Dostępne tylko dla zarejestrowanych użytkowników

Uploaded with Dostępne tylko dla zarejestrowanych użytkowników
Dostępne tylko dla zarejestrowanych użytkowników

Uploaded with Dostępne tylko dla zarejestrowanych użytkowników
Dostępne tylko dla zarejestrowanych użytkowników

Uploaded with Dostępne tylko dla zarejestrowanych użytkowników

-- 30 sie 2011, 10:19 --

Nikt się już nie odezwie?

[cosik_ktosik]

Zainstaluj to: http://www.hotfix.pl/infusions/pro_down ... r-p201.htm
Potem najnowsze sterowniki do grafiki

[luzak25]

Zainstaluj to: http://www.hotfix.pl/infusions/pro_down ... r-p201.htm
Potem najnowsze sterowniki do grafiki

Po instalacji bez zmian.