Windows 7 Forum: konfiguracja, optymalizacja, porady, gadżety •

Witam.
Od ponad tygodnia posiadam laptopa Asus K52J i już od 2-3 dni po zakupie pokazują mi się BSOD podczas normalnego korzystania z laptopa, jak i przy grach. Szczegóły BSOD:

Kod:

Podpis problemu: 

  Nazwa zdarzenia problemu:     BlueScreen

  Wersja systemu operacyjnego:     6.1.7600.2.0.0.256.48

  Identyfikator ustawień regionalnych:     1045

Dodatkowe informacje o problemie: 

  BCCode:     3b

  BCP1:     00000000C0000005

  BCP2:     FFFFF960001377C0

  BCP3:     FFFFF8800B961060

  BCP4:     0000000000000000

  OS Version:     6_1_7600

  Service Pack:     0_0

  Product:     256_1

Pliki pomagające opisać problem: 

  C: \Windows\Minidump\081411-21028-01.dmp

  C: \Users\Bartek\AppData\Local\Temp\WER-44725-0.sysdata.xml

Przeczytaj w trybie online nasze zasady zachowania poufności informacji: 

  http: //go.microsoft.com/fwlink/?linkid=104288&clcid=0x0415

Jeśli zasady zachowania poufności informacji w trybie online nie są dostępne, przeczytaj nasze zasady zachowania poufności informacji w trybie offline: 

  C: \Windows\system32\pl-PL\erofflps.txt

Tak samo różne programy mi się zamykają od tak(np. mozilla firefox)
Moje parametry:

Procesor (rodzaj) Intel® Pentium® Dual-Core P6200 (dwurdzeniowy 2.13 GHz, 3M Cache)
System operacyjny Brak systemu operacyjnego
Pamięć RAM 5 GB
Pamięć (technologia) SO-DIMM DDR3
Dysk twardy (pojemność) 640 GB
Karta graficzna (producent) AMD
Karta graficzna (model) Mobility Radeon HD 6370
Karta graficzna (pamięć) 512 MB
Bios version K52J.206

Tutaj macie, wszystkie pliki .dmp
http://www.speedyshare.com/files/30015067/Minidump.rar
Dziennie mam 3-4 BSOD, jeden próbowałem otworzyć programem WinDbg ale nic z tego nie rozumiem(prawdopodobnie źle skonfigurowany program): http://wklej.to/sc3zg

Sprawdzałem Pamieć ram programem memtest86+ 4.2.0 i nic nie wykrył..

Przeskanuj antywirusem.
Sprawdź czy sterowniki są aktualne do grafiki i płyty głównej (użyj do tego SlimDrivers - albo DriverMax)

Skanowałem Antywirusem nic nie wykazało, co do aktualizacji sterowników musiałem zaktualizować 7. Na razie pokazuje mi że niema żadnych sterowników do aktualizacji, poczekajmy co będzie z BSOD.

@EDIT.
Aktualizacja sterowników nic nie pomogła dzisiaj znów sie sie pokazał BSOD...

I kolejny BSOD tym razem z numerem 0x0000004E. wiem że trzeba uaktualnić sterownik, ale nie wiem jaki? No wiec moje pytanie jak mam sprawdzić który sterownik to wywołał. Nie mam żadnych programów antywirusowych. Prosze o pilną pomoc.

Spróbuj jeszcze przeczyścić dyski i rejestr programem CCleaner.
Sterowniki takie jak do płyty głównej, chipsetu, etc. pobierz ze strony producenta płyty głównej. Może te co masz są jakieś lewe albo uszkodzone.

Po przejrzeniu bsodów najwięcej jest błędów 0x50;0x19;0x24;0xA;0x1A.
Najczęściej są problemy ze sterownikami grafiki, przeglądarki, aqq, i kilka plików systemowych.
Radzę zrobić backup, postawić system od nowa. Sterowniki tylko udostępnione ze strony producenta, żadne referencyjne, soft av/is, jakaś gierka, kodeki odtwarzacz i to wszystko. Na razie minimum softu do testowania. Gdyby nie pomogło, podmienić pamięci ram - memtest nie zawsze jest w 100% pewny niestety.

Kod:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced.  This cannot be protected by try-except,

it must be protected by a Probe.  Typically the address is just plain bad or it

is pointing at freed memory.

Arguments: 

Arg1:  fffff8a00f9494cc, memory referenced.

Arg2:  0000000000000000, value 0 = read operation, 1 = write operation.

Arg3:  fffff88003e4ce88, If non-zero, the instruction address which referenced the bad memory

    address.

Arg4:  0000000000000002, (reserved)

Debugging Details: 

------------------

Could not read faulting driver name

READ_ADDRESS:  GetPointerFromAddress:  unable to read from fffff80002ef10e0

 fffff8a00f9494cc 

FAULTING_IP:  

atikmdag!DisplayManager: DPPE_SetPowerSavingMode+f0

