BSOD - što, zašto i kako izdvojena tema

poruka: 3.547
|
čitano: 1.298.764
|
moderatori: DrNasty, pirat, XXX-Man, vincimus
+/- sve poruke
ravni prikaz
starije poruke gore
15 godina
neaktivan
offline
BSOD - što, zašto i kako

pozdrav. u zadnje vrijeme imam problema sa bsod. to se dešava kad igram ovaj novi skyrim, i još neke igre.  evo o čemu se radi.

Problem signature:
  Problem Event Name:    BlueScreen
  OS Version:    6.1.7601.2.1.0.256.1
  Locale ID:    5146

Additional information about the problem:
  BCCode:    50
  BCP1:    FFFFFFF8
  BCP2:    00000001
  BCP3:    82CDB540
  BCP4:    00000000
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    256_1

Files that help describe the problem:
  C:\Windows\Minidump\112511-11013-01.dmp
  C:\Users\Matko\AppData\Local\Temp\WER-17581-0.sysdata.xml

 

evo print screen blue screen view
http://pokit.etf.ba/get/912882c0a7637ee6518713c950a5d0a8.jpg

 

Poruka je uređivana zadnji put pet 25.11.2011 20:32 (nikmak1).
 
0 0 hvala 0
15 godina
protjeran
offline
Re: BSOD - što, zašto i kako
Lazarus Long kaže...

  Jedan BSOD je vezan uz Dxgmms1.sys [DirectX memoru manager]

Koristis ATI graficke u crossfireu? Pogledaj njihove drivere odnosno Update for Windows 7 (KB974431) 

 

Ostali dumpovi su memeory corruption. Pogledaj koje se zadace izvrsavaju u tom periodu od 1 do 3 ujutro. Iskljuci da se driveri ne apdejtaju automtski

 

Ne koristim CF, ali imam CF ploču pa sam svejedno skinuo 64bit verziju tog updatea, i neda mi instalirati..
Možda je već autoupdateao taj fix. 

 

ihush kaže...
Don Kihoty kaže...

..isključio sva power saveing "govanca",

..

- mora biti 'power'.. ako je nakon 6+ sati mirovanja:

- hibernate je još malo dublje, bez obzira što napraviš, automatika nakon 360min. (stavi nulu i u CMD powercfg hibernate /off).

 

 

To sam napravio.

 

Lazarus Long kaže...

Kolega  powercfg -h off {#}

 

 

I to sam napravio. Za sada trenutno nema BSoD-ova (kuc kuc).

 

Strah me kad ću ponovno morati instalirati OS. 

Gigabyte Superman, ASRock Kryptonite http://www.mein-pc.eu/Profil/Don-Kihoty-/14184
14 godina
offline
BSOD - što, zašto i kako

Pozdrav svima.

Kako sam nabavio novi HW (matična, proc i RAM-i) koji možete vidjeti unutar mog PC-a, počelo mi se na windows 7 pri pokretanju shut down-a ili restarta pojavljivati BSOD.

Pretpostavljam da je do nekih starih driver-a koji su zaostali pri promijeni HW-a, ali sada me zanima da li se može iz dumpa koji se kreira pri pojavi BSOD saznati o kojim se točno driver-ima radi?

Hvala i živjeli :)

Moj PC  
0 0 hvala 0
17 godina
neaktivan
offline
Re: BSOD - što, zašto i kako
plavi83 kaže...

Pozdrav svima.

Kako sam nabavio novi HW (matična, proc i RAM-i)

  Samo promjena maticne, procesora i RAM-a nije dovoljna. Staru si instalaciju trebao ocistiti od starih drivera (grafika, chipset) i zatim menjati komponente. Pravo je cudo sto imas tako malo BSOD-va.

 

Dakle, odgovor si dao sam. Pretpostavljam da imas piratske Windoze i to bi bilo to. Reinstalacija ce srediti sve!

