[Leinö]

Peale nVidia driverite uuendamist 3.11 hakkas arvuti lampi BSoDi tekitama. Sai maha võetud, vanemad peale lastud, ikka sama jama. Natuke hiljem tulid Beta driverid välja, lasin need peale.
nVidia põhjustatud BSoD on kadunud, kuid nüüd on probleemiks ntoskrnl.exe ja ntkrnlmp.exe.
Googlest vastust ei leidnud.
Memtest erroreid ei leidnud.

Spoileris mõningad minidumpid.

Spoiler

On Wed 18.01.2012 18:52:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011812-29452-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800032D5FBC)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Wed 18.01.2012 18:52:22 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800032D5FBC)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Mon 16.01.2012 18:20:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011612-39296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032C21A6, 0xFFFFF8800D681240, 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.


On Sat 7.01.2012 8:50:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\010712-30451-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 Mon 26.12.2011 17:54:16 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122611-29952-01.dmp
This was probably caused by the following module: afd.sys (afd+0x6896A)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\afd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Ancillary Function Driver for WinSock
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
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 26.12.2011 0:24:15 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122611-38485-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032CCD8A, 0xFFFFF8800A643080, 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.


On Wed 21.12.2011 20:16:00 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122111-23259-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF88006E496E4)
Bugcheck code: 0x50 (0xFFFFF1000A40FC58, 0x0, 0xFFFFF8000327219F, 0x7)
Error: PAGE_FAULT_IN_NONPAGED_AREA
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.
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: Unknown .
Google query: Unknown PAGE_FAULT_IN_NONPAGED_AREA




On Fri 16.12.2011 19:48:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121611-28813-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71ED0)
Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program generated an exception which the error handler did not catch.
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 Mon 7.11.2011 16:20:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110711-28423-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0xC3BAE4)
Bugcheck code: 0x116 (0xFFFFFA8006575010, 0xFFFFF88012ABDAE4, 0xFFFFFFFFC000009A, 0x4)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 290.53
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 290.53
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 290.53 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR




