Šta je novo?
Od:
Filteri

BSOD 0x0000F4 Physical memory dump failed..

To je isto :) Ali 16 giga ram-a se malo teži popuni. Pre će biti do HDD-a.

Inače, pola stvari windbg ne može da analizira zbog previše grešaka u sistemu.

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

CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80100f9b30, Terminating object
Arg3: fffffa80100f9e10, Process image file name
Arg4: fffff80002be48b0, Explanatory message (ascii)

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


PROCESS_OBJECT: fffffa80100f9b30

IMAGE_NAME: wininit.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

MODULE_NAME: wininit

FAULTING_MODULE: 0000000000000000

PROCESS_NAME: wininit.exe

EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

BUGCHECK_STR: 0xF4_IOERR

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`0599c9c8 fffff800`02c6b5e2 : 00000000`000000f4 00000000`00000003 fffffa80`100f9b30 fffffa80`100f9e10 : nt!KeBugCheckEx
fffff880`0599c9d0 fffff800`02c1899b : ffffffff`ffffffff fffffa80`12d30320 fffffa80`100f9b30 fffffa80`100f9b30 : nt!PspCatchCriticalBreak+0x92
fffff880`0599ca10 fffff800`02b98448 : ffffffff`ffffffff 00000000`00000001 fffffa80`100f9b30 0000007f`00000008 : nt! ?? ::NNGAKEGL::`string'+0x176d6
fffff880`0599ca60 fffff800`028dfed3 : fffffa80`100f9b30 00000000`c0000006 fffffa80`12d30320 00000000`775ec521 : nt!NtTerminateProcess+0xf4
fffff880`0599cae0 00000000`776115da : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0254f828 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x776115da


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe

BUCKET_ID: X64_0xF4_IOERR_IMAGE_wininit.exe

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

2: kd> !process fffffa80100f9b30 3
GetPointerFromAddress: unable to read from fffff80002b13000
PROCESS fffffa80100f9b30
SessionId: none Cid: 022c Peb: 7fffffdb000 ParentCid: 01bc
DirBase: 3cb6fd000 ObjectTable: fffff8a005e7ebf0 HandleCount: <Data Not Accessible>
Image: wininit.exe
VadRoot fffffa80100e7c50 Vads 64 Clone 0 Private 346. Modified 11. Locked 3.
DeviceMap fffff8a0000060f0
Token fffff8a005e7ac50
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
fffff78000000000: Unable to get shared data
ElapsedTime 00:00:00.000
UserTime 00:00:00.000
KernelTime 00:00:00.000
QuotaPoolUsage[PagedPool] 0
QuotaPoolUsage[NonPagedPool] 0
Working Set Sizes (now,min,max) (1201, 50, 345) (4804KB, 200KB, 1380KB)
PeakWorkingSetSize 1201
VirtualSize 49 Mb
PeakVirtualSize 51 Mb
PageFaultCount 1449
MemoryPriority BACKGROUND
BasePriority 13
CommitCharge 457

*** Error in reading nt!_ETHREAD @ fffffa80100fab60

2: kd> lmvm wininit
start end module name
2: kd> !object fffffa80100f9b30
GetUlongFromAddress: unable to read from fffff80002b13010
Could not read ObjectType address
2: kd> !object 100f9b30
GetUlongFromAddress: unable to read from fffff80002b13010

2: kd> dc fffffa80100f9e10
fffffa80`100f9e10 696e6977 2e74696e 00657865 03000000 wininit.exe.....
fffffa80`100f9e20 00000000 00000000 00000000 00000000 ................
fffffa80`100f9e30 00000000 00000000 100faf80 fffffa80 ................
fffffa80`100f9e40 12d30740 fffffa80 00000000 00000000 @...............
fffffa80`100f9e50 00000000 00000000 00000005 65fcaecd ...............e
fffffa80`100f9e60 00008000 00000000 fffdb000 000007ff ................
fffffa80`100f9e70 00000000 00000000 00000000 00000000 ................
fffffa80`100f9e80 00000000 00000000 000000e7 00000000 ................
2: kd> dc fffff80002be48b0
fffff800`02be48b0 6d726554 74616e69 20676e69 74697263 Terminating crit
fffff800`02be48c0 6c616369 6f727020 73736563 25783020 ical process 0x%
fffff800`02be48d0 25282070 000a2973 90909090 90909090 p (%s)..........
fffff800`02be48e0 61657242 6f202c6b 67492072 65726f6e Break, or Ignore
fffff800`02be48f0 69622820 00203f29 90909090 90909090 (bi)? .........
fffff800`02be4900 74697243 6c616369 72687420 20646165 Critical thread
fffff800`02be4910 70257830 6e692820 29732520 69786520 0x%p (in %s) exi
fffff800`02be4920 0a646574 90909000 90909090 90909090 ted.............
2: kd> !vm 2

*** Virtual Memory Usage ***
GetUlongFromAddress: unable to read from fffff80002b13060
Physical Memory: 0 ( 0 Kb)
GetUlongFromAddress: unable to read from fffff80002a92ce4

************ NO PAGING FILE *********************

fffff80002b138d0: Unable to get paged pool info
GetUlongPtrFromAddress: unable to read from fffff80002b13490
GetUlongPtrFromAddress: unable to read from fffff80002b132e8
GetUlongPtrFromAddress: unable to read from fffff80002aa9708
GetUlongPtrFromAddress: unable to read from fffff80002a91cd8
GetUlongPtrFromAddress: unable to read from fffff80002a7d2a0
GetUlongPtrFromAddress: unable to read from fffff80002a91cb0
GetUlongPtrFromAddress: unable to read from fffff80002a91d20
GetUlongPtrFromAddress: unable to read from fffff80002b16280
GetUlongPtrFromAddress: unable to read from fffff80002a53448
GetUlongPtrFromAddress: unable to read from fffff80002a5fbc0
GetUlongPtrFromAddress: unable to read from fffff80002a5fc00
unable to get nt!MmTotalFreeSystemPtes
unable to get nt!MmSystemLockPagesCount
GetUlongPtrFromAddress: unable to read from fffff80002a7d2b8
GetUlongFromAddress: unable to read from fffff80002a93210
Available Pages: 0 ( 0 Kb)
ResAvail Pages: 0 ( 0 Kb)

********** Running out of physical memory **********

Locked IO Pages: 0 ( 0 Kb)
Free System PTEs: 0 ( 0 Kb)

********** Running out of system PTEs **************

GetUlongFromAddress: unable to read from fffff80002aa9f48
Modified Pages: 0 ( 0 Kb)
Modified PF Pages: 0 ( 0 Kb)
fffff80002a6b340: Unable to get pool descriptor
GetUlongFromAddress: unable to read from fffff80002b13088
NonPagedPool Usage: 0 ( 0 Kb)
NonPagedPool Max: 0 ( 0 Kb)
GetUlongFromAddress: unable to read from fffff80002b13078
PagedPool Usage: 0 ( 0 Kb)
PagedPool Maximum: 0 ( 0 Kb)
GetUlongFromAddress: unable to read from fffff80002a81a10
Unable to read _LIST_ENTRY @ fffff80002a91d90
Session Commit: 0 ( 0 Kb)
Shared Commit: 0 ( 0 Kb)
Special Pool: 0 ( 0 Kb)
Shared Process: 0 ( 0 Kb)
PagedPool Commit: 0 ( 0 Kb)
Driver Commit: 0 ( 0 Kb)
Committed pages: 418667 ( 1674668 Kb)
Commit limit: 0 ( 0 Kb)

********** Number of committed pages is near limit ********
GetUlongFromAddress: unable to read from fffff80002a91cc0
GetUlongFromAddress: unable to read from fffff80002a91cc4
GetUlongFromAddress: unable to read from fffff80002a91cc8
GetUlongFromAddress: unable to read from fffff80002a91ccc

Unable to read/NULL value _LIST_ENTRY @ fffff80002a8b350

ProcessCommitUsage could not be calculated

Memory Management Thread Stacks:
Unable to read nt!_LIST_ENTRY @ fffff80002a8b350
Kliknite za proširenje...
 
Poslednja izmena:
hmm, znaimljivo.
Evo i meni se pojavio bsod LOL.
 

Prilozi

  • 090711-8034-01.rar
    26.6 KB · Pregleda: 15
Problem ti pravi ntfs.sys.

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: fffff88008853138
Arg3: fffff88008852990
Arg4: fffff80002ebbdb8

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


EXCEPTION_RECORD: fffff88008853138 -- (.exr 0xfffff88008853138)
ExceptionAddress: fffff80002ebbdb8 (nt!MmCopyToCachedPage+0x0000000000000248)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000000476c
Attempt to read from address 000000000000476c

CONTEXT: fffff88008852990 -- (.cxr 0xfffff88008852990)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000001
rdx=fffff80002e13100 rsi=ffffffffffffffff rdi=0000000000000000
rip=fffff80002ebbdb8 rsp=fffff88008853370 rbp=fffff880088533c0
r8=0000098000000000 r9=000000000957f03b r10=0000058000000000
r11=fffff9800e1b7ff5 r12=fffff6fcc0070dc0 r13=0000000000000000
r14=000000000000002d r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!MmCopyToCachedPage+0x248:
fffff800`02ebbdb8 668bb86c470000 mov di,word ptr [rax+476Ch] ds:002b:00000000`0000476c=????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: deadislandgame

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 000000000000476c

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c2100
000000000000476c

FOLLOWUP_IP:
Ntfs!NtfsCommonWrite+3390
fffff880`0123ebf6 84c0 test al,al

