BSOD svako malo

[Gigi1]

Dakle pojavljuje mi se BSOD cca svakih 2 sata(nekad i svakih 10 min, a nekad ga nema po 4-5 sati), problem se poceo javljati pred 5 dana i neovisan je o razini opterecenja racunala.
Radi se o konfi iz siga(gigabyte p55a ud3r, i7 860, gskill 2x2gb ddr3 ram, raid0 od dva wd blue 1TB hhd-a, 460gtx i dvd prža pioneer) koju sa vratio na defaultne postavke u BIOS-u kako oc nebi utjecao na stalna rušenja no napredka nije bilo.
Prvo sam mislio da je problem bio do nvidinih drivera(260.99) koje sam instalirao pred 5/6 dana, no vracanjem na stare problem je ostao.
Otvaranjem crash dump-a u windbg vidjeh da jedina dva razlozloga rušenja su:

1.razlog: ntkrnlmp.exe

BugCheck 7F, {8, 80050031, 6f8, fffff8000309dec8}

Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8000309dec8

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff800030d4ca9 to fffff800030d5740

STACK_TEXT:
fffff880`03169de8 fffff800`030d4ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`03169df0 fffff800`030d3172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03169f30 fffff800`0309dec8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`071b1f90 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x60


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!KiDoubleFaultAbort+b2
fffff800`030d3172 90 nop

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: nt!KiDoubleFaultAbort+b2

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 4c1c44a9

FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2

Followup: MachineOwner




2.razlog: NETIO.SYS

BugCheck 7F, {8, 80050031, 6f8, fffff8000304fd28}

Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff8000304fd28

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


BUGCHECK_STR: 0x7f_8

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80003086ca9 to fffff80003087740

STACK_TEXT:
fffff880`03169de8 fffff800`03086ca9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`03169df0 fffff800`03085172 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`03169f30 fffff800`0304fd28 : 0000057c`00000000 0000057c`00000000 0000057c`00000000 0000057c`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`03186000 fffff800`0304ff07 : fffffa80`060167c8 00000000`00000001 00000000`00000000 00000000`00000000 : nt!SepTokenFromAccessInformation+0x20
fffff880`03186030 fffff880`01844c5a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckFromState+0x9f
fffff880`03186720 fffff880`0184294f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!CompareSecurityContexts+0x6a
fffff880`03186790 fffff880`018449b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NETIO!MatchValues+0xef
fffff880`031867e0 fffff880`01844845 : fffffa80`0750d150 fffffa80`08ab8540 fffff880`03186a08 fffff880`03187140 : NETIO!FilterMatch+0x95
fffff880`03186830 fffff880`01845ccb : 00000000`00000000 00000000`00000000 fffff880`03187140 fffff880`031869f0 : NETIO!IndexListClassify+0x69
fffff880`031868b0 fffff880`01a40417 : fffff880`03186d88 fffff880`03186d88 fffff880`03187ac0 fffffa80`03de3030 : NETIO!KfdClassify+0xa4e
fffff880`03186c20 fffff880`01a3983e : fffff880`01b48690 00000000`00000000 fffffa80`073d3010 00000000`00000000 : tcpip!WfpAleClassify+0x57
fffff880`03186c60 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeSend+0x94e


STACK_COMMAND: kb

