Forum » Operacijski sistemi » Win 7 blue screen in restart
Win 7 blue screen in restart
Brainstorm ::
Kolega me je prosil, da povprašam na forumu, če bi kdo vedel približno, kaj bi lahko bil vzrok tej napaki oziroma restartu novega i3 desktop pcja, vsake toliko časa brez razloga.
Pri napaki pa mu javi tole:
Podpis težave:
Ime težave: BlueScreen
Različica operacijskega sistema: 6.1.7600.2.0.0.256.1
Področne nastavitve: 1060
Dodatne informacije o težavi:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF880048D4817
BCP3: FFFFF88006DE9900
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Datoteke, v katerih je opisana težava:
C:\Windows\Minidump\020711-17343-01.dmp
C:\Users\Mako\AppData\Local\Temp\WER-25234-0.sysdata.xml
Hvala
Pri napaki pa mu javi tole:
Podpis težave:
Ime težave: BlueScreen
Različica operacijskega sistema: 6.1.7600.2.0.0.256.1
Področne nastavitve: 1060
Dodatne informacije o težavi:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF880048D4817
BCP3: FFFFF88006DE9900
BCP4: 0000000000000000
OS Version: 6_1_7600
Service Pack: 0_0
Product: 256_1
Datoteke, v katerih je opisana težava:
C:\Windows\Minidump\020711-17343-01.dmp
C:\Users\Mako\AppData\Local\Temp\WER-25234-0.sysdata.xml
Hvala
- spremenilo: Brainstorm ()
Brainstorm ::
Ati catalyst driverje ima tazadnje.
Bom pa še počakal, da se še enkrat pojavi blue screen, da zapišejo winsi mini dump, namreč tazadnjega mu je ccleaner pobrisal, ker mislim da iz tistega bi se dalo še kaj bolj natančno videt, kaj je vzrok.
Bom pa še počakal, da se še enkrat pojavi blue screen, da zapišejo winsi mini dump, namreč tazadnjega mu je ccleaner pobrisal, ker mislim da iz tistega bi se dalo še kaj bolj natančno videt, kaj je vzrok.
connel ::
Malce več povej, kakšne so komponente v PC-ju ? Sama error koda je tko no, pove nekaj, ne pa vsega. Meni ni nič pomagalo, narobe naj bi bilo od diska, grafične, različnih driverjev in pa ram. Na koncu je bila kriva prenizka stock voltaža ramov.
Brainstorm ::
Tole mašino ima
http://www.enaa.com/oddelki/racunalnist...
Proizvajalec: Acord-92 d.o.o.
Osnovna plošča:: Intel H55 vezni nabor
Procesor:: Intel i3 540 3,06 GHz
Pomnilnik:: 4 GB DDR3 1333MHz
Trdi disk:: 1024GB SATA2
Optična enota:: DVD/RW SATA črn
Grafična kartica:: ATI Radeon HD 5670 512MB DDR5
Zvočna kartica:: integrirana
Tipkovnica:: brez
Miška:: brez
Zvočniki:: brez
Mrežna kartica:: integrirana
Priključki:: Spredaj:
- 2x USB
- Audio
Zadaj:
- 1 x PS/2 tipkovnica
- 1 x VGA/D-Sub
- 1 x VGA/DVI-D
- 6 x USB 2.0
- 1 x RJ-45 LAN
- HD Audio Jack: zadnji zvočnik / central / bas / Line in / sprednji zvočnik / mikrofon
Dodatno:: Čitalec kartic
Tip procesorja:: 1
Količina pomnilnika:: 4
Operacijski sistem:: Brez
Ohišje: LCpower ATX s 600W napajalnikom
Who crashed pri analizi pokaže tole:
On Sat 12.2.2011 12:13:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021211-17953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0xFFFFF8A0031FE966, 0x2, 0x0, 0xFFFFF88000C042DF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft(R) Windows(R) 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.
http://www.enaa.com/oddelki/racunalnist...
Proizvajalec: Acord-92 d.o.o.
Osnovna plošča:: Intel H55 vezni nabor
Procesor:: Intel i3 540 3,06 GHz
Pomnilnik:: 4 GB DDR3 1333MHz
Trdi disk:: 1024GB SATA2
Optična enota:: DVD/RW SATA črn
Grafična kartica:: ATI Radeon HD 5670 512MB DDR5
Zvočna kartica:: integrirana
Tipkovnica:: brez
Miška:: brez
Zvočniki:: brez
Mrežna kartica:: integrirana
Priključki:: Spredaj:
- 2x USB
- Audio
Zadaj:
- 1 x PS/2 tipkovnica
- 1 x VGA/D-Sub
- 1 x VGA/DVI-D
- 6 x USB 2.0
- 1 x RJ-45 LAN
- HD Audio Jack: zadnji zvočnik / central / bas / Line in / sprednji zvočnik / mikrofon
Dodatno:: Čitalec kartic
Tip procesorja:: 1
Količina pomnilnika:: 4
Operacijski sistem:: Brez
Ohišje: LCpower ATX s 600W napajalnikom
Who crashed pri analizi pokaže tole:
On Sat 12.2.2011 12:13:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021211-17953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0xFFFFF8A0031FE966, 0x2, 0x0, 0xFFFFF88000C042DF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft(R) Windows(R) 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.
Zgodovina sprememb…
- spremenilo: Brainstorm ()
Brainstorm ::
Who crashed pri analizi minidumpa pokaže tole:
Kaj bi se dalo tukaj uredit, da ntoskrnl.exe (nt+0x70740) ne bi več povzročal težav ali se driverji od grafe tepejo s čim ali kaj bi lahko bilo krivo.
Hvala
On Sat 12.2.2011 12:13:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021211-17953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0xFFFFF8A0031FE966, 0x2, 0x0, 0xFFFFF88000C042DF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft(R) Windows(R) 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.
Kaj bi se dalo tukaj uredit, da ntoskrnl.exe (nt+0x70740) ne bi več povzročal težav ali se driverji od grafe tepejo s čim ali kaj bi lahko bilo krivo.
Hvala
On Sat 12.2.2011 12:13:36 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\021211-17953-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x70740)
Bugcheck code: 0xD1 (0xFFFFF8A0031FE966, 0x2, 0x0, 0xFFFFF88000C042DF)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft(R) Windows(R) 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.
Zgodovina sprememb…
- spremenilo: Brainstorm ()
gorenjc ::
Dmp datoteko bi bilo potrebno analizirati z windbg programom, da se ugotovi vzrok težav. Nikakor pa ni problematičen ntoskrnl.exe 
Težave povzroča eden od gonilnikov na sistemu.
Težave povzroča eden od gonilnikov na sistemu. Brainstorm ::
windbg javi tole:
!analyze -v pa javi tole :
Kaj se kaj da iz tega videt, če grem gledat kaj je fltmgr.sys, spet nič ne vem.
Probably caused by : fltmgr.sys ( fltmgr+42df )
Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\021211-17953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02c09000 PsLoadedModuleList = 0xfffff800`02e46e50
Debug session time: Sat Feb 12 13:13:36.414 2011 (UTC + 1:00)
System Uptime: 0 days 2:23:59.617
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff8a0031fe966, 2, 0, fffff88000c042df}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for fltmgr.sys
*** ERROR: Module load completed but symbols could not be loaded for fltmgr.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : fltmgr.sys ( fltmgr+42df )
Followup: MachineOwner
---------
!analyze -v pa javi tole :
******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If kernel debugger is available get stack backtrace. Arguments: Arg1: fffff8a0031fe966, memory referenced Arg2: 0000000000000002, IRQL Arg3: 0000000000000000, value 0 = read operation, 1 = write operation Arg4: fffff88000c042df, address which referenced memory Debugging Details: ------------------ ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: fltmgr FAULTING_MODULE: fffff80002c09000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bc11f READ_ADDRESS: unable to get nt!MmSpecialPoolStart unable to get nt!MmSpecialPoolEnd unable to get nt!MmPoolCodeStart unable to get nt!MmPoolCodeEnd fffff8a0031fe966 CURRENT_IRQL: 0 FAULTING_IP: fltmgr+42df fffff880`00c042df f6410602 test byte ptr [rcx+6],2 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT BUGCHECK_STR: 0xD1 LAST_CONTROL_TRANSFER: from fffff80002c78ca9 to fffff80002c79740 STACK_TEXT: fffff800`00ba2398 fffff800`02c78ca9 : 00000000`0000000a fffff8a0`031fe966 00000000`00000002 00000000`00000000 : nt+0x70740 fffff800`00ba23a0 00000000`0000000a : fffff8a0`031fe966 00000000`00000002 00000000`00000000 fffff880`00c042df : nt+0x6fca9 fffff800`00ba23a8 fffff8a0`031fe966 : 00000000`00000002 00000000`00000000 fffff880`00c042df 00000000`00000000 : 0xa fffff800`00ba23b0 00000000`00000002 : 00000000`00000000 fffff880`00c042df 00000000`00000000 00000000`00000000 : 0xfffff8a0`031fe966 fffff800`00ba23b8 00000000`00000000 : fffff880`00c042df 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: fltmgr+42df fffff880`00c042df f6410602 test byte ptr [rcx+6],2 SYMBOL_NAME: fltmgr+42df FOLLOWUP_NAME: MachineOwner IMAGE_NAME: fltmgr.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner ---------
Kaj se kaj da iz tega videt, če grem gledat kaj je fltmgr.sys, spet nič ne vem.
Probably caused by : fltmgr.sys ( fltmgr+42df )
Zgodovina sprememb…
- spremenilo: Brainstorm ()
gorenjc ::
fltmgr.sys =Microsoft Windows file system filter manager file. je Os 32 ali 64 bitni? Kakšen antivirusni program je nameščen? V winddbg bi bilo potrebno nastaviti še "simbole", da bi se dalo kaj več razvozlati iz dump datoteke.
Duhec ::
Aha, bsod ni samo 0x3B ampak vsaj še 0xD1.
Po mojem smo se prehitro zapičli v te bsod podatke in bi bilo najprej sploh dobro vedet, da preveriš, če je njegov sistem res čist, brez kake virus/spyware zajedalcev ali "čudne" DVD WIn7 kopije, ker drugače se lahko vrtimo v krogu.
Ampak recimo, da je to vse ok, da se tudi nič ne pregreva (sploh grafika).
Če so bsodi različni potem lahko heca kak spomin (če že ni stabilen pa kaka nekompatibilnost, timingi...). Seveda je lahko je marsikaj drugega, lahko zgolj to, da bios ni posodobljen.
Poglej še v System Log in Event Viewer, če tam vidiš kake napake se beležijo.
Naredi test spominov in diska (s programom proizvajalca diska) in preveri, če obstaja novejši bios za to osn.ploščo.
p.s.
Mimogrede, zadnji furmani za grafiko HD 5670 so od včeraj (15.2.2011)
Po mojem smo se prehitro zapičli v te bsod podatke in bi bilo najprej sploh dobro vedet, da preveriš, če je njegov sistem res čist, brez kake virus/spyware zajedalcev ali "čudne" DVD WIn7 kopije, ker drugače se lahko vrtimo v krogu.
Ampak recimo, da je to vse ok, da se tudi nič ne pregreva (sploh grafika).
Če so bsodi različni potem lahko heca kak spomin (če že ni stabilen pa kaka nekompatibilnost, timingi...). Seveda je lahko je marsikaj drugega, lahko zgolj to, da bios ni posodobljen.
Poglej še v System Log in Event Viewer, če tam vidiš kake napake se beležijo.
Naredi test spominov in diska (s programom proizvajalca diska) in preveri, če obstaja novejši bios za to osn.ploščo.
p.s.
Mimogrede, zadnji furmani za grafiko HD 5670 so od včeraj (15.2.2011)
Zgodovina sprememb…
- spremenil: Duhec ()
Vredno ogleda ...
| Tema | Ogledi | Zadnje sporočilo | |
|---|---|---|---|
| Tema | Ogledi | Zadnje sporočilo | |
| » | BSOD problemOddelek: Pomoč in nasveti | 1618 (1276) | Oktan |
| » | BSODOddelek: Operacijski sistemi | 2034 (1708) | Bolf3nk |
| » | Windows XP Black screenOddelek: Pomoč in nasveti | 2949 (2689) | Twix |
| » | [ Windows Vista ] Vprašanja in težave (strani: 1 2 3 4 … 76 77 78 79 )Oddelek: Operacijski sistemi | 264354 (63946) | Seljak |
| » | BSOD pri Remote Desktopu v Win 2003 Server R2 Enterprise SP2Oddelek: Pomoč in nasveti | 1719 (1546) | ender |