FAULTING_IP:
nt!MmCopyToCachedPage+248
fffff800`02ebbdb8 668bb86c470000 mov di,word ptr [rax+476Ch]

BUGCHECK_STR: 0x24

DEVICE_OBJECT: fffffa80086f0000

LAST_CONTROL_TRANSFER: from fffff80002eb8e3e to fffff80002ebbdb8

STACK_TEXT:
fffff880`08853370 fffff800`02eb8e3e : fffff980`0e1b8000 00000000`0957f03b fffff880`00000000 00000000`0000002d : nt!MmCopyToCachedPage+0x248
fffff880`08853560 fffff800`02eb93f4 : fffffa80`08bf89e0 00000000`0957f03b fffff880`088536a0 00000000`00000000 : nt!CcMapAndCopyInToCache+0x20e
fffff880`08853650 fffff880`0123ebf6 : 00000000`00000000 fffff880`088538c0 fffffa80`08c68690 00000000`00000000 : nt!CcCopyWrite+0x194
fffff880`088536e0 fffff880`0123f1a3 : fffffa80`08c68690 fffffa80`086efc60 fffff880`08853801 fffff880`08853800 : Ntfs!NtfsCommonWrite+0x3390
fffff880`08853890 fffff880`00c02bcf : fffffa80`086effb8 fffffa80`086efc60 fffffa80`064cec30 00000000`00000001 : Ntfs!NtfsFsdWrite+0x1c3
fffff880`08853950 fffff880`00c016df : fffffa80`06876de0 00000000`00000001 fffffa80`06876d00 fffffa80`086efc60 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`088539e0 fffff800`0319821b : 00000000`00000001 fffffa80`08c04520 00000000`00000001 fffffa80`086efc60 : fltmgr!FltpDispatch+0xcf
fffff880`08853a40 fffff800`031a2c83 : fffffa80`086f0000 00000000`00000000 fffffa80`08c04520 fffff880`009ea180 : nt!IopSynchronousServiceTail+0xfb
fffff880`08853ab0 fffff800`02e8eed3 : ffffffff`ffffff01 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x7e2
fffff880`08853bb0 00000000`75332e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`08b5f0f8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x75332e09


SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: Ntfs!NtfsCommonWrite+3390

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Ntfs

IMAGE_NAME: Ntfs.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4d79997b

STACK_COMMAND: .cxr 0xfffff88008852990 ; kb

FAILURE_BUCKET_ID: X64_0x24_Ntfs!NtfsCommonWrite+3390

BUCKET_ID: X64_0x24_Ntfs!NtfsCommonWrite+3390

Followup: MachineOwner
Kliknite za proširenje...
 
A to znaciii...
Nov hdd :(
il reparacija c:
ili reinstal...

evo i novog dampa kad sam iskljucio page(pre bio 700 i kusr mb)
 

Prilozi

  • 090711-7488-01.rar
    14.8 KB · Pregleda: 13
Poslednja izmena:
@slobomo

Bolje da si otvorio novu tempu pošto tvoji BSODovi nisu isti kao od Kikibgd. Elem, ovaj zadnji kaže:

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002ec12d7

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff80002e851e9 to fffff80002e85c40

STACK_TEXT:
fffff800`0456dd28 fffff800`02e851e9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff800`0456dd30 fffff800`02e836b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`0456de70 fffff800`02ec12d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`091a2c50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0xab


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`02e836b2 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

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

0: kd> !vm

*** Virtual Memory Usage ***
GetUlongFromAddress: unable to read from fffff800030b8060
Physical Memory: 0 ( 0 Kb)
GetUlongFromAddress: unable to read from fffff80003037ce4

************ NO PAGING FILE *********************

fffff800030b88d0: Unable to get paged pool info
GetUlongPtrFromAddress: unable to read from fffff800030b8490
GetUlongPtrFromAddress: unable to read from fffff800030b82e8
GetUlongPtrFromAddress: unable to read from fffff8000304e708
GetUlongPtrFromAddress: unable to read from fffff80003036cd8
GetUlongPtrFromAddress: unable to read from fffff800030222a0
GetUlongPtrFromAddress: unable to read from fffff80003036cb0
GetUlongPtrFromAddress: unable to read from fffff80003036d20
GetUlongPtrFromAddress: unable to read from fffff800030bb280
GetUlongPtrFromAddress: unable to read from fffff80002ff8448
GetUlongPtrFromAddress: unable to read from fffff80003004bc0
GetUlongPtrFromAddress: unable to read from fffff80003004c00
unable to get nt!MmTotalFreeSystemPtes
GetUlongPtrFromAddress: unable to read from fffff800030222b8
GetUlongFromAddress: unable to read from fffff80003038210
Available Pages: 0 ( 0 Kb)
ResAvail Pages: 0 ( 0 Kb)

********** Running out of physical memory **********

Locked IO Pages: 0 ( 0 Kb)
Free System PTEs: 0 ( 0 Kb)

********** Running out of system PTEs **************

GetUlongFromAddress: unable to read from fffff8000304ef48
Modified Pages: 0 ( 0 Kb)
Modified PF Pages: 0 ( 0 Kb)
fffff80003010340: Unable to get pool descriptor
GetUlongFromAddress: unable to read from fffff800030b8088
NonPagedPool Usage: 0 ( 0 Kb)
NonPagedPoolNx Usage: 0 ( 0 Kb)
NonPagedPool Max: 0 ( 0 Kb)
GetUlongFromAddress: unable to read from fffff800030b8078
PagedPool Usage: 0 ( 0 Kb)
PagedPool Maximum: 0 ( 0 Kb)
GetUlongFromAddress: unable to read from fffff80003026a10
Unable to read _LIST_ENTRY @ fffff80003036d90
Session Commit: 0 ( 0 Kb)
Shared Commit: 0 ( 0 Kb)
Special Pool: 0 ( 0 Kb)
Shared Process: 0 ( 0 Kb)
PagedPool Commit: 0 ( 0 Kb)
Driver Commit: 0 ( 0 Kb)
Committed pages: 622017 ( 2488068 Kb)
Commit limit: 0 ( 0 Kb)

********** Number of committed pages is near limit ********
GetUlongFromAddress: unable to read from fffff80003036cc0
GetUlongFromAddress: unable to read from fffff80003036cc4
GetUlongFromAddress: unable to read from fffff80003036cc8
GetUlongFromAddress: unable to read from fffff80003036ccc

Unable to read/NULL value _LIST_ENTRY @ fffff80003030350

ProcessCommitUsage could not be calculated
Kliknite za proširenje...

Vrati page file nazad, pošto 2x4GB RAMa i nije baš mnogo.
 
Poslednja izmena:
jeste paging file je iskljucen jel moguce da je do toga?

btw jel mogu da trazim od microsystemsa da mi vrati pare pa izmem ja lepo neki intel 510?

PS: mogao si otvoris novu temu stvarno.....
 
Poslednja izmena:
DariusIII je napisao(la):
To je isto :) Ali 16 giga ram-a se malo teži popuni. Pre će biti do HDD-a.

Inače, pola stvari windbg ne može da analizira zbog previše grešaka u sistemu.
Kliknite za proširenje...


cek sta to treba da znaci "previse gresaka u sistemu" ? moguce da nije samo SSD koji pravi frku?
 
@Kikibgd

Moje prethodna poruka je bili kompletno upućena slobomo-u. Kod tebe ne bi trebalo da bude problema što si isključio page fajl pošto imaš 16GB RAMa, ali i ovo lako može da se proveri, vrati page fajl od jedno 1-2GB, pa vidi da li će BSOD opet da se pojavi.

A apropo SSD-a najjednostavnije je da otkačiš sve diskove i ostaviš samo SSD, pa probaj da li će BSOD da ti se javi.

Usput, ako neko od moderatora ovo čita, radi preglednosti ove teme, poruke od broja 32 do 35 bi najbolje bilo ako mogu da se izdvoje u posebnu temu.
 
Poslednja izmena:
ali sto je najsmesnije ja sam probao da izazovem bsod ponovo i ne mogu jednostavno je random.....
 
Debugger ne može neke od grešaka da analizira zato što fale neki parametri, koji opet fale zato što je isključen pagefile i zbog toga što HDD pravi problem.
 
ajde nista vraticu page file


jel bi mogo trazim od microsystemsa pare da mi vrate ?
 
Morate se prijaviti ili registrovati da odgovorite ovde.
Nazad
Vrh Dno