Šta je novo?
Od:
Filteri

BSOD na win7 sp1 x64

slobomo

slobomo

Slavan
Učlanjen(a)
24.06.2009
Poruke
2,495
Poena
445
Moja oprema  
Mobilni telefon
Xiaomi 13T Pro black
Pametni uređaji
Samsung smartwatch
Pristup internetu
  1. Kablovski internet
Dakle zanima me jel moze ovo nekako da se popravi.
Uzeo sam da malo odigram Dead Island kad ono...
stalno mi posle odredjenog vremena BSODuje.
 

Prilozi

  • 090711-7488-01.rar
    14.8 KB · Pregleda: 35
Novi :mad:
 

Prilozi

  • 090711-8112-01.rar
    23.6 KB · Pregleda: 24
Za prvi BSOD sam ti odgovorio ovde: http://forum.benchmark.rs/showthrea...ump-failed..&p=2655718&viewfull=1#post2655718

A za ovaj drugi:

0: 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: fffff880083697cc, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff800031a901d, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000000, (reserved)

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


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800030ce100
fffff880083697cc

FAULTING_IP:
nt!AlpcpDispatchNewMessage+21d
fffff800`031a901d 0fba64246011 bt dword ptr [rsp+60h],11h

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: deadislandgame

CURRENT_IRQL: 0

TRAP_FRAME: fffff880074cf6d0 -- (.trap 0xfffff880074cf6d0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000011 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800031a901d rsp=fffff880074cf860 rbp=fffffa8007d63090
r8=0000000000335b40 r9=000000000000005c r10=fffffa800644a5c0
r11=fffffa8008693e60 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!AlpcpDispatchNewMessage+0x21d:
fffff800`031a901d 0fba64246011 bt dword ptr [rsp+60h],11h ss:0018:fffff880`074cf8c0=c0020000
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002e479fc to fffff80002e9bc40

STACK_TEXT:
fffff880`074cf568 fffff800`02e479fc : 00000000`00000050 fffff880`083697cc 00000000`00000001 fffff880`074cf6d0 : nt!KeBugCheckEx
fffff880`074cf570 fffff800`02e99d6e : 00000000`00000001 fffff880`083697cc 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`074cf6d0 fffff800`031a901d : 00000000`00000000 00000000`08693e60 00000000`00000000 fffffa01`06610000 : nt!KiPageFault+0x16e
fffff880`074cf860 fffff800`031a694f : fffffa80`c0020000 fffff8a0`03f84278 00000000`00335b18 fffff8a0`028856c0 : nt!AlpcpDispatchNewMessage+0x21d
fffff880`074cf8c0 fffff800`031ab526 : 00000000`003717c0 fffffa80`08aeca00 00000000`003468c8 00000000`00000001 : nt!AlpcpSendMessage+0x4ad
fffff880`074cf9c0 fffff800`031a936b : fffffa80`08693e60 00000000`c0020000 00000000`00335b18 00000000`003468c8 : nt!AlpcpProcessSynchronousRequest+0x2f3
fffff880`074cfb00 fffff800`02e9aed3 : fffffa80`0661f3e0 fffff880`074cfca0 fffff880`746c6644 fffff880`074cfc38 : nt!NtAlpcSendWaitReceivePort+0x1ab
fffff880`074cfbb0 00000000`77d5019f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e208 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77d5019f


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!AlpcpDispatchNewMessage+21d
fffff800`031a901d 0fba64246011 bt dword ptr [rsp+60h],11h

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!AlpcpDispatchNewMessage+21d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

FAILURE_BUCKET_ID: X64_0x50_nt!AlpcpDispatchNewMessage+21d

BUCKET_ID: X64_0x50_nt!AlpcpDispatchNewMessage+21d

Followup: MachineOwner
Kliknite za proširenje...

Za početak vrati page fajl nazad.
 
@DariusIII upravo tu.
hehe
@mmsandi gde ces bolju apoteku od reloaded-ove :) (a i nema trenutno nista drugo-ubacen je updt 1)

@mr.maX nadam se da mislis na ovo
Start Menu -> Right-Click Computer -> Properties -> Advanced System Settings -> Settings (Performance) -> Advanced Tab -> Change ->
vm.jpg
 
Evo da osvezim temu.

Nema nista od PF, sad mi ni nepravi damp. Samo mi bsoduje LOL.

