Bluescreen 0x0000008E, aswMon2

[Czarro]

Zainstalowałem sterowniki do karty graficznej ati radeon 9550 i czasem wyłącza się komp i pojawia się Dostępne tylko dla zarejestrowanych użytkowników to co to jest?? dzięki za pomoc

[cosik_ktosik]

Sprawdź ostatni plik DMP. Zrób to wg tej instrukcji Czytanie plików DMP
Podaj raport na forum. Wklej go na Dostępne tylko dla zarejestrowanych użytkowników a tu daj tylko link do niego.

[Czarro]

coś nie mogę wyświetla mi się Dostępne tylko dla zarejestrowanych użytkowników co to jest?

[koleś git]

Musisz wybrać plik .DMP (zrzut pamięci). Domyślnie katalog z mini DMP'ami znajduje się w : C:\Windows\Minidmu .p

[Czarro]

Mini101709-01 BugCheck C5, {0, 2, 1, 8054ba39}
Mini101809-01 BugCheck 1000008E, {c0000005, 8054b487, b87a4818, 0}
Mini101809-02 BugCheck 19, {20, 81ec3600, 81ec3648, a09000e}

-- Dzisiaj, 12:35 --

Kod: Zaznacz cały

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: 8054b487, The address that the exception occurred at
Arg3: b87a4818, 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: aswMon2

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4aaf72cc

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

FAULTING_IP:
nt+74487
8054b487 ??              ???

TRAP_FRAME:  b87a4818 -- (.trap 0xffffffffb87a4818)
Unable to read trap frame at b87a4818

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

LAST_CONTROL_TRANSFER:  from 81ff2050 to 8054b487

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
b87a4888 81ff2050 e20b1000 81ff2074 b87a48a8 nt+0x74487
b87a48cc 8054b59e e1e73008 8054aa87 804fb95e 0x81ff2050
b87a490c b8a6672a e20b1008 00000000 b8a666c3 nt+0x7459e
b87a4a1c b8a6683c 81654e98 81654cc0 b87a4a53 aswMon2+0x672a
b87a4a54 b8a6083c 819e3940 00654cc0 804e37f7 aswMon2+0x683c
b87a4b50 805633ec 81f5c900 00000000 81a14930 aswMon2+0x83c
b87a4bd8 8056750a 00000000 b87a4c18 00000040 nt+0x8c3ec
b87a4c2c 8056fa93 00000000 00000000 a5051001 nt+0x9050a
b87a4ca8 8056fb62 0160fbe4 00110080 0160fb74 nt+0x98a93
b87a4d04 8056fc2a 0160fbe4 00110080 0160fb74 nt+0x98b62
b87a4d44 804de7ec 0160fbe4 00110080 0160fb74 nt+0x98c2a
b87a4d64 7c90eb94 badb0d00 0160fb34 00000000 nt+0x77ec
b87a4d68 badb0d00 0160fb34 00000000 00000000 0x7c90eb94
b87a4d6c 0160fb34 00000000 00000000 00000000 0xbadb0d00
b87a4d70 00000000 00000000 00000000 00000000 0x160fb34


STACK_COMMAND:  kb

FOLLOWUP_IP:
aswMon2+672a
b8a6672a ??              ???

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  aswMon2+672a

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  aswMon2.SYS

BUCKET_ID:  WRONG_SYMBOLS

Followup: MachineOwner

-- Dzisiaj, 12:36 --

Kod: Zaznacz cały

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 81ec3600, The pool entry we were looking for within the page.
Arg3: 81ec3648, The next pool entry.
Arg4: 0a09000e, (reserved)

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

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

Cannot get _POOL_TRACKER_BIG_PAGES type size

BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  81ec3600

CUSTOMER_CRASH_COUNT:  2

DEFAULT_BUCKET_ID:  DRIVER_FAULT

LAST_CONTROL_TRANSFER:  from 00000000 to 8053356e

STACK_TEXT: 
f8994cf4 00000000 00020000 00000000 33cda603 0x8053356e


STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

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

Raporty, logi itp proszę wklejać na strony typu Dostępne tylko dla zarejestrowanych użytkowników zaś w poście podawać tylko link
me@djohnsc

[cosik_ktosik]

aswMon2

To jest Avast, on tu spowodował błąd.

[Czarro]

jak to naprawic?

[me@djohnsc]

Przeinstalować avasta bądź zainstalować innego antywirusa (wcześniej usuwając avasta). Przeinstaluj avasta -> Prawidłowa reinstalacja oprogramowania

Najnowszego avasta pobierz stąd -> avast! Home Edition PL 4.8.1356

Tylko zrób to porządnie tak jak to polecono w poradniku (prawidłowa reinstalacja oprogramowania).

Jeśli reinstalacja nic nie pomoże, użyj innego antywirusa np avirę -> Avira AntiVir Personal - Free Antivirus 9.0.0.408 (dobry antywirus, po angielsku, bezpłatny)




--------------------------------------------
Czarro. Proszę używaj polskich znaków diakrytycznych.
Pozdrawiam me@djohnsc