Raz na jakiś czas pojawiają mi się błędy krytyczne systemu. Nie mogę to chyba do końca nazwać, że pojawia mi się Blue Screen tylko zamiast tego pojawia się ekran czarrny , różowy lub czerwony. Chociaż po sprawdzeniu debbugerem pokazane, że wystąpiły Blue Screeny. Nie wiem z jakiego powodu one sie pojawiają. Posiadam zaktualizowane sterowniki do urządzeń i nie widać jakichkolwiek konfliktów. Dodam, że od początku zainstalowania systemu takie problemy występowały. Zmieniałem pamięć RAM czyściłem cały komputer z kurzu. Kondensatory NIE wyglądają na “spuchnięte”. Skanowałem antivurusem, antimalware i online wykrył tylko NIEGROŻNE wirusy co odrazu usunąłem. lecz i tak niewiele to pomogło. Sprawdzałem spójność ważnych plikó systemowych (Wykazało, że WSZYSTKIE pliki nienaruszone). Oto lista błędów jakie w między czasie występują.
Welcome to WhoCrashed Home Edition 1.01
This program checks for drivers which have been crashing your computer.
Whenever a computer suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, on Windows most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.
This program does post-mortem crash dump analysis with the single click of a button.
To obtain technical support visit www.resplendence.com/support
To check if a newer version of this program is available, click here.
Just click the Analyze button for a comprehensible report …
Home Edition notice
This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition. The professional edition of WhoCrashed also allows analysis of crashdumps on remote drives and computers on the network and offers more detailed analysis.
Analysis
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
Too many crashes have been detected. Only the latest 40 crashes will be displayed.
On Sat 2009-07-25 02:23:06 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x10000050 (0xD3FF1ED3, 0x1, 0xBF8B7BB9, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 2009-07-20 15:59:03 your computer crashed
This was likely caused by the following module: csrss.exe
Bugcheck code: 0xF4 (0x3, 0x846D2DA0, 0x846D2F14, 0x805C8C88)
Error: CRITICAL_OBJECT_TERMINATION
file path: C:\WINDOWS\system32\csrss.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Client Server Runtime Process
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 2009-07-20 12:08:52 your computer crashed
This was likely caused by the following module: ntfs.sys
Bugcheck code: 0x24 (0x1902FE, 0xB0F79650, 0xB0F7934C, 0xF724CE16)
Error: NTFS_FILE_SYSTEM
file path: C:\WINDOWS\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 2009-07-19 16:56:31 your computer crashed
This was likely caused by the following module: usbd.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xF79BE635, 0xF78E348C, 0xF78E3188)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\usbd.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Universal Serial Bus Driver
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sat 2009-07-18 14:03:57 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0xBB39, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Wed 2009-07-15 21:01:48 your computer crashed
This was likely caused by the following module: s3gigp.dll
Bugcheck code: 0x100000EA (0x8381C020, 0x8438FBA8, 0xF78C7CB4, 0x1)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
file path: C:\WINDOWS\system32\s3gigp.dll
product: S3 Graphics UMA-series Display Driver
company: S3 Graphics Co., Ltd.
description: S3 Graphics UMA-series Display Driver
On Tue 2009-07-14 11:28:51 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x1000008E (0xC0000005, 0xBF141DE6, 0xF207F584, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware
On Mon 2009-07-13 11:18:50 your computer crashed
This was likely caused by the following module: hardware
Bugcheck code: 0x10000050 (0x96487550, 0x1, 0xBF143DE3, 0x0)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on hardware
On Fri 2009-07-10 10:03:53 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x80511FEB, 0xB0E5DA64, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 2009-07-06 16:54:40 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF8410E4, 0xF4517B40, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 2009-07-05 17:30:17 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xF04D8BF0, 0x1, 0x80544683, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Fri 2009-07-03 18:39:50 your computer crashed
This was likely caused by the following module: s3ginv.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF18C0D4, 0xF02A66C4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\s3ginv.dll
product: S3 Graphics CIL Driver.
company: S3 Graphics Co., Ltd.
description: S3 Graphics CIL Driver.
On Mon 2009-06-29 18:26:42 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000008E (0xC0000005, 0x805B19D3, 0xB0C4DC7C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sat 2009-06-27 14:45:07 your computer crashed
This was likely caused by the following module: s3ginv.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF18C0D4, 0xF0E2E6C4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\s3ginv.dll
product: S3 Graphics CIL Driver.
company: S3 Graphics Co., Ltd.
description: S3 Graphics CIL Driver.
On Fri 2009-06-19 10:25:20 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x1000000A (0xC0042740, 0x2, 0x0, 0x8051CEFA)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 2009-06-14 08:38:34 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x10000050 (0xB11200A4, 0x0, 0xBF813D90, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Thu 2009-06-11 13:28:49 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000000A (0xBAD0B0B4, 0x2, 0x1, 0x80500D20)
Error: Unknown
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Wed 2009-06-10 13:03:21 your computer crashed
This was likely caused by the following module: eamon.sys
Bugcheck code: 0x10000050 (0xFFFFFFF0, 0x1, 0xB1738FE4, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\eamon.sys
product: ESET Smart Security
company: ESET
description: Amon monitor
On Fri 2009-05-29 10:51:34 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x19 (0x20, 0xE147AE38, 0xE147AE60, 0xC050429)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Tue 2009-05-26 08:19:11 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x0, 0x0, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 2009-05-24 15:11:27 your computer crashed
This was likely caused by the following module: aswmon2.sys
Bugcheck code: 0x100000C5 (0x30004, 0x2, 0x0, 0x80544632)
Error: Unknown
This file could not be located on your computer, we suggest that you search on it with Google.
Click here to do a Google search on aswmon2.sys
On Fri 2009-05-22 20:57:35 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF84A560, 0xEC529B84, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Fri 2009-05-15 10:48:19 your computer crashed
This was likely caused by the following module: s3gigp.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF80EAF2, 0xF76CB54C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\s3gigp.dll
product: S3 Graphics UMA-series Display Driver
company: S3 Graphics Co., Ltd.
description: S3 Graphics UMA-series Display Driver
On Thu 2009-05-07 12:49:42 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0x80543ADE, 0xEB63A778, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Wed 2009-05-06 16:21:34 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF804986, 0xEC1FEB7C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sat 2009-04-25 18:05:14 your computer crashed
This was likely caused by the following module: kmixer.sys
Bugcheck code: 0x1000007E (0xC0000005, 0x8003D1A, 0xEB5ACCBC, 0xEB5AC9B8)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\kmixer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Audio Mixer
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Mon 2009-04-13 09:37:57 your computer crashed
This was likely caused by the following module: kmixer.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xEB329269, 0xBA617CC8, 0xBA6179C4)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\kmixer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Audio Mixer
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 2009-04-12 20:22:44 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF8054DF, 0xBA2B9C8C, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Tue 2009-04-07 19:26:35 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF8485FE, 0xEF38FB74, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Tue 2009-04-07 13:02:29 your computer crashed
This was likely caused by the following module: s3ginv.dll
Bugcheck code: 0x1000008E (0xC0000005, 0xBF13D439, 0xEEFCA568, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\s3ginv.dll
product: S3 Graphics CIL Driver.
company: S3 Graphics Co., Ltd.
description: S3 Graphics CIL Driver.
On Sun 2009-04-05 15:00:25 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000008E (0xC0000005, 0xBF848587, 0xEFF19BA4, 0x0)
Error: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 2009-04-05 10:33:43 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0xC2 (0x7, 0xCD4, 0x2E0033, 0xE11E0378)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sat 2009-04-04 11:41:39 your computer crashed
This was likely caused by the following module: s3gigp.dll
Bugcheck code: 0x10000050 (0xE18DF37F, 0x0, 0xBF801922, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\s3gigp.dll
product: S3 Graphics UMA-series Display Driver
company: S3 Graphics Co., Ltd.
description: S3 Graphics UMA-series Display Driver
On Fri 2009-04-03 20:42:04 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x7A (0x3, 0xC0000005, 0x17400, 0x0)
Error: KERNEL_DATA_INPAGE_ERROR
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Tue 2009-03-31 21:31:43 your computer crashed
This was likely caused by the following module: viahduaa.sys
Bugcheck code: 0x100000D1 (0xF6FE9BE4, 0x2, 0x8, 0xF6FE9BE4)
Error: Unknown
file path: C:\WINDOWS\system32\drivers\viahduaa.sys
product: VIA High Definition Audio Driver
company: VIA Technologies, Inc.
description: VIA High Definition Audio Function Driver
On Sun 2009-03-29 10:49:03 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xD27B5814, 0x0, 0x8060356D, 0x0)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sat 2009-03-28 07:47:29 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x4E (0x99, 0x2D256, 0x1, 0x0)
Error: PFN_LIST_CORRUPT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Tue 2009-03-24 11:54:42 your computer crashed
This was likely caused by the following module: ntoskrnl.exe
Bugcheck code: 0x10000050 (0xE31AF44C, 0x0, 0x80634B8C, 0x1)
Error: Unknown
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Jądro i system NT
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Sun 2009-03-22 05:57:05 your computer crashed
This was likely caused by the following module: kmixer.sys
Bugcheck code: 0x1000007E (0xC0000005, 0xEFA541C9, 0xF093DCC8, 0xF093D9C4)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\kmixer.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Kernel Mode Audio Mixer
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
On Thu 2009-03-19 09:22:44 your computer crashed
This was likely caused by the following module: win32k.sys
Bugcheck code: 0x1000000A (0x63, 0x2, 0x0, 0x805316AC)
Error: Unknown
file path: C:\WINDOWS\system32\win32k.sys
product: System operacyjny Microsoft® Windows®
company: Microsoft Corporation
description: Współużytkowany sterownik Win32
The crash took place in a standard Microsoft module. Likely the culprit is another driver on your system which cannot be identified.
Conclusion
42 crash dumps have been found on your computer. Only 40 have been analyzed. Note that it’s not always possible to state with certainty whether a reported driver is really responsible for crashing your system or that the root cause is in another module. Nonetheless it’s suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.