Posto trenutno nemam nista zahtevnije od DI igre, probacu novi deusex. Naravno linx61 prosao sa allmem na 20run(nekih 3h rada).
 
A koji je BSOD kod prijavljen kad si vratio page fajl nazad?
 
Evo najfriskiji.
ntfs i ntoskrnl
 

Prilozi

  • 090911-8923-01.rar
    27.3 KB · Pregleda: 18
Hardverska greška. NTFS.

3: 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: fffff880035fb828
Arg3: fffff880035fb080
Arg4: fffff880012e6bf5

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


EXCEPTION_RECORD: fffff880035fb828 -- (.exr 0xfffff880035fb828)
ExceptionAddress: fffff880012e6bf5 (Ntfs!NtfsWriteFileSizes+0x0000000000000045)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0

CONTEXT: fffff880035fb080 -- (.cxr 0xfffff880035fb080)
rax=fffffa8006984180 rbx=fffff8a008159ba0 rcx=fffffa8008501840
rdx=fffff8a008159ba0 rsi=fffff880035fbbf0 rdi=00000000006c0000
rip=fffff880012e6bf5 rsp=fffff880035fba60 rbp=fffff880035fbe20
r8=fffff880035fbbf0 r9=0000000000000001 r10=0000000000000000
r11=fffff8a008159ba0 r12=fffff880035fbc00 r13=0000000000000001
r14=fffffa8008501840 r15=fffffa80067a0500
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
Ntfs!NtfsWriteFileSizes+0x45:
fffff880`012e6bf5 06 ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x24

PROCESS_NAME: System

CURRENT_IRQL: 0

ERROR_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.

LAST_CONTROL_TRANSFER: from fffff880012476fa to fffff880012e6bf5

MISALIGNED_IP:
Ntfs!NtfsWriteFileSizes+45
fffff880`012e6bf5 06 ???

STACK_TEXT:
fffff880`035fba60 fffff880`012476fa : fffffa80`08501840 fffff880`035fbe00 fffff8a0`08159ba0 00000000`006c0000 : Ntfs!NtfsWriteFileSizes+0x45
fffff880`035fbbc0 fffff880`01246de8 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff8a0`08159ba0 : Ntfs!NtfsPostWriteProcessing+0x21a
fffff880`035fbc40 fffff880`012471a3 : fffffa80`08501840 fffffa80`081a0c60 fffff880`035fbe01 fffff880`00020000 : Ntfs!NtfsCommonWrite+0x3580
fffff880`035fbdf0 fffff880`01075bcf : fffffa80`081a0fb8 fffffa80`081a0c60 fffffa80`08b006b0 00000000`00000001 : Ntfs!NtfsFsdWrite+0x1c3
fffff880`035fbeb0 fffff880`010746df : fffffa80`06867900 00000000`00000001 fffffa80`06867900 fffffa80`081a0c60 : fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x24f
fffff880`035fbf40 fffff800`031dc21b : 00000000`00000001 fffffa80`0752fb00 00000000`00000001 fffffa80`081a0c60 : fltmgr!FltpDispatch+0xcf
fffff880`035fbfa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopSynchronousServiceTail+0xfb


FOLLOWUP_IP:
Ntfs!NtfsWriteFileSizes+45
fffff880`012e6bf5 06 ???

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: Ntfs!NtfsWriteFileSizes+45

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff880035fb080 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED_Ntfs.sys

BUCKET_ID: X64_IP_MISALIGNED_Ntfs.sys

Followup: MachineOwner
Kliknite za proširenje...
 
A to moze da se popravi kako...
 
Ako vas ne mrzi,analizirajte i meni :(
 

Prilozi

  • Minidump.rar
    124.2 KB · Pregleda: 20
Jedan od minidumpova i njegova analiza:

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002cd8e60, The address that the exception occurred at
Arg3: fffff8800218cc78, Exception Record Address
Arg4: fffff8800218c4d0, Context Record Address

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


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

FAULTING_IP:
nt!KeSetEvent+2ce
fffff800`02cd8e60 f0410fba2907 lock bts dword ptr [r9],7

