Blue Screen problem

marcozu · 01.04.2012., 20:10

Evo ovako,svako malo mi se pojavi blue screen ,poslije dizanja sustava dobijem ovu poruku:
Prva:Files that help describe the problem:
C:\Windows\Minidump\040112-16520-01.dmp
C:\Users\Marco\AppData\Local\Temp\WER-29000-0.sysdata.xml
ili
Druga:Files that help describe the problem:
C:\Windows\Minidump\032512-15678-01.dmp
C:\Users\Marco\AppData\Local\Temp\WER-28080-0.sysdata.xml

Inace u pitanju je laptop Lenovo z575,AMD A6 Quad core 3400M,8gb ram,SATA 750gb,AMD Radeon™ HD 6650M 2GB dual graphics.

Imam jos uvijek garanciju,nadam se da netko ima nekakvu ideju.Veliki pozdrav.

Izvinjavam se, još da navedem OS Windows 7 Ultimate sp1 64bit...

Joke · 01.04.2012., 20:41

Iskljuci automatically restart da vidis sto kaze bsod kad ga dobijes, ili pregledaj dump file sa nekim od alata.
How to read the small memory dump files that Windows creates for debugging

marcozu · 01.04.2012., 22:35

Evo odrađena analiza s Whocrashed professional edition 3.01,evo rezultata:

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

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sun 1.4.2012. 13:57:29 GMT your computer crashed
crash dump file: C:\Windows\Minidump\040112-16520-01.dmp
uptime: 01:53:39
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD5180, 0x3)
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 Sun 1.4.2012. 13:57:29 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
uptime: 01:53:39
This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD5180, 0x3)
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 Tue 27.3.2012. 22:01:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032812-15350-01.dmp
uptime: 03:48:11
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009E7180, 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 Mon 26.3.2012. 17:52:23 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032612-16068-01.dmp
uptime: 02:43:36
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD5180, 0x3)
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 Sun 25.3.2012. 13:19:26 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032512-15678-01.dmp
uptime: 03:00:04
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009E7180, 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 Fri 9.3.2012. 23:38:38 GMT your computer crashed
crash dump file: C:\Windows\Minidump\031012-16582-01.dmp
uptime: 00:00:17
This was probably caused by the following module: ntoskrnl.exe (nt+0x80640)
Bugcheck code: 0x50 (0xFFFFF8A002537000, 0x0, 0xFFFFF880041706C4, 0x0)
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

Po ovome je problem u pregrijavanju,da li netko zna možda dobar software za provjeru procesora?Ili neki prijedlog u vezi ovoga.Veliki pozdrav.

nino · 01.04.2012., 22:37

http://forum.pcekspert.com/showthread.php?t=58941

Joke · 02.04.2012., 00:33

Potpisujem link od kolege Nino, ali pogledaj tu ovaj http://www.sevenforums.com/crash-lockup-debug-how/63501-stop-0x101 -clock_watchdog_timeout-troubleshtg.html"]link da znas sto ti je radit.

01.04.2012., 20:10	#1
marcozu Registered User Datum registracije: Mar 2012 Lokacija: Županja Postovi: 7	Evo ovako,svako malo mi se pojavi blue screen ,poslije dizanja sustava dobijem ovu poruku: Prva:Files that help describe the problem: C:\Windows\Minidump\040112-16520-01.dmp C:\Users\Marco\AppData\Local\Temp\WER-29000-0.sysdata.xml ili Druga:Files that help describe the problem: C:\Windows\Minidump\032512-15678-01.dmp C:\Users\Marco\AppData\Local\Temp\WER-28080-0.sysdata.xml Inace u pitanju je laptop Lenovo z575,AMD A6 Quad core 3400M,8gb ram,SATA 750gb,AMD Radeon™ HD 6650M 2GB dual graphics. Imam jos uvijek garanciju,nadam se da netko ima nekakvu ideju.Veliki pozdrav. Izvinjavam se, još da navedem OS Windows 7 Ultimate sp1 64bit... Zadnje izmijenjeno od: nino. 01.04.2012. u 20:43.

01.04.2012., 20:41	#2
Joke N00B Moj komp Datum registracije: Oct 2006 Lokacija: Split Postovi: 3,886	Iskljuci automatically restart da vidis sto kaze bsod kad ga dobijes, ili pregledaj dump file sa nekim od alata. How to read the small memory dump files that Windows creates for debugging __________________ IE6 Linux is Not Windows

01.04.2012., 22:37	#4
nino PizzoZder Moj komp Datum registracije: Jan 2003 Lokacija: Umag Postovi: 12,451	http://forum.pcekspert.com/showthread.php?t=58941 __________________ Prodajem kucu na klizistu.. Nije puno presla..... Member Of PC Ekspert 100+kg Demolition Squad NAJNOVIJE = Povoljno RAM..http://www.downloadmoreram.com/... tor i AMD kupili.... NOVO! Prodajem visokokvalitetni tropleteni hardverski konac za fixiranje coolera

02.04.2012., 00:33	#5
Joke N00B Moj komp Datum registracije: Oct 2006 Lokacija: Split Postovi: 3,886	Potpisujem link od kolege Nino, ali pogledaj tu ovaj http://www.sevenforums.com/crash-lockup-debug-how/63501-stop-0x101 -clock_watchdog_timeout-troubleshtg.html"]link da znas sto ti je radit. __________________ IE6 Linux is Not Windows Zadnje izmijenjeno od: Joke. 02.04.2012. u 02:03.

01.04.2012., 22:35	#3
marcozu Registered User Datum registracije: Mar 2012 Lokacija: Županja Postovi: 7	Evo odrađena analiza s Whocrashed professional edition 3.01,evo rezultata: Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Sun 1.4.2012. 13:57:29 GMT your computer crashed crash dump file: C:\Windows\Minidump\040112-16520-01.dmp uptime: 01:53:39 This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD5180, 0x3) 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 Sun 1.4.2012. 13:57:29 GMT your computer crashed crash dump file: C:\Windows\memory.dmp uptime: 01:53:39 This was probably caused by the following module: hal.dll (hal!HalReturnToFirmware+0xB2D) Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD5180, 0x3) 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 Tue 27.3.2012. 22:01:35 GMT your computer crashed crash dump file: C:\Windows\Minidump\032812-15350-01.dmp uptime: 03:48:11 This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009E7180, 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 Mon 26.3.2012. 17:52:23 GMT your computer crashed crash dump file: C:\Windows\Minidump\032612-16068-01.dmp uptime: 02:43:36 This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF88002FD5180, 0x3) 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 Sun 25.3.2012. 13:19:26 GMT your computer crashed crash dump file: C:\Windows\Minidump\032512-15678-01.dmp uptime: 03:00:04 This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x101 (0x31, 0x0, 0xFFFFF880009E7180, 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 Fri 9.3.2012. 23:38:38 GMT your computer crashed crash dump file: C:\Windows\Minidump\031012-16582-01.dmp uptime: 00:00:17 This was probably caused by the following module: ntoskrnl.exe (nt+0x80640) Bugcheck code: 0x50 (0xFFFFF8A002537000, 0x0, 0xFFFFF880041706C4, 0x0) 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 Po ovome je problem u pregrijavanju,da li netko zna možda dobar software za provjeru procesora?Ili neki prijedlog u vezi ovoga.Veliki pozdrav.

Oglasni prostor
PC Ekspert Forum Oglas

Oglasni prostor
PC Ekspert Forum Oglas