Kako prebaciti BUG DVD u DivX da mi stane na obicni CD. (probao sam sa Dr DivX ali nejde)
14 godina
offline
Re: BSOD - što, zašto i kako
Lazarus Long kaže...
plavi83 kaže...

Pozdrav svima.

Kako sam nabavio novi HW (matična, proc i RAM-i)

  Samo promjena maticne, procesora i RAM-a nije dovoljna. Staru si instalaciju trebao ocistiti od starih drivera (grafika, chipset) i zatim menjati komponente. Pravo je cudo sto imas tako malo BSOD-va.

 

Dakle, odgovor si dao sam. Pretpostavljam da imas piratske Windoze i to bi bilo to. Reinstalacija ce srediti sve!

To sam si i mislio, ali sam htio i potvrdu moje sumnje.

Hvala i živio

14 godina
offline
Re: BSOD - što, zašto i kako

Evo samo da napišem što je na kraju bio uzrok mojih BSOD-a.

I nakon nove instalacije Windowsa 7, BSOD se pojavljivao nakon restart/shut down procesa. Na kraju se po dumpu koji se kreirao uspostavilo da to uzrokuje driver od moje matične (Gigabayte) AppleCharger.sys, koji je zadužen za punjenje Apple proizvoda (iPhone, iPod i sl.)

Ta se komponenta pri instalaciji drivera zove "ON/OFF Charge", pa eto da znate.

Možda nekome i uštedim malo živaca. :)

Živjeli

14 godina
offline
BSOD - što, zašto i kako

Da ne tražim,može li mi itko reći kako se zove program s kojim ću vidjeti zašto je pc Crasho tj. izbacio BSOD?

Evo sad pokrenuo skype i bsod odmah mi izbacio,temperature su ok,za CPU 29 GPU 35 HDD 32 MBO 38.

HVALA!

sve što me trebate javite se na evilmage007@gmail.com PM mi nešto šteka. HVALA na razumijevanju
Moj PC  
0 0 hvala 0
16 godina
neaktivan
offline
Re: BSOD - što, zašto i kako
If it ain't broken, you're not working hard enough ...
14 godina
offline
BSOD - što, zašto i kako

ja sam koristio ovaj pri pronalaženju razloga mog BSOD

http://www.resplendence.com/whocrashed

Moj PC  
0 0 hvala 1
16 godina
neaktivan
offline
BSOD - što, zašto i kako

ima tko ideju? 

i'm freaking out here :P

 

http://dl.dropbox.com/u/3112711/POSAO/120511-27362-01.dmp

 

KONF:

CPU: Intel Core2Quad Q6600 @ 2.4 GHz

RAM: 3 GB

GPU: NVIDIA GeForce 8800GT

HDD: WD 500 GB, Hitachi 500 GB

OS: Win 7 x32

 

imam u planu ruštit winse, možda je software-ski problem? tješ-tješ 

hvala, kakogod!

 

 

Evo WhoChrashed analiza, možda pomogne.

 

Crash Dump Analysis

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

 

Crash dump directory: C:\Windows\Minidump

 

Crash dumps are enabled on your computer.

 

 

On Mon 5.12.2011. 7:56:00 GMT your computer crashed

crash dump file: C:\Windows\Minidump\120511-27362-01.dmp

uptime: 00:56:36

This was probably caused by the following module: intelppm.sys (intelppm+0x15D6) 

