x-kom hosting

Niebieski ekran

Xesasi
utworzono
utworzono

Witam.

Jakiś czas temu formatowałem se kompa. Zainstalowałem wszystkie sterowniki itp... Mimo wszystko i tak komputer powolnie działa ale da się żyć. Od czasu do czasu pojawia mi się niebieski ekran i po nie całej sekundzie mój komputer się resetuje. Wie ktoś jak to naprawić?

Xesasi
komentarz
komentarz

a ktore mam pobrać? (jest z 7 do wyboru)

Xesasi
komentarz
komentarz

Tego jest aż 11...

 

1.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {89374da8, 88e9fb50, bace3cbc, 1}

Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
Probably caused by : nv4_mini.sys ( nv4_mini+6e7c6 )

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

2.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {bb051004, 6, 0, 805451c4}

Probably caused by : atapi.sys ( atapi!AtapiStartIo+7e )

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

3.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {11601, 2, 0, ba7103a9}

Probably caused by : atapi.sys ( atapi!IdeLogResetError+31 )

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

4.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {bac665f0, 6, 1, 806eaa8a}

Probably caused by : atapi.sys ( atapi!AtapiInterrupt+3df )

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

 

5.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 6, 1, ba7124f7}

Probably caused by : atapi.sys ( atapi!IdePortNotification+e3 )

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

 

6.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {b356a000, 6, 1, 806eaa8a}

Probably caused by : atapi.sys ( atapi!AtapiInterrupt+3df )

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

 

7.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 6, 1, ba7124f7}

Probably caused by : atapi.sys ( atapi!IdePortNotification+e3 )

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

 

8.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 6, 1, ba7124f7}

Probably caused by : atapi.sys ( atapi!IdePortNotification+e3 )

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

 

9.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {8, 2, 0, 804fc346}

Unable to load image aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : atapi.sys ( atapi!IdePortInsertByKeyDeviceQueue+42 )

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

 

10.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {bad474b8, 6, 1, 806eaa8a}

Probably caused by : atapi.sys ( atapi!AtapiInterrupt+3df )

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

11.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {e56c6a0e, 6, 0, ba713745}

Probably caused by : atapi.sys ( atapi!IdeLogBmStatus+13 )

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

 

 

 

Xesasi
komentarz
komentarz

Tego jest aż 11...

 

1.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000EA, {89374da8, 88e9fb50, bace3cbc, 1}

Unable to load image nv4_mini.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nv4_mini.sys
*** ERROR: Module load completed but symbols could not be loaded for nv4_mini.sys
Probably caused by : nv4_mini.sys ( nv4_mini+6e7c6 )

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

2.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {bb051004, 6, 0, 805451c4}

Probably caused by : atapi.sys ( atapi!AtapiStartIo+7e )

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

3.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {11601, 2, 0, ba7103a9}

Probably caused by : atapi.sys ( atapi!IdeLogResetError+31 )

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

4.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {bac665f0, 6, 1, 806eaa8a}

Probably caused by : atapi.sys ( atapi!AtapiInterrupt+3df )

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

 

5.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 6, 1, ba7124f7}

Probably caused by : atapi.sys ( atapi!IdePortNotification+e3 )

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

 

6.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {b356a000, 6, 1, 806eaa8a}

Probably caused by : atapi.sys ( atapi!AtapiInterrupt+3df )

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

 

7.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 6, 1, ba7124f7}

Probably caused by : atapi.sys ( atapi!IdePortNotification+e3 )

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

 

8.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 6, 1, ba7124f7}

Probably caused by : atapi.sys ( atapi!IdePortNotification+e3 )

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

 

9.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {8, 2, 0, 804fc346}

Unable to load image aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : atapi.sys ( atapi!IdePortInsertByKeyDeviceQueue+42 )

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

 

10.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {bad474b8, 6, 1, 806eaa8a}

Probably caused by : atapi.sys ( atapi!AtapiInterrupt+3df )

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

11.

 

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {e56c6a0e, 6, 0, ba713745}

Probably caused by : atapi.sys ( atapi!IdeLogBmStatus+13 )

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

 

 

 



Ups wysłało się podwujnie....

 

Tu są zdjęcia z CUP-Z

 

[attachment=22953:3.bmp][attachment=22954:1.bmp][attachment=22955:2.bmp]

 

Youki
komentarz
komentarz

Podaj jeszce marke i moc zasilacza :)

Xesasi
komentarz
komentarz

GPS-400AA-101A

Moc całkowita: 400 W

pepe0619
komentarz
komentarz (edytowane)

zainstaluj najnowsze stery karty graficznej. (ze strony producenta)

sprawdz rowniez dysk programem HDTune

Xesasi
komentarz
komentarz

Zainstalowałem sterowniki.

 

HD Tune: Chciałem wstawić załączniki ale "wyczerpałem limit". Więc opisze:

- Benchmark Min: 0,8MB/sek Max: 1.4MB/sek Average 1.3MB/sek

- Health status: ok

-Error skan: nic nie jest uszkodzone (wziołem szybki skan.... normalny trwał 1,5 linkijki 70 min)

 

Youki
komentarz
komentarz

Niezbyt obeznany jestem w diagnostyce bsod jednak wydaje mi się, ze jest to problem sterowników albo pamięci ram, usuń dokładnie sterowniki od karty graficznej i zainstaluj od nowa, poza tym instalowałeś coś ostatnio? Propo pamięci ram to możesz ściągać memtesta86+ nagrać na bootowalna płytę i sprawdzić kazda kostkę osobno.

Xesasi
komentarz
komentarz

Jestm kompletnym żółtodziobem, więc:

- niewiem jak usunąć sam sterowniki karty graficznej

- i nie wiem jak nagrać na bootowalna płytę i sprawdzić kazda kostkę osobno

Oprucz najnowszych sterowników  karty graficznej jak proponował pepe0619 to nie... 

Jak  mówiłem napoczatku że formatowałem kompa to wtedy coś zwaliłem

Xesasi
komentarz
komentarz

czyi co mam dokładnie usunąć?



AMB -Display

ASUS - Sound

Creative -Sound

Fresco Logic - USB

HP -Printer

Intel - Chipset

JMicron - Storage

Marvell - Storage

Microsoft - Keyboard

Microsoft -Mouse

NEC - USB

NVIDIA - Chipset

NVIDIA - Display

NVIDIA - Physx

Realtek - Sound

 

Troche tego jest... Jeśli widzicie coś zbędnego to powidźcie, a ja to usune

 

Wciąż szukasz rozwiązania problemu? Napisz teraz na forum!

Możesz zadać pytanie bez konieczności rejestracji - wystarczy, że wypełnisz formularz.

×
×
  • Dodaj nową pozycję...

Powiadomienie o plikach cookie

Strona wykorzystuje pliki cookies w celu prawidłowego świadczenia usług i wygody użytkowników. Warunki przechowywania i dostępu do plików cookies możesz zmienić w ustawieniach przeglądarki.