FOLLOWUP_IP:
NETIO!CompareSecurityContexts+6a
fffff880`01844c5a 448b442470 mov r8d,dword ptr [rsp+70h]

SYMBOL_STACK_INDEX: 5

SYMBOL_NAME: NETIO!CompareSecurityContexts+6a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: NETIO

IMAGE_NAME: NETIO.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4bbe946f

FAILURE_BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a

BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a

Followup: MachineOwner


Dakle NETIO.SYS i ntkrnlmp.exe

Što sam probao napraviti do sada, a problem je ostao:
-ponovno stavljanje drivera za chipset, graficku, zvucnu, LAN kontroler, raid
-vrcenje memstest-a(preko 200% bez errora), occt cpu stress kada bih imao srece da se komp ne srusi(90+minuta) i hdd error scan testa na hdtune programu bez grešaka
-stavljanjne zadnjeg BIOS-a na maticnu(F13)
-sve postavke vracene na defaultne vrijednosti u BIOS-u
-lupanje glavom o zid, dobacivanje svakavih psovki, razumljivih i nerazumljivih ostatku ljudskog roda

Još da napomenem da koristim raid 0 polje od 2 hdd-a, jedana particija (manja) je sistmska, dok je druga za sve ostalo.
Inace maticna mi je do sada „popapla“ tj. na njoj je crkla X-fi PCI zvucna kartica i 8800GTS graficka, dali same od sebe ili zbog ploce neznam, ono što znam da imam verziju 1.0, a vidio sam na gigabytovoj stranici da postoji i ver. 2.0
Windowsi 7 su na kompu i stari su cca 2-3 mjeseca, dakle relativno friški.

Što bi još mogo probat osim reinstalacije windowsa? Raid nebi htio razbijat jer neželim podatke izgubiti....hvala

[Sinac]

Pročitaj malo o ovome, nisu toga pošteđene ni matične ploče ostalih proizvođača. Mene je mučio taj problem ali samo prilikom prvog boota, sa ulaskom u BIOS i rebootom radilo je sve kako treba. Dakle, ostavi PC ugašen 2-3 sata, upali ga i odmah pokreni Memtest. Ja se nisam mogao načuditi tome, imam problema, uđem u BIOS i promijenim nešto glupo nevezano za RAM, recimo uključim/isključim serijski port i sve radi super. Idući dan kod paljenja opet BSOD. Uglavnom, nagnjavio se 2 mjeseca prije nego što sam uspio rješiti. Napominjem da je Memtest javljao greške samo kod prvog uključivanja PC-a, dakle nakon 2-3 sata mirovanja, nakon toga vrtio Memtest 4-5 sati i sve OK...

[Lewis]

I za slucaj da memtest nista ne pronadje probaj sa "gold memory" koji postoji na Hirens boot CDu do verzije 9.5. Meni je taj nasao erorore na Supertalet RAMu unutar 5 minuta a memtest je vrtio cijeli dan bez gresaka . Srecom garancija je prosla bez beda sa fotkama erorra iz GM-a.

[Gigi1]

Evo probao sam gold memory-ne nelazi greške, ali niti nije bio cold boot-isto kao s memtestom.

Sutra ujutro cu probat memtest i gold memory s cold boot-om pa cemo vidjet kaj bu bilo.

@Sinac citao sam malo postove s linka kojeg si mi dao, koliko sam skužio vecina ljudi tamo ima probleme kod cold boota i masu njih nemoze uopce uc u windowse iz prve, to nije slucaj kod mene, meni normalno svaki put uđe u win a tek onda se srusi nakon odredjenog vremena rada. No probat cu i cold boot memtest i gold memory, sutra update...


hvala na prijedlozima

[Gigi1]

evo update-a


sa cold boot-om niti memtest niti gold memory nisu pronašli greške.

zadnjih dan i pol/dva(cca 40-ak sati) nije mi se dogodio niti jedan BSOD, a nisam ništa mijenjao, dakle sve je ostalo isto kao i kada su se BSOD-i događali

ovo postaje frustrirajuce jer neznam na cemu se nalazim i kaj se događa, nekako imam osjecaj da ce me opet pogoditi BSOD-i za mjesec/dva.

nabavio sam dve gige(2x1GB) druge ddr3 memorije od frenda no kako nije bilo bsod-a neznam uopce dal da ih probavam...

Mozda još koji prijedlog/savjet?

[Sinac]

Jesi pogledao imaš li zadnju verziju BIOS-a na matičnoj?

[Gigi1]

Autor Sinac

Jesi pogledao imaš li zadnju verziju BIOS-a na matičnoj?

Je, imam zadnji bios F13.

[pocketGM]

To je najvjerojatnije problem do drivera.

CAUSE
This problem occurs if one or more of the processors in the computer:
•Require a microcode update that is not applied by the computer's basic input/output system (BIOS).
•Are damaged or defective.
•Are operating outside their specified ranges for temperature, power, or other conditions.


Probaj staviti nešto stariju inačicu biosa, a mogao bi i obavijestiti proizvođača matične o tim greškama.

Probaj reinstalaciju (znam da je long way arround), sa driverima koji su ti ranije radili bez problema. I nemoj instalirati nove drivere samo zato da bi bili zadnji izdani.. novo može biti i nedovoljno istestirano.

Najbolje instaliraj drivere za ploču sa njezinog CD-a, kao i za grafičku.
Provjeri uvijek pri update-u drivera što je točno izmijenjeno u njima i ako uopće - koliko dobiješ na performansama i znači li ti recimo 1% toliko.