EXCEPTION_RECORD: fffff8800218cc78 -- (.exr 0xfffff8800218cc78)
ExceptionAddress: fffff80002cd8e60 (nt!KeSetEvent+0x00000000000002ce)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT: fffff8800218c4d0 -- (.cxr 0xfffff8800218c4d0)
rax=0000000000000002 rbx=0000000000000000 rcx=fffffa80059aa6c0
rdx=fffffa80059aa728 rsi=0000000000000000 rdi=fffff88003088180
rip=fffff80002cd8e60 rsp=fffff8800218ceb0 rbp=0000000000000000
r8=fffffa80059aa728 r9=ffdffa800599e5b0 r10=fffffa8005ae3bd0
r11=0000000000000000 r12=fffffa8005ae3b01 r13=fffffa8005ae3bd0
r14=0000000000000001 r15=fffffa800599e010
iopl=0 nv up ei ng nz ac po cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00210297
nt!KeSetEvent+0x2ce:
fffff800`02cd8e60 f0410fba2907 lock bts dword ptr [r9],7 ds:002b:ffdffa80`0599e5b0=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 2

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

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f07100
ffffffffffffffff

FOLLOWUP_IP:
nt!KeSetEvent+2ce
fffff800`02cd8e60 f0410fba2907 lock bts dword ptr [r9],7

BUGCHECK_STR: 0x7E

LAST_CONTROL_TRANSFER: from fffff8800403a9a0 to fffff80002cd8e60

STACK_TEXT:
fffff880`0218ceb0 fffff880`0403a9a0 : fffffa80`00000000 fffffa80`00000000 fffffa80`05ae4d00 fffffa80`059aa728 : nt!KeSetEvent+0x2ce
fffff880`0218cf20 fffffa80`00000000 : fffffa80`00000000 fffffa80`05ae4d00 fffffa80`059aa728 fffff880`0218cf90 : 0xfffff880`0403a9a0
fffff880`0218cf28 fffffa80`00000000 : fffffa80`05ae4d00 fffffa80`059aa728 fffff880`0218cf90 fffffa80`05ae4d70 : 0xfffffa80`00000000
fffff880`0218cf30 fffffa80`05ae4d00 : fffffa80`059aa728 fffff880`0218cf90 fffffa80`05ae4d70 00000000`00000000 : 0xfffffa80`00000000
fffff880`0218cf38 fffffa80`059aa728 : fffff880`0218cf90 fffffa80`05ae4d70 00000000`00000000 00000000`00000000 : 0xfffffa80`05ae4d00
fffff880`0218cf40 fffff880`0218cf90 : fffffa80`05ae4d70 00000000`00000000 00000000`00000000 00000000`00000001 : 0xfffffa80`059aa728
fffff880`0218cf48 fffffa80`05ae4d70 : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`05ae4d70 : 0xfffff880`0218cf90
fffff880`0218cf50 00000000`00000000 : 00000000`00000000 00000000`00000001 fffffa80`05ae4d70 fffffa80`05ae3bd0 : 0xfffffa80`05ae4d70


SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KeSetEvent+2ce

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

STACK_COMMAND: .cxr 0xfffff8800218c4d0 ; kb

FAILURE_BUCKET_ID: X64_0x7E_nt!KeSetEvent+2ce

BUCKET_ID: X64_0x7E_nt!KeSetEvent+2ce

Followup: MachineOwner
---------
Kliknite za proširenje...

Sledeći koji sam analizirao prijavljuje grešku sa ntfs.sys.

Ovo je još jedan od dumpova, problem sa sistemskim drajverom za procesor:

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

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


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP:
+5256952f045ad958
00000000`00000000 ?? ???

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000000

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x1E

PROCESS_NAME: csrss.exe

CURRENT_IRQL: 2

EXCEPTION_RECORD: fffff88003046be8 -- (.exr 0xfffff88003046be8)
ExceptionAddress: fffff880041e8b80 (amdppm!PerfSelectionPTStates+0x0000000000000014)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

TRAP_FRAME: fffff88003046c90 -- (.trap 0xfffff88003046c90)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000000a rbx=0000000000000000 rcx=ffdffa800307f470
rdx=0000000000000064 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880041e8b80 rsp=fffff88003046e28 rbp=fffffa80030b9db8
r8=0000000000000001 r9=0000000000000064 r10=0000000000000064
r11=fffffa80030b9d00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
amdppm!PerfSelectionPTStates+0x14:
fffff880`041e8b80 4c8b5908 mov r11,qword ptr [rcx+8] ds:0001:ffdffa80`0307f478=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002cce5fe to fffff80002cd6c10

