Eli kone kaatuilee käynnistäessä sekä välillä nettiselailussa sekä muussa normaalissa käytössä mutta ei pelatessa.. msi emo athlon 64 x2 6000+ 3,1gz 6gb ram (3,31 usable) ?!?!? geforce GTX 560 ti 122511-12953-01.dmp 25.12.2011 17:29:51 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0x6c8c8cc8 0x0000008c 0x00000001 0x82e8d513 usbohci.sys usbohci.sys+494c OHCI USB Miniport Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+467eb C:\Windows\Minidump\122511-12953-01.dmp 2 15 7600 131 120 122611-25187-01.dmp 26.12.2011 18:59:51 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0x93f44fda 0x00000006 0x00000008 0x93f44fda ntkrnlpa.exe ntkrnlpa.exe+467eb NT Kernel & System Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+467eb C:\Windows\Minidump\122611-25187-01.dmp 2 15 7600 155 072 Mulla on jaettu toi kovo kahteen osioon (c ja d) kun kokeilin tehdä tota "error checking" juttua d osiolle kone kaatui ja tuli bluescreen.. 122811-25843-01.dmp 28.12.2011 20:36:34 UNEXPECTED_KERNEL_MODE_TRAP 0x0000007f 0x0000000d 0x00000000 0x00000000 0x00000000 usbohci.sys usbohci.sys+494c OHCI USB Miniport Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+46f2b C:\Windows\Minidump\122811-25843-01.dmp 2 15 7600 135 248 Osaako kukaan auttaa mua?
Ainakin tämä: "6gb ram (3,31 usable) ?!?!? " Johtuu siitä, että sinulla on 32-bittinen käyttis... 32-bittinen käyttis kun ei tue kuin 3 GT keskusmuistia, eli sinun tapauksessa 3 GT muistia jää yli/käyttämättä.... 64-bittinen käyttis tukee taas yli 10 GT....
Juu jotain tommosta lueskelinki jostain jo,mutta kiitos kuitenkin. onkin pitänyt hankkia toi 64bittinen.. BSOD tulee muuten aina kun koitan tehdä (error checking) D asemalle.
Usb ajuri näyttäisi olevan logissa ongelman aiheuttaja (usbohci.sys). Koitas päivittää piirisarjan ajurit. Kenties jopa BIOS ja aja komentokehotteesta "sfc /scannow" joka tarkistaa windows tiedostojen eheyden.
Latasin ton drivermaxin jonka mukaan 15 ajuria olis vanhentunut. niiden seassa gtx 560ti jonka kyllä päivitin pariviikkoo sitten... Pari jotain usb ajuria päivitin.. ei nyt toistaseksi ole kone kaatuillut. Kun kirjotin tuon sfc /scannow niin pieni musta ruutu vain välähtää näytöllä... normaalia?
Nooh ei löytä slimdriver ohjelmalla mitään usb liittyvää muutakun ton logitechin g25 mutta tuskin se voi vaikuttaa.. Kone jopa boottasi nyt normaalisti! kokeilen vielä tuota D aseman "error checking" juttua..
Ja kaatui taas. -.- 122911-16140-01.dmp 29.12.2011 18:26:07 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0xc07e1e9a 0x000000ff 0x00000000 0x82e99e39 amdk8.sys amdk8.sys+1bb6 Processor Device Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+467eb ntkrnlpa.exe+43e39 C:\Windows\Minidump\122911-16140-01.dmp 2 15 7600 156 976
Latasin logitechin setpoint ohjelman jolla saisin päivitettyä näppäimmistön sekä hiiren ajurit.. kone kaatui päivityksen yhteydessä! 122911-26312-01.dmp 29.12.2011 19:22:46 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000d1 0xd5fecfda 0x00000004 0x00000008 0xd5fecfda dxgmms1.sys dxgmms1.sys+d460 DirectX Graphics MMS Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+467eb C:\Windows\Minidump\122911-26312-01.dmp 2 15 7600 154 856 Kone kaatui myös käynnistäessä.. 122911-27890-01.dmp 29.12.2011 19:27:45 IRQL_NOT_LESS_OR_EQUAL 0x0000000a 0xa7f507b0 0x00000006 0x00000000 0x830504fa usbohci.sys usbohci.sys+494c OHCI USB Miniport Driver Microsoft® Windows® Operating System Microsoft Corporation 6.1.7600.16385 (win7_rtm.090713-1255) 32-bit ntkrnlpa.exe+467eb C:\Windows\Minidump\122911-27890-01.dmp 2 15 7600 131 120
Lisää random kaatumisia siis. Kenties muistikammassa vikaa. Tuosta yöksi testiä pyörimään. Toinen vaihtoehto että otat muut kammat pois ja jätät yhden. Jos toimii niin kammassa kenties vikaa. Koita vielä sillä toisellakin kammalla mitä tapahtuu.
Jonkun muistitestin teetinkIn heti kun ensimmäinen blue screen tuli noin viikko sitte.. Mutta nyt memtest rullaamassa. ihmettelin että miksi ton pitää koko yön olla päällä? ... Ostaessani uuden näyttiksen ostin myös pari gigaa lisää muistia joka on eri merkkistä kuin aiemmat kammat.. Voisiko bsod johtua tästä?
Virheet saattaa tulla niin harvoin että ei valttämättä parin tunnin testaus riitä. Vai uusi erimerkkinen kampa, saattaapa hyvin johtuakin. Koitas pelkästään vanhoilla. Ja onko niitä nyt sitten kolme kampaa. Suositeltavaa mielestäni on kaksi tai neljä. Kolmella jossain saattaa olla yhteensopivuus ongelmia.
Memtest oli 11tuntia ja n.30min päälllä. pass:4 error:0 Kolme 2gt kampaa on. kaksi a-data ja olisko tuo uus ollu kingston. Juu täytyy koittaa ilman tuota uutta kampaa.
Muistikin että olen koittanut jo ilman tuota uutta kampaa eikä ollu mitään muutosta.. eikös tuon memtestin pitäis huomata tuollainen virhe? Muutenkin koneesee tuli uudet palikat yli kuukausi sitten mutta viat alkoivat vasta n.viikko sitten.
No ei ainakaan näyttäisi olevan mitään vikaa. Tuota kaatumislogia tarttis syvällisemmin tutkia. Tällä nyt näkee jotain ja . Ja minkähän mallinen emolevy on?
Emo on Msi ms-7501. Crash Dump Analysis -------------------------------------------------------------------------------- Crash dump directory: C:\Windows\Minidump Crash dumps are enabled on your computer. On Fri 30.12.2011 16:16:44 GMT your computer crashed crash dump file: C:\Windows\Minidump\123011-16390-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB) Bugcheck code: 0xA (0x0, 0xFD, 0x1, 0xFFFFFFFF83051513) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Fri 30.12.2011 16:16:44 GMT your computer crashed crash dump file: C:\Windows\memory.dmp This was probably caused by the following module: ntkrpamp.exe (nt!Kei386EoiHelper+0x29B3) Bugcheck code: 0xA (0x0, 0xFD, 0x1, 0xFFFFFFFF83051513) Error: IRQL_NOT_LESS_OR_EQUAL Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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: ntkrpamp.exe . Google query: ntkrpamp.exe IRQL_NOT_LESS_OR_EQUAL On Fri 30.12.2011 16:14:36 GMT your computer crashed crash dump file: C:\Windows\Minidump\123011-16359-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB) Bugcheck code: 0xA (0x10AA40, 0x2C, 0x1, 0xFFFFFFFF83051513) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Fri 30.12.2011 16:06:57 GMT your computer crashed crash dump file: C:\Windows\Minidump\123011-17250-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB) Bugcheck code: 0xA (0xFFFFFFFFA7FD87B0, 0x6, 0x0, 0xFFFFFFFF8305A4FA) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Thu 29.12.2011 17:26:44 GMT your computer crashed crash dump file: C:\Windows\Minidump\122911-27890-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB) Bugcheck code: 0xA (0xFFFFFFFFA7F507B0, 0x6, 0x0, 0xFFFFFFFF830504FA) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Thu 29.12.2011 17:21:46 GMT your computer crashed crash dump file: C:\Windows\Minidump\122911-26312-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB) Bugcheck code: 0xD1 (0xFFFFFFFFD5FECFDA, 0x4, 0x8, 0xFFFFFFFFD5FECFDA) Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System 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. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 29.12.2011 17:19:50 GMT your computer crashed crash dump file: C:\Windows\Minidump\122911-24812-01.dmp This was probably caused by the following module: amdk8.sys (amdk8+0x1BB6) Bugcheck code: 0xA (0x0, 0xFF, 0x0, 0xFFFFFFFF8301CC01) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\amdk8.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Processor Device Driver Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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 which cannot be identified at this time. On Thu 29.12.2011 17:09:11 GMT your computer crashed crash dump file: C:\Windows\Minidump\122911-18500-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB) Bugcheck code: 0xA (0x0, 0x4, 0x1, 0xFFFFFFFF83084513) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Thu 29.12.2011 17:05:37 GMT your computer crashed crash dump file: C:\Windows\Minidump\122911-18218-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x46F2B) Bugcheck code: 0x7F (0xD, 0x0, 0x0, 0x0) Error: UNEXPECTED_KERNEL_MODE_TRAP file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This bug check indicates that the Intel CPU generated a trap and the kernel failed to catch this trap. The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time. On Thu 29.12.2011 16:25:21 GMT your computer crashed crash dump file: C:\Windows\Minidump\122911-16140-01.dmp This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x24642) Bugcheck code: 0xA (0xFFFFFFFFC07E1E9A, 0xFF, 0x0, 0xFFFFFFFF82E99E39) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\drivers\nvlddmkm.sys product: NVIDIA Windows Kernel Mode Driver, Version 285.62 company: NVIDIA Corporation description: NVIDIA Windows Kernel Mode Driver, Version 285.62 Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 285.62 , NVIDIA Corporation). Google query: nvlddmkm.sys NVIDIA Corporation IRQL_NOT_LESS_OR_EQUAL On Thu 29.12.2011 14:24:08 GMT your computer crashed crash dump file: C:\Windows\Minidump\122911-24656-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB) Bugcheck code: 0xA (0x649A3, 0x49, 0x1, 0xFFFFFFFF82E8A513) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Mon 26.12.2011 14:43:11 GMT your computer crashed crash dump file: C:\Windows\Minidump\122611-16265-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB) Bugcheck code: 0xA (0xFFFFFFFFE7AF77B0, 0x6, 0x0, 0xFFFFFFFF82E504FA) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Sun 25.12.2011 15:01:44 GMT your computer crashed crash dump file: C:\Windows\Minidump\122511-12953-01.dmp This was probably caused by the following module: ntkrnlpa.exe (nt+0x467EB) Bugcheck code: 0xA (0x6C8C8CC8, 0x8C, 0x1, 0xFFFFFFFF82E8D513) Error: IRQL_NOT_LESS_OR_EQUAL file path: C:\Windows\system32\ntkrnlpa.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. 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. On Mon 7.11.2011 15:59:11 GMT your computer crashed crash dump file: C:\Windows\Minidump\110711-29531-01.dmp This was probably caused by the following module: cdd.dll (cdd+0x1D09) Bugcheck code: 0x50 (0xFFFFFFFF82F35000, 0x0, 0xFFFFFFFF995119BE, 0x0) Error: PAGE_FAULT_IN_NONPAGED_AREA file path: C:\Windows\system32\cdd.dll product: Microsoft® Windows® Operating System company: Microsoft Corporation description: Canonical Display Driver 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 which cannot be identified at this time.
Onko normaalia että myös "safe modessa" tulee blue screen? meinaa kun kokeilin taas tuota error checking juttua D asemalle niin kone kaatui.. Mikä voisi aiheuttaa sen että kone kaatuu aina tuota error checkkiä tehdessä? Kovo rikki?
No ei tuo safe mode kaatuilu hyvä juttu ole. Kenties alkaa jokin komponentti koneesta olla tiensä päässä, onhan tuo jo aika vanhakin. Katos emolevyn kondensaattoreita onko pullistunut päältä . Ota kaikki ylimääräiset lisälaitteet irti koneesta jos auttaisi. Windowsin uudelleen asennuskin voisi kokeilla jos vielä kaatuilee jossain raudassa kenties vikaa.
Näyttäis jotkut konkat pullistuneen. mutta vuotoja ei ainakaan ole.. Hmm.. ei kyllä yhtään yllätävää 4 vuotta vanhalta msi emolta. teen vielä varmuuden vuoksi clean intallin ja laitan tällä kertaa sen 64bit.