fffff880`03e4ce88 80784c00        cmp     byte ptr [rax+4Ch],0

MM_INTERNAL_CODE:   2

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0x50

PROCESS_NAME:   dwm.exe

CURRENT_IRQL:   0

TRAP_FRAME:   fffff880076c52c0 -- (.trap 0xfffff880076c52c0)

NOTE:  The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffff8a00f949480 rbx=0000000000000000 rcx=fffff8a00793a238

rdx=000000000000000b rsi=0000000000000000 rdi=0000000000000000

rip=fffff88003e4ce88 rsp=fffff880076c5458 rbp=0000000000000000

 r8=0000000000000000  r9=0000000000000000 r10=000000000000003f

r11=0000000000000002 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei ng nz na pe nc

atikmdag!DisplayManager: DPPE_SetPowerSavingMode+0xf0: 

fffff880`03e4ce88 80784c00        cmp     byte ptr [rax+4Ch],0 ds: 6600: fffff8a0`0f9494cc=?

Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff80002d387d2 to fffff80002cb95c0

STACK_TEXT:   

fffff880`076c5158 fffff800`02d387d2 :  00000000`00000050 fffff8a0`0f9494cc 00000000`00000000 fffff880`076c52c0 :  nt!KeBugCheckEx

fffff880`076c5160 fffff800`02cb76ae :  00000000`00000000 00000000`0000000b 00000000`00000000 00000000`00000000 :  nt! ? : FNODOBFM: `string'+0x40d80

fffff880`076c52c0 fffff880`03e4ce88 :  fffff880`041a70d3 fffffa80`0ba5a000 00000000`0000001d 00000000`01e30000 :  nt!KiPageFault+0x16e

fffff880`076c5458 fffff880`041a70d3 :  fffffa80`0ba5a000 00000000`0000001d 00000000`01e30000 00000000`00000077 :  atikmdag!DisplayManager: DPPE_SetPowerSavingMode+0xf0

fffff880`076c5460 fffffa80`0ba5a000 :  00000000`0000001d 00000000`01e30000 00000000`00000077 fffff880`076c57c0 :  atikmdag!RS400_IRQSources+0x83

fffff880`076c5468 00000000`0000001d :  00000000`01e30000 00000000`00000077 fffff880`076c57c0 fffffa80`05ab2020 :  0xfffffa80`0ba5a000

fffff880`076c5470 00000000`01e30000 :  00000000`00000077 fffff880`076c57c0 fffffa80`05ab2020 fffff880`04293550 :  0x1d

fffff880`076c5478 00000000`00000077 :  fffff880`076c57c0 fffffa80`05ab2020 fffff880`04293550 fffff880`041a6620 :  0x1e30000

fffff880`076c5480 fffff880`076c57c0 :  fffffa80`05ab2020 fffff880`04293550 fffff880`041a6620 fffffa80`0be6a010 :  0x77

fffff880`076c5488 fffffa80`05ab2020 :  fffff880`04293550 fffff880`041a6620 fffffa80`0be6a010 fffffa80`05a8f220 :  0xfffff880`076c57c0

fffff880`076c5490 fffff880`04293550 :  fffff880`041a6620 fffffa80`0be6a010 fffffa80`05a8f220 00000000`00000000 :  0xfffffa80`05ab2020

fffff880`076c5498 fffff880`041a6620 :  fffffa80`0be6a010 fffffa80`05a8f220 00000000`00000000 00000000`00000000 :  atikmdag!_NULL_IMPORT_DESCRIPTOR <PERF> (atikmdag+0x484550)

fffff880`076c54a0 fffffa80`0be6a010 :  fffffa80`05a8f220 00000000`00000000 00000000`00000000 00000000`00000300 :  atikmdag!R200_IRQSources+0xa8

fffff880`076c54a8 fffffa80`05a8f220 :  00000000`00000000 00000000`00000000 00000000`00000300 fffff8a0`00000020 :  0xfffffa80`0be6a010

fffff880`076c54b0 00000000`00000000 :  00000000`00000000 00000000`00000300 fffff8a0`00000020 0000309f`0000000b :  0xfffffa80`05a8f220

STACK_COMMAND:   kb

FOLLOWUP_IP:  

atikmdag!DisplayManager: DPPE_SetPowerSavingMode+f0

fffff880`03e4ce88 80784c00        cmp     byte ptr [rax+4Ch],0

SYMBOL_STACK_INDEX:   3

SYMBOL_NAME:   atikmdag!DisplayManager: DPPE_SetPowerSavingMode+f0

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  atikmdag

IMAGE_NAME:   atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   4c63518d

FAILURE_BUCKET_ID:   X64_0x50_atikmdag!DisplayManager: DPPE_SetPowerSavingMode+f0

BUCKET_ID:   X64_0x50_atikmdag!DisplayManager: DPPE_SetPowerSavingMode+f0

Followup:  MachineOwner