STACK_TEXT:
fffff880`03045cc8 fffff800`02cce5fe : 00000000`00000000 00000000`00000000 fffff880`03046440 fffff800`02d02830 : nt!KeBugCheck
fffff880`03045cd0 fffff800`02d024fd : fffff800`02ee071c fffff800`02e1dc30 fffff800`02c5a000 fffff880`03046be8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`03045d00 fffff800`02d012d5 : fffff800`02e21028 fffff880`03045d78 fffff880`03046be8 fffff800`02c5a000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`03045d30 fffff800`02d12361 : fffff880`03046be8 fffff880`03046440 fffff880`00000000 00000000`00000014 : nt!RtlDispatchException+0x415
fffff880`03046410 fffff800`02cd62c2 : fffff880`03046be8 00000000`00000064 fffff880`03046c90 00000000`0000000a : nt!KiDispatchException+0x135
fffff880`03046ab0 fffff800`02cd4bca : 00000000`00000004 fffffa80`03ebb9d0 00000001`00000000 00000000`00000000 : nt!KiExceptionDispatch+0xc2
fffff880`03046c90 fffff880`041e8b80 : fffff800`02d8a9e0 00000000`00000064 00000000`0000000a 00000000`00000014 : nt!KiGeneralProtectionFault+0x10a
fffff880`03046e28 fffff800`02d8a9e0 : 00000000`00000064 00000000`0000000a 00000000`00000014 00000000`00000002 : amdppm!PerfSelectionPTStates+0x14
fffff880`03046e30 fffff800`02d8b17d : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000002 : nt!PpmPerfSelectProcessorState+0x1c0
fffff880`03046e90 fffff800`02d887ec : fffff880`009b1180 00000000`00000000 fffff800`02e73fd0 00000000`00000000 : nt!PpmPerfSelectProcessorStates+0xbd
fffff880`03046ed0 fffff800`02ce20ac : fffff880`009b1180 fffffa80`00000576 fffffa80`026b0050 00000000`00000076 : nt!PpmCheckRun+0x8c
fffff880`03046f00 fffff800`02cd9765 : 00000000`00000000 fffffa80`041db930 00000000`00000000 fffff800`02d88760 : nt!KiRetireDpcList+0x1bc
fffff880`03046fb0 fffff800`02cd957c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KyRetireDpcList+0x5
fffff880`0277b4a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue


STACK_COMMAND: kb

FOLLOWUP_IP:
amdppm!PerfSelectionPTStates+14
fffff880`041e8b80 4c8b5908 mov r11,qword ptr [rcx+8]

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: amdppm!PerfSelectionPTStates+14

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: amdppm

IMAGE_NAME: amdppm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc0fd

FAILURE_BUCKET_ID: X64_0x1E_amdppm!PerfSelectionPTStates+14

BUCKET_ID: X64_0x1E_amdppm!PerfSelectionPTStates+14

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

4: kd> lmvm amdppm
start end module name
fffff880`041e6000 fffff880`041fb000 amdppm (pdb symbols) c:\symbols\amdppm.pdb\AB154B73C6884E70807CA6407175368D1\amdppm.pdb
Loaded symbol image file: amdppm.sys
Mapped memory image file: c:\symbols\amdppm.sys\4A5BC0FD15000\amdppm.sys
Image path: \SystemRoot\system32\DRIVERS\amdppm.sys
Image name: amdppm.sys
Timestamp: Tue Jul 14 01:19:25 2009 (4A5BC0FD)
CheckSum: 0001EA42
ImageSize: 00015000
File version: 6.1.7600.16385
Product version: 6.1.7600.16385
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: amdppm.sys
OriginalFilename: amdppm.sys
ProductVersion: 6.1.7600.16385
FileVersion: 6.1.7600.16385 (win7_rtm.090713-1255)
FileDescription: Processor Device Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
Kliknite za proširenje...
 
Poslednja izmena:
@slobomo,

Pošto je NTFS greška i još ukazana na hardver, problem je vezan za HDD. A gde je tačno problem kod HDD-a (sam disk, kabl, kontroler, itd.) - your guess is good as mine... :)
 
OK thx. Raskacio sam hdd da vidim jel ce da pada skrin opet.
 
