BSOD - što, zašto i kako

Može neko objašnjenje toga? :p

  Dobro proveri mrezne drivere ili mozda ste stavili neki program za nadziranje mreze (download/upload ili "mjerni" program)

Ako je Wi-Fi kartica probajte staviti drivere preko Windows Updatea

Evo i mojeg problema.... isto mi se javlja BSOD pri pokretanju određenih igara, dakle sve je normalno kod NFS, Tomb Raidera, Assassin Creeda i brda igara, ali kad pokreće LEGO Batman ili LEGO Star Wars dolazi mi do reseta i plavog ekrana.... ali najnoviji LEGO Harry Potter radi normalno...  to je identičan ovaj ekran sa slike:

Hvala....

Jučer nisam imao vremena se pozabaviti uputama iz prvog posta pa sam samo ovu sliku BSOD-a stavio jer očito je da je grafička tu problematična i taj ati3duag.dll problem.... ali eto sad i analiza...

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini030411-05.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols

Executable search path is: 

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x805634c0

Debug session time: Fri Mar  4 16:10:30.687 2011 (UTC + 1:00)

System Uptime: 0 days 0:02:08.718

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

....

Loading User Symbols

Loading unloaded module list

............

Unable to load image ati3duag.dll, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ati3duag.dll

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

*                                        *

*             Bugcheck Analysis                   *

*                                        *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, bf314b7c, a9b8da64, 0}

Probably caused by : ati3duag.dll ( ati3duag!IRInst::SetConstArg+2bc )

Followup: MachineOwner

---------

3: kd> 

3: kd> !analyze -v

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

*                                        *

*             Bugcheck Analysis                   *

*                                        *

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

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: c0000005, The exception code that was not handled

Arg2: bf314b7c, The address that the exception occurred at

Arg3: a9b8da64, Trap Frame

Arg4: 00000000

Debugging Details:

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

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

FAULTING_IP: 

ati3duag!IRInst::SetConstArg+2bc

bf314b7c 21710c      and    dword ptr [ecx+0Ch],esi

TRAP_FRAME:  a9b8da64 -- (.trap 0xffffffffa9b8da64)

ErrCode = 00000002

eax=e141bd84 ebx=e141bd80 ecx=00000000 edx=00000001 esi=f7ffffff edi=e141b010

eip=bf314b7c esp=a9b8dad8 ebp=00000000 iopl=0      nv up ei pl zr na pe nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000        efl=00010246

ati3duag!IRInst::SetConstArg+0x2bc:

bf314b7c 21710c      and    dword ptr [ecx+0Ch],esi ds:0023:0000000c=????????

Resetting default scope

CUSTOMER_CRASH_COUNT:  5

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  LEGOStarWarsSag

LAST_CONTROL_TRANSFER:  from bf2f4318 to bf314b7c

STACK_TEXT:  

a9b8db0c bf2f4318 00000000 00000001 00000000 ati3duag!IRInst::SetConstArg+0x2bc

a9b8db7c 00000000 804dc605 e401dff0 e401a000 ati3duag!PSO2IMeetsDependencies+0x25e8

STACK_COMMAND:  kb

FOLLOWUP_IP: 

ati3duag!IRInst::SetConstArg+2bc

bf314b7c 21710c      and    dword ptr [ecx+0Ch],esi

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ati3duag!IRInst::SetConstArg+2bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ati3duag

IMAGE_NAME:  ati3duag.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  4d40a337

FAILURE_BUCKET_ID:  0x8E_ati3duag!IRInst::SetConstArg+2bc

BUCKET_ID:  0x8E_ati3duag!IRInst::SetConstArg+2bc

Followup: MachineOwner

---------

Jel ima tko ikakve savjete??? Hvala 

Može meni analiza onoga sa prošle stranice.

Molim da budete što brži jer mi se BSOD pojavljuje svakodnevno.

Mogu li odmah provjerit jesam li popravio problem reinstalacijom drivera ili da samo čekam?

http://hotfile.com/dl/109970669/d9104e0/031211-35537-01.dmp.html

pozz ljudi,moze li   netko ovo analizirati,moj debuger   javlja nekakve errore no ovo mi je jako hitno pa bih molio pomoc

Tražim vašu pomoć, jer sam već seve obišao.
Računalo mi se (neovisno o sustavu XP, W7)
U nasumičnim vremenskim razmacima restarta.