On Thu 3.11.2011 15:42:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\110311-26629-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x1759C8)
Bugcheck code: 0x116 (0xFFFFFA8002A154E0, 0xFFFFF8801125E9C8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 290.53
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 290.53
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 290.53 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR

Arvuti specid,
CPU:AMD Phenom II x6 3.0GHz
MEM:Kingston HyperX PC3-12800 1600MHz 6GB (4+2)
HDD: Samsung F1 750GB
GPU:Palit GTX460 1GB Sonic Edition
MOBO: ASUS M5A99X EVO
HIIR:Logitech G9
PSU: Chieftec A135 series
SCR: 23" Dell U2311H

Käisin raua veel üle ka. Mälud on korralikult kinni, video samuti, prosel läks pasta vahetusse, seega see on ka korralikult kinni.

[RCC]

huvitav et üks video niipalju vigu saab tekitada, peale draiverite uuendamist ? mis seal siis enne olid ja miks oli vaja uuendada? see ntos jne on ikka videokaardi süü, seega pead ka betad maha võtma ja ned asemele panema mis enne olid. kõige paremini saad asjasse selgust kui kasutad vahepeal mõnda teist täiesti erinevat kaarti.

[Tomorrow]

Page_Fault ja IRQ vead viitavad pigem mäludele

[Leinö]

driverimajandust proovin täna, memtest mäludepoolset viga ei leidnud.

[RCC]

page fault ja irq ei ole kindlasti mälud, tegelikult võiks öelda, et mälust põhjustatud vigu ma polegi siiani kohanud, sõltumata sellest kas mälu on suvaline põrandaalune või tipp-firma. mälud lihtsalt kas töötavad või mitte

[Tomorrow]

RCC, Kui nad pole mälu omad siis mille omad nad on?
Hiljuti just sai proovitud mälu ülekiirendamist ja ebastabiilsel sättel sai just Page_Fault BSOD erroreid näha

Seega mälud võivad ka mingil määral töötada aga mingil hetkel annavad lihtsalt BSOD-i. Pole nii, et kas töötab või on kutu.

[Leinö]

Aga kuidas seda selgeks teha, kumb pulk järgi annab? mul 1 4GB ja 1 2GB pulk. BSoD esines näiteks mängude mängimisel, idles püsimisega probleeme ei olnud. Et 1 pulk välja võtta ja siis proovida mänge ei tule kõne alla, sest aint 2GB või 4GB pulgaga Win7 ei mängi välja

Installib augustis releasetuid drivereid praegu. Need olid viimased enne BSoDe. Intervallid BSoDidel on pikad, seega kuskil 10 päeva proovin. Kui vanade driveritega ei tule BSOD selle ajaga, siis oli probla nVidia uutes driverites.

[Tomorrow]

Win7 toimib ka 2GB pulgaga. Mitte nii kiiresti kui 4GB või rohkemaga aga testimiseks käib kah.

[RCC]

page_fault, ei tähenda mitte et mälu oleks rikkis, vaid et mälus pole kõik asjad seal kus nad olema peavad, lihtsalt maakeeli seletatuna kipuvad ühed programmid kasutama teiste programmide aadresse, või andmed mis peaks olema ühes kohas on teises kohas. ja siis on kohe paanika (page fault in nonpaged area) ja see pole ju võimalik, overklokkimisel on muidugi võimalik saada erinevaid vigu, aga sellisel juhul ei lähe arvutt üldse käimagi, enamasti. ainult 2 gb mängib välja küll, tuleb oma 7 taltsaks muuta

[Betamax]

[Leinö]

Soovitage head GPU stressitesti?
Vaatame, kas pinge all on uued vanad driverid korras.

Memtesti tegin paar päeva tagasi, lasin erinevatel pulkadel tegutseda kuskil 2 tunni jagu. Erroreid ei leidnud.


E: FurMark sobib GPU jaoks?

[Betamax]

Yeah, võid erinevaid katsetada.

[Leinö]

Spoiler

Kokku ei jooksnud vahepeal.

Panen memtesti veel igaksjuhuks jooksma.

[Betamax]

Leinö, sul Windows 7 Service Packi polegi installitud?

[Leinö]

Memtest ei leidnud midagi.

Betamax, tuleb nii välja. Ma isegi ei teadnud seda



Edit:

Ja keset FurMarki tuli BSoD

Spoiler

On Sat 21.01.2012 17:05:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012112-28594-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x705C0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800032D9B67, 0xFFFFF8800D11F9A0, 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.


On Wed 18.01.2012 18:52:22 GMT your computer crashed
crash dump file: C:\Windows\Minidump\011812-29452-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00)
Bugcheck code: 0xA (0x0, 0x2, 0x0, 0xFFFFF800032D5FBC)
Error: IRQL_NOT_LESS_OR_EQUAL
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 Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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.

[A.S.]

Tõsta see viimane dump fail näiteks http://www.osronline.com/page.cfm?name=analyze peale, WhoCrashed infot ei maksaks eriti uskuda.

Ega see memtest sul äkki mingi Windowsi all töötav asjandus polnud?
 

[Betamax]

Tõmba SP1 peale ja viimased driverid ka.

[Leinö]

A.S., tegin mälupulga bootivaks (cd-lugejat mul ei eksisteeri), restart, boot from USB ja hakkas testima.
SP1 laseb hetkel peale

Spoiler

