mati290
Nowy
Liczba postów: 1
|
Problem z BSOD-ami
Witam. Dzisiaj zacząłem doświadczać problemów z BSOD-ami. Występują przy korzystaniu z Firefoxa, włączeniu jakiejkolwiek gry itp. Nie znam się na tym więc liczę na waszą pomoc. Załączam pliki z minidump'a:
http://www.przeklej.pl/plik/110211-11060...35ia628bq4
http://www.przeklej.pl/plik/110211-11216...35ia65p2mv
http://www.przeklej.pl/plik/110211-11653...35ia6ie96u
Z góry dzięki za pomoc.
|
thermalfake
Ostatni Mohikanin
Liczba postów: 13.580
|
RE: Problem z BSOD-ami
Problem z wyrysowaniem okienek w firefoxie i podczas gry przez systemowy sterownik win32k.sys jak i równieź może coś bruździć od strony sterowników karty graficznej - błędne odwołania do pamięci, rywalizacja dostępu do pamięci itp. Być może przeinstalowanie sterowników vga pomoże.
http://windows7forums.com/blue-screen-de...ader.html7
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp6\110211_11653_01_www.przeklej.pl.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03051000 PsLoadedModuleList = 0xfffff800`03296670
Debug session time: Wed Nov 2 14: 08: 42.591 2011 (UTC + 1: 00)
System Uptime: 0 days 0: 25: 44.590
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {3, fffff88008ba2830, fffff88008ba2830, 0}
Probably caused by : Pool_Corruption ( nt!ExDeferredFreePool+a53 )
Followup: Pool_corruption
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 0000000000000003, the pool freelist is corrupt.
Arg2: fffff88008ba2830, the pool entry being checked.
Arg3: fffff88008ba2830, the read back flink freelist value (should be the same as 2).
Arg4: 0000000000000000, the read back blink freelist value (should be the same as 2).
Debugging Details:
------------------
BUGCHECK_STR: 0x19_3
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: explorer.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800031fb4b3 to fffff800030cdc40
STACK_TEXT:
fffff880`0b299b98 fffff800`031fb4b3 : 00000000`00000019 00000000`00000003 fffff880`08ba2830 fffff880`08ba2830 : nt!KeBugCheckEx
fffff880`0b299ba0 fffff960`00116494 : fffff900`00000000 00000000`00000000 00000000`00000000 fffff880`00000000 : nt!ExDeferredFreePool+0xa53
fffff880`0b299c90 fffff960`00116433 : 00000000`00000000 fffff800`030d782b fffff880`0b29a2b0 00000000`00000000 : win32k!AllocThreadBufferWithTag+0x24
fffff880`0b299cc0 fffff960`000eb155 : fffff900`c069c010 fffff800`030d79e2 fffff900`c0750420 00000000`00000000 : win32k!AllocFreeTmpBuffer+0x27
fffff880`0b299cf0 fffff960`000c294e : 00000000`41800000 00000000`00000000 00000000`00000038 fffff880`0b29a2b0 : win32k!ESTROBJ: vInit+0x105
fffff880`0b299d80 fffff960`0029686a : fffff880`00000000 fffff880`00000031 00000000`00000009 00000000`00000000 : win32k!GreExtTextOutWLocked+0xb12
fffff880`0b29a1a0 fffff960`0010d043 : 00000000`03a3fa30 fffff960`00116814 fffff880`00993300 fffff900`00ffffff : win32k!GreBatchTextOut+0x26a
fffff880`0b29a240 fffff800`030ccddc : fffffa80`06fadb60 00000000`00000031 00000000`00000020 00000000`01c74c18 : win32k!NtGdiFlushUserBatch+0x377
fffff880`0b29a4a0 000007fe`ff66108a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceGdiTebAccess+0x25
00000000`02e3ed38 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff66108a
STACK_COMMAND: kb
FOLLOWUP_IP:
nt!ExDeferredFreePool+a53
fffff800`031fb4b3 cc int 3
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!ExDeferredFreePool+a53
FOLLOWUP_NAME: Pool_corruption
IMAGE_NAME: Pool_Corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: Pool_Corruption
FAILURE_BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a53
BUCKET_ID: X64_0x19_3_nt!ExDeferredFreePool+a53
Followup: Pool_corruption
---------
Kod:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C: \Users\user\Desktop\bsody\dmp6\110211_11216_01_www.przeklej.pl.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: symsrv*symsrv.dll*c: \symb*http: //msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03008000 PsLoadedModuleList = 0xfffff800`0324d670
Debug session time: Wed Nov 2 13: 14: 58.228 2011 (UTC + 1: 00)
System Uptime: 0 days 0: 03: 13.243
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 19, {21, fffff900c226b000, 35b0, 0}
Probably caused by : win32k.sys ( win32k!EngFreeMem+21 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 0000000000000021, the data following the pool block being freed is corrupt. Typically this means the consumer (call stack ) has overrun the block.
Arg2: fffff900c226b000, The pool pointer being freed.
Arg3: 00000000000035b0, The number of bytes allocated for the pool block.
Arg4: 0000000000000000, The corrupted value found following the pool block.
Debugging Details:
------------------
BUGCHECK_STR: 0x19_21
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b7100
fffff900c226b000
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800031b29b2 to fffff80003084c40
STACK_TEXT:
fffff880`0bc32768 fffff800`031b29b2 : 00000000`00000019 00000000`00000021 fffff900`c226b000 00000000`000035b0 : nt!KeBugCheckEx
fffff880`0bc32770 fffff960`000f9481 : fffff900`c0696010 fffff900`c0696010 00000000`64667454 fffff900`00000000 : nt!ExDeferredFreePool+0xfaa
fffff880`0bc32820 fffff960`0036e36c : fffff880`0bc32970 00000000`72cb2450 fffffa80`00000060 00000000`00000000 : win32k!EngFreeMem+0x21
fffff880`0bc32850 fffff960`003355a2 : fffff960`0036e2f8 fffff880`0bc32970 fffff900`c0737760 00000000`72cb2450 : win32k!ttfdSemDestroyFont+0x74
fffff880`0bc32880 fffff960`003337de : fffffa80`05dde9b0 fffff880`0bc32980 fffff880`0bc329e0 fffff880`0bc32b58 : win32k!PDEVOBJ: DestroyFont+0xf2
fffff880`0bc328f0 fffff960`00157c13 : fffffa80`05dde9b0 fffff900`c0696010 fffff900`c008a010 fffff960`0015b594 : win32k!RFONTOBJ: vDeleteRFONT+0x4a
fffff880`0bc32960 fffff960`00157643 : fffff900`c0696010 fffff880`0bc32a00 fffff900`c0696010 00000000`00000000 : win32k!RFONTOBJ: bMakeInactiveHelper+0x427
fffff880`0bc329e0 fffff960`001a6725 : fffff880`0bc32b60 fffff880`0bc32b60 00000000`00000000 00000000`00000001 : win32k!RFONTOBJ: vMakeInactive+0xa3
fffff880`0bc32a80 fffff960`001a6984 : fffff880`0bc32b60 fffff900`c1cccdc0 00000000`00000000 fffff900`c23f0ca0 : win32k!XDCOBJ: bCleanDC+0x36d
fffff880`0bc32b40 fffff960`0019f93b : fffff900`c1cccdc0 fffff900`c0581e90 00000000`72cb2450 00000000`0026ec50 : win32k!GreCleanDC+0x34
fffff880`0bc32b80 fffff960`0019f82b : 00000000`11010879 fffff880`0bc32ca0 00000000`fffdb000 00000000`00000000 : win32k!ReleaseCacheDC+0xfb
fffff880`0bc32bc0 fffff960`001b45be : 00000000`00000000 fffff880`00000041 00000000`00000000 00000000`00000000 : win32k!ReleaseDC+0xb
fffff880`0bc32bf0 fffff800`03083ed3 : fffffa80`05ca8a20 fffff880`0bc32ca0 00000000`046409c0 00000000`fffdb001 : win32k!NtUserCallOneParam+0x4e
fffff880`0bc32c20 00000000`72cffdfa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0026e2e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72cffdfa
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!EngFreeMem+21
fffff960`000f9481 4883c420 add rsp,20h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: win32k!EngFreeMem+21
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e658d5a
FAILURE_BUCKET_ID: X64_0x19_21_win32k!EngFreeMem+21
BUCKET_ID: X64_0x19_21_win32k!EngFreeMem+21
Followup: MachineOwner
---------
![[Obrazek: 2089620800_1406976151.png]](http://obrazki.elektroda.pl/2089620800_1406976151.png)
W zamian za pomoc oczekuję poprawnej pisowni. Stop niechlujstwu.
Jak mądrze zadawać pytania? - przejrzyj poradnik na forum.
Nie udzielam porad via PW.
|
Post: #1