I bez obzira na zahtjevnost radnji, ili uopće jesam li ja šta u tom trenu kliknuo ili ne.
1. put su mi u servisu rekli da "sve prolazi testove", ali promjenili HDD i RAM
2. su promjenili HDD (reko je da nevalja) i premjestili memorije na druge slotove.
No sve je i dalje isto.
Prilažem 2/4 dump-a.
Najuljudnije molim za pomoć i razumijevanje :o
____________________________________________________

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: c0000005, The exception code that was not handled
Arg2: 83052449, The address that the exception occurred at
Arg3: a6449be8, Trap Frame
Arg4: 00000000

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************

ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 82e16000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

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

FAULTING_IP:
nt+23c449
83052449 ff20 jmp dword ptr [eax]

TRAP_FRAME: a6449be8 -- (.trap 0xffffffffa6449be8)
ErrCode = 00000000
eax=00000002 ebx=00000000 ecx=864fb470 edx=8813ea08 esi=8813ea08 edi=8829dc50
eip=83052449 esp=a6449c5c ebp=a6449c7c iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt+0x23c449:
83052449 ff20 jmp dword ptr [eax] ds:0023:00000002=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

CURRENT_IRQL: 0

MISALIGNED_IP:
nt+23c449
83052449 ff20 jmp dword ptr [eax]

LAST_CONTROL_TRANSFER: from 83066382 to 83052449

STACK_TEXT:


STACK_COMMAND: kb

FOLLOWUP_IP:
nt+23c449
83052449 ff20 jmp dword ptr [eax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt+23c449

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

MODULE_NAME: hardware

FAILURE_BUCKET_ID: IP_MISALIGNED

BUCKET_ID: IP_MISALIGNED

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

jel mi može tko pomoć,molim vas...vec sam lud,ne znam sta bi napravio....

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\Mini031411-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols

Executable search path is: 

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Machine Name:

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720

Debug session time: Mon Mar 14 16:38:51.828 2011 (UTC + 1:00)

System Uptime: 0 days 1:31:00.550

Unable to load image ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

.......

Loading User Symbols

Loading unloaded module list

.........

Unable to load image RtkHDAud.sys, Win32 error 0n2

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

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

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

*                                        *

*             Bugcheck Analysis                   *

*                                        *

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

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, b5afebee, b45e570c, 0}

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

Unable to load image ks.sys, Win32 error 0n2

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

Unable to load image sysaudio.sys, Win32 error 0n2

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

Probably caused by : RtkHDAud.sys ( RtkHDAud+148bee )

Followup: MachineOwner

---------

0: kd> !analyze -v

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

*                                        *

*             Bugcheck Analysis                   *

*                                        *

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)

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: c0000005, The exception code that was not handled

Arg2: b5afebee, The address that the exception occurred at

Arg3: b45e570c, Trap Frame

Arg4: 00000000

Debugging Details:

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

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

FAULTING_IP: 

RtkHDAud+148bee

b5afebee 8982bc000000   mov    dword ptr [edx+0BCh],eax

TRAP_FRAME:  b45e570c -- (.trap 0xffffffffb45e570c)

ErrCode = 00000002

eax=00000001 ebx=88ca1178 ecx=886fd028 edx=00000000 esi=b5b9ecf8 edi=b5b9ecf8

eip=b5afebee esp=b45e5780 ebp=b45e5784 iopl=0      nv up ei pl zr na pe nc

cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000        efl=00010246

RtkHDAud+0x148bee:

b5afebee 8982bc000000   mov    dword ptr [edx+0BCh],eax ds:0023:000000bc=????????

Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  war3.exe

LAST_CONTROL_TRANSFER:  from b5ad1e6a to b5afebee

STACK_TEXT:  

WARNING: Stack unwind information not available. Following frames may be wrong.

b45e5784 b5ad1e6a 00000000 88b4bbe8 88ca1178 RtkHDAud+0x148bee

b45e59ec b59a497d 88ca1178 0000000c 88cb4008 RtkHDAud+0x11be6a

b45e5a04 b59a49cf 88cb4008 88b4bbe8 e1bfa3a4 portcls!PcDispatchProperty+0x130

b45e5a2c b9b27f5c 00000004 88e32ef8 88e32ef0 portcls!PropertyItemPropertyHandler+0x2b

b45e5a90 b9b27ed9 88cb4008 0000000c e1bfa3a4 ks!KspPropertyHandler+0x616

b45e5ab4 b59a26a9 88cb4008 0000000c e1bfa318 ks!KsPropertyHandler+0x19

b45e5ac8 b59af70f 88cb4008 0000000c e1bfa318 portcls!PcHandlePropertyWithTable+0x1b

b45e5b00 b59a274d 88b4bb68 8a11fc80 88cb4008 portcls!CPortPinWaveCyclic::DeviceIoControl+0x1e5