Izgleda da mi memorija brljavi na 1600mhz(rucno sve podeseno po SPD-u).
 
Da ne otvaram novu temu posto je problem slican..
Naime dobijam bsod povremeno, win 7 64bit. Poslednje sto sam menjao je ati drajver (stavio najnoviji 11.8)
Ako neko moze da mi protumaci sta je u pitanju bio bih mu zahvalan..
 

Prilozi

  • 091711-20311-01.zip
    42.4 KB · Pregleda: 17
Upravo je problem u ATI drajveru (atikmdag.sys). Možda nije dobro urađen update prethodne verzije.

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A0000001, {5, 0, 0, 0}

Probably caused by : atikmdag.sys ( atikmdag+4d591 )

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

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

Unknown bugcheck code (a0000001)
Unknown bugcheck description
Arguments:
Arg1: 0000000000000005
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA0000001

PROCESS_NAME: System

CURRENT_IRQL: b

LAST_CONTROL_TRANSFER: from fffff88004e76591 to fffff80003294c40

STACK_TEXT:
fffff880`0338b668 fffff880`04e76591 : 00000000`a0000001 00000000`00000005 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`0338b670 00000000`a0000001 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : atikmdag+0x4d591
fffff880`0338b678 00000000`00000005 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`00000000 : 0xa0000001
fffff880`0338b680 00000000`00000000 : 00000000`00000000 00000000`00000000 fffffa80`00000000 00000000`00000000 : 0x5


STACK_COMMAND: kb

FOLLOWUP_IP:
atikmdag+4d591
fffff880`04e76591 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: atikmdag+4d591

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: atikmdag

IMAGE_NAME: atikmdag.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4e31d49f

FAILURE_BUCKET_ID: X64_0xA0000001_atikmdag+4d591

BUCKET_ID: X64_0xA0000001_atikmdag+4d591

Followup: MachineOwner
Kliknite za proširenje...
 
Hvala mr.maX na odgovoru..
Odradio sam novi instal drajvera pa cu da vidim da li ce da se ponovi.
 
da ja ne kacim novu temu, dva puta mi se restartovao komp i ovo su detalji koje ostavi analaiza minidumpa, sta li moze da bude... ram memoriju sam tek dobio posto mi je crkla pre neki dan, znaci memorija je nova, i memtest za sada nije pokazao da joj nesto fali?
prvi
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [H:\101411-24944-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03056000 PsLoadedModuleList = 0xfffff800`0329b670
Debug session time: Fri Oct 14 21:51:44.404 2011 (UTC + 2:00)
System Uptime: 0 days 2:07:08.825
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A, {100000000000, 2, 0, fffff80003103db6}

Probably caused by : memory_corruption ( nt!MiResolveTransitionFault+136 )

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: 0000100000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, 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: fffff80003103db6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003305100
0000100000000000

CURRENT_IRQL: 2

FAULTING_IP:
nt!MiResolveTransitionFault+136
fffff800`03103db6 488b10 mov rdx,qword ptr [rax]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: avp.exe

TRAP_FRAME: fffff88008f89700 -- (.trap 0xfffff88008f89700)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000100000000000 rbx=0000000000000000 rcx=0000000000000004
rdx=0000000fffffffff rsi=0000000000000000 rdi=0000000000000000
rip=fffff80003103db6 rsp=fffff88008f89890 rbp=fffff8a0025cfa18
r8=ffffffffffffffff r9=0000000124207860 r10=0000000000000000
r11=0000058000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiResolveTransitionFault+0x136:
fffff800`03103db6 488b10 mov rdx,qword ptr [rax] ds:00001000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800030d21e9 to fffff800030d2c40

STACK_TEXT:
fffff880`08f895b8 fffff800`030d21e9 : 00000000`0000000a 00001000`00000000 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`08f895c0 fffff800`030d0e60 : 00000000`00000003 00000000`000000e2 00000000`00000001 00000001`24207860 : nt!KiBugCheckDispatch+0x69
fffff880`08f89700 fffff800`03103db6 : 7ff00000`00000000 00000000`01cac028 fffffa80`038a9240 fffff700`01080000 : nt!KiPageFault+0x260
fffff880`08f89890 fffff800`030f1695 : 00000000`00000000 00000001`24207860 fffffa80`038a9240 fffffa80`0764c9c8 : nt!MiResolveTransitionFault+0x136
fffff880`08f89920 fffff800`030f0053 : 00000000`0013316a 00000000`6d1f0500 fffff680`00368f80 fffffa80`0764c9c8 : nt!MiResolveProtoPteFault+0x325
fffff880`08f899b0 fffff800`030dff19 : fffffa80`07c37c00 00000000`6d1f0500 fffff880`08f89bf8 00000000`00000000 : nt!MiDispatchFault+0x1c3
fffff880`08f89ac0 fffff800`030d0d6e : 00000000`00000008 00000000`6d1f0500 fffff880`08f89b01 00000000`01cb96f4 : nt!MmAccessFault+0x359
fffff880`08f89c20 00000000`6d1f0500 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
00000000`01e9fe28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6d1f0500


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiResolveTransitionFault+136
fffff800`03103db6 488b10 mov rdx,qword ptr [rax]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiResolveTransitionFault+136

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0xA_nt!MiResolveTransitionFault+136

BUCKET_ID: X64_0xA_nt!MiResolveTransitionFault+136

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

drugi

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [H:\101511-23899-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\WINDOWS\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03052000 PsLoadedModuleList = 0xfffff800`03297670
Debug session time: Sat Oct 15 03:33:17.178 2011 (UTC + 2:00)
System Uptime: 0 days 0:21:43.599
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41287, 0, 0, 0}

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

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

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

MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041287, The subtype of the bugcheck.
Arg2: 0000000000000000
Arg3: 0000000000000000
Arg4: 0000000000000000

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


BUGCHECK_STR: 0x1a_41287

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: avp.exe

CURRENT_IRQL: 0

TRAP_FRAME: fffff88007b69930 -- (.trap 0xfffff88007b69930)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffffa800525fc50
rdx=00000000000000ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff800030be111 rsp=fffff88007b69ac0 rbp=fffffa80075024a8
r8=fffffa80057bb5c0 r9=fffffa8008010ee0 r10=0000000000000000
r11=fffffa800525fc50 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!MiRebalanceNode+0x21:
fffff800`030be111 498b0a mov rcx,qword ptr [r10] ds:60b0:00000000`00000000=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80003061d7e to fffff800030cec40

STACK_TEXT:
fffff880`07b697c8 fffff800`03061d7e : 00000000`0000001a 00000000`00041287 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff880`07b697d0 fffff800`030ccd6e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x46485
fffff880`07b69930 fffff800`030be111 : fffffa80`05583060 fffffa80`07502060 fffffa80`08216000 0007ffff`ffffffff : nt!KiPageFault+0x16e
fffff880`07b69ac0 fffff800`03101423 : fffffa80`0530b6b0 00000000`00000000 00000000`027f0000 fffff880`07b69ca0 : nt!MiRebalanceNode+0x21
fffff880`07b69af0 fffff800`030bc0c2 : fffffa80`07502060 fffff880`07b69ca0 00000000`02800000 00000000`00000000 : nt!MiRemoveNode+0x233
fffff880`07b69b20 fffff800`030cded3 : ffffffff`ffffffff 00000000`136ee810 00000000`136ee808 00000000`00008000 : nt!NtFreeVirtualMemory+0x5e2
fffff880`07b69c20 00000000`770914fa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`136ee7d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770914fa


STACK_COMMAND: kb

FOLLOWUP_IP:
nt! ?? ::FNODOBFM::`string'+46485
fffff800`03061d7e cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt! ?? ::FNODOBFM::`string'+46485

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4e02aaa3

FAILURE_BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485

BUCKET_ID: X64_0x1a_41287_nt!_??_::FNODOBFM::_string_+46485

Followup: MachineOwner
---------
 
nema odgovora ali resio sam problem, posle vise testova ipak je memtest pokazao da ni jedna od novih ram memorija nije valjala, sad sam dobio opet nove i za sada rade....
 
A kako stvari stoje za moje bsode, izgleda da mi je ploca pravila problem.
 
Sve zivo i nezivo sam pokusao ali i na 1333 je PC radio vrlo nestabilno.
Ploca je u prodavnici gde sam je i kupio a kada ce mi je popraviti/zameniti/vratiti novac nemam pojma.
 
Morate se prijaviti ili registrovati da odgovorite ovde.
Nazad
Vrh Dno