Bugcheck code: 0x50 (0xFFFFFFFFBC9E41FC, 0x0, 0xFFFFFFFF82E581AE, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\drivers\intelppm.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Processor Device Driver

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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 

 

 

On Mon 5.12.2011. 7:56:00 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

uptime: 00:56:36

This was probably caused by the following module: intelppm.sys (intelppm+0x15D6) 

Bugcheck code: 0x50 (0xFFFFFFFFBC9E41FC, 0x0, 0xFFFFFFFF82E581AE, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\drivers\intelppm.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Processor Device Driver

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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time. 

R.I.P. EnlightenedPhoenix 24.6.2011.
Poruka je uređivana zadnji put pon 5.12.2011 9:23 (eterna luchar).
Moj PC  
0 0 hvala 0
14 godina
offline
Re: BSOD - što, zašto i kako

koju MBO imaš?

16 godina
neaktivan
offline
Re: BSOD - što, zašto i kako
Gigabyte X38-DQ6
R.I.P. EnlightenedPhoenix 24.6.2011.
14 godina
offline
Re: BSOD - što, zašto i kako

Pošto je intelppm.sys Intel procesor driver, probaj instalirati zadnje verzije Intel chipset drivere, Intel grafičke drivere i Intel mrežne drivere sa intel-ovi stranica ili sa stranice proizvođača svoje MBO.

16 godina
offline
Re: BSOD - što, zašto i kako

@ e.l.,

- RAM (bilo koji, RAM, VRAM, L2-L3)..

- ako je (ili je bio) OC, vrati nazad clockove i provjeri temp, moguće da su ostale posljedice na CPU-cache ili imaš sreće.

- prvo testiraj RAM MemTest86+ (ima na svakom liveCDu.., neki ubuntu). Za to vrijeme odspoji HDD da se ne boota nepotrebno, ako je greška u RAMu ili CPU često se zbrljavi sys-hdd. Možda će biti potreban i chkdsk /r ...

- ako ne otkriješ grešku u RAMu (ili smrzavanjem pa to znači CPU) onda može biti u VRAM (VGA) problem.

- MBO vjerojatno nije (osim ako je dugotrajni OC učinio svoje.. počisti, prišarafi, povadi komponente i vrati nazad, možda pomogne.

- tek kad eliminiraš uzrok, spoji nazad HDD i napravi chkdsk. (i /r ili /f)

 

C64/TurboModul-OpenSourceProject.org.cn.部分作品为网上收集整理,供开源爱好者学习使用
16 godina
neaktivan
offline
Re: BSOD - što, zašto i kako
ok, momci... hvala na brzom odgovoru. malo će pričekati jer mi je to poslovni, a kako to hoće obično, posla ima previše da bih mogao nekoliko sati izgubiti. mislio sam možda je nešto jednostavnije. ali čim uhvatim vremena odradim po vašim savjetima ;)
hvala još jednom...
R.I.P. EnlightenedPhoenix 24.6.2011.
13 godina
neaktivan
offline
Re: BSOD - što, zašto i kako
evo stavio sam taj bug pa ako mi neko može reći u ćemu je problem,za informaciju uzo sam novi monitor i otad su problemi počeli.na starom je sve ok radilo



Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\mario\Desktop\Nova mapa\120711-37375-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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03450000 PsLoadedModuleList = 0xfffff800`03695670
Debug session time: Wed Dec 7 20:01:48.978 2011 (GMT+1)
System Uptime: 0 days 9:56:52.791
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8001fd5200, fffff880069b08b8, 0, 2}

Unable to load image \SystemRoot\system32\DRIVERS\atikmpag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : atikmpag.sys ( atikmpag+78b8 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8001fd5200, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880069b08b8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
atikmpag+78b8
fffff880`069b08b8 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`047db9c8 fffff880`03e6d000 : 00000000`00000116 fffffa80`01fd5200 fffff880`069b08b8 00000000`00000000 : nt!KeBugCheckEx
fffff880`047db9d0 fffff880`03e6cd0a : fffff880`069b08b8 fffffa80`01fd5200 fffffa80`032cad50 fffffa80`019ce410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`047dba10 fffff880`03f13f07 : fffffa80`01fd5200 00000000`00000000 fffffa80`032cad50 fffffa80`019ce410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`047dba40 fffff880`03f3db75 : 00000000`ffffffff 00000000`0022f643 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`047dbb20 fffff880`03f3c2bb : 00000000`00000102 00000000`00000000 00000000`0022f643 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`047dbb50 fffff880`03f0f2c6 : ffffffff`ff676980 fffffa80`019ce410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`047dbbf0 fffff880`03f3be7a : 00000000`00000000 fffffa80`022ee220 00000000`00000080 fffffa80`019ce410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`047dbd00 fffff800`03767fee : fffff880`fffffc32 fffffa80`01dd9b60 fffffa80`018479e0 fffff800`034c4757 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`047dbd40 fffff800`034be5e6 : fffff800`03642e80 fffffa80`01dd9b60 fffffa80`031e9400 fffff880`01244cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`047dbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+78b8
fffff880`069b08b8 4883ec28 sub rsp,28h
SYMBOL_NAME: atikmpag+78b8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea760b6
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys

Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8001fd5200, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880069b08b8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

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


FAULTING_IP:
atikmpag+78b8
fffff880`069b08b8 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`047db9c8 fffff880`03e6d000 : 00000000`00000116 fffffa80`01fd5200 fffff880`069b08b8 00000000`00000000 : nt!KeBugCheckEx
fffff880`047db9d0 fffff880`03e6cd0a : fffff880`069b08b8 fffffa80`01fd5200 fffffa80`032cad50 fffffa80`019ce410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`047dba10 fffff880`03f13f07 : fffffa80`01fd5200 00000000`00000000 fffffa80`032cad50 fffffa80`019ce410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`047dba40 fffff880`03f3db75 : 00000000`ffffffff 00000000`0022f643 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`047dbb20 fffff880`03f3c2bb : 00000000`00000102 00000000`00000000 00000000`0022f643 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`047dbb50 fffff880`03f0f2c6 : ffffffff`ff676980 fffffa80`019ce410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`047dbbf0 fffff880`03f3be7a : 00000000`00000000 fffffa80`022ee220 00000000`00000080 fffffa80`019ce410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`047dbd00 fffff800`03767fee : fffff880`fffffc32 fffffa80`01dd9b60 fffffa80`018479e0 fffff800`034c4757 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`047dbd40 fffff800`034be5e6 : fffff800`03642e80 fffffa80`01dd9b60 fffffa80`031e9400 fffff880`01244cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`047dbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
atikmpag+78b8
fffff880`069b08b8 4883ec28 sub rsp,28h
SYMBOL_NAME: atikmpag+78b8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmpag
IMAGE_NAME: atikmpag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ea760b6
FAILURE_BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
BUCKET_ID: X64_0x116_IMAGE_atikmpag.sys
Followup: MachineOwner
---------

14 godina
offline
BSOD - što, zašto i kako

Ova greška ti je do ATI driver-a....jesi li stavljao neku beta verziju drivera ili slično? Probaj napraviti uninstall driver-a od grafičke te staviti zadnju "službenu" verziju...

Moj PC  
0 0 hvala 0
14 godina
offline
BSOD - što, zašto i kako

Dobio jedan krasni bsod

 Moze pomoc?

 

 

BCCode:    d1
  BCP1:    000000000000009C
  BCP2:    0000000000000002
  BCP3:    0000000000000001
  BCP4:    FFFFF88007F5DE7D
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    256_1

Poruka je uređivana zadnji put uto 13.12.2011 12:48 (drahic).
Moj PC  
0 0 hvala 0
14 godina
offline
Re: BSOD - što, zašto i kako
drahic kaže...

Dobio jedan krasni bsod

 Moze pomoc?

 

 

BCCode:    d1
  BCP1:    000000000000009C
  BCP2:    0000000000000002
  BCP3:    0000000000000001
  BCP4:    FFFFF88007F5DE7D
  OS Version:    6_1_7601
  Service Pack:    1_0
  Product:    256_1

Skini ovaj programčić pa pošalji što ti je on napisao u analizi memory dump-a.

14 godina
offline
BSOD - što, zašto i kako

Evo od danas

 

crash dump file: C:\Windows\Minidump\121311-21777-01.dmp

This was probably caused by the following module dxgmms1+0xBE7D

Bugcheck code: 0xD1 (0x9C, 0x2, 0x1, 0xFFFFF88007F5DE7D)

description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

description: DirectX Graphics MMS

 

I evo od jucer ali sam stavio druge drivere za graficku

crash dump file: C:\Windows\Minidump\121311-29920-01.dmp

This was probably caused by the following module atikmpag+0x745C

Bugcheck code: 0x116 (0xFFFFFA8006D1F160, 0xFFFFF880046AE45C, 0x0, 0x2)

error-VIDEO TDR ERROR

description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).

Poruka je uređivana zadnji put uto 13.12.2011 13:44 (drahic).
Moj PC  
0 0 hvala 0
13 godina
neaktivan
offline
BSOD - što, zašto i kako
dobar dan

ovako imam jedan laptop na popravku radi se o dell inspirion 1525
laptop je bio na servisu 3 puta 2 puta radi harda 1 radi windowsa i cdroma

lap je originalno zamisljen za vistu trenutno je na njemu win7 i sa vistom i sa win7 stalo se rusi i javlja bsod
javlja ovu gresku:

BCCode: c2
BCP1: 00000007
BCP2: 00001097
BCP3: 00000000
BCP4: 964F8008
OS Version: 6_1_7600
Service pack: 0_0
Product: 256 1

Files that help describe the problem
c:\Windows\Minidump\121211-23181-01.dmp
c:\Windows\Temp|WER-29702-0.sysdata.xml

neznam o cem se radi ali stalno se rusi probao sam instalirat win xp ali nazalost nedopusta mi i javlja mi da provjerim dali je hard dobro spojen i nezeli instalirat

HELP!!!
Moj PC  
0 0 hvala 0
14 godina
offline
Re: BSOD - što, zašto i kako
drahic kaže...

Evo od danas

 

crash dump file: C:\Windows\Minidump\121311-21777-01.dmp

This was probably caused by the following module dxgmms1+0xBE7D

Bugcheck code: 0xD1 (0x9C, 0x2, 0x1, 0xFFFFF88007F5DE7D)

description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.

description: DirectX Graphics MMS

 

I evo od jucer ali sam stavio druge drivere za graficku

crash dump file: C:\Windows\Minidump\121311-29920-01.dmp

This was probably caused by the following module atikmpag+0x745C

Bugcheck code: 0x116 (0xFFFFFA8006D1F160, 0xFFFFF880046AE45C, 0x0, 0x2)

error-VIDEO TDR ERROR

description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).

ovo mi se sve čini kao problemi sa driverima od grafičke...probaj deinstalirati stare drivere i napraviti čistu instalaciju najnovijih službenih drivera za grafičku...

ako to ne upali, de napiši svoje komponente....

14 godina
offline
Re: BSOD - što, zašto i kako
bubach1989 kaže...
dobar dan

ovako imam jedan laptop na popravku radi se o dell inspirion 1525
laptop je bio na servisu 3 puta 2 puta radi harda 1 radi windowsa i cdroma

lap je originalno zamisljen za vistu trenutno je na njemu win7 i sa vistom i sa win7 stalo se rusi i javlja bsod
javlja ovu gresku:

BCCode: c2
BCP1: 00000007
BCP2: 00001097
BCP3: 00000000
BCP4: 964F8008
OS Version: 6_1_7600
Service pack: 0_0
Product: 256 1

Files that help describe the problem
c:\Windows\Minidump\121211-23181-01.dmp
c:\Windows\Temp|WER-29702-0.sysdata.xml

neznam o cem se radi ali stalno se rusi probao sam instalirat win xp ali nazalost nedopusta mi i javlja mi da provjerim dali je hard dobro spojen i nezeli instalirat

HELP!!!

Skini ovaj programčić pa pošalji što ti je on napisao u analizi memory dump-a.

16 godina
neaktivan
offline
BSOD - što, zašto i kako

Dali taj program za čitanje BSOD-a mora biti non stop upaljen, jer meni se dešava BSOD u nepravilnim razmacima, i ne mogu skužiti u kojem trenutku će se pojaviti?

Moj PC  
0 0 hvala 0
15 godina
offline
Re: BSOD - što, zašto i kako
the_dammed kaže...

Dali taj program za čitanje BSOD-a mora biti non stop upaljen, jer meni se dešava BSOD u nepravilnim razmacima, i ne mogu skužiti u kojem trenutku će se pojaviti?

Ne. Svaki put kad se dogodi BSOD kreira se file u C:\WINDOWS\minidump. Taj file analiziraš s tim programom ili ga upload-aj negdje i postavi ode da ga netko analizira

13 godina
neaktivan
offline
BSOD - što, zašto i kako

@plavi83

 

evo napravio sam analizu i bilo je 3 crasha

 

znaci ovo je prvi koji se desio kad je bio lap kod mene

 

"On Tue 13.12.2011. 1:10:35 GMT your computer crashed

crash dump file: C:\Windows\Minidump\121211-23181-01.dmp

This was probably caused by the following module: ntkrnlpa.exe (nt+0x11F1B6) 

Bugcheck code: 0xC2 (0x7, 0x1097, 0x0, 0xFFFFFFFF964F8008)

Error: BAD_POOL_CALLER

file path: C:\Windows\system32\ntkrnlpa.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System"

 

sljedeca 2 su se desila kod cure kad je doso lap u njene ruke

 

"On Wed 14.12.2011. 6:48:25 GMT your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: win32k.sys (win32k!EngLpkInstalled+0xA13F) 

Bugcheck code: 0x50 (0xFFFFFFFFFFA58AEC, 0x0, 0xFFFFFFFF82B7604D, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\win32k.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Multi-User Win32 Driver"

 

"On Wed 14.12.2011. 6:48:25 GMT your computer crashed

crash dump file: C:\Windows\Minidump\121311-18220-01.dmp

This was probably caused by the following module: win32k.sys (win32k+0xCCCF0) 

Bugcheck code: 0x50 (0xFFFFFFFFFFA58AEC, 0x0, 0xFFFFFFFF82B7604D, 0x0)

Error: PAGE_FAULT_IN_NONPAGED_AREA

file path: C:\Windows\system32\win32k.sys

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: Multi-User Win32 Driver"

 

znaci koliko ja vidim 3 puta se dogodio crash u 2 dana otkad su novi windowsi i sva 3 su razlicita

u cemu bi mogo bit problem

Moj PC  
0 0 hvala 0
16 godina
offline
Re: BSOD - što, zašto i kako

@ bubach

- ubaci install medij (nije obavezno)

- iz CMDa pokreni ''sfc /csannow'', nakon tog ''scanreg /fix''

- memtest, može s bootCDa, win, hirens, linux... preporuka MemTest86+ desetak minuta.

 

Problemi koje računalo ima su ozbiljni, treba testirati sve, AV, memtest.. ali najčešći uzrok (osim neispravnog RAMa) su alati kao CC, Mehanic i sl. (tj. korisnici), rijeđe zbog drivera npr VGA-HDA..., ... ili 'jogurt' koji se slučajno nađe na računalu.

C64/TurboModul-OpenSourceProject.org.cn.部分作品为网上收集整理,供开源爱好者学习使用
13 godina
neaktivan
offline
Re: BSOD - što, zašto i kako

znaci vjerojatno je memorija krepala pa zato zajebava ako sam dobro skuzio

14 godina
offline
BSOD - što, zašto i kako

lako vjerojatno...ali zato probaj napraviti ove testove kako je ihush napisao da budeš siguran...

Moj PC  
0 0 hvala 0
13 godina
neaktivan
offline
BSOD - što, zašto i kako

ok hvala na pomoci javim ako sam rijesio problem i koji je problem bio

Moj PC  
0 0 hvala 0
E-mail:
Lozinka:
 
vrh stranice