b45e5b1c b9b27f1f 8a11fc80 88cb4008 b45e5b44 portcls!DispatchDeviceIoControl+0x49

b45e5b2c b59a28c0 8a11fc80 88cb4008 8a11fd38 ks!KsDispatchIrp+0x126

b45e5b44 b59a2881 8a11fc80 88cb4008 b45e5b78 portcls!KsoDispatchIrp+0x43

b45e5b54 b5d7e08e 8a11fc80 88cb4008 00000000 portcls!PcDispatchIrp+0x5f

b45e5b78 804ef19f 8a11fc80 00000004 88cb4008 RtkHDAud+0x3c808e

b45e5bd8 b4d822a2 88cb4008 88e32ef8 e3802458 nt!MiFlushSectionInternal+0x256

b45e5c30 b9b27f95 8a1a08d0 88cb4008 b45e5c64 sysaudio!CPinInstance::PinDispatchIoControl+0x153

b45e5c40 804ef19f 8a1a08d0 88cb4008 806e7410 ks!DispatchDeviceIoControl+0x28

b45e5c64 8058081c 8a1a08d0 88cb4008 8a3da7b0 nt!MiFlushSectionInternal+0x256

b45e5d00 80579298 00004894 000043b0 00000000 nt!PsGetNextProcess+0xa

b45e5d34 8054167c 00004894 000043b0 00000000 nt!SeAccessCheckByType+0x411

b45e5d64 7c90e514 badb0d00 0012f198 00000000 nt!RtlIpv4StringToAddressExW+0xfd

b45e5d78 00000000 00000000 00000000 00000000 0x7c90e514

STACK_COMMAND:  kb

FOLLOWUP_IP: 

RtkHDAud+148bee

b5afebee 8982bc000000   mov    dword ptr [edx+0BCh],eax

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  RtkHDAud+148bee

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: RtkHDAud

IMAGE_NAME:  RtkHDAud.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4670ff4f

FAILURE_BUCKET_ID:  0x8E_RtkHDAud+148bee

BUCKET_ID:  0x8E_RtkHDAud+148bee

Followup: MachineOwner

---------

  Makni sve sto emulira CD/DVD pogone/snimace/citace (Daemon toolse, Alcohol 120%, Clone CD...) Ugasi/onemoguci/disjeblaj VirtualBox ali prvo ono sa virtualnim masinama

Nadam se da si provjerio memoriju sa Memtest86+?

  Nisam rekao da deinstaliras virtualca vec da ga privremeno onesposobis od pokretanja zajedno sa Windowsima (msconfig) tek toliko da izoliras problem sa BSOD-om. A sto se tice Alcohola, Daemona i ostale bratije samo mogu reci   - Lose...vrlo, vrlo lose!

Nadam se da imas originalan Alcohol 120% jer koliko se ja sjecam nije postojao krek za njega a da nije bio opaki virus. Sad ne znam kakva je situacija (sa krekovima) ali i ne interesuje me.

Sve u svemu, Alcohol 120% deinstaliraj sa oficijalnim deinstalerom od proizvodaca (ako ima takvog) nemoj upotrebljavati Revo Uninstaller ili slicno posto je vrlo agresivan i moze povuci na dno i ostatak podsustava zaduzen za CD/DVD pogone (snimanje i same pogone)

Upravo i tvoj problem vuce korjene od Alcohola, je...Alcohol nema svoj drive u My Computer ali stavlja svoj driver (Device Manager---Show hiden devices)

Koliko vidim imas i ATI graficku. Jes li instalirao nove divere ili maknuo stare?

Jos jednom, mada nemam pravo ponasati se ovako "pedagoski"

Pitanje i pomoc oko BSOD-a postavljate tek kada ste testirali memoriju sa Memtestom86+, vratili BIOS na setup defaults i naravno, 100% ste sigurni da vam je napajanje ispravno i ispunjuje norme vaseg sustava sto se tice vataze

Evo nesto opcenito o bsod-u mozda nekom pomogne.

http://www.howcast.com/videos/224670-How-To-Fix-a-Windows-BSOD

  ATI driveri! Provjeri temperaturu CPU-a i graficke

BTW

atikmdag.sys je dio ATI drivera a dxgkrnl.sys je dio DirectX Graphics Kernela. Jesi li provjerio RAM? Ako nisi onda pravac na Memtest86+ (5-6 prolaza)

Da li se BSOD ponovio? Da li je ovo prvi put? Ako da moze biti i do oscilacija napona na gradskoj mrezi