BSOD - što, zašto i kako

-prepusti BIOSu postavke.

-ntoskrnl je osnova OSa -kernel, on sam nemože biti krivac (osim da je u pitanju virus pa poskeniraj 'just in case' s MBAMom).

 -postavke RAMa se rade prema CPU i chipsetu (BIOS je postavio optimalno), tvornička deklaracija 1333-9 je samo normalna granica.

-obavezno provrti MemTest86+ (ima na svim liveCDima npr ubuntu i na repairu sedmice)

.. počni sumnjati u ispravnost ploče (možda CPU). To je problem s novim serijama CPU+MBO što ih obično netko prije prodaje 'izmrcvari', možda čak u BUGovom testlabu.

konkretniji test bi bilo korištenje nekog npr ubuntua nekoliko sati .. jedan dan. (provjeri svoju verziju sedmice...tj. dali je normalna aktivacija ili ona druga?)

Evo novi BSOD....ali ovaj put sa greskom ntfs.sys. Poludit cu vise.... :/

Evo i moj dmp file....pa ako netko moze pogledat, bio bih vrlo zahvalan.

http://hotfile.com/dl/104887280/a116227/021411-25334-01.rar.html

Disableao sam Virtual CloneDrive i sada sam probao par puta s USB-om (nemam sad eksterni hard pri ruci) i sve je OK.

Autoplay je omogućen, ali evo, sada ću i njega isključiti. Btw. imam i Bluetooth donge..hehe..

AV je Avast!. Hvala, u svakom slučaju. Ako se pojavi opet, probat ću i iskopčavanjem Bluetootha.

Evo i minidumpova, bio bih zahvalan da netko pogleda

http://www.fileserve.com/file/bwZNRbf

EDIT: Nova greška ovaj put je PAGE_FAULT_IN_NONPAGED_AREA pa sve više sumnjam na RAM.

http://www.fileserve.com/file/k7JdFcM (minidump)

Smanjio sam OC, sad sam na 3.4 GHz i ostavit ću ga tako nema veze jer mi je lik koji mi je stavljao Windoze rekao da se hal.dll i kernel ruše prvenstveno zbog lošeg OC-a. Očito nisam baš imao sreće pri kupnji chipa; grafe su testirane sat vremena u FurMarku i nije se rušilo ništa kao ni u igrama. Većinu BSOD-a je uzrokovao Avastov driver s kojim dosta ljudi ima problema inače (svi oni preporučaju Microsoft Security Essentials za koji nisam ni čuo moram priznati), ali valjda je rješeno sa RegCureom koji je našao preko 900 grešaka...

Javim kada završim sa Memtestom, par sati će biti dosta; latencije su dobre to sam provjerio odmah. RAM je Corsair, ne znam ako to nešto znači danas više ionako.

Deinstaliran RegCure i napravljen full scan sa MBAM-om bez ikakvih zaraženih fajlova. Nije mi se javio BSOD već skoro 24 sata, a to je napredak sigurno.

  Prvo za OFF topic. Gigabyte nije glup, skoro na svim maticnim first boot device je CD-ROM a na nekima je floppy (ako ga ima) i naravno sve to zavisi od BIOS venodora (da li je AMI ili Phoenix ...) Dakle stavis rucno first boot da ti bude HDD i mirna backa

Sto se tice testiranja video memorije, testiraj sa ovim

Video Memory Stress Test 1.7.116 

Mislim da bi trebao testirati u ''Clean Enviromentu'' odnosno u DOS-u jer ćeš samo tako vidjeti koje ti greške izbacuje. Dobio si downloadom podfolder di ti je iso image file i samo ga sprži na CD (tako ću ja) i pokreni iz BIOS-a direktno.

Vidim da imaš Intelovu integriranu grafiku, a ovaj igxpdx32.dll je njen driver koji se čini nekako corruptao putem tako da je odgovor na tvoje pitanje ''da''  Potraži na netu neke tutoriale kako to ispraviti, ima sigurno.

neznam da li će ovo kome pomoći, no do prije mjesec dana sam imao konstantne BSOD-ove u sasvim različitim situacijama (imate moje postove iznad), unatoč svakakvim pokušajima da to riješim (formatiranje diska, reinstalacija, testiranje i zamjena nekih komponenti i sl.). ni na kraj pameti mi nije bilo da bi disejblana wireless kartica mogla biti uzrok. bezveze sam ju izvadio van, jer ju nisam koristio mjesecima, i voila, nema vise plavih ekrana za mene :D

neznam kako\zašto, al eto, živim happily ever after :D