---------

Kod:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {3452, 7fffffdd000, fffff70001085468, 9ce00000aa123c66}

Probably caused by :  ntkrnlmp.exe ( nt! ? : FNODOBFM: `string'+339a3 )

Followup:  MachineOwner

---------

1:  kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

MEMORY_MANAGEMENT (1a)

    # Any other values for parameter 1 must be individually examined.

Arguments: 

Arg1:  0000000000003452, The subtype of the bugcheck.

Arg2:  000007fffffdd000

Arg3:  fffff70001085468

Arg4:  9ce00000aa123c66

Debugging Details: 

------------------

BUGCHECK_STR:   0x1a_3452

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

PROCESS_NAME:   ETDCtrl.exe

CURRENT_IRQL:   0

LAST_CONTROL_TRANSFER:   from fffff80002cf0fd3 to fffff80002c7d5c0

STACK_TEXT:   

fffff880`06f41068 fffff800`02cf0fd3 :  00000000`0000001a 00000000`00003452 000007ff`fffdd000 fffff700`01085468 :  nt!KeBugCheckEx

fffff880`06f41070 fffff800`02c5060e :  fffffa80`0cd8a060 fffffa80`00000000 fffff8a0`00000289 fffff880`00000000 :  nt! ? : FNODOBFM: `string'+0x339a3

fffff880`06f41920 fffff800`02f5fa8b :  fffff8a0`0e35f060 fffff880`06f41c20 00000000`00000000 fffffa80`0ca6d060 :  nt!MmCleanProcessAddressSpace+0x96

fffff880`06f41970 fffff800`02f38131 :  00000000`c0000005 fffff8a0`0c5ffd01 000007ff`fffa2000 fffffa80`0cb84060 :  nt!PspExitThread+0x92f

fffff880`06f41a30 fffff800`02c5a11b :  fffffa80`0c4562a0 fffffa80`05988f50 00000000`00000000 00000000`00000000 :  nt!PsExitSpecialApc+0x1d

fffff880`06f41a60 fffff800`02c5a560 :  00000000`77365298 fffff880`06f41ae0 fffff800`02f381b8 00000000`00000001 :  nt!KiDeliverApc+0x2eb

fffff880`06f41ae0 fffff800`02c7c8b7 :  fffffa80`0ca6d060 00000000`77365270 00000000`000000c0 fffffa80`07e83240 :  nt!KiInitiateUserApc+0x70

fffff880`06f41c20 00000000`772b0fba :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceExit+0x9c

00000000`03eff7f8 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  0x772b0fba

STACK_COMMAND:   kb

FOLLOWUP_IP:  

nt! ? : FNODOBFM: `string'+339a3

fffff800`02cf0fd3 cc              int     3

SYMBOL_STACK_INDEX:   1

SYMBOL_NAME:   nt! ? : FNODOBFM: `string'+339a3

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nt

IMAGE_NAME:   ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:   4e02aa44

FAILURE_BUCKET_ID:   X64_0x1a_3452_nt!_??_: FNODOBFM: _string_+339a3

BUCKET_ID:   X64_0x1a_3452_nt!_??_: FNODOBFM: _string_+339a3

Followup:  MachineOwner

---------

Kod:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, b9d61, 0, ac461}

Probably caused by :  memory_corruption ( nt!MiBadShareCount+4c )

Followup:  MachineOwner

---------

1:  kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

PFN_LIST_CORRUPT (4e)

Typically caused by drivers passing bad memory descriptor lists (ie:  calling

MmUnlockPages twice with the same list, etc).  If a kernel debugger is

available get the stack trace.

Arguments: 

Arg1:  0000000000000099, A PTE or PFN is corrupt

Arg2:  00000000000b9d61, page frame number

Arg3:  0000000000000000, current page state

Arg4:  00000000000ac461, 0

Debugging Details: 

------------------

BUGCHECK_STR:   0x4E_99

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

PROCESS_NAME:   filezilla.exe

CURRENT_IRQL:   2

LAST_CONTROL_TRANSFER:   from fffff80002d5f13c to fffff80002ccf5c0

STACK_TEXT:   

fffff880`0ba2bf98 fffff800`02d5f13c :  00000000`0000004e 00000000`00000099 00000000`000b9d61 00000000`00000000 :  nt!KeBugCheckEx

fffff880`0ba2bfa0 fffff800`02d41957 :  00000000`00000000 fffff680`00003f28 25b00000`94c08005 00000000`00000001 :  nt!MiBadShareCount+0x4c