Crash Dump Analysis provided by OSR Open Systems Resources, Inc. (http://www.osr.com)
Online Crash Dump Analysis Service
See http://www.osronline.com for more information
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03264000 PsLoadedModuleList = 0xfffff800`034a1e70
Debug session time: Sat Jan 21 12:05:56.135 2012 (UTC - 5:00)
System Uptime: 0 days 0:15:58.509
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800032d9b67, Address of the instruction which caused the bugcheck
Arg3: fffff8800d11f9a0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


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

FAULTING_IP:
nt!SeAccessCheckWithHint+237
fffff800`032d9b67 6300 movsxd eax,dword ptr [rax]

CONTEXT: fffff8800d11f9a0 -- (.cxr 0xfffff8800d11f9a0)
rax=00000000000000b8 rbx=0000000000000000 rcx=fffff8a011103140
rdx=fffff8a00ac72d80 rsi=fffff8a011103061 rdi=00000000000f0040
rip=fffff800032d9b67 rsp=fffff8800d120370 rbp=fffffa8009b4c850
r8=0000000000020000 r9=0000000000100000 r10=0000000000000000
r11=fffff8800d120368 r12=fffff8a011103140 r13=fffff8a00ac72cc8
r14=0000000000000001 r15=fffff8800d120518
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nt!SeAccessCheckWithHint+0x237:
fffff800`032d9b67 6300 movsxd eax,dword ptr [rax] ds:002b:00000000`000000b8=????????
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x3B

PROCESS_NAME: TrustedInstall

CURRENT_IRQL: 0

MISALIGNED_IP:
nt!SeAccessCheckWithHint+237
fffff800`032d9b67 6300 movsxd eax,dword ptr [rax]

LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800032d9b67

STACK_TEXT:
fffff880`0d120370 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!SeAccessCheckWithHint+0x237


FOLLOWUP_IP:
nt!SeAccessCheckWithHint+237
fffff800`032d9b67 6300 movsxd eax,dword ptr [rax]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!SeAccessCheckWithHint+237

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .cxr 0xfffff8800d11f9a0 ; kb

MODULE_NAME: hardware

FAILURE_BUCKET_ID: X64_IP_MISALIGNED

BUCKET_ID: X64_IP_MISALIGNED

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

€: viskasin uuemad videodriverid. Mängud hangusid 280 driveritega.

[A.S.]

Tundub siiski endiselt videokaardi viga olevat.
Proovimiseks korraks Hardware acceleration maha keerata? Display Advanced seadete alt kusagilt.
Naabrimeest aitas (https://foorum.hinnavaatlus.ee/viewtopic.php?t=519244), ta pole selle lahendusega aga rahul.

Või proovi BIOS uuendada. Kui muidugi midagi uuendada on.
http://support.asus.com/Download.aspx?SLanguage=en&m=M5A99X+EVO

P.S. Huvitav. Kui vanasti 32. bitise opsüsteemi omanikud niiviisi hädas olid, siis piisas tavaliselt videodraiveri vahetusest.
 

[RCC]

Huvitav jah, sellist jama oli alati ati-ga, aga mitte kunagi nvidiaga, kas kaart ise tehniliselt korras on? äkki vahetad välja?

[Leinö]

Spoiler

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000024, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800032e2ce6, address which referenced memory

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


READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80003511100
0000000000000024

CURRENT_IRQL: 2

FAULTING_IP:
nt!KeSetEvent+146
fffff800`032e2ce6 488b5220 mov rdx,qword ptr [rdx+20h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: csrss.exe

TRAP_FRAME: fffff8800931d870 -- (.trap 0xfffff8800931d870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000003 rbx=0000000000000000 rcx=fffffa8005489100
rdx=fffffa8005489168 rsi=0000000000000000 rdi=0000000000000000
rip=fffff800032e2ce6 rsp=fffff8800931da00 rbp=0000000000000000
r8=fffffa8005489168 r9=0000000000000000 r10=fffffffffffffffd
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
nt!KeSetEvent+0x146:
fffff800`032e2ce6 488b5220 mov rdx,qword ptr [rdx+20h] ds:fffffa80`05489188=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800032de1e9 to fffff800032dec40

STACK_TEXT:
fffff880`0931d728 fffff800`032de1e9 : 00000000`0000000a 00000000`00000024 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`0931d730 fffff800`032dce60 : 00000000`00000004 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`0931d870 fffff800`032e2ce6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`0931da00 fffff960`0012c7bc : 00000000`00000000 fffff960`00000002 00000000`00000000 fffffa80`05489168 : nt!KeSetEvent+0x146
fffff880`0931da70 fffff960`001240d3 : fffff900`c20cc3d0 00000000`00000001 00000000`00000004 fffff800`032e87f3 : win32k!SetWakeBit+0xf8
fffff880`0931daa0 fffff960`00124ae7 : 00000000`00000000 fffff960`00344cb0 00000000`00000004 00000000`00000001 : win32k!TimersProc+0x157
fffff880`0931daf0 fffff960`000b511c : fffffa80`0000007b 00000000`0000000f fffff880`00000001 ffffffff`80000414 : win32k!RawInputThread+0x9ab
fffff880`0931dbc0 fffff960`0013539a : fffffa80`00000002 fffff880`0939ff40 00000000`00000020 00000000`00000000 : win32k!xxxCreateSystemThreads+0x58
fffff880`0931dbf0 fffff800`032dded3 : fffffa80`08079060 00000000`00000004 000007ff`fffd4000 00000000`00000000 : win32k!NtUserCallNoParam+0x36
fffff880`0931dc20 000007fe`fcfd1eea : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01a7f9b8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fcfd1eea


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!SetWakeBit+f8
fffff960`0012c7bc 488b5c2430 mov rbx,qword ptr [rsp+30h]

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: win32k!SetWakeBit+f8

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4ecdcd5a

FAILURE_BUCKET_ID: X64_0xA_win32k!SetWakeBit+f8

BUCKET_ID: X64_0xA_win32k!SetWakeBit+f8

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

Kaart on välimuselt ok. Lahti ei hakka kakkuma. Ostetud sai Faunist 03.11.2010 ja garantii on 24kuud.

[Sven]

[Leinö]

Ja sai proovitud Sveni vana kaarti, HD4850-i, probleem ei esinenud. Seega asi pole kaardis, vaid mu windoozale ja uefile ei meeldi praegune rauakooslus vist


E:
Ja nüüd tuleb selliseid erroreid.
Nädala pärast teen formati. Valutu viis probleemidest vabanemiseks.

Spoiler

On Sun 29.01.2012 16:19:02 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012912-29218-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x2017E2)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800034A3BFE, 0x1, 0xC5FFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 285.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 285.62
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation KMODE_EXCEPTION_NOT_HANDLED




On Sun 29.01.2012 16:01:09 GMT your computer crashed
crash dump file: C:\Windows\Minidump\012912-35474-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x19CD65)
Bugcheck code: 0x3B (0xC000001D, 0xFFFFF88011266D65, 0xFFFFF8800E1652C0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 285.62
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 285.62
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.
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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation).
Google query: nvlddmkm.sys NVIDIA Corporation SYSTEM_SERVICE_EXCEPTION

[Dogbert]

RCC, kui mälu on rikkis, näiteks mingitel mäluaadressidel mingid bitid ühte olekusse "kinni jäänud" või annavad muul põhjusel sinna salvestatud väärtuste asemel välja midagi muud, siis pole page fault in nonpaged area BSOD-i tekkimine selle tõttu üldse võimatu - piisab sellest kui vigasest kohast küsitakse mäluaadressi ja saadakse vastuseks aadress, mis asub väljaspool programmile eraldatud piirkonda. On piisavalt seda kohatud. Samuti võib olla viga selline, mille puhul arvuti enamasti töötab normaalselt ja alles siis annab BSOD-i, kui vigast mälupiirkonda reaalselt kasutama hakatakse - näiteks rohkem mälu nõudva rakenduse kasutamisel. Samuti piisavalt palju ette tulnud nii minul kui teistel. Selle jaoks mälu testimise programmid ja riistvaralised testerid olemas ongi. Ei ole nii, et kas töötab korrektselt või ei tööta üldse - kohe üldse mitte.

Samuti võivad mõned vead sarnaneda klokkimisel saadavate vigadega, kui mälu parameetrid ei vasta täielikult nõutavatele ja vead tekivad juba SPD poolt ettenähtud töökiirustel. Sel juhul on ajutuselt võimalik asi tööle saada SPD-s määratust madalamate sageduste ja timingute kasutamisel või väikese ülepingega või nende kombineerimisega.

Ma ei tea, kust sinu info pärineb, aga see pole päris õige.

[Leinö]

Paistab, et videovahetus ja format ei aitand.
Sinist screeni enam ette ei tule, kuid restardi teeb ikka:

Spoiler

On Sat 4.02.2012 7:25:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020412-21980-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF880009E8180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time.


On Sat 4.02.2012 7:25:53 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x21, 0x0, 0xFFFFF880009E8180, 0x1)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
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 Fri 3.02.2012 15:58:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020312-41777-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
Bugcheck code: 0x50 (0xFFFFF880565E97F0, 0x0, 0xFFFFF800030E0907, 0x5)
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.