tak da, provjerite i ostale komponente, možda vam one zagorčavaju život, mene je wireless kartica počela zezat mjesec-dva nakon kaj sam ju disejblao.

Može pomoč oko ovoga:

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


Loading Dump File [C:\Windows\Minidump\022711-35365-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 \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82e54000 PsLoadedModuleList = 0x82f9c810
Debug session time: Sat Feb 26 22:46:24.497 2011 (UTC + 1:00)
System Uptime: 0 days 0:00:22.105
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
...............................................................
................................................................
..............
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\system32\DRIVERS\athur.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for athur.sys
*** ERROR: Module load completed but symbols could not be loaded for athur.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {c0000005, 92286874, 96eecc78, 96eec850}

***** 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                                     ***
***                                                                   ***
*************************************************************************
Probably caused by : athur.sys ( athur+d874 )

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

2: 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: c0000005, The exception code that was not handled
Arg2: 92286874, The address that the exception occurred at
Arg3: 96eecc78, Exception Record Address
Arg4: 96eec850, Context Record Address

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.

MODULE_NAME: athur

FAULTING_MODULE: 82e54000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a30ef61

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

FAULTING_IP:
athur+d874
92286874 8b88f8210000    mov     ecx,dword ptr [eax+21F8h]

EXCEPTION_RECORD:  96eecc78 -- (.exr 0xffffffff96eecc78)
ExceptionAddress: 92286874 (athur+0x0000d874)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 000021f8
Attempt to read from address 000021f8

CONTEXT:  96eec850 -- (.cxr 0xffffffff96eec850)
eax=00000000 ebx=00000000 ecx=0000000a edx=87931020 esi=879f2a18 edi=00000000
eip=92286874 esp=96eecd40 ebp=96eecd50 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210246
athur+0xd874:
92286874 8b88f8210000    mov     ecx,dword ptr [eax+21F8h] ds:0023:000021f8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 830629df to 92286874

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
96eecd50 830629df 87931020 ba5ff329 00000000 athur+0xd874
96eecd90 82f141d9 922867f0 87931020 00000000 nt+0x20e9df
00000000 00000000 00000000 00000000 00000000 nt+0xc01d9


FOLLOWUP_IP:
athur+d874
92286874 8b88f8210000    mov     ecx,dword ptr [eax+21F8h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  athur+d874

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  athur.sys

STACK_COMMAND:  .cxr 0xffffffff96eec850 ; kb

BUCKET_ID:  WRONG_SYMBOLS

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

2: kd> !analyze-v
No export analyze-v found
2: 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: c0000005, The exception code that was not handled
Arg2: 92286874, The address that the exception occurred at
Arg3: 96eecc78, Exception Record Address
Arg4: 96eec850, Context Record Address

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.

MODULE_NAME: athur

FAULTING_MODULE: 82e54000 nt

DEBUG_FLR_IMAGE_TIMESTAMP:  4a30ef61

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

FAULTING_IP:
athur+d874
92286874 8b88f8210000    mov     ecx,dword ptr [eax+21F8h]

EXCEPTION_RECORD:  96eecc78 -- (.exr 0xffffffff96eecc78)
ExceptionAddress: 92286874 (athur+0x0000d874)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000000
   Parameter[1]: 000021f8
Attempt to read from address 000021f8

CONTEXT:  96eec850 -- (.cxr 0xffffffff96eec850)
eax=00000000 ebx=00000000 ecx=0000000a edx=87931020 esi=879f2a18 edi=00000000
eip=92286874 esp=96eecd40 ebp=96eecd50 iopl=0         nv up ei pl zr na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00210246
athur+0xd874:
92286874 8b88f8210000    mov     ecx,dword ptr [eax+21F8h] ds:0023:000021f8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x7E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 830629df to 92286874

STACK_TEXT: 
WARNING: Stack unwind information not available. Following frames may be wrong.
96eecd50 830629df 87931020 ba5ff329 00000000 athur+0xd874
96eecd90 82f141d9 922867f0 87931020 00000000 nt+0x20e9df
00000000 00000000 00000000 00000000 00000000 nt+0xc01d9


FOLLOWUP_IP:
athur+d874
92286874 8b88f8210000    mov     ecx,dword ptr [eax+21F8h]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  athur+d874

FOLLOWUP_NAME:  MachineOwner

IMAGE_NAME:  athur.sys

STACK_COMMAND:  .cxr 0xffffffff96eec850 ; kb

BUCKET_ID:  WRONG_SYMBOLS

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