fffff880`0ba2bfe0 fffff800`02ca3bb3 :  fffffa80`0c8b0b30 fffff700`000012f3 0000007f`fffffff8 fffff8a0`02adaf70 :  nt! ? : FNODOBFM: `string'+0x321fe

fffff880`0ba2c070 fffff800`02ca260e :  fffffa80`0c8b0b30 fffffa80`00000008 fffff880`00000559 fffff800`00000000 :  nt!MiDeleteAddressesInWorkingSet+0x307

fffff880`0ba2c920 fffff800`02fb1a8b :  fffff8a0`0fab4060 fffff880`0ba2cc20 00000000`00000000 fffffa80`07f30060 :  nt!MmCleanProcessAddressSpace+0x96

fffff880`0ba2c970 fffff800`02f8a131 :  00000000`c0000096 fffffa80`0567c601 00000000`7efd5000 fffffa80`05b43930 :  nt!PspExitThread+0x92f

fffff880`0ba2ca30 fffff800`02cac11b :  00000000`7efd5000 fffffa80`052fe2b0 00000000`00000000 00000000`00000000 :  nt!PsExitSpecialApc+0x1d

fffff880`0ba2ca60 fffff800`02cac560 :  00000000`0421fedc fffff880`0ba2cae0 fffff800`02f8a1b8 00000000`00000001 :  nt!KiDeliverApc+0x2eb

fffff880`0ba2cae0 fffff800`02cce8b7 :  fffffa80`07f30060 00000000`7efd5000 00000000`000000c0 00000000`7efd5000 :  nt!KiInitiateUserApc+0x70

fffff880`0ba2cc20 00000000`77600fba :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceExit+0x9c

00000000`02aae7e8 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  0x77600fba

STACK_COMMAND:   kb

FOLLOWUP_IP:  

nt!MiBadShareCount+4c

fffff800`02d5f13c cc              int     3

SYMBOL_STACK_INDEX:   1

SYMBOL_NAME:   nt!MiBadShareCount+4c

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nt

DEBUG_FLR_IMAGE_TIMESTAMP:   4e02aa44

IMAGE_NAME:   memory_corruption

FAILURE_BUCKET_ID:   X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:   X64_0x4E_99_nt!MiBadShareCount+4c

Followup:  MachineOwner

---------

Kod:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a00fd1d2c8, 0, fffff880049ce135, 2}

Could not read faulting driver name

Probably caused by :  dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL: ReferenceDmaBuffer+1e5 )

Followup:  MachineOwner

---------

1:  kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)

Invalid system memory was referenced.  This cannot be protected by try-except,

it must be protected by a Probe.  Typically the address is just plain bad or it

is pointing at freed memory.

Arguments: 

Arg1:  fffff8a00fd1d2c8, memory referenced.

Arg2:  0000000000000000, value 0 = read operation, 1 = write operation.

Arg3:  fffff880049ce135, If non-zero, the instruction address which referenced the bad memory

    address.

Arg4:  0000000000000002, (reserved)

Debugging Details: 

------------------

Could not read faulting driver name

READ_ADDRESS:  GetPointerFromAddress:  unable to read from fffff80002eff0e0

 fffff8a00fd1d2c8 

FAULTING_IP:  

dxgmms1!VIDMM_GLOBAL: ReferenceDmaBuffer+1e5

fffff880`049ce135 48395f18        cmp     qword ptr [rdi+18h],rbx

MM_INTERNAL_CODE:   2

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0x50

PROCESS_NAME:   League of Lege

CURRENT_IRQL:   0

TRAP_FRAME:   fffff88007eca0a0 -- (.trap 0xfffff88007eca0a0)

NOTE:  The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=0000000000000005 rbx=0000000000000000 rcx=00000000000003c2

rdx=fffff8a007e92000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff880049ce135 rsp=fffff88007eca230 rbp=fffff88007ecaa40

 r8=fffffa8004cbb4d8  r9=0000000000000001 r10=0000000000000015

r11=000000004000f080 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei ng nz na pe nc

dxgmms1!VIDMM_GLOBAL: ReferenceDmaBuffer+0x1e5: 

fffff880`049ce135 48395f18        cmp     qword ptr [rdi+18h],rbx ds: 76c8: 00000000`00000018=?

Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff80002d467d2 to fffff80002cc75c0

STACK_TEXT:   

fffff880`07ec9f38 fffff800`02d467d2 :  00000000`00000050 fffff8a0`0fd1d2c8 00000000`00000000 fffff880`07eca0a0 :  nt!KeBugCheckEx