[RCC]

format ei aita kunagi, kettale tehakse format vaid üks kord elus, rohkem neid ei tehta. kuna krässis hal ja tuum ise, siis on võimalik toide või ketas, tseki esmalt toite piisavaust ja et ketta smart oleks korras

[Dogbert]

Juhuslikku laadi, erinevate veakoodidega kerneli BSOD-id viitavad ülekuumenemisele, -kellamisele või mälu vigadele. Emaplaadi ja prose vead pole samuti välistatud ja kui toide on kehvasti silutud (toiteploki või emaplaadi kondekate mahtuvus vähenenud, kondekad lekkinud) või ebapiisav, võivad samad sümptomid esineda. Ketas muidugi ka. SMART andmed kõigepealt üle vaadata.

[Leinö]

Tempid on korras, kellanud ei ole.

Spoiler

[RCC]

aga kettale tee küll üks priske kontroll

[Leinö]

Mida selle priske kontrolli all mõtled ?

[RCC]

error scan tab vali hdtunes ja vaata mis ütleb.

[Leinö]

Eile mõlemale kettale tehtud ja damaged blocks´e ei ole.

[Dogbert]

Kumbki ketas pole "tippvormis". Mõlemal on juba füüsilised vead sees, mis automaatselt ümber mapitud (sellepärast error scan neid ei näita). 750GB kettal on reallocated sector count nii suureks kasvanud, et normaliseeritud väärtus on 100 pealt 83-le langenud (lubatud miinimum on 10). Samuti on kalibreerimine 4 korral ebaõnnestunud - normaliseeritud väärtusele see veel mõjunud pole ja kui neid vigu juurde ei tule, ei ole selle parameetri pärast eriti muretseda vaja. Kui vigu juurde tuleb, võib seda lisaks ketta enda probleemidele põhjustada ka ebapiisav toide.

