patro44 utworzono 28 lutego 2015 utworzono 28 lutego 2015 (edytowane) Jakiś miesiąc temu zainstalowałem "siódemke" i jeszcze do niedawna wszystko było ok, dopóki nie zainstalowałem oprogramowanie, które miało przyspieszyć prace dysku (Intel Rapid Storage). Od 2 dni zaczeły pojawiać się dosyć często bluescreeny, np. podczas przeglądania stron internetowych lub włączania gier i programów. Paradoksalnie po tym jak udało mi się odinstalować to oprogramowanie, dysk znacznie przyspieszył, jednak bluescreeny wciąż się pojawiają. Zainstalowałem program "Whocrashed", żeby dowiedzieć się czegoś o tych błędach, ale niestety nie wiele mi to mówi. Taki dostałem raport: computer name: PATRYK-KOMPUTER windows version: Windows 7 , 6.1, build: 7600 windows dir: C:\Windows Hardware: H81M-HD3, Gigabyte Technology Co., Ltd. CPU: GenuineIntel Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz Intel586, level: 6 4 logical processors, active mask: 15 RAM: 4150157312 total Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer.On Sat 2015-02-28 03:20:38 GMT your computer crashed crash dump file: C:\Windows\Minidump\022815-21387-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0xF4 (0x3, 0xFFFFFA80055B8160, 0xFFFFFA80055B8440, 0xFFFFF80002D8D240) Error: CRITICAL_OBJECT_TERMINATION 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 process or thread crucial to system operation has unexpectedly exited or been terminated. 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 Sat 2015-02-28 03:20:38 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: 0xF4 (0x3, 0xFFFFFA80055B8160, 0xFFFFFA80055B8440, 0xFFFFF80002D8D240) Error: CRITICAL_OBJECT_TERMINATION Bug check description: This indicates that a process or thread crucial to system operation has unexpectedly exited or been terminated. 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 Sat 2015-02-28 03:19:05 GMT your computer crashed crash dump file: C:\Windows\Minidump\022815-17440-01.dmp This was probably caused by the following module: ataport.sys (0xFFFFF88000EC0000) Bugcheck code: 0x50 (0xFFFFF87FC31CBCEA, 0x0, 0xFFFFF88000EC0000, 0x5) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\ataport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: ATAPI Driver Extension 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.On Fri 2015-02-27 23:28:40 GMT your computer crashed crash dump file: C:\Windows\Minidump\022815-172973-01.dmp This was probably caused by the following module: ataport.sys (0xFFFFF880010FC000) Bugcheck code: 0x50 (0xFFFFF87FC10F259A, 0x0, 0xFFFFF880010FC000, 0x5) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\drivers\ataport.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: ATAPI Driver Extension 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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.On Fri 2015-02-27 22:55:40 GMT your computer crashed crash dump file: C:\Windows\Minidump\022715-13213-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x71F00) Bugcheck code: 0x74 (0x2, 0xFFFFF88003D52AE0, 0x1, 0xFFFFFFFFC000015C) Error: BAD_SYSTEM_CONFIG_INFO file path: C:\Windows\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that there is an error in the registry. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.On Fri 2015-02-27 21:45:54 GMT your computer crashed crash dump file: C:\Windows\Minidump\022715-19936-01.dmp This was probably caused by the following module: videoprt.sys (VIDEOPRT+0x18066) Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8800439A066, 0x1, 0x1) Error: KMODE_EXCEPTION_NOT_HANDLED file path: C:\Windows\system32\drivers\videoprt.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Video Port Driver 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 that cannot be identified at this time.
szynszyl1337 komentarz 28 lutego 2015 komentarz 28 lutego 2015 Ja bym zaproponował postawienie nowego Windows, bo Intel rapid nieco namieszał w plikach systemowych oraz sterownikach. 1
patro44 komentarz 28 lutego 2015 Autor komentarz 28 lutego 2015 Ja bym zaproponował postawienie nowego Windows, bo Intel rapid nieco namieszał w plikach systemowych oraz sterownikach. Mhm, to chyba będzie najlepsze rozwiązanie. Te błędy, to wynik nieprawidłowego działania pewnych plików systemowych i sterowników, więc nie będę musiał formatować wszystkich partycji przed instalacją?
szynszyl1337 komentarz 28 lutego 2015 komentarz 28 lutego 2015 Wystarczy systemowa, oczywiście wypada usunąć pozostałości sterowników z innych partycji jak tak je instalowałeś
Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!
Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.