fffff880`07ec9f40 fffff800`02cc56ae :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt! ? : FNODOBFM: `string'+0x40d80

fffff880`07eca0a0 fffff880`049ce135 :  00000000`00000000 00000000`0000000f fffffa80`04a0e901 fffffa80`04a0e960 :  nt!KiPageFault+0x16e

fffff880`07eca230 fffff880`049b43e7 :  fffffa80`04a6e701 fffffa80`049b6680 00000000`04c404d8 fffff880`000000cc :  dxgmms1!VIDMM_GLOBAL: ReferenceDmaBuffer+0x1e5

fffff880`07eca320 fffff880`0492cf12 :  00000000`00000000 00000000`00000200 fffff880`07ecaa40 00000000`00000000 :  dxgmms1!VidMmReferenceDmaBuffer+0x43

fffff880`07eca370 fffff880`0492c6d7 :  fffff8a0`00000001 fffff8a0`03eb4010 fffff880`07eca9f0 00000000`00000000 :  dxgkrnl!DXGCONTEXT: Render+0x326

fffff880`07eca980 fffff960`001ee54a :  00000000`085fe6b0 fffffa80`04bb4060 00000000`7ef8c000 00000000`00000020 :  dxgkrnl!DxgkRender+0x3e7

fffff880`07ecabf0 fffff800`02cc6813 :  fffffa80`04bb4060 00000000`0000035c 00000000`00000000 fffffa80`04bd3480 :  win32k!NtGdiDdDDIRender+0x12

fffff880`07ecac20 00000000`755a164a :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceCopyEnd+0x13

00000000`085fe688 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  0x755a164a

STACK_COMMAND:   kb

FOLLOWUP_IP:  

dxgmms1!VIDMM_GLOBAL: ReferenceDmaBuffer+1e5

fffff880`049ce135 48395f18        cmp     qword ptr [rdi+18h],rbx

SYMBOL_STACK_INDEX:   3

SYMBOL_NAME:   dxgmms1!VIDMM_GLOBAL: ReferenceDmaBuffer+1e5

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  dxgmms1

IMAGE_NAME:   dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   4d3fa174

FAILURE_BUCKET_ID:   X64_0x50_dxgmms1!VIDMM_GLOBAL: ReferenceDmaBuffer+1e5

BUCKET_ID:   X64_0x50_dxgmms1!VIDMM_GLOBAL: ReferenceDmaBuffer+1e5

Followup:  MachineOwner

---------

Kod:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {3, fffffa80047ac790, fffffa800c7ac790, fffffa80047ac790}

Unable to load image \SystemRoot\system32\DRIVERS\tmxpflt.sys, Win32 error 0n2

*** WARNING:  Unable to verify timestamp for tmxpflt.sys

*** ERROR:  Module load completed but symbols could not be loaded for tmxpflt.sys

Probably caused by :  Pool_Corruption ( nt!ExDeferredFreePool+a56 )

Followup:  Pool_corruption

---------

0:  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:  fffffa80047ac790, the pool entry being checked.

Arg3:  fffffa800c7ac790, the read back flink freelist value (should be the same as 2).

Arg4:  fffffa80047ac790, the read back blink freelist value (should be the same as 2).

Debugging Details: 

------------------

BUGCHECK_STR:   0x19_3

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

PROCESS_NAME:   AQQ.exe

CURRENT_IRQL:   0

LAST_CONTROL_TRANSFER:   from fffff80002decd6f to fffff80002cb95c0

STACK_TEXT:   

fffff880`0ace67b8 fffff800`02decd6f :  00000000`00000019 00000000`00000003 fffffa80`047ac790 fffffa80`0c7ac790 :  nt!KeBugCheckEx

fffff880`0ace67c0 fffff880`0541e067 :  fffff880`00000002 00000000`00000000 fffffa80`058c4108 fffffa80`00000000 :  nt!ExDeferredFreePool+0xa56

fffff880`0ace68b0 fffff880`00000002 :  00000000`00000000 fffffa80`058c4108 fffffa80`00000000 fffffa80`054ac4b0 :  tmxpflt+0x1e067

fffff880`0ace68b8 00000000`00000000 :  fffffa80`058c4108 fffffa80`00000000 fffffa80`054ac4b0 fffff880`01239b58 :  0xfffff880`00000002

STACK_COMMAND:   kb

FOLLOWUP_IP:  

nt!ExDeferredFreePool+a56

fffff800`02decd6f cc              int     3

SYMBOL_STACK_INDEX:   1

SYMBOL_NAME:   nt!ExDeferredFreePool+a56

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

BUCKET_ID:   X64_0x19_3_nt!ExDeferredFreePool+a56

Followup:  Pool_corruption

---------

Kod:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {fffffa8023eae9a8, 2, 1, fffff80002d357b7}

Probably caused by :  memory_corruption ( nt!MiReleaseConfirmedPageFileSpace+87 )

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:  fffffa8023eae9a8, memory referenced

Arg2:  0000000000000002, IRQL

Arg3:  0000000000000001, 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:  fffff80002d357b7, address which referenced memory

Debugging Details: 

------------------

WRITE_ADDRESS:  GetPointerFromAddress:  unable to read from fffff80002eaf0e0

 fffffa8023eae9a8 

CURRENT_IRQL:   2

FAULTING_IP:  

nt!MiReleaseConfirmedPageFileSpace+87

fffff800`02d357b7 480fb328        btr     qword ptr [rax],rbp

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

BUGCHECK_STR:   0xA

PROCESS_NAME:   System

TRAP_FRAME:   fffff88003124900 -- (.trap 0xfffff88003124900)

