Blue screen - docela často

[maxixxx]

Bios sem neupdatoval - kupodivu tam je poslední 5001
Instalace ovladačů pro nForce570 z NVIDIE proběhla
Instalace nejnovějších ovladačů pro GK z ATI.AMD

Tak su zvědavej

Zatím díky

[Reklama]

[MiliNess]

Myslím, že o tobě ještě uslyšíme. Často u tebe dochází k chybě CLOCK_WATCHDOG_TIMEOUT,
tedy jedno jádro procesoru přestává zpracovávat pravidelná přerušení od systémových hodin (dojde k zavěšení jádra)
Bývá to způsobeno operační pamětí, základní deskou nebo např. přehříváním CPU.

[maxixxx]

Použil sem soft WhoCrashed

a tam toto (dvě opakující se chyby)

On Fri 7.2.2014 9:54:11 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020714-16598-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x61, 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 that cannot be identified at this time.



On Thu 6.2.2014 21:23:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\020714-31247-01.dmp
This was probably caused by the following module: nvstor.sys (0xFFFFF8800105A068)
Bugcheck code: 0xD1 (0xFFFFF88043370440, 0x8, 0x0, 0xFFFFF8800105A068)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\nvstor.sys
product: NVIDIA nForce(TM) SATA Driver
company: NVIDIA Corporation
description: NVIDIA® nForce(TM) Sata Performance Driver
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.
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: nvstor.sys (NVIDIA® nForce(TM) Sata Performance Driver, NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

Takže si myslím, že jsem v předchozí aktualizaci ovladáčů udělal maximum.

Uvidíme

[MiliNess]

Tohle máš nainstalováno?
Vypadá to, že současný ovladač úložiště od nVidia má nějaké problémy.

[maxixxx]

Od včerejší aktualizace to zatím jede.

Ten výpis z WhoCrashed je z BSOD před aktualizací.

Uvidím snad to nezakřiknu.

[MrekS]

Tohle máš nainstalováno?
Vypadá to, že současný ovladač úložiště od nVidia má nějaké problémy.

Psal že instalace ovladačů od NVIDIA proběhla...

[maxixxx]

Včera sem vše aktualizoval a od tý doby pořád v pohodě.

Ten výpis z WhoCrashed je z minidumpů před aktualizací - jen pro upřesnění v čem byl asi problém.

Tak uvidím jak dlouho to pojede.

[MrekS]

čipset od NVIDIA (NVIDIA nForce® 570 Ultra) dělal neplechu (součást MB), snad to bylo pouze starým ovladačem a už to bude ok.

[maxixxx]

Tak je tady zase.

Fakt už nevím co s tím. S XP to jelo v pohodě kolik let.

minidump v příloze

Výpis z WhoCrashed



System Information (local)
--------------------------------------------------------------------------------

computer name: POKAS
windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
Hardware: ASUSTeK Computer INC., M2N-E
CPU: AuthenticAMD AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ AMD586, level: 15
2 logical processors, active mask: 3
RAM: 4293386240 total
VM: 2147352576, free: 1913565184




--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 13.2.2014 17:57:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-16364-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x61, 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 that cannot be identified at this time.

--- Doplnění předchozího příspěvku (13 Úno 2014 19:26) ---

A zase

dump v příloze

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 13.2.2014 18:16:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-23400-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x61, 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 that cannot be identified at this time.

--- Doplnění předchozího příspěvku (13 Úno 2014 20:39) ---

A do třetice

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Thu 13.2.2014 18:45:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021314-18454-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x101 (0x61, 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 that cannot be identified at this time.


Conclusion
--------------------------------------------------------------------------------

12 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

nvstor.sys (NVIDIA® nForce(TM) Sata Performance Driver, NVIDIA Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination the errors that have been reported for these drivers and include the brand and model name of your computer as well in the query. This often yields interesting results from discussions from users who have been experiencing similar problems.

[MrekS]

To je to co ti psal mistr Miliness viz. " Často u tebe dochází k chybě CLOCK_WATCHDOG_TIMEOUT,
tedy jedno jádro procesoru přestává zpracovávat pravidelná přerušení od systémových hodin (dojde k zavěšení jádra)
Bývá to způsobeno operační pamětí, základní deskou nebo např. přehříváním CPU"

Projeď si paměti třeba MemTestem, a CPU se ti opravdu nepřehřívá? raději to ještě otestuj (HeavyLoad na zatížení systému a Hardware Monitor na sledování teplot.) spusť oba třeba po pěti minutách udělej sreen HW Monitoru a sem s ním.
Co je dobrá zpráva, že se ti zatím neobjevila chyba s GPU a čipsetem.