bsod - po nabehnutí systému

Ak potrebujete pomoc alebo poradiť, píšte sem (len PC, elektronika atď.)...
GIGABYTE
King
King
Používateľov profilový obrázok
Príspevky: 1828
Registrovaný: 18 jún 2007, 18:28
Bydlisko: Nitra
Kontaktovať používateľa:

bsod - po nabehnutí systému

Príspevok od používateľa GIGABYTE »

Ahojte, po dlhšom čase sa na vás obraciam s problémom s ktorým si sám neviem pomôcť. Ako už z názvu témy vyplýva po tom čo mi nabehne OS cca. po 5-6 minútach (niekedy aj skôr) na mňa vyletí bsod.
On Thu 7. 6. 2012 16:33:10 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-26504-01.dmp
uptime: 00:04:11
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A00AB66000, 0x0, 0xFFFFF80002F4F079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Thu 7. 6. 2012 16:27:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-15256-01.dmp
uptime: 00:04:12
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x50 (0xFFFFF8A00A766000, 0x0, 0xFFFFF80002F51079, 0x0)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
2x mi naskočil aj tento:
On Thu 7. 6. 2012 10:26:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\060712-17877-01.dmp
uptime: 00:00:56
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002C8E105, 0xFFFFF880087A8AA0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.
Prvý krát mi to spravilo 4.6, odvtedy nič. Tak som sa tým nejako nezaoberal. No dneska to robí od rána, myslel som, že za tým bude OC, tak som vrátil všetko na pôvodné hodnoty. Keď ani to nepomohlo prebehol som HDD cez hdtune, všetko v pohode. Tiež som spravil memtest, taktiež ramky v poriadku. Vychádzalo mi z toho, že to robí nejaký driver tak som hodil jeden z tých crash dumpov do WinDbg a výsledok bol takýto:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a00a766000, 0, fffff80002f49079, 0}


Could not read faulting driver name
Probably caused by : memory_corruption ( nt!MiCompressRelocations+70 )

---------

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ebb0e0
fffff8a00a766000

FAULTING_IP:
nt!MiCompressRelocations+70
fffff800`02f49079 410fb701 movzx eax,word ptr [r9]

MM_INTERNAL_CODE: 0

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x50

PROCESS_NAME: SearchProtocol

CURRENT_IRQL: 0

TRAP_FRAME: fffff8800b16b590 -- (.trap 0xfffff8800b16b590)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f49079 rsp=fffff8800b16b720 rbp=000000000008fc28
r8=000000007ffff960 r9=fffff8a00a766000 r10=000000000006ed2c
r11=0000000000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!MiCompressRelocations+0x70:
fffff800`02f49079 410fb701 movzx eax,word ptr [r9] ds:b600:fffff8a0`0a766000=????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff80002d041e4 to fffff80002c84f00

STACK_TEXT:
fffff880`0b16b428 fffff800`02d041e4 : 00000000`00000050 fffff8a0`0a766000 00000000`00000000 fffff880`0b16b590 : nt!KeBugCheckEx
fffff880`0b16b430 fffff800`02c82fee : 00000000`00000000 00000000`00000003 fffffa80`00000000 fffff8a0`0a6f89b0 : nt! ?? ::FNODOBFM::`string'+0x42907
fffff880`0b16b590 fffff800`02f49079 : 00000000`01000000 fffff800`02f49461 fffffa80`03e559e0 fffff800`02f495a4 : nt!KiPageFault+0x16e
fffff880`0b16b720 fffff800`02f47932 : 00000000`000d56a0 00000000`01000000 00000000`00000001 00000000`00000004 : nt!MiCompressRelocations+0x70
fffff880`0b16b770 fffff800`02f7d5d1 : fffff8a0`0e2a7000 fffff880`0b16b980 00000000`00000095 00000000`00000000 : nt!MiRelocateImage+0x4a2
fffff880`0b16b8e0 fffff800`02f72893 : fffff880`0b16bb40 00000000`00000000 00000000`00000000 00000000`00000001 : nt!MmCreateSection+0x825
fffff880`0b16baf0 fffff800`02c84153 : fffffa80`0836a6d0 00000000`009283b8 fffff880`0b16bb88 00000000`00928668 : nt!NtCreateSection+0x162
fffff880`0b16bb70 00000000`770c035a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`00928398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x770c035a


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!MiCompressRelocations+70
fffff800`02f49079 410fb701 movzx eax,word ptr [r9]

SYMBOL_STACK_INDEX: 3

SYMBOL_NAME: nt!MiCompressRelocations+70

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc600

IMAGE_NAME: memory_corruption

FAILURE_BUCKET_ID: X64_0x50_nt!MiCompressRelocations+70

BUCKET_ID: X64_0x50_nt!MiCompressRelocations+70
Takže ak by niekto vedel nejako pomôcť alebo ako tie crash dumpy fixnúť budem mu vďačný. :)

Zostava:
MB: Asus P5Q Pro
CPU: Intel Q9400
RAM: Adata PC8500 2x2GB 1066mhz
GPU: GTX275
PSU: Fortron BlueStorm II 500W
HDD: WD6400AAKS
test
Hardcore addict
Hardcore addict
Používateľov profilový obrázok
Príspevky: 5099
Registrovaný: 13 mar 2005, 5:20
Bydlisko: Doma

Re: bsod - po nabehnutí systému

Príspevok od používateľa test »

Prebehnut pamate cez MemTest86, potom disk cez HD Tune. Potom skusit instalovat najnovsie ovladace, najma grafika, chipset a zvukova karta.
GIGABYTE
King
King
Používateľov profilový obrázok
Príspevky: 1828
Registrovaný: 18 jún 2007, 18:28
Bydlisko: Nitra
Kontaktovať používateľa:

Re: bsod - po nabehnutí systému

Príspevok od používateľa GIGABYTE »

Ako som už písal, memtest86 som robil, hdtune som robil. Skúsim ešte tie driveri. Odinštaloval som nejaké somariny zo safe modu a zatial bežím asi 5 min stabilne :oops:
Napísať odpoveď