NOTE:  The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffffa800b20b010 rbx=0000000000000000 rcx=0000000000000000

rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000

rip=fffff80002d357b7 rsp=fffff88003124a90 rbp=00000000c651cce9

 r8=fffff88003124ac0  r9=fffff80002df1e80 r10=fffff80002eb1840

r11=0000000000000000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0         nv up ei pl zr na po nc

nt!MiReleaseConfirmedPageFileSpace+0x87: 

fffff800`02d357b7 480fb328        btr     qword ptr [rax],rbp ds: fffffa80`0b20b010=?

Resetting default scope

LAST_CONTROL_TRANSFER:   from fffff80002c76b29 to fffff80002c775c0

STACK_TEXT:   

fffff880`031247b8 fffff800`02c76b29 :  00000000`0000000a fffffa80`23eae9a8 00000000`00000002 00000000`00000001 :  nt!KeBugCheckEx

fffff880`031247c0 fffff800`02c757a0 :  fffff8a0`03631c70 fffffa80`04858b60 fffffa80`0df4e010 fffffa80`05bc6180 :  nt!KiBugCheckDispatch+0x69

fffff880`03124900 fffff800`02d357b7 :  00000980`00000000 fffffa80`04858b60 fffffa80`08940300 fffffa80`0089dc90 :  nt!KiPageFault+0x260

fffff880`03124a90 fffff800`02c6189a :  c651cce9`00000000 00000000`0003f9a6 fffffa80`05498950 c651cce9`00000000 :  nt!MiReleaseConfirmedPageFileSpace+0x87

fffff880`03124b10 fffff800`02f652ff :  fffffa80`054988d0 00000000`00000000 00000000`00080081 fffffa80`00080081 :  nt!MiDeleteSegmentPages+0x316

fffff880`03124bc0 fffff800`02d9edeb :  fffffa80`054988d8 00000000`00000001 00000000`00000000 00000000`00000631 :  nt!MiSegmentDelete+0x7b

fffff880`03124c00 fffff800`02d9f45d :  00000000`00000000 00000000`00000080 fffffa80`0483a890 00000000`00000012 :  nt!MiProcessDereferenceList+0x23b

fffff880`03124cc0 fffff800`02f176fa :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!MiDereferenceSegmentThread+0x10d

fffff880`03124d40 fffff800`02c55b46 :  fffff800`02df1e80 fffffa80`04858b60 fffff800`02dffc40 00000000`00000000 :  nt!PspSystemThreadStartup+0x5a

fffff880`03124d80 00000000`00000000 :  fffff880`03125000 fffff880`0311f000 fffff880`03124800 00000000`00000000 :  nt!KiStartSystemThread+0x16

STACK_COMMAND:   kb

FOLLOWUP_IP:  

nt!MiReleaseConfirmedPageFileSpace+87

fffff800`02d357b7 480fb328        btr     qword ptr [rax],rbp

SYMBOL_STACK_INDEX:   3

SYMBOL_NAME:   nt!MiReleaseConfirmedPageFileSpace+87

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nt

DEBUG_FLR_IMAGE_TIMESTAMP:   4e02aa44

IMAGE_NAME:   memory_corruption

FAILURE_BUCKET_ID:   X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87

BUCKET_ID:   X64_0xA_nt!MiReleaseConfirmedPageFileSpace+87

Followup:  MachineOwner

---------

Kod:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 4E, {99, 109147, 0, 99988}

Probably caused by :  memory_corruption ( nt!MiBadShareCount+4c )

Followup:  MachineOwner

---------

0:  kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

PFN_LIST_CORRUPT (4e)

Typically caused by drivers passing bad memory descriptor lists (ie:  calling

MmUnlockPages twice with the same list, etc).  If a kernel debugger is

available get the stack trace.

Arguments: 

Arg1:  0000000000000099, A PTE or PFN is corrupt

Arg2:  0000000000109147, page frame number

Arg3:  0000000000000000, current page state

Arg4:  0000000000099988, 0

Debugging Details: 

------------------

BUGCHECK_STR:   0x4E_99

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

PROCESS_NAME:   MOM.exe

CURRENT_IRQL:   2

LAST_CONTROL_TRANSFER:   from fffff80002d1113c to fffff80002c815c0

STACK_TEXT:   

fffff880`0849e1b8 fffff800`02d1113c :  00000000`0000004e 00000000`00000099 00000000`00109147 00000000`00000000 :  nt!KeBugCheckEx

fffff880`0849e1c0 fffff800`02c3194b :  fffffa80`01c31940 fffff6fb`83200000 fffffa80`031b3d50 00000000`00000000 :  nt!MiBadShareCount+0x4c

fffff880`0849e200 fffff800`02cb491b :  00000000`00000001 00000000`00000000 80000000`965dc863 00000000`0000001c :  nt! ? : FNODOBFM: `string'+0x20846