Väiksemal kettal on ka mõned sektorid vigased, aga mitte nii palju, et see normaliseeritud väärtust langetanud oleks.

Kuna vigastel aladel on sandiks kombeks levida, siis peaks hakkama mõtlema andmetest varukoopia tegemise ja vähemalt suurema ketta puhul uue ketta muretsemise peale.

BSOD-id võivad ka olla põhjustatud veel isoleerimata vigastest sektoritest, kuluks chkdsk x: /r /v kontroll teha mõlema ketta kõigile partitsioonidele, eelkõige süsteemipartitsioonile (x asenda kettatähisega).

Kuna juba vähemalt paar esinevat probleemi võivad viidata kehvale toitele, siis ma alustaks sealt. Prooviks teise toiteplokiga.

_________________

Parandus - kui oled kettakontrolli koos bad sector scan-iga teinud juba, siis eelviimane lõik eelnevas tekstis on üleliigne, lihtsama kontrolli puhul aga asjakohane.

[RCC]

algse konfi järgi otsustades ei ole see sifteki plokk 6 tuumasele siiski piisav, kaks raili ja 25A, proovi teise võimsama plokiga

[Dogbert]

[Leinö]

Hmm, pole just võtta kusagilt teist toitekat. Räägitakse, et battlefieldi mängides soovitatakse underclocki teha videokaartidele. Proovin enne selle variandi ära. Kui viga ikka veel olemas, siis otsin uue toiteka.

[Märt.]

Leinö, Reallocated Sector Count viitab üheselt ketta koolemisele, sul on seal badid sees, nobe backup abiks, siis testi kui tahad ja abiks oleks juba ka kohe uue vindi soetamine.
Ja priske kontroll oleks siis kettatootja utiliidiga ülekäimine.

[Leinö]

[Sven]

[Leinö]

Noh, vahetasin laupäeval termopasta, kontrollisin jahutuse üle, proovin veel BIOS update täna. Googeldades leidsin, et paljudel tuleb see CLOCK_WATCHDOG_TIMEOUT protsessori vea tõttu. Siiani umbes 2-3h mänguajal pole kokku jooksnud.

[A.S.]

[Sven]