fffff880`0849e300 fffff800`02c9af75 :  fffffa80`04a8b3f8 00000000`00000000 00000000`00000000 00000001`0000001c :  nt!MiDeletePteRange+0x291

fffff880`0849e380 fffff800`02c9b0bf :  000007ff`fffb0015 00000000`00000001 00000000`00000023 00000000`0000002a :  nt!MiUpdateWsleHash+0x2d6

fffff880`0849e3e0 fffff800`02cc914c :  fffffa80`03151ad0 fffffa80`04a8b3f8 00000000`00000000 00000000`00000001 :  nt!MiRemoveWsle+0x7f

fffff880`0849e420 fffff800`02d5348f :  fffffa80`04a8b3f8 fffff880`0849e630 00000000`0000000f 00000000`0000000b :  nt!MiFreeWsleList+0x304

fffff880`0849e610 fffff800`02d53668 :  00000000`00000411 fffff880`00000569 00000000`00000005 00000000`00000000 :  nt!MiTrimWorkingSet+0x14f

fffff880`0849e6c0 fffff800`02ec9687 :  ffffffff`ffffffff fffffa80`04a8b3f8 fffffa80`04b26b60 00000000`00000032 :  nt!MiReduceWs+0x48

fffff880`0849e6f0 fffff800`030d36bd :  00000000`00000001 fffff880`0849eca0 00000000`00000000 00000000`1c0fde01 :  nt!MmAdjustWorkingSetSizeEx+0x397

fffff880`0849e780 fffff800`02fdbcbb :  00000000`00000008 00000000`00000000 00000000`00000001 00000000`1c0fdea0 :  nt!PspSetQuotaLimits+0x32d

fffff880`0849e8d0 fffff800`02c80813 :  fffffa80`04b26b60 fffff880`0849eca0 00000000`1af7c1f0 00000000`1af7c1f0 :  nt! ? : NNGAKEGL: `string'+0x48d70

fffff880`0849ec20 00000000`7738f87a :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  nt!KiSystemServiceCopyEnd+0x13

00000000`1c0fde68 00000000`00000000 :  00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 :  0x7738f87a

STACK_COMMAND:   kb

FOLLOWUP_IP:  

nt!MiBadShareCount+4c

fffff800`02d1113c cc              int     3

SYMBOL_STACK_INDEX:   1

SYMBOL_NAME:   nt!MiBadShareCount+4c

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  nt

DEBUG_FLR_IMAGE_TIMESTAMP:   4e02aa44

IMAGE_NAME:   memory_corruption

FAILURE_BUCKET_ID:   X64_0x4E_99_nt!MiBadShareCount+4c

BUCKET_ID:   X64_0x4E_99_nt!MiBadShareCount+4c

Followup:  MachineOwner

---------

Kod:

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 24, {1904fb, fffff880074816e8, fffff88007480f50, fffff880012b299d}

Unable to load image \SystemRoot\System32\Drivers\AsDsm.sys, Win32 error 0n2

*** WARNING:  Unable to verify timestamp for AsDsm.sys

*** ERROR:  Module load completed but symbols could not be loaded for AsDsm.sys

Probably caused by :  Ntfs.sys ( Ntfs!NtfsCommonCleanup+128d )

Followup:  MachineOwner

---------

1:  kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

NTFS_FILE_SYSTEM (24)

    If you see NtfsExceptionFilter on the stack then the 2nd and 3rd

    parameters are the exception record and context record. Do a .cxr

    on the 3rd parameter and then kb to obtain a more informative stack

    trace.

Arguments: 

Arg1:  00000000001904fb

Arg2:  fffff880074816e8

Arg3:  fffff88007480f50

Arg4:  fffff880012b299d

Debugging Details: 

------------------

EXCEPTION_RECORD:   fffff880074816e8 -- (.exr 0xfffff880074816e8)

ExceptionAddress:  fffff880012b299d (Ntfs!NtfsCommonCleanup+0x000000000000128d)

   ExceptionCode:  c0000005 (Access violation)

  ExceptionFlags:  00000000

NumberParameters:  2

   Parameter[0]:  0000000000000000

   Parameter[1]:  0000000008000058

Attempt to read from address 0000000008000058

CONTEXT:   fffff88007480f50 -- (.cxr 0xfffff88007480f50)

rax=0000000008000000 rbx=fffff8a000e298c0 rcx=0000000000000000

rdx=0000000000000000 rsi=fffff8a000e299f0 rdi=fffff88006ee5100

rip=fffff880012b299d rsp=fffff88007481920 rbp=fffff88006ee5440

 r8=01ca041093ae477f  r9=0000000000000000 r10=fffff8a000e29c58

r11=fffff8a000e299f0 r12=fffff88006ee5104 r13=0000000000000000

r14=fffff88006ee51f0 r15=fffff8a00b650f80

iopl=0         nv up ei pl nz na po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206

Ntfs!NtfsCommonCleanup+0x128d: 

fffff880`012b299d 83785800        cmp     dword ptr [rax+58h],0 ds: 002b: 00000000`08000058=?

Resetting default scope

CUSTOMER_CRASH_COUNT:   1

DEFAULT_BUCKET_ID:   VISTA_DRIVER_FAULT

PROCESS_NAME:   System

CURRENT_IRQL:   0

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

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

EXCEPTION_PARAMETER1:   0000000000000000

EXCEPTION_PARAMETER2:   0000000008000058

READ_ADDRESS:  GetPointerFromAddress:  unable to read from fffff80002ef90e0

 0000000008000058 

FOLLOWUP_IP:  

Ntfs!NtfsCommonCleanup+128d

fffff880`012b299d 83785800        cmp     dword ptr [rax+58h],0

FAULTING_IP:  

Ntfs!NtfsCommonCleanup+128d

fffff880`012b299d 83785800        cmp     dword ptr [rax+58h],0

BUGCHECK_STR:   0x24

LAST_CONTROL_TRANSFER:   from fffff88001223829 to fffff880012b299d

STACK_TEXT:   

fffff880`07481920 fffff880`01223829 :  fffff880`06ee4138 00000000`00000000 fffff880`06ee5150 fffffa80`0c647060 :  Ntfs!NtfsCommonCleanup+0x128d

fffff880`07481d30 fffff800`02cb9447 :  fffff880`06ee5150 00000000`00000000 00000000`00000000 00000000`00000000 :  Ntfs!NtfsCommonCleanupCallout+0x19

fffff880`07481d60 fffff800`02cb9401 :  00000000`00000000 fffffa80`0c647060 fffff880`07482000 fffff800`02cd0e9a :  nt!KySwitchKernelStackCallout+0x27

fffff880`06ee5020 fffff800`02cd0e9a :  00000000`00000001 fffffa80`0c647060 00000000`00000000 00000000`00000000 :  nt!KiSwitchKernelStackContinue

fffff880`06ee5040 fffff880`012233e2 :  fffff880`01223810 fffff880`06ee5150 fffff880`06ee5400 00000000`00000000 :  nt!KeExpandKernelStackAndCalloutEx+0x29a

fffff880`06ee5120 fffff880`012c2324 :  fffff880`06ee51f0 fffff880`06ee51f0 fffff880`06ee51f0 00000000`00000000 :  Ntfs!NtfsCommonCleanupOnNewStack+0x42

fffff880`06ee5190 fffff880`00d9623f :  fffff880`06ee51f0 fffffa80`04f71790 fffffa80`04f71b78 fffffa80`04f4fc30 :  Ntfs!NtfsFsdCleanup+0x144

fffff880`06ee5400 fffff880`00d946df :  fffffa80`05aa1de0 00000000`00000000 fffffa80`052a1f00 fffffa80`04f71790 :  fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f

fffff880`06ee5490 fffff880`011e98dd :  fffffa80`04f71790 fffff8a0`0b6e9c00 fffffa80`05aa1040 00000000`00000000 :  fltmgr!FltpDispatch+0xcf

fffff880`06ee54f0 fffffa80`04f71790 :  fffff8a0`0b6e9c00 fffffa80`05aa1040 00000000`00000000 fffffa80`04e2ff20 :  AsDsm+0x78dd

fffff880`06ee54f8 fffff8a0`0b6e9c00 :  fffffa80`05aa1040 00000000`00000000 fffffa80`04e2ff20 fffff800`02fd488f :  0xfffffa80`04f71790

fffff880`06ee5500 fffffa80`05aa1040 :  00000000`00000000 fffffa80`04e2ff20 fffff800`02fd488f fffffa80`04f71790 :  0xfffff8a0`0b6e9c00

fffff880`06ee5508 00000000`00000000 :  fffffa80`04e2ff20 fffff800`02fd488f fffffa80`04f71790 fffffa80`0483b890 :  0xfffffa80`05aa1040

SYMBOL_STACK_INDEX:   0

SYMBOL_NAME:   Ntfs!NtfsCommonCleanup+128d

FOLLOWUP_NAME:   MachineOwner

MODULE_NAME:  Ntfs

IMAGE_NAME:   Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP:   4d79996d

STACK_COMMAND:   .cxr 0xfffff88007480f50 ; kb

FAILURE_BUCKET_ID:   X64_0x24_Ntfs!NtfsCommonCleanup+128d

BUCKET_ID:   X64_0x24_Ntfs!NtfsCommonCleanup+128d

Followup:  MachineOwner

---------

Mam 3 partycje C (systemowa), D(programy i inne) i O. Po zformatowaniu dysków C i D, i ponownej instalacji systemu problem nadal nie ustąpił

STOP 0x050...

Na reklamację jak nie umiesz sobie poradzić.

Windows 7 Forum: konfiguracja, optymalizacja, porady, gadżety •

Destylator

peciaq

Destylator

Destylator

peciaq

thermalfake

Destylator

thermalfake